THE ACCOUNTABILITY DOSSIER — EVIDENCE, NOT CERTIFICATION

A period in, a signed record out.

Hand Solora a period of your fleet's work and get back a signed, immutable, timestamped dossier: every load-bearing commitment the fleet made, the falsifiable test each was graded by, the outcome — misses kept — and the immutable record trail behind all of it, behind a thin login portal. Evidence a board can trust, read out of a record that was kept before anyone asked for it.

SATISFYING · NEAR The record it reads is graded and kept daily; the packaged, signed dossier over a period is the surface that ships next, near — evidence, not certification, and not legal advice.

One of four ways in — the ways in. The world it reads from is one river.

WHAT IT IS — A PERIOD IN, A SIGNED RECORD OUT

A signed snapshot of what your fleet already recorded.

A company hands Solora a period of its fleet's work and gets back a signed, immutable, timestamped dossier: every load-bearing commitment the fleet made over that period, the falsifiable test each was translated into, whether it was graded satisfied, violated, or retracted — misses kept — and the immutable aska trail behind all of it, behind a thin login portal.

It is the record of many makers on one ledger, packaged as an evidence artifact for a moment that demands one — a signed snapshot of what the substrate already recorded, read out of the ledger, attested, and delivered. This is the lowest-infrastructure surface: no fleet to run, no live hooks, nothing to keep running — read the existing graded record for a period, sign it, serve it. That thinness is exactly why it ships first.

Nothing is generated for the dossier that the fleet did not already bind and grade in the normal course of its work; the dossier's whole value is that it is faithful to a record that was kept before anyone asked for it.

The buyer is a function with a mandate and a budget — a risk, audit, or governance team that increasingly cannot answer "what did our agents commit to over the last quarter, and did they deliver?" from a task tracker or a pile of prose, and is increasingly required to. What the frameworks expect →

WHAT THE DOSSIER CONTAINS

Six things, all read from the same record.

The graded bindings

Every load-bearing commitment the fleet made over the period: the claim, its conditions, the agent id and kind that made it, and when it was bound.

The falsifiable tests

For each commitment, the test it was translated into: the specific thing that would have proven it wrong. Legibility is the point — a reviewer sees what a promise could fail.

The outcomes

Each commitment's grade — satisfied, violated, indeterminate, or retracted with its stated reason — and the evidence a concluding verdict is refused without. Violations are kept and shown as prominently as the wins, and an indeterminate is kept as its own conclusion rather than rounded to either neighbour.

The aska trail

The immutable, append-only, fully audit-trailed sequence of state changes each commitment left as it moved. Every grade links back to the trail that produced it.

The coverage statement

What the grading actually covered, what was out of scope, what was left unresolved — and the checks that do not run at all, named. No contradiction-check exists today, so the dossier claims no coverage over contradictions and quotes no bound for one. It is part of the deliverable, not an appendix.

The apparatus-version snapshot

The version of the substrate and its published coverage under which the period was recorded, stamped onto the dossier so the evidence is anchored in time.

One entry, as the dossier keeps it — the commitment, its conditions, its bound test, its satisfier, its grade, and the trail; with a violated binding kept beneath, because the record keeps its misses.

an intent, as the ledger keeps itillustrative — real shapes, sample rows

intentask_7f3e2c19goalcheckout latency

statedeclared → claimed → satisfying → graded

commitment"Checkout p95 stays under 200 ms at 1k rps after the cart rewrite."

test specload-run checkout.k6.js — p95 < 200 ms, three consecutive runs

carried bymira-2

verdictSATISFIED p95 = 164 ms · filed by mira-2, the seat that carried it — grades are append-only, so a corrected reading is a second grade, never an edit

walk the aska trail

▸ 09:41:02  declared     "Checkout p95 stays under 200 ms…" — seat mira-2, under goal "checkout latency"
▸ 09:41:07  test_spec    load-run checkout.k6.js — p95 < 200 ms, three consecutive runs
▸ 09:41:11  claimed      mira-2 takes carriage
▸ 10:02:19  satisfying   work begins
✓ 10:19:35  graded       SATISFIED — filed by mira-2, the seat that carried it

VIOLATEDask_5d11a04b — "Import handles 50k-row files" · failed at 38k · kept and owned, read by the next wave

A record that only remembers successes is not a memory, it is marketing.

A PORTAL, NOT A PDF

A living artifact you query and re-open — not a document that goes stale.

The deliverable is a thin login portal over the immutable record — a living artifact the buyer can query by commitment, by agent, by outcome and re-open, not a one-off document that goes stale the day it ships. The signed period is fixed; the way you read it is not.

By commitment. Pull one binding and read its whole life — the claim, its conditions, the test it was graded by, and the trail that produced the grade.
By agent. Every commitment a given agent made over the period, its kind, and how its work graded — humans and agents the same kind of participant.
By outcome. Filter to the violated and the unresolved as easily as the satisfied — the misses are first-class, never buried.

A one-time signed snapshot over a fixed period. The standing, every-wave version is the shared workspace.

ONE PORTAL SESSION — Q3, ONE FLEET, ONE RECORD

filteroutcome = satisfied — 178 of 214 commitmentsSATISFIED
filteroutcome = violated — 29 commitments, kept in fullVIOLATED
filteroutcome = unresolved — 7 never resolved, shown as unresolvedUNRESOLVED
agent orbit-341 commitments · grades linked to the aska trailTRACED
row ask_5d11a04b"import handles 50k-row files" · failed at 38kVIOLATED
coverageno contradiction-check runs · no coverage figure quoted for oneSTATED

Illustrated. Query by commitment, agent, or outcome and re-open it — grades computed from ground truth, never asserted.

THE COVERAGE STATEMENT & THE UNRESOLVED REGISTER

The bound is shown as plainly as the findings.

The coverage statement ships inside the dossier, not beside it — the buyer sees the limits as plainly as the findings. What the grading covered over the period, what was out of scope, what was left unresolved, and which checks do not run at all are part of the deliverable, not an appendix. Where nothing has been measured, the statement says so rather than quoting a figure.

And the register of what was not settled travels with it: a contradiction Solora could not read is not implied caught, and a commitment that never resolved is shown as unresolved, never dressed as a win.

What was not checked at all. No automated contradiction-check runs today, so the dossier claims no coverage over contradictions between commitments and quotes no bound — an unmeasured bound is a guess wearing a percentage sign. What the dossier covers is the graded record: what was committed to, and how each one resolved.
Everything left unresolved. A commitment that never resolved appears as unresolved — the dossier never quietly drops what it could not grade well.
Everything out of scope. What the period did not cover is stated plainly, so nothing outside the bound is implied covered.

Grades are computed from ground truth and stamped with the apparatus version used to record the period — never back-filled to look better. How this maps to the EU AI Act and NIST →

ALREADY KEPT — NOTHING TO ASSEMBLE BY HAND

A period in, a signed dossier out — already kept, not assembled.

The whole advantage is what the same evidence would take to assemble by hand — because when the record was kept before anyone asked, there is barely anything to assemble at all.

the same evidence	assembled by hand	read from the ledger
Every commitment the fleet made	Reconstructed after the fact from memory, chat logs, and tickets	Already bound before the work, timestamped, with the agent that made it
The test each was graded by	Argued in review, if it was ever written down at all	The falsifiable test it was translated into, kept beside the commitment
The outcome, misses included	Curated into a status deck that flatters the record	Satisfied / violated / retracted, computed from ground truth, misses kept
The audit trail	Stitched together across four hand-kept documents	One immutable, append-only, fully audit-trailed aska trail
The coverage	Asserted, and rarely bounded	Published inside the dossier and never exceeded

SIGNED DOSSIER · PER ENGAGEMENT READ, NOT RUN

A discrete deliverable — produced once, per reporting need, not a live service you keep running. It reads straight out of the record the house already keeps.

THE FRAMING DISCIPLINE — EVIDENCE, NOT A VERDICT

Held to the honesty rule hardest, because this is the surface a board might over-read.

The dossier is evidence — and only that

Evidence, not certification. It records what the fleet committed to and whether the bound test held — graded facts. It is not a seal of approval, not a certification, and not legal advice.
A grade is "the test held," never "the work was wise." A satisfied commitment means its falsifiable test passed; it does not mean the decision behind it was correct. The record is faithful, not omniscient.
Append-only, fully audit-trailed — not "tamper-proof." Nothing is edited in place and every change is itself recorded. That is what is claimed; it is not claimed to be unforgeable against a hostile insider.
Not a certification, seal, or attestation of correctness. It attests only that these commitments were made and these graded outcomes resolved this way.
Coverage is stated, never exceeded. Grading covers what was bound. No contradiction-check runs today, and the dossier neither claims one nor quotes a coverage figure for one.
No compliance guarantee. Solora produces the evidence artifact a governance obligation calls for — the kind the EU AI Act and NIST frameworks expect; it does not certify compliance or discharge the obligation. Confirm obligations with counsel. The mapping →

A dossier can be full of violated commitments — and if the fleet's record is, the dossier shows it. It is trustworthy because it does not flatter the record.

A dossier is readable end-to-end: the commitment, its test, its satisfier, its grade, and its aska trail — everything a reviewer needs, in the discipline's own plain terms. The trust story →