Uh oh!
There was an error while loading. Please reload this page.
docs(adr): ADR-0054 — prove-it-runs gate for the authorable surface - #2024
Merged
Conversation
Extends ADR-0049 (enforce-or-remove) with a third leg. The liveness ledger (#1919) classifies every authorable property live/experimental/dead, but "live" means only a static file:line consumer pointer — proof that something reads the property, not that authoring it produces correct runtime behavior. #2018 (tz bucketing: live at every layer, broken in integration) and the field-type fidelity gaps (#2022: rating/slider/toggle read back wrong-typed) fell through that gap — call it "unproven liveness". For a platform whose authors are AI emitting metadata across a combinatorial space the examples never cover, unproven liveness ships silently into third-party apps. ADR-0054 upgrades a `live` classification to optionally carry a `proof` — a @objectstack/dogfood test that authors the property against the real in-process stack and asserts the runtime outcome. Required as a ratchet (not a retrofit) for a high-risk authorable class on change, and for any property implicated in a shipped regression (the fix carries its proof). Generative testing is explicitly deferred (Phase 3, evidence-gated). Proposed — for architect review. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Jun 18, 2026
Merged
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extends ADR-0049 (enforce-or-remove) with a third leg: prove-it-runs.
The spec-liveness ledger (#1919) classifies every authorable property live / experimental / dead with evidence — and kills silent dead surface. But "live" today means only a static
file:lineconsumer pointer: proof that something reads the property, not that authoring it produces correct runtime behavior. That gap — call it unproven liveness — is where the recent regressions fell:rating/slider/togglereading back wrong-typed on its first run.Why it matters for this platform
ObjectStack's authors are AI emitting arbitrary metadata across a combinatorial space the curated examples never cover. When a human authors something broken they notice; when an AI is told a property is "live" and it silently misbehaves, it ships into a third-party app. So "live" must carry a stronger guarantee for the primitives most likely to break in integration.
The decision
A
liveclassification may be backed by aproof— a@objectstack/dogfoodtest that authors the property against the real in-process stack and asserts the runtime outcome. Enforced as a ratchet, not a retrofit:it.failsquarantine);Composes the three gates into one honest chain: valid (build-time guardrails) → has a consumer (liveness) → runs correctly (dogfood).
Generative property testing is explicitly deferred (Phase 3, evidence-gated) — high-ceiling, high-maintenance, doesn't lead.
Status
Proposed— for Protocol Architect review. Doc-only (docs/adr/0054-...md); no code change.