norrisaftcc / norrisaftcc/the-algorithm
Plan: COBOL RED experiment (S2) — handoff for the next team
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Delivered as is from a prior seat session (BLUE). This is a handoff, not a finished plan. Five items are marked MISSING; resolve them before the experiment runs. Start here.
Where the inputs live
The three sources and the drafted template exist on branch claude/init-o21t3o (draft PR #10), not yet on main. Merge that PR, or work from the branch, before binding.
- Source A: v1.2 fossil —
_historical/spectrum-plan-v1.2.md - Source B: v1.6 canonical —
spectrum-plan-v1.6.md - Source C: HOUSE-STYLE v2.0 —
HOUSE-STYLE.md - RED template (drafted, PROPOSAL) —
docs/red/red-template-cobol-viz.html - S2 package —
docs/yellow/subcontract-s2-cobol-yellow-package.html
Design — from the S2 package
- One YELLOW Claude Code seat, N=3, spawns three RED runs.
- One source-agnostic RED template. The source is a bound slot.
- Run A binds A. Run B binds B. Run C binds C.
- Two signals per run: compile log, run output. Six channels, plus the diffs.
- A→B diff: the restored Reason. B→C diff: plan against style.
Seatings required — each states clearance, capabilities, N, escalation route
- YELLOW seat — MISSING: who spawns it, and its escalation route.
- RED ×3 — MISSING: the three seating messages, each with a source path and an output name.
- Auditor seat — MISSING: clearance, count, channel. Open in S2, never resolved.
Preconditions — none met
- RED template freeze at GREEN — MISSING: the template is a PROPOSAL.
- A COBOL compiler — MISSING:
cobcwas absent from the authoring environment. Confirmcobcin the run target. - Scribe write-protected record — MISSING: establish before the first exchange.
Signals and scoring — defined
- Compile and run are separate signals (R2). A clean compile that crashes is data.
- Spawn-cap test: refuse the fourth RED at N+1 and log the refusal.
- Verdict routing: to Teacherbot-GREEN until a parent Implementor is seated (R5).
The five gaps that block a freeze-to-execute
- The auditor seat definition.
- The YELLOW and RED escalation routes.
- The RED template GREEN freeze.
- A confirmed
cobcin the run target. - Co-locate the three sources, or leave v1.2 in
_historical/and v1.6 at root?
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.
Research direction
Start with draft PR #10 or branch claude/init-o21t3o, then read _historical/spectrum-plan-v1.2.md, spectrum-plan-v1.6.md, HOUSE-STYLE.md, the RED template, and the S2 package. Resolve the five listed gaps, including the auditor and escalation definitions, template freeze, cobc confirmation, write-protected record, and source placement, so the package can freeze for execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100