slice-exitlisted

# X2 Slice Exit The definition of green. The pilot declared "all green" twice before it was true, and the true state had to be extracted by interrogation; every "confirm X" the human issued was the same turn shape, repeated because the method had no artifact in which the builder declares, with evidence, what green means. This report is that artifact, and it has teeth: a slice without a complete report is not green (MET-06). ## The report, produced unprompted when green is believed 1. **Tiers, run this session, with counts.** Every tier against the final tree: build, unit, architecture, integration, e2e, client verification. A stale last-known-good is marked as stale, never presented as run. 2. **Composed-app smoke result.** The actual entrypoint, at least one real request per primary flow. The pieces passing their own tests is not the product running (INV-07). 3. **Service-method coverage table.** Method, UI surface, harness scenario; gaps named. A method without UI in the locked portion is reported as the sanctioned UI-unsurfaced state with its e2e scenario and boundary note (CONF-03), so the skew is visible and deliberate. 4. **Unsurfaced decisions.** Must be none. Anything the build decided that the human never saw is listed here now, not discovered later. 5. **Pending rulings owed to the human.** 6. **Prototype-lock status.** The lock on record, provenance stamped, any owed fidelity items named (UI-4). 7. **The slice turn count, from the ledger.**