Uh oh!
There was an error while loading. Please reload this page.
docs(audits): dead-surface disposition plan (spec liveness → executable decision) - #1939
Merged
Conversation
…le decision) The spec-liveness gate now quantifies 89 dead properties across 10 governed metadata types, but the gate only measures — it doesn't decide what to do. This turns that measurement into an executable plan: for each dead property, recommend prune / wire-rename / enforce-or-prune / objectui with rationale, cost and risk, priority-ordered (P0 false-compliance → P1 naming-drift bugs → P2 aspirational-surface prune). Headline: ~64 of 89 are PRUNE candidates — aspirational enterprise config, duplicate flags, and display options with no roadmap. For a platform selling a trustworthy metadata contract, shedding false surface is the highest-leverage hygiene move (narrow-and-true). The team owns execution (spec removals, enforcement); this is the decision input. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Uh oh!
There was an error while loading. Please reload this page.
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.
Turns the spec-liveness gate's measurement into a decision. The gate now quantifies 89
deadproperties across 10 governed metadata types, but only measures — this plan decides what to do with each.What it is
For every dead property: a recommendation — prune / wire-rename / enforce-or-prune / objectui — with rationale, cost, and risk, priority-ordered:
Headline
~64 of 89 are PRUNE candidates — aspirational enterprise config (object
versioning/partitioning/cdc/recordTypes...), duplicate flags, and enhanced-type display options (fieldtheme/marks/barcode*/master-detail overrides...) with no roadmap and no consumer. For a platform whose value is a trustworthy metadata contract (open-Ontology positioning), shedding false surface is the highest-leverage hygiene move — narrow-and-true.Why a doc, not code
Spec removals and runtime enforcement are team-owned decisions. This is the decision input that unblocks the ADR-0049 spec-hygiene clusters (#3–#7). Pruning is low-risk/mechanical (spec prop + ledger removal; CI + the liveness gate catch fixtures); batchable ~2 PRs for the object+field bulk.
Linked from
docs/audits/README.md. Builds on ADR-0049.🤖 Generated with Claude Code