Did the governance loop close? Here is the daily, reproducible measurement.
This feed measures, every day, how the Phionyx self-governance runtime governs the AI that writes Phionyx itself — aggregate numbers only, reviewer-reproducible. The headline is no longer just how often the gate ran (coverage); it is whether each governed decision was signed into a tamper-evident record and confirmed by a real outcome — the L3 lifecycle. Coverage is kept below as one input, not the goal.
L3 · the lifecycle, not just the invocation
A governed decision is “complete” only when it is signed AND a real outcome confirms it — not merely when the gate ran. These three counts have different scopes — do not divide them. Per-claim completion is honestly near zero today because real outcomes accumulate over time; it is never fabricated. That honesty is the point.
every governed decision is signed + hash-chained — tamper-evident and replayable from the records alone.
Invocation discipline · rolling 30-day window (one input, not the headline)
The CLAUDE.md rule expects two gate calls per commit (verify_claim + response_gate), so coverage measures how often the gate was invoked. At L3 this is kept as one falsifier, not the goal: coverage conflates a skipped gate with a commit made outside the harness, and a gate call never proves the work is correct — which is exactly why the lifecycle above (signed record + real outcome) is the headline.
Per-day breakdown (27 days)
since 2026-05-04 17:48 UTC
| Date | Commits | Gate | All MCP | Coverage |
|---|---|---|---|---|
| 2026-06-03 | 2 | 3 | 3 | 75.0% |
| 2026-06-02 | 11 | 26 | 38 | 118.2% |
| 2026-06-01 | 3 | 11 | 14 | 183.3% |
| 2026-05-31 | 27 | 1 | 1 | 1.9% |
| 2026-05-29 | 19 | 10 | 10 | 26.3% |
| 2026-05-28 | 67 | 51 | 51 | 38.1% |
| 2026-05-27 | 24 | 36 | 36 | 75.0% |
| 2026-05-26 | 40 | 15 | 22 | 18.8% |
| 2026-05-25 | 34 | 2 | 5 | 2.9% |
| 2026-05-24 | 26 | 4 | 16 | 7.7% |
| 2026-05-23 | 27 | 0 | 0 | 0.0% |
| 2026-05-22 | 17 | 0 | 0 | 0.0% |
| 2026-05-21 | 6 | 0 | 0 | 0.0% |
| 2026-05-20 | 3 | 0 | 0 | 0.0% |
| 2026-05-19 | 18 | 0 | 0 | 0.0% |
| 2026-05-18 | 2 | 0 | 0 | 0.0% |
| 2026-05-16 | 13 | 0 | 0 | 0.0% |
| 2026-05-15 | 16 | 0 | 0 | 0.0% |
| 2026-05-13 | 1 | 0 | 0 | 0.0% |
| 2026-05-11 | 1 | 0 | 0 | 0.0% |
| 2026-05-10 | 14 | 0 | 0 | 0.0% |
| 2026-05-09 | 4 | 0 | 2 | 0.0% |
| 2026-05-08 | 10 | 0 | 0 | 0.0% |
| 2026-05-07 | 18 | 0 | 0 | 0.0% |
| 2026-05-06 | 8 | 0 | 0 | 0.0% |
| 2026-05-05 | 14 | 0 | 0 | 0.0% |
| 2026-05-04 | 7 | 0 | 0 | 0.0% |
Directive distribution
The aggregate of every directive written to telemetry across MCP tools + observability hooks — broader than the gate's five directive dispositions (pass · damp · rewrite · regenerate · reject) because non-gate tools also write entries.
auto_attest — observability hooks (session start, user prompt log, commit attestation, …). Recorded but excluded from coverage math by design.
checkpoint — emitted by phionyx_checkpoint (lightweight context-note tool, not a gate).
n/a — entries without an explicit directive field (e.g. session start, prompt log, attestation writes).
solid / weak / incomplete — emitted by phionyx_causal_trace (chain-quality verdicts, distinct from the gate's five directive dispositions).
ok — emitted by the trust-boundary MCP server on successful third-party-tool attestation writes.
Reproduce
python3 case-studies/agentic-development-2026-05/scripts/runtime_evidence_self_audit.py --days 30Same audit script lives at case-studies/.../scripts/runtime_evidence_self_audit.py. Generated 2026-06-03 14:48 UTC · schema v0.7.2 · daily refresh.