Early Access Open - Planned GA: June 2026

AI coding with receipts.

Bring us the work order. We'll bring the receipts.

Mainely Code turns feature requests into bounded, reviewable, proof-backed code changes. Verified diffs. Bounded files. Proof before merge.

Live lane work order → verified diff

Request early access See the proof flow

Built from Maine.
Governed by SENTINEL.
A TAHAI Web Services project.

Why Mainely Code

Fast code help is not enough. The review path has to be clear.

Mainely Code is built for teams that want AI assistance without losing control of scope, diffs, tests, approvals, or reviewer context.

Requests stay bounded

Every task starts with owned files, blocked files, and acceptance checks.

Diffs stay readable

Changes are shaped for human review instead of drifting across the repo.

Proof travels with the work

Run reports and notes make the handoff credible before merge.

Bounded coding flow

From work order to proof bundle.

Step 1

Work order

Define the request, owner, lane, allowed files, blocked files, and acceptance checks.

Step 2

Bounded build

SENTINEL plans and drafts changes inside the agreed file boundary.

Step 3

Diff review

The output is presented as a readable diff with risk notes and reviewer context.

Step 4

Proof bundle

Scope checks, static checks, build notes, and run reports are packaged for review.

Demo work order

The boundary is visible before the build begins.

Mainely Code work order Status: review-safe

MC-104

Polish account settings flow

Bounded

Owned files

settings.html
settings.css
settings.js

Blocked files

billing/*
auth/secrets/*
deploy.toml

Acceptance checks

No horizontal scroll at 390px

Keyboard focus remains visible

Static build path stays clean

verified.diff

@@ settings-flow @@
- submitForm(payload)
+ submitBoundedChange(payload, proof)
+ assertOwnedFiles(workOrder.files)
+ writeRunReport(result)
scope: settings.html, settings.css, settings.js

Proof before merge

Receipts reviewers can actually use.

Scope check

Owned files match the work order. Blocked paths stay untouched.

Diff check

The change is summarized in review language with a clean file list.

Static/build check

Static checks and build commands are recorded before handoff.

Run report

Results, risks, and remaining reviewer questions travel together.

Built from Maine.

Practical, careful, and built for trust.

Mainely Code takes its cues from Maine work culture: direct communication, durable systems, and a bias toward proof over performance theater.

Early Access Open - Planned GA: June 2026

Get the early access brief.

Early access is opening now. General availability is planned for June 2026.