REMEMBER — WHAT SOLORA LEARNS FROM ITSELF
The record that compounds.
Bind, grade, and keep leave one thing behind: an append-only record of every commitment the team made and how each one resolved. This last chapter is about what that record is worth — not an archive to file, but the thing that makes the fire compound. Query it instead of re-writing it, read it before the next wave, and Solora stops starting cold every morning.
GRADED · DOGFOODED The house runs on this record daily — the misses kept as loudly as the wins.
ONE RECORD — FOUR DOCUMENTS RETIRED
Journal, changelog, audit, postmortem — one record.
Keep leaves one thing behind: an immutable, append-only trail — the aska. Every state change is itself a versioned row; nothing is edited in place, and every violated binding stays there and owned. It is append-only by construction and fully audit-trailed — the history is the point, not an incidental log.
Which is why four documents retire. The journal, the changelog, the audit, and the postmortem stop being four things anyone keeps by hand and become four questions asked of the same trail. Nobody grooms four artifacts; you query one record — and the next run reads against the misses instead of re-deriving them.
- The journal — what did we work on.
- The changelog — what shipped.
- The audit — what was committed to.
- The postmortem — what did we miss, and why.
journal · changelog · audit · postmortem — four views, one aska
The same record the observatory reads as a live orbital view of every intent in flight — queried as documents here, watched as motion there. The observatory →
A record that only remembers successes is not a memory, it is marketing.
AGENT-NATIVE — THE RECORD KEEPS ITSELF
The record rides inside the agent loop.
Nobody keeps this ledger by hand; the agents do. Bind, grade, and query are called directly by the agent doing the work — through a CLI and an MCP tool surface — so the commitment is laid down in the same motion as the work, and the grade is recorded the moment the outcome is known. The discipline rides inside the loop instead of being a form a human fills in afterward — the form nobody fills in.
A human is still in the loop: you can read, retract, or override. But the default path needs no bookkeeping — the only reason the record is ever complete enough to compound. And nothing un-gradeable ever enters it: a commitment with no test that could prove it wrong is refused at bind-time, the rule set in the first chapter. Bind. Grade. Keep. →
| move | CLI | MCP tool |
|---|---|---|
| bind | solora bind --commitment "…" --test checkout.k6.js | bind({ commitment, conditions, test_spec }) |
| grade | solora grade ask_7f3e2c19 --from ci | grade({ binding, satisfier }) |
| query | solora query --as postmortem --since :sprint | query({ view: "postmortem" }) |
Illustrative shape, not a fixed contract — the surface is open. Same three verbs from either surface, called against the same record.
WHAT THE RECORD TEACHES — THE ASH SETTLES INTO GROUND
Settled ground a new binding cannot silently violate.
As commitments resolve, the satisfied, un-retracted ones accrete into settled ground — the basalt the fire leaves behind. A new binding cannot silently contradict what the record has already settled — in the design. DECLARED · FRONTIER The check that would read the standing record before a bind lands does not run, so today the settled ground is protected by a human reading it, not by the ledger. That is the gap between a record that remembers and a record that acts on what it remembers, and it is the single largest one on this page. Where a clash would be caught →
And the record feeds forward instead of scattering. The next wave does not start cold — it reads the standing record, the settled ground and the kept misses and the procedures that reliably cast to satisfied, so what Solora already paid to learn is carried in, not paid for twice. Yesterday's grades inform today's dispatch. Into the next wave →
THE LEARNING LOOP — CONSENT-GATED, HONESTLY FRONTIER
Across organizations the same graded record can — only with explicit, revocable, scoped consent — feed a shared learning loop: the more consented commitments run through Solora, the sharper the shared intelligence gets for everyone who opts in. Nothing enters any shared corpus by default; silence is opt-out. DECLARED · FRONTIER
That it learns is open; how it learns is proprietary — and your record never depends on it to be read. What crosses is aggregated, pseudonymized graded structure, never a readable window into a neighbor's plan. Where the line is drawn →
The improvement is in the shared intelligence, never in your neighbor's record.
WHOSE RECORD IT IS — YOURS, AND IT STAYS YOURS
A record of intent is yours.
A record of intent is among the most sensitive artifacts an organization produces: what it bet on, what it missed, what it retracted, and why. That is exactly why the governing principle is one line — a record of intent belongs to the tenant that wrote it.
And the ledger is a working instrument, not a publication. It is never published — not a customer's, and not the house's own, which runs under the same law. The house is proven by living on the record daily, misses kept, never by inviting anyone to scroll it. What you are shown is the shape of the discipline, never the contents of a ledger.
The nevers
- Never publish the ledger — a tenant's or the house's own. It is a working instrument, not a feed.
- Never let one tenant's commitments, traces, satisfier content, or grades cross into another tenant's record — or into a shared computation.
- Never feed a record into any shared corpus without explicit, revocable, scoped consent; silence is opt-out.
- Never fabricate a grade to flatter the record — an unresolved commitment is shown unresolved, a miss is kept, an abstain is an abstain.
Solora keeps it in the light; it does not get to mine it.
THE THESIS — WHY KEEP ANY OF IT
Memory is what turns a circle into a spiral.
A forge that scatters its ash each night starts cold every morning and forges the same flawed blade forever. A forge that keeps and reads its ash learns the temper of its own fire — its next blade is truer than its last.
Bind. Grade. Keep. Coordinate. See. Beneath every chapter lies this one record — and the record is the only reason Solora grows truer at its own work instead of repeating it. The record is what makes the fire compound.