A module specification, drafted for adoption: the branching maturity model entered into the Common Information System as record. The internal end, already built, is cited rather than rebuilt. The origin is protected from being ranked, counted, or given standing by activity, and whether it may be named at all is an election for the board. The external end is specified for construction. Every decision the build requires is staged for hands, and the agent constructs nothing until the conditions that name those hands are met.
This module gives the branching maturity model a body in the record.1 It follows the only intake route the commons offers: PATRONAGE, TREASURY, and AGY each entered as a module document, an adoption, and a graft into the ledger, and this capability takes the same door.2 Adopting this module is not a formality downstream of the model; it is the election that adopts the branch. Until that adoption lands as an event, everything here is drafted and nothing here is true of the cooperative.
The posture is the standing one: Nou drafts and surfaces; Todd decides and the board adopts. Construction proceeds under the Common Agency discipline as it operates today, steward-relayed, every artifact under two hands, and this module grants the agent no authority it does not already hold; it asks for none.2
A body of work is any sustained activity at the cooperative, whether or not the record knows it. A standing is a state the record can prove: it is conferred by an adopted instrument and tallied from events at read time, never stored as a mutable label. The origin is project standing, which is to say no recorded standing at all. The internal end is Program standing; the external end is Venture standing; both is one body of work holding an instrument of each family. Four principles govern, within the eleven laws of the information model and adding none; conformance is asserted by the suites, not by this sentence.3
P1 · Standing tallies from instruments. A standing exists exactly when an adoption event stands in the record concerning the body of work, citing an instrument of the standing's family whose marks are settled. Anticipated instruments confer nothing.
P2 · Kind is structure; standing is instrument. The identity spine's kind column names what a thing structurally is. It is never consulted to answer what standings a thing holds, which is why one body of work can hold two.
P3 · The origin confers nothing. A body of work at the origin holds no standing, and no amount of activity, posting, responding, or resolving confers one; only an adopted instrument does, per P1. Whether the record may know a project by name, as a row carrying name and purpose and nothing else, is decision STANDING-D6, staged and not taken. Until it is taken the builder introduces no such object, and on either answer the sentence above does not move.
P4 · Crossings are adoptions. Work moving between ends, or adding the second, is the other family's instrument adopting. There is no crossing verb, no transition machinery, and nothing changes standing silently.
Program standing is governed by PATRONAGE and is live in the parts that matter here: designate_program() writes the agent row and the program.designated event, the POLICY-PATRONAGE adoption confers policy standing, programs_roster() tallies that standing from agreement.adopted events, and affiliation lands as events, never a table.4 This module changes none of it. The internal end is cited as the pattern the external end mirrors, and as proof the pattern holds under live use: both principal Programs were designated from the intranet on the applied migrations.2
The opportunity board and the unaffiliated shelf are the origin's only surfaces, and they already exist. A person with an idea posts, gathers, responds, and resolves without anything being created first, which is the model's open door and stays open on either answer below: no piece of this module, and no future convenience, may make a project a precondition for posting to the board.
What v0.2 said beyond that, that no object called a project would ever exist, went further than the model requires and further than anyone adopted. The steward challenged it on 2026-08-10 on the ground that no member and no board ever took that decision. The challenge is correct, and this section records it rather than quietly restating the principle. The refusal that carries weight is about standing, not about names: P1 already guarantees that a named project would hold nothing, since standing comes only from an adopted instrument, and P2 says the same in the spine's own grammar, kind is structure and standing is instrument, which is exactly why a row could name a body of work without conferring anything on it.
So the question is open, and it is a real one. The use it would serve is plain: a person shares a project and posts several asks against it over months, and today the record cannot say those asks belong together. The costs belong to the board and not to the builder: whose hand may name a project, whether naming becomes a ceremony where there was none, and whether an object invites the counting R4 forbids. Section 10 stages it as STANDING-D6, with the terms named and no recommendation. The builder introduces nothing until it is answered.
A venture enters the record the way a Program does: by a designation act that names it, with substance arriving later by instrument. The verb contract, emitted as migration 0021 once its conditions land, mirrors the applied designation act line for line.4
-- contract, not yet an emission · mirrors 0012 · conditioned on adoption and STANDING-D1
designate_venture(p_display_name text, p_purpose text default null) returns uuid
-- floor: actor is steward or director (Bylaws §3.1, §4.1, the 0012 floor)
-- idempotent by name; writes one agents row and one venture.designated event
-- designation carries only name and purpose; no policy widened; the verb is the only doorWhat kind the agent row carries is decision STANDING-D1, staged in Section 10 with a recommendation and its alternative honestly priced. The verb builds against whichever shape STANDING-D1 records; the events namespace costs nothing either way, since event kinds are free text in the substrate.3
Venture standing is conferred by instrument, in two layers that mirror how PATRONAGE governs its end. The covering layer is VENTURE-TERMS, one board-adopted agreements row authored by people with securities counsel, never by the agent: it names which instrument shapes qualify (royalty units, revenue shares, a cap table), the counsel checkpoints each shape requires, the linkage to the counting rules wherever an instrument values member labor, and the one sentence decision STANDING-D4 asks for. The per-venture layer is a venture instrument for each body of work, an agreements row in the VENTURE code family citing VENTURE-TERMS, whose agreement.adopted event concerning the venture confers standing under P1.5
The dependency worth stating plainly: any labor-valued instrument leans on the fair-market-value rates the Q3 resolution would name, when it is taken, the same board decision that unblocks the Share bed. One decision feeds both ends of the branch, which is why this module adds no economics of its own and waits where waiting is honest.2 5
Three reads, emitted as migration 0022, all computed from events at read time with every row tracing to the event that made it, definer at launch per the recorded visibility decision the Programs view took.4
-- contracts, not yet emissions · read-time tallies, security definer at launch
ventures_roster() -- each designated venture with its standing and dates
venture_standing(p_venture) -- the instruments in force for one venture, each citing its adoption event
work_standing(p_agent) -- zero, one, or two standings for any body of work, by family,
-- kind never consulted (P2); the both surface and the crossing historywork_standing() is where the branch becomes visible: a Program that later adopts a venture instrument, or a venture the cooperative later takes inside by ratifying a patronage policy, simply shows two standings with two dates. The crossing was the adoption; the tally is its memory; the narrative belongs to prose.
One principal page at /intranet/ventures/, inside the shell like every signed-in surface, with a window on the Overview beside the Programs window: the roster, each venture's standing shown in the constitution's chip states, and each standing tracing to its instrument on the agreements shelf. The surface speaks the member's language, not the build's, per the register the shell established, and no tally or verb name reaches member copy. Before any instrument exists, the page stands the way the U-07 parked door stands: designated ventures shown with zero standings and the waiting named by name, a promise that cannot yet be kept still owed its place on the map. No public surface exists until decision STANDING-D5 names one; until then the grammar quarantine holds and the word stays inside.2
JC-1 · with PATRONAGE. Venture standing never diminishes patronage. Member labor toward a venture may still register inward as a Contribution under whatever counting rules govern; the layers stack rather than substitute, as the record has held since March.5
JC-2 · with TREASURY. This module moves no money. Venture receipts, when they exist, enter by the intake rail's seam pattern as movements citing the venture instrument, and reconciliation remains the Treasury bed's tally. Nothing in STANDING touches a disbursement.
JC-3 · with AGY. All construction proceeds under Directions in the mode currently in force, steward-relayed, two hands on every artifact. The first-grant decision staged at A-03 neither waits on this module nor widens for it.2
R1 · No standing at the origin, ever. A body of work for which no instrument has been adopted holds no standing, whatever else the record may know about it, and no piece may make a project a precondition for posting to the board. Whether an object may carry a project's name is STANDING-D6, an election for hands: a piece proposing one before that election is out of order, and a piece proposing standing by activity is out of order on any answer.
R2 · No retroactive classification. The agent never reclassifies existing bodies of work. Whether Parachute, or any Program, holds a second standing is decided by humans adopting an instrument, one body of work at a time, or not at all.
R3 · No instrument authored by the agent. VENTURE-TERMS and every venture instrument are people's writing, with counsel where their shape requires it. The agent builds the shelf they rest on.
R4 · No maturity scoring. Standings are named states, never numbers. No metric, funnel, rank, or progress bar represents the branch, in the schema or on any surface, matching the guard the marks already carry.
Two emissions, numbered as the chain stands and yielding to it at application time: 0021 carries the STANDING-D1 shape and the designation verb with its probe cells; 0022 carries the three tallies and theirs. Every new function gains cells in the probe matrix citing their authority anchors, the validator's coherence rules apply to the pieces below unchanged, and the grammar lint needs nothing, since the module introduces no quarantined vocabulary to a public surface.2 The graft enters a bed of four pieces and one proof, none of which conditions launch and none of which launch conditions on.