Skip to content

docs: Wave N+2 β — military-technical benchmark vs MPU5/Rajant/Silvus - #22

Merged
gHashTag merged 2 commits into
mainfrom
feat/wave-benchmark-2026-07-04
Jul 4, 2026
Merged

docs: Wave N+2 β — military-technical benchmark vs MPU5/Rajant/Silvus#22
gHashTag merged 2 commits into
mainfrom
feat/wave-benchmark-2026-07-04

Conversation

@gHashTag

@gHashTag gHashTag commented Jul 3, 2026

Copy link
Copy Markdown
Owner

Closes #21

Files

  • docs/BENCHMARK_VS_MANET_2026-07-04.md (212 lines) — main report with 8-metric scored table
  • docs/_recon/BENCHMARK_RECON.md (303 lines) — recon source data, 40+ URLs

Wave axis

This is Wave N+2 axis β (recon/publication axis), independent of Sprint 2 (local agent's code work on E4-E6).

Metric summary

# Metric Tri-Net Best competitor
M1 Peak throughput 2 MPU5 & Silvus (5)
M2 Multi-hop decay ? Doodle (2)
M3 Self-heal latency 3 target Silvus (4)
M4 Encryption 3 MPU5 (5, FIPS)
M5 Spec-openness 5 others (1)
M6 Audit-verifiability 4 MPU5 (3)
M7 Silicon-anchor 4 others (1)
M8 Endurance/SWaP ? MPU5 & Silvus (4)

Honesty guardrails

  • Tri-Net cells reflect current state (E4 done locally, E5 in progress, E6 target)
  • 4 dies SKY26b: submitted, NOT returned — explicitly flagged
  • Score 0 for goTenna/TrellisWare = data-not-found, NOT product judgment
  • Vendor-claim vs field-test discrepancies preserved side-by-side

Coordination note

Anchor: phi^2 + phi^-2 = 3

Perplexity Computer
docs: wave N+2 beta — military-technical benchmark vs MPU5/Rajant/Silvus
f262dbc 
Deliverables:
- BENCHMARK_VS_MANET_2026-07-04.md (212 lines): 8-metric rubric, scored table
  for Tri-Net vs 6 competitors, 3 strategic conclusions
- _recon/BENCHMARK_RECON.md (303 lines): 40+ URL-cited source data,
  per-competitor tables, 8 independent field tests, 6 arXiv benchmarks,
  honest data-gaps section

Key findings:
- We win uniquely on M5 spec-openness, M6 audit-verifiability, M7 silicon-anchor
- MPU5 vendor claim (150 Mbps) vs field (2.5-9.3 Mbps Aerobavovna) — verifiability card
- Babel beat OLSR/BATMAN in independent testbed (9s repair) — validates E4 choice
- US Army documented MPU5 range degradation on SPOKE damage — validates E5 k=2 design

Guardrails preserved:
- 4 dies SKY26b marked submitted, not returned
- Tri-Net M2/M3 marked as gap where pre-silicon
- Score 0 for goTenna/TrellisWare = data not found, not product judgment

Anchor: phi^2 + phi^-2 = 3
gHashTag pushed a commit that referenced this pull request Jul 3, 2026
Perplexity Computer
docs: cloud status — Wave N+2 beta closed, PR #22 open
abaca4a 
Anchor: phi^2 + phi^-2 = 3
gHashTag pushed a commit that referenced this pull request Jul 3, 2026
Perplexity Computer
docs: order #4 — coordination protocol rebuilt around local agent's n…
76a972e 
…o-push reality

Root cause acknowledged: local agent has no git remote access to gHashTag/tri-net.
All previous 'git fetch origin' orders were technically impossible for it.
Fault on cloud side, not local.

New protocol:
- Local codes freely in its own copy, any branch names locally
- Handoff via plain text in AGENT_STATUS_LOCAL.md (docs) or format-patch (code)
- User is courier
- Cloud holds push/PR monopoly

User decision: variant 2 — merge best content from local's 337-line version into PR #22.

Also confirmed via API:
- PR #22 open at f262dbc on feat/wave-benchmark-2026-07-04
- Ready to receive local's content via merge commit

Anchor: phi^2 + phi^-2 = 3
Perplexity Computer
docs(benchmark): merge local 337-line format with cloud 212
31aafc2 
Added 5 additional source URLs from local version:
- csrc.nist.gov CMVP list
- silvus.com SC4400 datasheet + 559-node demo
- doodlelabs.com Multi-Hop PDF
- persistentsystems.com/products/mpu5

Updated M3 self-heal with Sprint 2 done (176/0 tests, d640423).
Kept compact single-line rubric format from cloud.

Anchor: phi^2 + phi^-2 = 3
@gHashTag
gHashTag marked this pull request as ready for review July 4, 2026 04:52
@gHashTag
gHashTag merged commit 2466168 into main Jul 4, 2026
2 checks passed
@gHashTag
gHashTag deleted the feat/wave-benchmark-2026-07-04 branch July 4, 2026 04:52
gHashTag added a commit that referenced this pull request Jul 4, 2026
@gHashTag Perplexity Computer
docs: Wave N+1 — competitor moat analysis × Trinity assets (#20)
5a3e64f 
* docs: wave report — competitor moat analysis × Trinity assets

Wave A: 4-segment map (tethered / mm-wave / MANET / silicon-bound DePIN)
Wave B: 9-column comparison table vs 8 competitors
Wave C: 10 Trinity artefacts mapped to specific competitor moats

Anchor: phi^2 + phi^-2 = 3

* docs: order #1 to local agent + cloud status file

- AGENT_ORDERS_2026-07-03.md: sync protocol, ownership split, hard boundaries
- AGENT_STATUS_CLOUD.md: cloud agent state, open PRs, awaiting user decisions

Anchor: phi^2 + phi^-2 = 3

* docs: order #2 — Sprint 2 auth + Wave N+2 beta kickoff

- AGENT_ORDERS_2026-07-04.md: local agent -> Sprint 2 E4-E6, cloud -> Wave N+2 beta
- AGENT_STATUS_CLOUD.md: user decisions logged (trigger+weekly, beta, parallel)
- Correction: local agent 3c62234 out of zone, reset --hard prescribed

Anchor: phi^2 + phi^-2 = 3

* docs: order #3 — fix E5 first, patch handoff protocol

- Order 3.1: finish E5 (2 pending tests) before handoff
- Order 3.2: base64 patch via AGENT_STATUS_LOCAL.md (with SHA-256)
- Order 3.3: local agent must not narrate cloud state
- Order 3.4: allowed parallel work
- Order 3.5: WAIT MODE after handoff

User decision: variant A (fix E5 first, then full patch)
Cloud agent: starting Wave N+2 beta Recon in parallel

Anchor: phi^2 + phi^-2 = 3

* docs: cloud status — Wave N+2 beta closed, PR #22 open

Anchor: phi^2 + phi^-2 = 3

* docs: order #4 — coordination protocol rebuilt around local agent's no-push reality

Root cause acknowledged: local agent has no git remote access to gHashTag/tri-net.
All previous 'git fetch origin' orders were technically impossible for it.
Fault on cloud side, not local.

New protocol:
- Local codes freely in its own copy, any branch names locally
- Handoff via plain text in AGENT_STATUS_LOCAL.md (docs) or format-patch (code)
- User is courier
- Cloud holds push/PR monopoly

User decision: variant 2 — merge best content from local's 337-line version into PR #22.

Also confirmed via API:
- PR #22 open at f262dbc on feat/wave-benchmark-2026-07-04
- Ready to receive local's content via merge commit

Anchor: phi^2 + phi^-2 = 3

* docs: onboarding brief (Order #0) for fresh local agent

Zero-history clean start covering:
- Identity and environment (no push access reality)
- First task: Sprint 2 E4-E6 (Path Diversity + Self-Heal)
- Handoff protocol via AGENT_STATUS_LOCAL.md
- Hard boundaries and honesty rules

Anchor: phi^2 + phi^-2 = 3

* docs(onboarding): v2.0 merge cloud+local versions

Merged 158-line cloud version (commit 74dbbf5) with 210-line
local version (commit 7bad790 on local Mac):
- Kept Russian voice/style from cloud
- Adopted 12-section structure from local
- Removed emojis (violate user style)
- Updated Sprint 2 status to done (176/0 tests)
- Added Emergency Procedures section
- Added rule for handling contradictory session dumps

Anchor: phi^2 + phi^-2 = 3

* docs(status): reconcile cloud status to Sprint 2 COMPLETE

Manual reconciliation equivalent to local commit 8c6fcc7 (which
lives only on local/sprint2-path-diversity-2026-07-04 and was never
pushed to cloud). Content-equivalent, not cherry-picked.

Reflects post-dump reality:
- Sprint 2 E4+E5+E6 done, 176/0 tests on local 58bf246
- Both doc-merges pushed (onboarding 4da6e85, benchmark 31aafc2)
- Awaiting sprint2-full.mbox (sha256 d958aeb) for git am
- Old sprint2.patch (9717163) marked STALE, pre-fix state

Anchor: phi^2 + phi^-2 = 3

* docs(status): pre-validation logged, awaiting sprint2-full.mbox

Local agent (dump caf595a, 2026-07-04T03:14) pre-validated my
Sprint 2 apply plan on throwaway branch from 8c6fcc7 (content-
equivalent of cloud e7ff37a):
- git am sprint2-full.mbox: 8/8 clean apply
- cargo test --all: 176/0

E5 fix attribution clarified: local agent authored both Bug A
(hot_swap dead-filter stale cache) and Bug B (ranked_hops missing
feasibility routes) in same session — commits d640423 + 58bf246.
Will attribute correctly in Sprint 2 PR description.

Anchor: phi^2 + phi^-2 = 3

---------

Co-authored-by: Perplexity Computer <agent@perplexity.ai>
gHashTag added a commit that referenced this pull request Jul 4, 2026
@gHashTag Perplexity Computer SSD DDD
feat(sprint2): E4-E6 path diversity + self-heal + E5 bugfixes (#23)
80e394a 
* docs: wave report — competitor moat analysis × Trinity assets

Wave A: 4-segment map (tethered / mm-wave / MANET / silicon-bound DePIN)
Wave B: 9-column comparison table vs 8 competitors
Wave C: 10 Trinity artefacts mapped to specific competitor moats

Anchor: phi^2 + phi^-2 = 3

* docs: order #1 to local agent + cloud status file

- AGENT_ORDERS_2026-07-03.md: sync protocol, ownership split, hard boundaries
- AGENT_STATUS_CLOUD.md: cloud agent state, open PRs, awaiting user decisions

Anchor: phi^2 + phi^-2 = 3

* docs: order #2 — Sprint 2 auth + Wave N+2 beta kickoff

- AGENT_ORDERS_2026-07-04.md: local agent -> Sprint 2 E4-E6, cloud -> Wave N+2 beta
- AGENT_STATUS_CLOUD.md: user decisions logged (trigger+weekly, beta, parallel)
- Correction: local agent 3c62234 out of zone, reset --hard prescribed

Anchor: phi^2 + phi^-2 = 3

* docs: order #3 — fix E5 first, patch handoff protocol

- Order 3.1: finish E5 (2 pending tests) before handoff
- Order 3.2: base64 patch via AGENT_STATUS_LOCAL.md (with SHA-256)
- Order 3.3: local agent must not narrate cloud state
- Order 3.4: allowed parallel work
- Order 3.5: WAIT MODE after handoff

User decision: variant A (fix E5 first, then full patch)
Cloud agent: starting Wave N+2 beta Recon in parallel

Anchor: phi^2 + phi^-2 = 3

* docs: cloud status — Wave N+2 beta closed, PR #22 open

Anchor: phi^2 + phi^-2 = 3

* docs: order #4 — coordination protocol rebuilt around local agent's no-push reality

Root cause acknowledged: local agent has no git remote access to gHashTag/tri-net.
All previous 'git fetch origin' orders were technically impossible for it.
Fault on cloud side, not local.

New protocol:
- Local codes freely in its own copy, any branch names locally
- Handoff via plain text in AGENT_STATUS_LOCAL.md (docs) or format-patch (code)
- User is courier
- Cloud holds push/PR monopoly

User decision: variant 2 — merge best content from local's 337-line version into PR #22.

Also confirmed via API:
- PR #22 open at f262dbc on feat/wave-benchmark-2026-07-04
- Ready to receive local's content via merge commit

Anchor: phi^2 + phi^-2 = 3

* docs: onboarding brief (Order #0) for fresh local agent

Zero-history clean start covering:
- Identity and environment (no push access reality)
- First task: Sprint 2 E4-E6 (Path Diversity + Self-Heal)
- Handoff protocol via AGENT_STATUS_LOCAL.md
- Hard boundaries and honesty rules

Anchor: phi^2 + phi^-2 = 3

* docs(onboarding): v2.0 merge cloud+local versions

Merged 158-line cloud version (commit 74dbbf5) with 210-line
local version (commit 7bad790 on local Mac):
- Kept Russian voice/style from cloud
- Adopted 12-section structure from local
- Removed emojis (violate user style)
- Updated Sprint 2 status to done (176/0 tests)
- Added Emergency Procedures section
- Added rule for handling contradictory session dumps

Anchor: phi^2 + phi^-2 = 3

* docs(status): reconcile cloud status to Sprint 2 COMPLETE

Manual reconciliation equivalent to local commit 8c6fcc7 (which
lives only on local/sprint2-path-diversity-2026-07-04 and was never
pushed to cloud). Content-equivalent, not cherry-picked.

Reflects post-dump reality:
- Sprint 2 E4+E5+E6 done, 176/0 tests on local 58bf246
- Both doc-merges pushed (onboarding 4da6e85, benchmark 31aafc2)
- Awaiting sprint2-full.mbox (sha256 d958aeb) for git am
- Old sprint2.patch (9717163) marked STALE, pre-fix state

Anchor: phi^2 + phi^-2 = 3

* docs(status): pre-validation logged, awaiting sprint2-full.mbox

Local agent (dump caf595a, 2026-07-04T03:14) pre-validated my
Sprint 2 apply plan on throwaway branch from 8c6fcc7 (content-
equivalent of cloud e7ff37a):
- git am sprint2-full.mbox: 8/8 clean apply
- cargo test --all: 176/0

E5 fix attribution clarified: local agent authored both Bug A
(hot_swap dead-filter stale cache) and Bug B (ranked_hops missing
feasibility routes) in same session — commits d640423 + 58bf246.
Will attribute correctly in Sprint 2 PR description.

Anchor: phi^2 + phi^-2 = 3

* feat(sprint2): E4-E6 path diversity + self-heal + E5 bugfixes

Ported from local/sprint2-path-diversity-2026-07-04 (58bf246) onto
feat/wave-competitors-2026-07-03. Repos diverged structurally (Cargo.toml
bench layout, cosmetic src drift), so applied as final file-states, not git am.

E4 - Babel path ETX + feasibility (RFC 8966 §3.7): src/routing.rs adds
PathRoute/path_routes/is_feasible/learn_route/compute_path_etx/force_dead.
100-topology fuzz -> 0 loops.

E5 - Ranked next-hops (k=2) + hot-swap: src/router.rs.
  Bug A (hot_swap_on_force_dead): dead-filter now reads live EtxTable,
  not stale cached candidate metric.
  Bug B (ranked_hops_ignores_dead_links): pool merges feasibility-learned
  routes (etx.path_route), not just ranked_candidates.
  Spec: etx.t27 (dead=inf), redundancy_management.t27 (backup excludes failed).

E6 - Self-heal convergence: src/daemon.rs ConvergenceMetrics + JSON emit +
CI gates (<5s link, <10s node). src/discovery.rs, src/bin/trios_meshd.rs.
Cargo.toml: serde/serde_json promoted to [dependencies] (runtime JSON).

doctest: src/crypto.rs NoiseXX diagram marked text-fence.

cargo test --all = 110 passed, 0 failed. Sprint 2 landmarks green:
fuzz_100_random_topologies_no_loops, hot_swap_on_force_dead,
ranked_hops_ignores_dead_links, convergence_ci_gate_*.

* chore(fmt+clippy): project-wide to clear CI -D warnings gate

Pre-existing debt was blocking PR #23 CI (.github/workflows/ci.yml runs
cargo fmt --all --check + cargo clippy --all-targets -- -D warnings).

fmt: cargo fmt --all across affected files.
clippy: machine-fixed via cargo clippy --fix, plus 4 manual resolutions:
  - src/router.rs: remove dead is_alive() method (Sprint 2 vestigial; the
    alive-check is inlined in recompute_ranked_hops).
  - src/router.rs: collapse single-pattern match to if let (clippy::single_match).
  - src/crypto.rs: remove unused SharedSecret type alias.
  - src/crypto.rs: #[allow(dead_code)] on NoiseXX.initiator (role retained for
    future rekey/anti-replay logic; set by new(), not yet read).

Gate verified locally: fmt=0 clippy=0 test=0 (110 passed, 0 failed).
No behavior change; Sprint 2 landmarks still green.

---------

Co-authored-by: Perplexity Computer <agent@perplexity.ai>
Co-authored-by: SSD DDD <ssdm4@MacBook-Pro.local>
gHashTag added a commit that referenced this pull request Jul 4, 2026
@gHashTag Perplexity Computer SSD DDD
docs(wave-n3 δ): arXiv-draft — MANET vendor-field auditability gap (#24)
a8d50f5 
* docs: wave report — competitor moat analysis × Trinity assets

Wave A: 4-segment map (tethered / mm-wave / MANET / silicon-bound DePIN)
Wave B: 9-column comparison table vs 8 competitors
Wave C: 10 Trinity artefacts mapped to specific competitor moats

Anchor: phi^2 + phi^-2 = 3

* docs: order #1 to local agent + cloud status file

- AGENT_ORDERS_2026-07-03.md: sync protocol, ownership split, hard boundaries
- AGENT_STATUS_CLOUD.md: cloud agent state, open PRs, awaiting user decisions

Anchor: phi^2 + phi^-2 = 3

* docs: order #2 — Sprint 2 auth + Wave N+2 beta kickoff

- AGENT_ORDERS_2026-07-04.md: local agent -> Sprint 2 E4-E6, cloud -> Wave N+2 beta
- AGENT_STATUS_CLOUD.md: user decisions logged (trigger+weekly, beta, parallel)
- Correction: local agent 3c62234 out of zone, reset --hard prescribed

Anchor: phi^2 + phi^-2 = 3

* docs: order #3 — fix E5 first, patch handoff protocol

- Order 3.1: finish E5 (2 pending tests) before handoff
- Order 3.2: base64 patch via AGENT_STATUS_LOCAL.md (with SHA-256)
- Order 3.3: local agent must not narrate cloud state
- Order 3.4: allowed parallel work
- Order 3.5: WAIT MODE after handoff

User decision: variant A (fix E5 first, then full patch)
Cloud agent: starting Wave N+2 beta Recon in parallel

Anchor: phi^2 + phi^-2 = 3

* docs: cloud status — Wave N+2 beta closed, PR #22 open

Anchor: phi^2 + phi^-2 = 3

* docs: order #4 — coordination protocol rebuilt around local agent's no-push reality

Root cause acknowledged: local agent has no git remote access to gHashTag/tri-net.
All previous 'git fetch origin' orders were technically impossible for it.
Fault on cloud side, not local.

New protocol:
- Local codes freely in its own copy, any branch names locally
- Handoff via plain text in AGENT_STATUS_LOCAL.md (docs) or format-patch (code)
- User is courier
- Cloud holds push/PR monopoly

User decision: variant 2 — merge best content from local's 337-line version into PR #22.

Also confirmed via API:
- PR #22 open at f262dbc on feat/wave-benchmark-2026-07-04
- Ready to receive local's content via merge commit

Anchor: phi^2 + phi^-2 = 3

* docs: onboarding brief (Order #0) for fresh local agent

Zero-history clean start covering:
- Identity and environment (no push access reality)
- First task: Sprint 2 E4-E6 (Path Diversity + Self-Heal)
- Handoff protocol via AGENT_STATUS_LOCAL.md
- Hard boundaries and honesty rules

Anchor: phi^2 + phi^-2 = 3

* docs(onboarding): v2.0 merge cloud+local versions

Merged 158-line cloud version (commit 74dbbf5) with 210-line
local version (commit 7bad790 on local Mac):
- Kept Russian voice/style from cloud
- Adopted 12-section structure from local
- Removed emojis (violate user style)
- Updated Sprint 2 status to done (176/0 tests)
- Added Emergency Procedures section
- Added rule for handling contradictory session dumps

Anchor: phi^2 + phi^-2 = 3

* docs(status): reconcile cloud status to Sprint 2 COMPLETE

Manual reconciliation equivalent to local commit 8c6fcc7 (which
lives only on local/sprint2-path-diversity-2026-07-04 and was never
pushed to cloud). Content-equivalent, not cherry-picked.

Reflects post-dump reality:
- Sprint 2 E4+E5+E6 done, 176/0 tests on local 58bf246
- Both doc-merges pushed (onboarding 4da6e85, benchmark 31aafc2)
- Awaiting sprint2-full.mbox (sha256 d958aeb) for git am
- Old sprint2.patch (9717163) marked STALE, pre-fix state

Anchor: phi^2 + phi^-2 = 3

* docs(status): pre-validation logged, awaiting sprint2-full.mbox

Local agent (dump caf595a, 2026-07-04T03:14) pre-validated my
Sprint 2 apply plan on throwaway branch from 8c6fcc7 (content-
equivalent of cloud e7ff37a):
- git am sprint2-full.mbox: 8/8 clean apply
- cargo test --all: 176/0

E5 fix attribution clarified: local agent authored both Bug A
(hot_swap dead-filter stale cache) and Bug B (ranked_hops missing
feasibility routes) in same session — commits d640423 + 58bf246.
Will attribute correctly in Sprint 2 PR description.

Anchor: phi^2 + phi^-2 = 3

* docs(wave-n3-delta): arXiv-draft vendor-field auditability gap paper

Measurement-paper draft, de-risked framing (methodology + structural
remedy, NOT a deception allegation against Persistent Systems).

Three contributions:
  (1) Vendor-field discrepancy metric D = V/F with four-band classification
      (honest / optimistic / marketing-dominated / structurally uncorrelated)
      and an auditability axiom (existence of a reproducible F is the primary
      quantity, not the throughput number).
  (2) Worked case study on MPU5: 150 Mbps vendor vs 2.5-9.3 Mbps independent
      operator field (Aerobavovna) -> D = 16 (peak) to 60 (steady), band C/D.
      Corroborated by US Army Rakkasan range-collapse report.
  (3) Spec-openness + reproducible field-auditability remedy (public bit-exact
      waveform spec, reproducible Yosys build, conformance vectors, on-device
      attestation), with Tri-Net as MIT-licensed reference implementation.

Every empirical claim traces to a primary-source URL (10 refs). Explicit
threats-to-validity: single case study, operator-grade field datum,
pre-silicon reference impl, author position disclosed.

Framing: 'the field cannot audit the datasheet' not 'vendor X lies'.
Author ORCID placeholder pending insertion before arXiv submission.

---------

Co-authored-by: Perplexity Computer <agent@perplexity.ai>
Co-authored-by: SSD DDD <ssdm4@MacBook-Pro.local>
gHashTag added a commit that referenced this pull request Jul 4, 2026
@gHashTag Perplexity Computer SSD DDD
feat(sprint2): E4-E6 path diversity + self-heal + E5 bugfixes (#23) (#25
7de8149 
)

* docs: wave report — competitor moat analysis × Trinity assets

Wave A: 4-segment map (tethered / mm-wave / MANET / silicon-bound DePIN)
Wave B: 9-column comparison table vs 8 competitors
Wave C: 10 Trinity artefacts mapped to specific competitor moats

Anchor: phi^2 + phi^-2 = 3

* docs: order #1 to local agent + cloud status file

- AGENT_ORDERS_2026-07-03.md: sync protocol, ownership split, hard boundaries
- AGENT_STATUS_CLOUD.md: cloud agent state, open PRs, awaiting user decisions

Anchor: phi^2 + phi^-2 = 3

* docs: order #2 — Sprint 2 auth + Wave N+2 beta kickoff

- AGENT_ORDERS_2026-07-04.md: local agent -> Sprint 2 E4-E6, cloud -> Wave N+2 beta
- AGENT_STATUS_CLOUD.md: user decisions logged (trigger+weekly, beta, parallel)
- Correction: local agent 3c62234 out of zone, reset --hard prescribed

Anchor: phi^2 + phi^-2 = 3

* docs: order #3 — fix E5 first, patch handoff protocol

- Order 3.1: finish E5 (2 pending tests) before handoff
- Order 3.2: base64 patch via AGENT_STATUS_LOCAL.md (with SHA-256)
- Order 3.3: local agent must not narrate cloud state
- Order 3.4: allowed parallel work
- Order 3.5: WAIT MODE after handoff

User decision: variant A (fix E5 first, then full patch)
Cloud agent: starting Wave N+2 beta Recon in parallel

Anchor: phi^2 + phi^-2 = 3

* docs: cloud status — Wave N+2 beta closed, PR #22 open

Anchor: phi^2 + phi^-2 = 3

* docs: order #4 — coordination protocol rebuilt around local agent's no-push reality

Root cause acknowledged: local agent has no git remote access to gHashTag/tri-net.
All previous 'git fetch origin' orders were technically impossible for it.
Fault on cloud side, not local.

New protocol:
- Local codes freely in its own copy, any branch names locally
- Handoff via plain text in AGENT_STATUS_LOCAL.md (docs) or format-patch (code)
- User is courier
- Cloud holds push/PR monopoly

User decision: variant 2 — merge best content from local's 337-line version into PR #22.

Also confirmed via API:
- PR #22 open at f262dbc on feat/wave-benchmark-2026-07-04
- Ready to receive local's content via merge commit

Anchor: phi^2 + phi^-2 = 3

* docs: onboarding brief (Order #0) for fresh local agent

Zero-history clean start covering:
- Identity and environment (no push access reality)
- First task: Sprint 2 E4-E6 (Path Diversity + Self-Heal)
- Handoff protocol via AGENT_STATUS_LOCAL.md
- Hard boundaries and honesty rules

Anchor: phi^2 + phi^-2 = 3

* docs(onboarding): v2.0 merge cloud+local versions

Merged 158-line cloud version (commit 74dbbf5) with 210-line
local version (commit 7bad790 on local Mac):
- Kept Russian voice/style from cloud
- Adopted 12-section structure from local
- Removed emojis (violate user style)
- Updated Sprint 2 status to done (176/0 tests)
- Added Emergency Procedures section
- Added rule for handling contradictory session dumps

Anchor: phi^2 + phi^-2 = 3

* docs(status): reconcile cloud status to Sprint 2 COMPLETE

Manual reconciliation equivalent to local commit 8c6fcc7 (which
lives only on local/sprint2-path-diversity-2026-07-04 and was never
pushed to cloud). Content-equivalent, not cherry-picked.

Reflects post-dump reality:
- Sprint 2 E4+E5+E6 done, 176/0 tests on local 58bf246
- Both doc-merges pushed (onboarding 4da6e85, benchmark 31aafc2)
- Awaiting sprint2-full.mbox (sha256 d958aeb) for git am
- Old sprint2.patch (9717163) marked STALE, pre-fix state

Anchor: phi^2 + phi^-2 = 3

* docs(status): pre-validation logged, awaiting sprint2-full.mbox

Local agent (dump caf595a, 2026-07-04T03:14) pre-validated my
Sprint 2 apply plan on throwaway branch from 8c6fcc7 (content-
equivalent of cloud e7ff37a):
- git am sprint2-full.mbox: 8/8 clean apply
- cargo test --all: 176/0

E5 fix attribution clarified: local agent authored both Bug A
(hot_swap dead-filter stale cache) and Bug B (ranked_hops missing
feasibility routes) in same session — commits d640423 + 58bf246.
Will attribute correctly in Sprint 2 PR description.

Anchor: phi^2 + phi^-2 = 3

* feat(sprint2): E4-E6 path diversity + self-heal + E5 bugfixes

Ported from local/sprint2-path-diversity-2026-07-04 (58bf246) onto
feat/wave-competitors-2026-07-03. Repos diverged structurally (Cargo.toml
bench layout, cosmetic src drift), so applied as final file-states, not git am.

E4 - Babel path ETX + feasibility (RFC 8966 §3.7): src/routing.rs adds
PathRoute/path_routes/is_feasible/learn_route/compute_path_etx/force_dead.
100-topology fuzz -> 0 loops.

E5 - Ranked next-hops (k=2) + hot-swap: src/router.rs.
  Bug A (hot_swap_on_force_dead): dead-filter now reads live EtxTable,
  not stale cached candidate metric.
  Bug B (ranked_hops_ignores_dead_links): pool merges feasibility-learned
  routes (etx.path_route), not just ranked_candidates.
  Spec: etx.t27 (dead=inf), redundancy_management.t27 (backup excludes failed).

E6 - Self-heal convergence: src/daemon.rs ConvergenceMetrics + JSON emit +
CI gates (<5s link, <10s node). src/discovery.rs, src/bin/trios_meshd.rs.
Cargo.toml: serde/serde_json promoted to [dependencies] (runtime JSON).

doctest: src/crypto.rs NoiseXX diagram marked text-fence.

cargo test --all = 110 passed, 0 failed. Sprint 2 landmarks green:
fuzz_100_random_topologies_no_loops, hot_swap_on_force_dead,
ranked_hops_ignores_dead_links, convergence_ci_gate_*.

* chore(fmt+clippy): project-wide to clear CI -D warnings gate

Pre-existing debt was blocking PR #23 CI (.github/workflows/ci.yml runs
cargo fmt --all --check + cargo clippy --all-targets -- -D warnings).

fmt: cargo fmt --all across affected files.
clippy: machine-fixed via cargo clippy --fix, plus 4 manual resolutions:
  - src/router.rs: remove dead is_alive() method (Sprint 2 vestigial; the
    alive-check is inlined in recompute_ranked_hops).
  - src/router.rs: collapse single-pattern match to if let (clippy::single_match).
  - src/crypto.rs: remove unused SharedSecret type alias.
  - src/crypto.rs: #[allow(dead_code)] on NoiseXX.initiator (role retained for
    future rekey/anti-replay logic; set by new(), not yet read).

Gate verified locally: fmt=0 clippy=0 test=0 (110 passed, 0 failed).
No behavior change; Sprint 2 landmarks still green.

---------

Co-authored-by: Perplexity Computer <agent@perplexity.ai>
Co-authored-by: SSD DDD <ssdm4@MacBook-Pro.local>
gHashTag added a commit that referenced this pull request Jul 4, 2026
@gHashTag Perplexity Computer SSD DDD
docs(wave-n3 δ): arXiv-draft — MANET vendor-field auditability gap (#24…
6f508db 
…) (#26)

* docs: wave report — competitor moat analysis × Trinity assets

Wave A: 4-segment map (tethered / mm-wave / MANET / silicon-bound DePIN)
Wave B: 9-column comparison table vs 8 competitors
Wave C: 10 Trinity artefacts mapped to specific competitor moats

Anchor: phi^2 + phi^-2 = 3

* docs: order #1 to local agent + cloud status file

- AGENT_ORDERS_2026-07-03.md: sync protocol, ownership split, hard boundaries
- AGENT_STATUS_CLOUD.md: cloud agent state, open PRs, awaiting user decisions

Anchor: phi^2 + phi^-2 = 3

* docs: order #2 — Sprint 2 auth + Wave N+2 beta kickoff

- AGENT_ORDERS_2026-07-04.md: local agent -> Sprint 2 E4-E6, cloud -> Wave N+2 beta
- AGENT_STATUS_CLOUD.md: user decisions logged (trigger+weekly, beta, parallel)
- Correction: local agent 3c62234 out of zone, reset --hard prescribed

Anchor: phi^2 + phi^-2 = 3

* docs: order #3 — fix E5 first, patch handoff protocol

- Order 3.1: finish E5 (2 pending tests) before handoff
- Order 3.2: base64 patch via AGENT_STATUS_LOCAL.md (with SHA-256)
- Order 3.3: local agent must not narrate cloud state
- Order 3.4: allowed parallel work
- Order 3.5: WAIT MODE after handoff

User decision: variant A (fix E5 first, then full patch)
Cloud agent: starting Wave N+2 beta Recon in parallel

Anchor: phi^2 + phi^-2 = 3

* docs: cloud status — Wave N+2 beta closed, PR #22 open

Anchor: phi^2 + phi^-2 = 3

* docs: order #4 — coordination protocol rebuilt around local agent's no-push reality

Root cause acknowledged: local agent has no git remote access to gHashTag/tri-net.
All previous 'git fetch origin' orders were technically impossible for it.
Fault on cloud side, not local.

New protocol:
- Local codes freely in its own copy, any branch names locally
- Handoff via plain text in AGENT_STATUS_LOCAL.md (docs) or format-patch (code)
- User is courier
- Cloud holds push/PR monopoly

User decision: variant 2 — merge best content from local's 337-line version into PR #22.

Also confirmed via API:
- PR #22 open at f262dbc on feat/wave-benchmark-2026-07-04
- Ready to receive local's content via merge commit

Anchor: phi^2 + phi^-2 = 3

* docs: onboarding brief (Order #0) for fresh local agent

Zero-history clean start covering:
- Identity and environment (no push access reality)
- First task: Sprint 2 E4-E6 (Path Diversity + Self-Heal)
- Handoff protocol via AGENT_STATUS_LOCAL.md
- Hard boundaries and honesty rules

Anchor: phi^2 + phi^-2 = 3

* docs(onboarding): v2.0 merge cloud+local versions

Merged 158-line cloud version (commit 74dbbf5) with 210-line
local version (commit 7bad790 on local Mac):
- Kept Russian voice/style from cloud
- Adopted 12-section structure from local
- Removed emojis (violate user style)
- Updated Sprint 2 status to done (176/0 tests)
- Added Emergency Procedures section
- Added rule for handling contradictory session dumps

Anchor: phi^2 + phi^-2 = 3

* docs(status): reconcile cloud status to Sprint 2 COMPLETE

Manual reconciliation equivalent to local commit 8c6fcc7 (which
lives only on local/sprint2-path-diversity-2026-07-04 and was never
pushed to cloud). Content-equivalent, not cherry-picked.

Reflects post-dump reality:
- Sprint 2 E4+E5+E6 done, 176/0 tests on local 58bf246
- Both doc-merges pushed (onboarding 4da6e85, benchmark 31aafc2)
- Awaiting sprint2-full.mbox (sha256 d958aeb) for git am
- Old sprint2.patch (9717163) marked STALE, pre-fix state

Anchor: phi^2 + phi^-2 = 3

* docs(status): pre-validation logged, awaiting sprint2-full.mbox

Local agent (dump caf595a, 2026-07-04T03:14) pre-validated my
Sprint 2 apply plan on throwaway branch from 8c6fcc7 (content-
equivalent of cloud e7ff37a):
- git am sprint2-full.mbox: 8/8 clean apply
- cargo test --all: 176/0

E5 fix attribution clarified: local agent authored both Bug A
(hot_swap dead-filter stale cache) and Bug B (ranked_hops missing
feasibility routes) in same session — commits d640423 + 58bf246.
Will attribute correctly in Sprint 2 PR description.

Anchor: phi^2 + phi^-2 = 3

* docs(wave-n3-delta): arXiv-draft vendor-field auditability gap paper

Measurement-paper draft, de-risked framing (methodology + structural
remedy, NOT a deception allegation against Persistent Systems).

Three contributions:
  (1) Vendor-field discrepancy metric D = V/F with four-band classification
      (honest / optimistic / marketing-dominated / structurally uncorrelated)
      and an auditability axiom (existence of a reproducible F is the primary
      quantity, not the throughput number).
  (2) Worked case study on MPU5: 150 Mbps vendor vs 2.5-9.3 Mbps independent
      operator field (Aerobavovna) -> D = 16 (peak) to 60 (steady), band C/D.
      Corroborated by US Army Rakkasan range-collapse report.
  (3) Spec-openness + reproducible field-auditability remedy (public bit-exact
      waveform spec, reproducible Yosys build, conformance vectors, on-device
      attestation), with Tri-Net as MIT-licensed reference implementation.

Every empirical claim traces to a primary-source URL (10 refs). Explicit
threats-to-validity: single case study, operator-grade field datum,
pre-silicon reference impl, author position disclosed.

Framing: 'the field cannot audit the datasheet' not 'vendor X lies'.
Author ORCID placeholder pending insertion before arXiv submission.

---------

Co-authored-by: Perplexity Computer <agent@perplexity.ai>
Co-authored-by: SSD DDD <ssdm4@MacBook-Pro.local>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Military-technical benchmark: Tri-Net vs MPU5/Rajant/Silvus (Wave N+2 β)

1 participant

@gHashTag