Read the mark
A glass for the Golden Thread.
Loupe reads a
trace-manifest
, the machine-checkable record from intent to build to proof, and lays the whole Golden Thread open to read: every statement of intent, the build that carries it, the proof that answers for it. No scores, no dashboard. It is the evidence room: you come here when you want to see for yourself.
Daily verification lives in the pull request: the Gate checks, the Thread Report briefs. Loupe is for the moments that deserve a longer look:
The morning after
The agents ran all night and every PR was briefed. Before you build on the result, put the manifest under the glass and walk what moved, end to end, at your own pace.
Onboarding
New to the codebase, human or agent? The thread is the tour: every statement of intent, what carries it, what answers for it, before you read a line of code.
The audit
A dispute, a handover, a regulator. The manifest carries its meaning at rest, so the record still reads true long after everyone's gone home.
Pick any intent and Loupe walks it top to bottom: the intent (its durable ID and statement), the build that carries it (
@covers
in source), and the proof that answers for it (a named test). A solid braid means the thread holds. A frayed one means it doesn't.
Intent → Build → Proof
Every durable ID, walked from intent to build to proof. No spreadsheet, no second system that lags the repo.
The refusal
A silent gap is gilt : work gilded to gleam like done, with no metal underneath. Loupe frays the thread exactly there.
Meaning at rest
It reads what a gate emitted; it never re-scans the target. Printed or screenshotted, it still tells the truth.
SpecAssay
assays the work: it mints durable IDs at intent, refuses silent gaps, and strikes a
trace-manifest
on every push.
Loupe
is the glass you read that mark through. The manifest belongs to no single tool, so Loupe reads any emitter's, not just SpecAssay's.