Closes the cycle for the seats now that both halves are on their main branches (mesh-catalog #69, mesh-controller #63, 19 packages passing).
New 03-DESIGN/00-as-is/12-the-seats.md, written from the code and the manifests rather than from the design: the closed set of fourteen (seven mesh, seven node; five deliver a provision), the three refusals a claim meets in order, the holder being a module assignment with nothing recorded beside it, the two resolution passes, the seats command including unheld seats and claims held outside the set, and the build source recorded as a path on the git seat with the clone URL composed at build time.
03-DESIGN/01-to-be/26-the-seats.md → implemented — defensible from both repositories' main branches, which is what cycle.py asks of that status.
The as-is README table gains its row.
Two things stated plainly rather than smoothed over, since that is what the layer is for:
A seat cannot answer before it is held. A seat decides which of several providers answers; it never makes a requirement optional. Before the seat is held, the requirement is refused like any other unanswerable one — the standing condition issue 121 records, now diagnosed in hq #119.
Capacity is not implemented. The glossary and the design have a seat with a capacity, and a bench as a higher-capacity seat several holders share. Neither exists in the code: a seat as it runs is one role with one holder at its scope. Nothing has needed a bench yet, but a design that says capacity and an implementation that has none is a disagreement that belongs in the as-is layer.
Checks: cycle 285 documents, the chain holds; records 104, all passed; index current.
Closes the cycle for the seats now that both halves are on their main branches (mesh-catalog #69, mesh-controller #63, 19 packages passing).
- **New `03-DESIGN/00-as-is/12-the-seats.md`**, written from the code and the manifests rather than from the design: the closed set of fourteen (seven mesh, seven node; five deliver a provision), the three refusals a claim meets in order, the holder being a module assignment with nothing recorded beside it, the two resolution passes, the `seats` command including unheld seats and claims held outside the set, and the build source recorded as a path on the git seat with the clone URL composed at build time.
- **`03-DESIGN/01-to-be/26-the-seats.md` → `implemented`** — defensible from both repositories' main branches, which is what `cycle.py` asks of that status.
- The as-is README table gains its row.
Two things stated plainly rather than smoothed over, since that is what the layer is for:
1. **A seat cannot answer before it is held.** A seat decides *which* of several providers answers; it never makes a requirement optional. Before the seat is held, the requirement is refused like any other unanswerable one — the standing condition issue 121 records, now diagnosed in hq #119.
2. **Capacity is not implemented.** The glossary and the design have a seat with a capacity, and a bench as a higher-capacity seat several holders share. Neither exists in the code: a seat as it runs is one role with one holder at its scope. Nothing has needed a bench yet, but a design that says capacity and an implementation that has none is a disagreement that belongs in the as-is layer.
Checks: cycle 285 documents, the chain holds; records 104, all passed; index current.
Both halves are on their main branches, so the seats stop being an intention. Writes the as-is
document from the controller's code and the catalogue's manifests: the closed set of fourteen, the
three refusals a claim meets, the holder being an assignment and nothing else, and the one place a
seat changes resolution — which of several providers answers, never whether a requirement may go
unanswered.
Two things the as-is layer exists for are stated rather than smoothed over: a seat cannot answer
before it is held, which is the standing condition issue 121 records; and capacity is not
implemented at all, so the design's bench has no counterpart in the code.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes the cycle for the seats now that both halves are on their main branches (mesh-catalog #69, mesh-controller #63, 19 packages passing).
03-DESIGN/00-as-is/12-the-seats.md, written from the code and the manifests rather than from the design: the closed set of fourteen (seven mesh, seven node; five deliver a provision), the three refusals a claim meets in order, the holder being a module assignment with nothing recorded beside it, the two resolution passes, theseatscommand including unheld seats and claims held outside the set, and the build source recorded as a path on the git seat with the clone URL composed at build time.03-DESIGN/01-to-be/26-the-seats.md→implemented— defensible from both repositories' main branches, which is whatcycle.pyasks of that status.Two things stated plainly rather than smoothed over, since that is what the layer is for:
Checks: cycle 285 documents, the chain holds; records 104, all passed; index current.