From c9210f436e5d63008fb855caff80451292c14c0b Mon Sep 17 00:00:00 2001 From: Dmitrii Vasilev Date: Wed, 29 Jul 2026 21:52:46 +0700 Subject: [PATCH] docs: mark three archived issue bodies as superseded on hardware status 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 --- docs/issues-archive/bodies/p2-self-heal.md | 16 ++++++++++++++++ docs/issues-archive/bodies/p2-shared-uplink.md | 13 +++++++++++++ docs/issues-archive/bodies/tri-net-skill.md | 13 +++++++++++++ 3 files changed, 42 insertions(+) diff --git a/docs/issues-archive/bodies/p2-self-heal.md b/docs/issues-archive/bodies/p2-self-heal.md index b6abad65..340a3d62 100644 --- a/docs/issues-archive/bodies/p2-self-heal.md +++ b/docs/issues-archive/bodies/p2-self-heal.md @@ -1,3 +1,19 @@ +> **Archived issue body. Point-in-time record, not current status.** +> +> Written before milestone M1 ran on hardware. Two statements below are superseded: +> +> - the crypto core has since run on-device, twice, with RC=0 and recorded binary +> hashes - see [`smoke/M1_RESULTS.md`](../../../smoke/M1_RESULTS.md), runs dated +> 2026-07-01 and 2026-07-04; +> - `gHashTag/trios-mesh` now exists as a repository. +> +> Current status is the table in the repository [`README.md`](../../../README.md). +> The body text below is preserved unedited so the record of what was believed at +> the time stays intact. + +> Still accurate as written: the M5 self-healing convergence threshold remains +> undefined, and no self-healing re-route has been observed on hardware. + ## 🎯 Goal Kill one radio link (or power off one relay node) in the 3-node triangle and prove the ETX metric re-routes traffic around the failure so internet service continues on the surviving nodes — with a recorded, measurable convergence-time pass/fail threshold. **This is the go/no-go DEMO GATE.** diff --git a/docs/issues-archive/bodies/p2-shared-uplink.md b/docs/issues-archive/bodies/p2-shared-uplink.md index 808cf900..fdbc7f02 100644 --- a/docs/issues-archive/bodies/p2-shared-uplink.md +++ b/docs/issues-archive/bodies/p2-shared-uplink.md @@ -1,3 +1,16 @@ +> **Archived issue body. Point-in-time record, not current status.** +> +> Written before milestone M1 ran on hardware. Two statements below are superseded: +> +> - the crypto core has since run on-device, twice, with RC=0 and recorded binary +> hashes - see [`smoke/M1_RESULTS.md`](../../../smoke/M1_RESULTS.md), runs dated +> 2026-07-01 and 2026-07-04; +> - `gHashTag/trios-mesh` now exists as a repository. +> +> Current status is the table in the repository [`README.md`](../../../README.md). +> The body text below is preserved unedited so the record of what was believed at +> the time stays intact. + ## Goal Route ONE physical uplink's internet (4G or Starlink Mini) across a 3-node mesh triangle so a node with **no** direct uplink reaches the public internet over 2 mesh hops — the "Starlink without satellites" service MVP. diff --git a/docs/issues-archive/bodies/tri-net-skill.md b/docs/issues-archive/bodies/tri-net-skill.md index 83799337..121a3f75 100644 --- a/docs/issues-archive/bodies/tri-net-skill.md +++ b/docs/issues-archive/bodies/tri-net-skill.md @@ -1,3 +1,16 @@ +> **Archived issue body. Point-in-time record, not current status.** +> +> Written before milestone M1 ran on hardware. Two statements below are superseded: +> +> - the crypto core has since run on-device, twice, with RC=0 and recorded binary +> hashes - see [`smoke/M1_RESULTS.md`](../../../smoke/M1_RESULTS.md), runs dated +> 2026-07-01 and 2026-07-04; +> - `gHashTag/trios-mesh` now exists as a repository. +> +> Current status is the table in the repository [`README.md`](../../../README.md). +> The body text below is preserved unedited so the record of what was believed at +> the time stays intact. + ## Goal Create an on-disk `tri-net` Claude skill under `trinity/.claude/skills/tri-net/` that captures the honest Phase-0 status of the TRI-NET drone-mesh track (both boards now physically connected), with `-sim` markers on every unverified claim.