The covering document for the refactor of the Common Information System: eleven principal artifacts, what each is for, what it inherits from the existing estate, what it retires, and the order in which the set becomes ready to write. There are no dates in this series. Dependency is the schedule.
In an agent-driven build, these artifacts are not documentation of the work. They are the medium of it. A build agent's working context is assembled from exactly these documents, so each one is versioned in the repository, citable by section, and honest about its own status. An ambiguity here is an ambiguity multiplied across every packet of work downstream.
This series is a refactor, not a greenfield. An estate already exists at the commons repository: a seventy-milestone ledger organized into waves, ten recorded decisions, an operating contract for agents, a validator that enforces dependency order, a schema reference, a probe matrix, gate definitions, and live instruments. Much of that estate was shaped around a grant that no longer exists, and the design discipline it carried has been retired as a requirement. The mechanics, however, were sound. Each entry in this series therefore carries a lineage line naming what it supersedes, what it salvages, and what it retires, so that nothing is erased and nothing is quietly carried forward either.
Two vocabularies bind the whole set. The status marks (Filed, Ratified, Drafted, Anticipated, Open) apply to every claim in every artifact. And the four slices named on the public page (Belong, Gather, Find one another, See your share) are the shared shape of the build, so that the public promise and the work plan use one language. The series includes itself: SER is the first entry in its own register.
Because there are no time estimates, readiness does the scheduling. A packet of work is ready when everything it cites is settled enough, and a blocked packet wears the chip of the item that blocks it, by name.
The citation grammar is code, version, section: IM v0.1 §3 is a complete address. The section addressing scheme already decided in the estate (D7) carries forward unchanged. Supersession is always explicit: a new version names what it replaces in its preamble, and the replaced document remains in the record as history. Nothing in this series is deleted; things are succeeded.
Three further disciplines carry from the estate and from board practice. First, only humans record decisions; agents may improve a deliberation brief but never resolve it. Second, the vocabulary quarantine holds: Subchapter K grammar throughout (distributive share, capital account, allocation), with the retired cooperative-tax vocabulary kept out of every artifact. Third, provenance is marked conservatively: agent-authored work is labeled as such, and simulated or illustrative entries write nothing back to the live record.
Eleven artifacts. Each entry names its purpose, what it cites upstream, and its lineage against the estate.
This document. The map of the set, including itself: what each artifact is for, its readiness condition, and its lineage. Revised whenever an artifact lands or the set changes shape.
What the system is and does: the four slices as scope, the information model at the level of meaning, success criteria including the walkaway test, and open questions. Its preamble absorbs the deprecation record, stating plainly that the CROPS discipline moved from gate to design note when the funder context ended, so the change is recorded rather than absorbed.
The canonical schema: agents, memberships, agreements, signatures, and the REA event log, with the conservation laws stated declaratively (one share per member, vote arithmetic, accounts that balance) and the three-axis status contract (provenance, settlement, temporal state) generalized as the system-wide vocabulary. The single artifact every build agent touches.
Member classes, roles, and every row-level policy, each citing its bylaw anchor. Drafted honestly against Drafted bylaws and hardened at ratification. Agents are never permitted to invent a permission; this is the document they cite instead.
The methodology: the shape of a work packet, what an agent may decide and what it must escalate, how agent-authored work is provenance-marked, branch and review conventions, and decision records for anything consequential, so agency stays visibly with the organizers.
How done is judged without a clock or a supervisor: invariant checks that run as code, acceptance criteria per packet, slice gates with human attestation, and eventually the walkaway test as an executable check. The security floor gate carries unchanged.
The runtime instrument, distinct from the build agents: read scope, draft scope, the citation duty, and refusal boundaries for the Ask door. Retrieves and drafts; members and the board decide. Supersedes the charter that still points at the retired token set.
Where the verb operate lives: environments, migrations, backup and restore actually tested rather than merely present, key custody, and secret handling. Thin at first, growing with the slices, but never absent.
Techne v4 as the shared token layer in code, the two-grammar rule (document and instrument), and a pattern inventory, so agents apply the design system rather than reinterpret it on each surface.
The dependency-ordered packet ledger, shaped by slice rather than by wave, with a readiness condition on every packet and no dates anywhere. Kept separate from the PRD deliberately: the PRD should stay stable while the roadmap versions rapidly under agent traffic.
The public door of the record, replacing the current index at the commons address. Leads with the system rather than the build, and may claim only what a series artifact holds; every public sentence should be traceable to a code. The instruments remain linked, quietly, rather than centered.
The sequence below is dependency order, not a calendar. Each entry names the condition under which it is ready to write; several can proceed in parallel once their conditions hold.
The landing page is a series member, not an afterthought, because it is the artifact where the refactor's positioning becomes a public promise.
Its rule is simple: the page may claim only what a series artifact holds. The current index at the commons address leads with the build (milestones, waves, decision registers); the replacement leads with the system, in the voice of the v0.1 introduction, and lets the instruments recede to a quiet strip. Whether one page serves both the cooperative's public address and the repository's front door, or the two addresses carry different registers of the same page, is an open design choice that belongs with Todd, as does the working name itself.
A covering document earns its keep by naming its edges.
Retired with the grant: the Hub Operations PRD as a governing specification, the KPI fixture pack, the liaison interface decision, and the KPI-gated wave. Their salvageable parts are named in the register above; the documents themselves remain in the record as history. The eight remaining recorded decisions carry forward unless a slice reopens one, and the two ratification items stay open where they belong, with the members, gated to August 14.
Left out of the series, deliberately: the bylaws, membership agreement, and patronage policy, which are upstream dependencies owned by the board and counsel rather than build artifacts, though AM and PRD consume them. The dispatch cadence, which documents the build publicly but does not govern it. And member-facing content, which is an output of the system rather than an input to it.
Nothing erased, everything succeeded. Every claim wears a mark. Dependency is the schedule. Agents draft and build; people decide. And the public page never says more than the shelf can back.