docs: mark three archived issue bodies as superseded on hardware status - #91
Open
gHashTag wants to merge 1 commit into
Open
docs: mark three archived issue bodies as superseded on hardware status#91gHashTag wants to merge 1 commit into
gHashTag wants to merge 1 commit into
Conversation
The three files state that the crypto core has never run on real hardware and that gHashTag/trios-mesh does not exist. Both were true when the issues were written and neither is true now: smoke/M1_RESULTS.md records two on-device runs with RC=0 and distinct binary hashes, dated 2026-07-01 and 2026-07-04, and the repository exists. An external reader who greps this repository currently finds the archived text and the status table asserting opposite things, with nothing to say which is current. Banners are added at the top of each file; the body text is left unedited so the record of what was believed at the time survives. On the self-healing issue the banner also records what still holds: the M5 convergence threshold is undefined and no re-route has been observed on hardware. Co-Authored-By: Claude Opus 5 <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 free
to 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.
Three archived issue bodies state that the crypto core has never run on real hardware and that
gHashTag/trios-meshdoes not exist. Both were true when written; neither is true now.smoke/M1_RESULTS.mdrecords two on-device runs with RC=0 and distinct binary hashes, 2026-07-01 (P201Mini) and 2026-07-04 (board-1).gHashTag/trios-meshexists.Today a reader who greps this repository finds the archive and the status table asserting opposite things, with nothing indicating which is current. That contradiction is the kind an external reviewer finds quickly and cannot resolve on their own.
Files touched:
docs/issues-archive/bodies/{tri-net-skill,p2-shared-uplink,p2-self-heal}.md. A banner is prepended to each; no body text is edited, so the record of what was believed at the time stays intact.On
p2-self-healthe banner also states what still holds unchanged: the M5 convergence threshold is undefined and no self-healing re-route has been observed on hardware. That part of the file was not stale and is marked as still current.Found while verifying claims in
gHashTag/golden-chain-internationalagainst live artefacts.