Repository navigation
docs(adr): ADR-0060 — Conformance Ledger as a Platform Pattern - #2103
Merged
Merged
Conversation
The platform has hand-written the same conformance ledger twice (ADR-0056 D10 authz matrix + ADR-0058 D7 expression surface) to defend against the declared-but-unenforced failure class (#1887). Promote it to a reusable pattern: one ledger model + assertLedger CI helper (in @objectstack/verify), the two existing instances refactored onto it, and a third for the object validation-rule surface (pinning the ADR-0020 state_machine enforcement). A declaration surface is "landed" iff it has a conformance ledger whose ratchet is green. Decision-only; implementation follows P1–P3. 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 21, 2026
Merged
os-zhuang
added a commit
that referenced
this pull request
Jun 30, 2026
…s) (#2471) Pins the vendored @objectstack/console to objectui d23d6ebfa so the served console includes the kind:'react' renderer + the full HTML tag set for kind:'html' (objectui #2105). Carries two small list inline-edit toggles (#2102/#2103) since the previous pin. Activates the CRM Workbench showcase page (ADR-0081) in the real serving path. Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This branch was successfully deployed
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Promotes the conformance-ledger discipline from a hand-written habit to a reusable platform pattern.
Why
We've now written the same ledger twice — ADR-0056 D10 (authz matrix) and ADR-0058 D7 (expression surface) — both defending against the declared-but-unenforced failure class: a property that's authorable but the runtime never wires, so it silently does nothing (#1887). AI authorship amplifies this — LLMs produce config that looks complete and don't notice nothing reads it. Two near-identical instances is the signal to standardize.
Decision (decision-only PR)
ConformanceRowmodel +assertLedgerCI helper (unique ids / valid state / enforced-has-site / proof-exists / ratchet: discover the real surface from source, fail if any is unclassified).state_machine/cross_field/script/…) — pins the ADR-0020state_machineenforcement into CI; a new rule type with no enforcement becomes a build break.@objectstack/verify(static complement to its runtime harness).Phasing
P1 model + unify the two · P2 validation-rule ledger · P3 the "landed" bar + extend to next surfaces.
Non-goal: no runtime-semantics change; purely the conformance/verification layer.
🤖 Generated with Claude Code