This hub gathers the intake-and-prioritization mechanics of a content-production workflow. The spine is a [first-class In Review state] (Claim_InReviewFirstClassState) (witnessed 2026-06-12): a five-state flow where claiming-complete and verified are distinct, with a single queue serving both code (staging verifies) and content (Scarlet verifies). Two operational corrections govern scoping: [scope-domain-first from reviewer-chosen TX zones] (Claim_EyeChartScoping) (Correction 5), and a [four-step large-TX scale flow] (Claim_LargeTXScale) (Correction 4) — summary, zone ID, targeted shifts, fact review — echoed by an [observation restating that same flow] (Observation_TXScaleFlow). Backlog hygiene is set by [parking ~165 stale n8n-era tasks] (Claim_StaleTasksParkedNotCancelled) rather than cancelling them (2026-06-12). A structural [observation maps interview ordering to CLAUDE.md onboarding priority] (Obs_InterviewMapsToOnboarding). The children split by attachment: supports claims fix workflow facts, while aboutNode Corrections 4 and 5 narrate how scoping decisions get made.
Witness phrases
verbatim To Do → In Progress → In Review → Done, plus Blocked
verbatim In Review = a session claims complete, nothing verified. Done = verified.
verbatim The ~165 stale n8n-era tasks get archived as parked, not cancelled
verbatim summary → zone identification → 2-4 targeted shifts in chosen zones → fact review catches the rest before merge
verbatim Scope domain first from TX zones reviewer chose
verbatim vision/mission → architecture/decisions → current priorities → team → recent decisions
verbatim Parking the ~165 stale tasks is explicitly flagged as NOT a migration decision — consistent with the deferred Clojure migration, a road deliberately left open.
verbatim One queue serves two verification regimes — code verified by staging vs content verified by Scarlet — a unified intake masking divergent done-criteria.
verbatim The scale flow appears twice with differing weight: a normative Correction (aboutNode) and a flatter restating observation (skos:broader) — same four steps, different authority.
verbatim Scoping (Correction 5) leaves room to draft from worldview when no doc fits and to negotiate when scope is too broad or narrow — an escape hatch from the zone-first default.
In this area
ClaimClaim_EyeChartScoping Correction 5: Scope domain first from TX zones reviewer chose; check for existing compilation doc; draft from worldview if none fits; negotiate scope if doc is too broad or narrow.
ClaimClaim_LargeTXScale Correction 4: Large TXs handled via TX summary → zone identification → 2-4 targeted shifts in chosen zones → fact review catches the rest before merge.
ObservationObs_InterviewMapsToOnboarding Interview question order intentionally mirrors CLAUDE.md onboarding mode priority: vision/mission → architecture/decisions → current priorities → team → recent decisions
ObservationObservation_TXScaleFlow Four-step scale management for large TXs: summary, zone ID, targeted shifts, fact review.
2 further nodes are not published in the public projection. Each node links from the entity index.