# The concordance — chapter → commit

Hashes and dates are real; messages are paraphrased for confidentiality until the source
repository's public perimeter is ruled.

- `fca0c1d` 2026-07-08 · Part II — The founder moved his ventures into a single shared repository — company documents, plans, and principles now live where an AI can work on them directly.
- `abda10e` 2026-07-08 · Part II — Standing rules landed on day one: an instruction file for the AI, a naming standard, a single task board, and standing permission for the AI to commit finished work.
- `028c23d` 2026-07-09 · Part II — A universal entry point was added so that any AI tool or fresh session boots into the workspace through one README door.
- `1d59946` 2026-07-09 · Part II — One file was designated as the permanent home for durable lessons about working with AI, so nothing learned survives only in a chat.
- `2a35ff0` 2026-07-09 · Part II — A rejected company-profile draft was removed and the rejection itself recorded, turning the founder's taste into calibration input for future design work.
- `1bf9759` 2026-07-09 · Part II — An editorial standard was set for how rules graduate: chat learnings are promoted into the standing-rules file deliberately, one considered rule at a time.
- `94acdec` 2026-07-09 · Part III — Build order was corrected on principle: inventory every workflow's verbs first, and only then design the database schema.
- `e93c501` 2026-07-10 · Part III — The full canon of actions the software must support was ratified and closed before any interface work began.
- `8777092` 2026-07-10 · Part III — An ownership question was settled: the technology venture builds the operating system, and the industrial venture is its first operator.
- `70c3d5a` 2026-07-11 · Part III — A protocol for processing the founder's brain dumps was fixed — preserve, classify, triage, test, integrate — with a rule that no item may disappear silently.
- `b2e7b7b` 2026-07-11 · Part III — The naming standard was promoted to workspace level: one grammar for identifiers, dates, statuses, and corrections across every venture.
- `716322b` 2026-07-11 · Part VI — Outbound documents became records: the exact bytes attached to a client email are archived unchanged, and an append-only ledger of everything sent was opened.
- `d1c1b81` 2026-07-13 · Part III — A single design system was adopted as the substrate for every venture's sites and apps, with each venture's visual identity reduced to a theme on top of it.
- `40fab8c` 2026-07-14 · Part V — Skills were rebuilt into one tool-agnostic canonical home that any AI harness can load, and a legacy generation of tool-specific skills was retired.
- `7705e93` 2026-07-14 · Part IV — A nightly automated backup push became a standing rule — upload-only, machine-scheduled, approved once by the founder.
- `1111bc2` 2026-07-14 · Part IV — The repository became the canonical home for the machine's own setup, with scheduled jobs reinstallable from the repo and a written recovery runbook.
- `f212f9a` 2026-07-14 · Part V — A working rule proposed by one AI tool was ratified for all of them: restate the founder's probable underlying question and proceed, instead of clarification ping-pong.
- `3a93d34` 2026-07-15 · Part III — Task doctrine was promoted to law — how commitments are recorded, how many may exist at once, how they expire, and how much autonomy an agent may take.
- `b0c93c9` 2026-07-15 · Part III — A single one-glance map of all ventures was built alongside an append-only decision log, and each venture's board became a detail record beneath it.
- `94cb2ba` 2026-07-17 · Part VI — A power-plant client accepted the completed cleaning scope — the first field campaign run end-to-end inside the shared workspace.
- `367cc61` 2026-07-19 · Part IV — Encryption was switched on for sensitive paths: people records, chat archives, personal files, and identity documents leave the machine only as ciphertext.
- `9a10f4b` 2026-07-19 · Part IV — A tool-agnostic pre-commit gate was wired in so that no AI or human can accidentally commit sensitive material.
- `fb0ed03` 2026-07-20 · Part VI — A cost-truth register was founded: quote quantities are now derived from evidence, and legacy figures were quarantined to a comparison column.
- `640f7cc` 2026-07-20 · Part VI — Labor premiums, statutory burden, and fuel were re-derived from primary sources — and the inherited cost basis was exposed as under-costed.
- `77fbc42` 2026-07-21 · Part IV — A workspace-wide rule was promoted: any file made for an external reader is written assuming it will reach competitors — ranged claims with validity clauses, nothing executable, a notice on every copy.
- `e4d5a4a` 2026-07-22 · Part V — The rule was promoted that durable AI rules live in the shared workspace, where every tool reads them.
- `a3abcf6` 2026-07-22 · Part V — A cross-model review amended the memory doctrine: a tool's private memory is a cache of workspace truth, and the repository wins on conflict.
- `fc43dfa` 2026-07-24 · Part VI — The education venture's pilot was accepted at the client meeting; the minutes were filed and the queue turned to standing up the hosted app.
- `9f57859` 2026-07-25 · Part VI — A pilot price was set by a delegated pricing hat, derived from a named standard rather than negotiated ad hoc.
- `1e454a5` 2026-07-25 · Part VI — A pricing derivation standard was written after an anchoring failure was caught on record — five gates, with the old price register demoted to a last check.
- `4aae05a` 2026-07-26 · Part VI — The founder caught a fee that had been copied from a register; it was re-derived from zero, and a rule was set that only fees that will really be charged appear on client papers.
- `2d1f5cd` 2026-07-28 · Part IV — An operating layer was added for asset initiatives, so the system carries the reminders and the founder keeps only the verdicts.
- `7403bbd` 2026-07-28 · Part IV — A gap in the encryption was closed: file names stay readable even when contents are encrypted, so batches of files named after people now arrive as sealed archives.
- `e74ca26` 2026-07-29 · Part III — An entire finished interface was deleted the day a better one proved itself — the founder's kill verdict was recorded, and no legacy surface was kept alive.
- `fc3092f` 2026-07-30 · Part VI — Pricing doctrine was ratified: a hard margin floor computed from direct cost, banded rates with a verifiability rule, and a standing estimating convention.
- `8792d33` 2026-08-04 · Part V — Delegation doctrine was extended: agents graduate through verifiability classes, judged work logs its counterfactual, and every agent seat binds to a human whose accountability cannot be delegated.
- `868d343` 2026-08-04 · Part VI — A pre-works survey report for a mining client was built from a structured multi-agent photo analysis, including an honest-limits section stating what the survey could not see.
- `f531074` 2026-08-04 · Part IV — A weekly triage of the venture map was bound to the calendar: the system initiates the review on schedule, and the founder only renders verdicts.
- `eb50bce` 2026-08-04 · Part VI — A revised quote went out to a client and its ledger rows flipped to sent — the archived bytes are now immutable.
- `29f2538` 2026-08-05 · Part V — The workspace boot path was rebuilt to be tool-agnostic — one always-on rules file with a single task router, and a three-step boot door that every AI harness enters the same way.
- `380bb26` 2026-08-05 · Part VI — A revised quote went out to a processing-plant client with a negotiated award discount ratified on the record — the concession logged with its reasoning, the rate card left untouched.
- `1abe49c` 2026-08-07 · Part V — The roster of scheduled routines was consolidated under short stable names and the outdated ones retired, with every definition mirrored in the repository so the automation survives any one machine.
- `9eba330` 2026-08-07 · Part VI — A pipeline-and-heat-exchanger descaling quote for a power-plant client was issued the day after the inquiry arrived, its rates re-derived from the cost registers instead of inherited from past papers.
- `38a6a2d` 2026-08-08 · Part IV — A hard gate was promoted to workspace law: no AI writes anything to the outside world — a message, an upload, a register edit — without the founder's explicit approval of that specific write.
- `810cd22` 2026-08-08 · Part IV — The personal site's publishing press gained a machine guard — every generated page is checked for non-public material before anything can ship.
- `b918b50` 2026-08-09 · Part VII — The personal layer was founded and named: a governed system of record for the founder's own commitments, separate from every venture board.
- `25cfc4c` 2026-08-09 · Part VII — An authority invariant was ratified for the personal record — natural language may propose a commitment, correction, or completion, but only the founder's explicit approval makes it canonical.
- `200ecfc` 2026-08-09 · Part VI — A duration-banded rate curve was derived from the cost registers, putting three clients' pricing on one defensible model and retiring per-client historical anchors.
- `5077fe6` 2026-08-11 · Part IV — A separation rule was promoted for live client pages: the internal field-ingestion layer and the client-facing layer are distinct by construction, so raw field detail can never leak into what a client sees.
- `ea47887` 2026-08-11 · Part VI — A live progress page was deployed for a power-plant campaign — the client now watches reviewed field status and progress curves instead of waiting for reports.
- `0cec5df` 2026-08-11 · Part VII — The all-ventures overview map was retired, and the founder's current focus cut over to a deterministic projection of the governed personal record — capped at three commitments and always read from the record itself.
- `e5b8750` 2026-08-16 · Part III — A record-layer vocabulary was ratified into the naming standard — register, record, registry, and ledger each carry one fixed meaning — with a standing duty to correct misuse in either direction, founder included.
- `88b8421` 2026-08-17 · Part V — A bootstrap requirement was promoted and packaged as a skill any AI harness can run: before writing a business artifact, a session must first load the workspace authorities.
- `a171426` 2026-08-18 · Part VI — Field execution began for a manufacturing client with the record layer running from hour one — a field log, provisional progress rows, and a client sign-off form all issued on day one.
- `9cd9143` 2026-08-21 · Part III — A document-design rule was promoted out of a client-report polish pass: consistent vertical rhythm is now a standing requirement for every outbound document.
- `3d1ed45` 2026-08-21 · Part VI — A pipeline-cleaning engagement for a manufacturing client closed end-to-end inside the workspace — pre-work pipe map, signed field checklist, and a transmitted completion report, with transmission verified.
- `f8d9c5f` 2026-08-21 · Part III — The personal site was ruled to carry the founder's full name — project, domain references, and launch configuration renamed in one pass, with the public-material guard re-verified from the new path.