Agents build
your software.
Your filed rules
decide what ships.
The workflow you have to build and cannot staff, live in four to eight weeks, scoped and priced before it starts. A change that breaks a rule you filed never reaches a reviewer: it is refused before anyone is asked, and the refusal is a row with the rule on it.
A control you have only ever seen pass is a control you have not seen.
✓ core-boundary: no writes across the domain boundary
✓ filed-rate-conformance: 1.55 sits inside the filed band 1.38–1.61, checked against the filed rate on record
No human was asked. The rule ran first.
A named person on your team, with the reason in their own words.
Two fixture changes, four days apart: CHG-2418 refused at the gate, CHG-2417 approved. Fields the spec marks proposed (the change number, the exhibit pack) appear as they will. Click any line.
Type your filed band.
Then try to break it.
Two numbers off one of your filings, and a value for the agent to propose.
This is the fixture rule. Type your own band.
Fixture program, fixture rule, your numbers. The comparison runs in your browser and nothing you type leaves this page. In production a check of this shape runs in CI, before merge. There is no override in this panel: changing a rule you filed is its own change, with its own approval and its own row.
“We’re not doing AI.
Compliance won’t let us.”
Then bring your compliance lead to the first call. The Model Audit Rule, the DOI exam, and every carrier audit ask who changed it, who reviewed it, and who approved it. Each of those is a column on the row, written while the work happened.
Three steps.
One receipt per change.
The software on the line, as it actually is.
Read from your code, never drawn by hand, and the build fails if it drifts.
Agents build. Your people approve.
Checked against policy before it merges, then approved by a named person on your team. Bad changes don’t get reviewed. They get blocked.
Every change leaves one row.
Who asked, what ran, which checks passed, who approved, frozen to the exact code. Exam day becomes a query.
The three builds already on your list: submission intake · the Excel rater · bordereaux.
One workbook in.
This is what a build delivers.
A first build is one workflow, four to eight weeks, scoped and priced before anything starts. This is that scope, itemised, on a fixture program.
The receipt is what one change leaves behind. This is what one build is scoped to deliver. Both run on the same fixture program, WC-MGA-2024.
Wrap a workbook and you record
that it was opened. Not that the
multiplier left the filed band.
The trail stops at the boundary of whatever it calls. Haltere is what the systems are built out of, so the record covers the whole transaction you build on it, not one layer’s view of it.
What gets built is the software that was never a system: the rater in the workbook, the clearance nobody owns, the bordereau assembled by hand. Not your policy admin system, and not anything you rent. We switch nothing of yours off: the workbook keeps rating until you decide it stops. And not every workflow should be rebuilt — where the only statement of how one behaves is the thing itself, writing that down is the first part of the work. The argument, and the evidence against us
The receipt format is public, and so is a sample pack. Send both to the person who has to sign off.The receipt format · The sample evidence pack (PDF) · fixture data
Start with the workflow you
already have to build.
Thirty minutes with the engineers who build the line. Name the workflow and the examiner you answer to; we tell you what a governed build looks like, what it costs, and when it can start. Bring your compliance lead.
One workflow, four to eight weeks, scoped and priced before anything starts, live in your environment with the evidence pack. Afterward we run the line, or we train your operator to. Either way you own it and do not rent it, in open formats inside your boundary, and nothing you run trains us or anyone. Walk at renewal with everything.
Inquiries are answered within one business day, by someone who can answer them.