cia

Topics in the source

• SKILL: cia — Code Integrity Auditor
• 0. Skill Identity and Routing — HARD RULES
• 0.1 Canonical Identity
• 0.2 Explicit Invocation Is Exclusive
• 0.3 Pre-Launch Trigger Words — Universal, Commerce-Aware
• 0.4 Commerce Boundary
• 0.5 Project Runtime Discovery (bootstrap on invocation)
• 0.6 Pre-Launch Integrity Audit Protocol (canonical for any project)

A universal audit skill for software codebases. Its primary target is cross-boundary invariant violations — integration-level, emergent defects where every function is individually correct and the defect lives in the channel between two of them. The theory is Stafford Beer's Viable System Model; the method is a map of the codebase onto Systems 1–5 and then twenty-four sweeps along that map's channels; the standard is that nothing dies silently. This file holds routing, discovery, the six-step protocol, the autonomy contract, the sweep index, escalation and the reference index. The doctrine itself lives in references/ and is loaded per the table in §0.13 — read those files in full when the protocol reaches them; they are the audit, this file is the runbook. What the audit prioritises, in any domain. Every priority rule below — S15 first when time is short, the tier matrices, build mode, every grading that says "primary path" — keys on the system's primary quantity, the state the system exists to get right, and on irreversibility and blast radius. Examples, in no order of importance: the scene or document an editor or 3D tool holds and saves, the claim on a job in a runner, the rows

This is an excerpt. Refer to the complete source and its current requirements.