Harden the manifest from the fidelity-honesty findings - #389
Merged
Conversation
Acting on spec/fidelity_honesty.py's first run: - Promote the three branch-ruleset payloads (repo-config/develop.json, operational/develop.json, main.json) from intent to verbatim. The tool confirmed they are byte-identical across every carrying repo (0 divergent copies), so verbatim adds committed-file drift-detection they lacked - a hand-edited payload is now caught, not just judged by hand. (Their live rulesets are separately diffed by the audit already.) Drop the now-unused intentRef. - Add .editorconfig-checker.json to the manifest as intent - it was carried by the fleet (18/20 identical) but untracked, so it drifted unaudited (the configure.sh bug class the tool was built to catch). Intent, not verbatim, because 2 repos diverge - a verbatim candidate once those are triaged. Deferred (need judgment): the two other untracked workflows (publish-release.yml, validate-task.yml) vary widely and are not universally carried; configure.sh's true fidelity given a heavily-forked copy; and whether to promote .editorconfig-checker.json once the 2 divergences are reconciled. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the standardization manifest (spec/files.json) to reflect findings from the new fidelity-honesty analysis, increasing drift detection coverage for carried governance/config assets.
Changes:
- Adds
.editorconfig-checker.jsonto the manifest withfidelity: intentso its presence and intent-alignment are audited. - Promotes the three branch ruleset payloads (
repo-config/develop.json,repo-config/operational/develop.json,repo-config/main.json) tofidelity: verbatimwithwhole: trueto enable byte-level drift detection.
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
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.
Acting on
spec/fidelity_honesty.py's first run (merged in #387).Changes
verbatim(repo-config/develop.json,operational/develop.json,main.json). The tool confirmed they're byte-identical across every carrying repo (0 divergent copies), soverbatimadds committed-file drift-detection they lacked — a hand-edited payload is now caught, not just judged by hand. (Their live rulesets are already diffed separately by the audit.) Dropped the now-unusedintentRef..editorconfig-checker.json(intent) — carried by the fleet (18/20 identical) but absent from the manifest, so it drifted unaudited (theconfigure.shbug class).intentrather thanverbatimbecause 2 repos diverge — a verbatim candidate once those are triaged.Verification
spec/validate.pygreen;spec/audit.py --selftestpass; live audit — the promoted payloads verbatim-check clean on PlexCleaner,.editorconfig-checker.jsonpresence-checks clean, exit 0. CRLF preserved.Deferred (need your judgment)
publish-release.yml(12 divergent, 5 absent) andvalidate-task.yml(11 divergent, 9 absent) — vary widely and aren't universally carried, so their fidelity (interface vs intent) andappliesToare real decisions that'd also surface many new LETTERs.configure.sh's true fidelity given a heavily-forked copy (NxWitness ships a 196-line variant)..editorconfig-checker.jsonto verbatim once the 2 divergences (HomeAutomation-Config, HolidayLights) are reconciled.🤖 Generated with Claude Code