Skip to article
After the PromptJames Dimachkie
Menu
Gymnopédie No. 1 by Erik Satie.

Gymnopédie No. 1Erik Satie

Robin Alciatore · Musopen
All work

Catchwright

Product design · Archived project3 min read

A number found in a document is not yet a rule someone should use. This Catchwright study follows the steps between reading an agreement and checking a calculation against confirmed terms.

My role
Product direction, workflow decisions, and the new demonstration, with AI-assisted implementation.
Status
Archived project. This reconstruction uses one fictional agreement and creates no production records.
Catchwright’s document workspace, showing a proposed hourly wage with its exact source clause and confirmation controls.
Open full screenshot

Keep the source in reach

Catchwright was a project for checking contractor paperwork against source documents. The product is now retired; this example reconstructs one workflow from its preserved source.

The demonstration reads the digital text of a fictional two-page agreement. As you review each field, the PDF follows the relevant clause and shows the source beside the proposed value. You can confirm a field, mark it absent, or hold it for review. The interface keeps those choices distinct.

Confirm, then compare

Choose North or South, then review the rates and travel terms. One threshold is written as words in the agreement: read the clause and enter the value yourself. Review the confirmed terms together, then attest that you checked them against the agreement.

The sample-pay comparison uses only hourly rates you have confirmed. Enter matching pay, then change a paid amount to see the difference. Clearing an input stops that comparison until the value is complete. You can download the confirmed terms and comparison as JSON files.

The fictional straight-time comparison shows entered pay of 52 dollars, a confirmed source rate of 56 dollars, and a four-dollar hourly gap.
A sample comparison after confirmation. The entered pay, source rate, and difference remain visible together; this is not a compliance determination. Open full image

Why I stopped the product

I retired Catchwright in July 2026. I chose not to expand it into a full subcontractor management platform or compete for a narrow position between established vendors and a lower-cost entrant. I preserved the engineering privately and stopped pursuing the operating product.

This demonstration keeps one interaction available to examine: checking a proposed rule against its source before using it. The example stands on that workflow, without suggesting the business is still running.

The implementation behind the interaction

I directed the September 2026 interface and fictional agreement with AI assistance. The source follows the selected field, and only confirmed rates reach the comparison. Those choices keep the document available at the point of decision.

The document-reading, confirmation, export, and fixed hourly-rate rules come from thirteen archived source modules, preserved byte-for-byte in the recovery package. The responsive interface is a new demonstration around that implementation.

A deliberately bounded example

This study supports its supplied digital-text PDF. It has no OCR or arbitrary-document upload. Travel and subsistence terms can be captured and exported, but their eligibility and payroll-line checks are not implemented. The comparison is not a compliance determination.

The fixture is fictional, state stays in memory, and refreshing resets the work. No employer records are used and no production record is created. Catchwright remains an archived project; this demonstration is not an operating service.

Return to all work
Next project

Receiver Reliance

When should one AI agent rely on another’s work? A 1,805-episode study found fewer improper handoffs, at a cost to task completion. Wrong answers could still pass.