The feature registry needs enforcement tiers visible in the UI. Right now buyers can't see that our governance is real — it looks like a slide deck claim.
Understood. Let me pull the current registry state and map enforcement tiers to visible counters. I'll verify against the live CI pipeline data before proposing anything.
Registry has 20 features tracked. Five enforcement tiers are active: Structural (file ownership), CI Gates (3 PRs blocked this week), Brue Patterns (12 scans today), Scheduled Audits (nightly at 03:00 UTC), Session Protocol (auto-verified at session open). All data is live — no stale counters.
I want to flag a concern. The "3 PRs blocked" metric is misleading without context. Two of those blocks were the same PR re-submitted after a lint fix — it's really 2 unique enforcement events, not 3. If we show inflated numbers, a technical buyer will call it out.
Good catch. Deduplicate by PR number. Show unique enforcement events, not total attempts.
Capturing that as a decision.
ADR-0089: Registry enforcement counters show unique events per PR, not total attempts. Rationale: accuracy over impressiveness. Linked to: feature-registry, brue-pipeline.
I've drafted a TaskSpec for the registry UI. Scope: add enforcement tier section to /registry page with live counters, deduped by PR. Linking to initiative: Platform Layer. Assigning to Claude Code for overnight execution. @Tuck — do we have prior art on enforcement visualization?
Yes. ADR-0067 from Session 128 defined the five-tier model. The original design doc (CMD_DESIGN_EnforcementTiers_v2) specified counters but the UI was deferred to Block 4. We're now in Block 4. The design doc is still valid — I've verified it against current schema.
Perfect. Maren, ship the spec. Claude Code picks it up tonight. I want to see the enforcement section on /registry by morning.
TaskSpec PL-0312 created. Priority P1. Night-shift eligible. Claude Code will pick it up at next poll cycle (within 15 minutes).
One more thing — the nightly audit counter should show "last run" timestamp, not just a count. If the audit hasn't run in 48 hours, that's a signal. Silent failures are the enemy of trust.
Appending to ADR-0089: enforcement counters include last-run timestamp with staleness indicator (amber >24h, red >48h). Adding to PL-0312 scope.
PL-0312 updated with staleness indicators. Claude Code will see the full scope. Anything else before I close this thread?
Ship it. Let's move to the pricing page — that's the next blocker for launch.
Opening a new thread for pricing. Pulling in the competitive analysis from Session 142 and the margin model Tuck archived last week.