The engine opened this item itself — you didn't create it.
What this is. A conformance audit of the build against the locked engine-planning design confirmed the divergences below (re-verified against current main) and grouped them into one build-session-sized unit for the surfaces-tools subsystem.
Several of the engine's promised enforcement legs are built and fixture-tested but never fire in a real session because nothing wires them into a live lifecycle. The contract-threshold soft-warn and triage-pressure boot lines have compute loops and renderers but no production caller and no rate producer, so the tunable values govern nothing live. The agents dangling-lens coherence finding has no detector (frozen behind 'slice 24'), and the roster derivation is worded at pack granularity rather than the spec'd role/lens-frontmatter query, so a standalone operator- or module-authored persona is not admitted or checked. The interface single-active/conformance coherence leg is a pure fixture-tested function with no live caller, while its agent/skill siblings were wired post-install. The hard-fail floors still hold so the trust floor is intact, but these dormant soft/coherence legs are parked behind milestones (several already completed), which principles.md sec20 forbids. A build session gives each leg a live consumer -- telemetry producers + boot renderers wired into the session lifecycle, a registered dangling-lens coherence finding at the plan gate, and a registered interface-coherence check mirroring agent/skill-coherence -- and refreshes the stale 'later slice' comments. Not tracked by any open issue.
Findings in this unit:
-
U02: add contract-creation-rate and triage-pressure producers to telemetry, and wire telemetry.run + the two boot-line renderers into the boot/build-session lifecycle so the thresholds drive a live next-boot signal
-
U04: add the consumed-lens set + a coherence finding that fires when an installed lens dangles (disclosed at the plan gate), reword the runbook derivation to the role-frontmatter query, and refresh the stale validate.py comments (log a resolved-by-construction disposition if that is the intent)
-
U09: register an interface-coherence check (mirroring agent-coherence.json / skill-coherence.json) that runs interface_resolution_findings post-install (a no-op over the empty v1 set) and refresh the stale 'later slice' docstring
-
Spec authority: systems/surfaces/policies/README.md L33-43, L79-90 (contract-threshold soft-warn; triage-threshold pressure line at next boot); telemetry/README.md L61, L70-78 (contract-creation-rate and triage-pressure named streams; next-boot orientation renders one line); systems/surfaces/agents/README.md:90-100, 114-120 (roster derived by role/lens frontmatter; an installed review agent whose lens nothing consumes is a coherence finding at the plan gate); ratified by D-057, D-066, D-073; systems/surfaces/interfaces/README.md L48-56, 82-90 (single-active resolution + conformance confirmed by the coherence check-kind, RUN POST-INSTALL); D-064 clause (2); principles.md sec20 (no under-build behind a milestone)
-
Quality attributes: Auditability, Composability, Trustworthiness-for-a-non-engineer
What happens next. A single build session should resolve every item in the checklist above, each fixed to full spec capability (principles §20). The engine opened this item for your review; nothing merges without the protected-branch gate.
More detail.
The engine opened this item itself — you didn't create it.
What this is. A conformance audit of the build against the locked engine-planning design confirmed the divergences below (re-verified against current
main) and grouped them into one build-session-sized unit for the surfaces-tools subsystem.Several of the engine's promised enforcement legs are built and fixture-tested but never fire in a real session because nothing wires them into a live lifecycle. The contract-threshold soft-warn and triage-pressure boot lines have compute loops and renderers but no production caller and no rate producer, so the tunable values govern nothing live. The agents dangling-lens coherence finding has no detector (frozen behind 'slice 24'), and the roster derivation is worded at pack granularity rather than the spec'd role/lens-frontmatter query, so a standalone operator- or module-authored persona is not admitted or checked. The interface single-active/conformance coherence leg is a pure fixture-tested function with no live caller, while its agent/skill siblings were wired post-install. The hard-fail floors still hold so the trust floor is intact, but these dormant soft/coherence legs are parked behind milestones (several already completed), which principles.md sec20 forbids. A build session gives each leg a live consumer -- telemetry producers + boot renderers wired into the session lifecycle, a registered dangling-lens coherence finding at the plan gate, and a registered interface-coherence check mirroring agent/skill-coherence -- and refreshes the stale 'later slice' comments. Not tracked by any open issue.
Findings in this unit:
U02: add contract-creation-rate and triage-pressure producers to telemetry, and wire telemetry.run + the two boot-line renderers into the boot/build-session lifecycle so the thresholds drive a live next-boot signal
U04: add the consumed-lens set + a coherence finding that fires when an installed lens dangles (disclosed at the plan gate), reword the runbook derivation to the role-frontmatter query, and refresh the stale validate.py comments (log a resolved-by-construction disposition if that is the intent)
U09: register an interface-coherence check (mirroring agent-coherence.json / skill-coherence.json) that runs interface_resolution_findings post-install (a no-op over the empty v1 set) and refresh the stale 'later slice' docstring
Spec authority: systems/surfaces/policies/README.md L33-43, L79-90 (contract-threshold soft-warn; triage-threshold pressure line at next boot); telemetry/README.md L61, L70-78 (contract-creation-rate and triage-pressure named streams; next-boot orientation renders one line); systems/surfaces/agents/README.md:90-100, 114-120 (roster derived by role/lens frontmatter; an installed review agent whose lens nothing consumes is a coherence finding at the plan gate); ratified by D-057, D-066, D-073; systems/surfaces/interfaces/README.md L48-56, 82-90 (single-active resolution + conformance confirmed by the coherence check-kind, RUN POST-INSTALL); D-064 clause (2); principles.md sec20 (no under-build behind a milestone)
Quality attributes: Auditability, Composability, Trustworthiness-for-a-non-engineer
What happens next. A single build session should resolve every item in the checklist above, each fixed to full spec capability (principles §20). The engine opened this item for your review; nothing merges without the protected-branch gate.
More detail.