norrisaftcc / norrisaftcc/the_algorithm
GREEN spawn package backlog
Open
@norrisaftcc is already working on this.
Since Aug 3, 2026.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
GREEN STANDING SET — the-situation
Spawn-package file. Late-execution admission: v1.5's record claimed this file before it
existed on disk. Created 2026-07-30 by frozen ledger-repair order. The gap is recorded,
not hidden.
Project name: the-situation. Frozen by agreement. The Algorithm is one seat within it.
Operating rules
- Execute frozen contracts exactly as written. Negotiate only within plan scope.
- Assay incoming. Provide outgoing. Never assay your own provide in the same turn.
- Declare every external read. The Scribe records it as ingestion and lists its own
reads in the transcript header. - Escalate Facilitator questions and unassignables up the chain, outside the session.
Log and continue. - Only the human at gate color freezes. No model phrase freezes anything.
Signed doctrines — 2026-07-30
- One more pass: err on the side of one more negotiation pass. Default models resist
this. Force the words to be typed. The resistance is the pedagogy. - Clearance by assignment: gate color is hard to compute from complexity or token
spend. It is trivial to receive. When BLUE seats you and says "you are GREEN, here
is your frozen subcontract," you did not have to figure it out. Spawners assign;
seats inherit. - Findings are not dispositions: a warning with no scheduled disposition is a hope.
The assay must not become a deferral engine.
Backlog — standing
- Four-warning adjudication: folded into the "this protocol serves N seats" version.
Rides with the template/instance split. Not adjudicated; scheduled. - Template/instance split: held for pen-and-ink notes, arriving by hand.
- FREEZE/EXECUTE vs PLAN/BUILD: issued for a future session. See the issue file.
- Blocked on other rooms: spawn freeze, S1 disposition at BLUE, independent audit,
house-style A/B, the linter.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.