docs(archaeology): preserve 2026-05-26 Lemma B pivot audit + session notes#185
Merged
Merged
Conversation
…notes (archaeology banners prepended) Cherry-picked from the deleted orphan branch lemma-b-phase2-middle-narrow, which carried 14 commits dated 2026-05-26 attacking formal/Semantics.v via the now-banned Lemma B patterns (per CLAUDE.md owner directive 2026-05-27 DO-NOT #2). The Semantics.v changes are NOT cherry-picked; only the audit/session-note documentation that captures the pathway TO the counterexample. Three docs preserved, each with an archaeology banner explaining that they predate the counterexample and should NOT be applied as instructions: - docs/reports/audit/audit-2026-05-26-lemma-b-option-2-obstacle.md - docs/reports/audit/audit-2026-05-26-standards-134-reconciliation.md - docs/sessions/SESSION-2026-05-26-lemma-b-pivot.adoc Companion to #184 (the past-present-future doctrine landing). Orphan branch lemma-b-phase2-middle-narrow can now be deleted. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hyperpolymath
added a commit
that referenced
this pull request
May 27, 2026
Follow-up to #184 + #185. Aligns 5 secondary entry surfaces (EXPLAINME, TOPOLOGY, docs/vision, ephapax-linear/README, .machine_readable/META.a2ml) with the post-counterexample doctrine. ROADMAP.adoc + .gitignore + .gitattributes + wiki deferred (not blocking proof work). See commit body for per-file detail. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
🔍 Hypatia Security ScanFindings: 51 issues detected
View findings[
{
"reason": "Issue in abi-verify.yml",
"type": "unknown",
"file": "abi-verify.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in boj-build.yml",
"type": "unknown",
"file": "boj-build.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in codeql.yml",
"type": "unknown",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in governance.yml",
"type": "unknown",
"file": "governance.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in hypatia-scan.yml",
"type": "unknown",
"file": "hypatia-scan.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in instant-sync.yml",
"type": "unknown",
"file": "instant-sync.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in mirror.yml",
"type": "unknown",
"file": "mirror.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in rust-ci.yml",
"type": "unknown",
"file": "rust-ci.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in rust-ci.yml",
"type": "unknown",
"file": "rust-ci.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in scorecard-enforcer.yml",
"type": "unknown",
"file": "scorecard-enforcer.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
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.
Summary
Cherry-picked from the deleted orphan branch `lemma-b-phase2-middle-narrow`, which carried 14 commits dated 2026-05-26 attacking `formal/Semantics.v` via the now-banned Lemma B patterns (per CLAUDE.md owner directive 2026-05-27 DO-NOT #2).
Only the audit/session-note documentation is cherry-picked. The Semantics.v changes are deliberately left behind.
What lands
Each file gets a prepended archaeology banner explaining that it predates the counterexample and should NOT be applied as instructions — readers should consult `STATUS.adoc` + `formal/PRESERVATION-DESIGN.md` + `PROOF-NEEDS.md` for the current doctrine.
Companion to #184
This PR pairs with #184 (just-merged past-present-future doctrine landing). Together they complete the historical-record preservation while ensuring the post-discovery framing is what future readers and sessions land on.
After merge
Orphan branch `lemma-b-phase2-middle-narrow` will be deleted.
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com