diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 00000000..c0167cb6 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,79 @@ +# Contributing to Tri-Net + +> phi^2 + phi^-2 = 3 + +Welcome. This file exists so a human contributor can go from `git clone` to a +green PR in about 15 minutes. It intentionally does **not** cover the AI-agent +onboarding protocol — for that see [`docs/AGENT_ONBOARDING.md`](docs/AGENT_ONBOARDING.md). + +Addresses [W7 finding #8](docs/W7_WEAK_POINTS_STRUCTURAL.md#находка-8) (bus factor). + +## 60-second quickstart + +```bash +git clone https://github.com/gHashTag/tri-net.git +cd tri-net +cargo build --release +cargo test --release # expect: 137 passed, 0 failed on main @ 13e4692 +``` + +If the last line says `137 passed`, your environment is ready. If not, check: +- Rust toolchain (stable, minimum 1.75; check with `rustc --version`) +- macOS / Linux (Windows not tested) + +## Repository layout + +- `src/` — mesh daemon (`trios_meshd`), routing (`routing.rs`), wire codec (`wire.rs`) +- `specs/*.t27` — T27 spec language sources (single source of truth for wire format) +- `gen/{rust,c,zig}/` — auto-generated code from T27 specs, byte-identical to spec regeneration +- `smoke/` — smoke tests (`m2_loopback_smoke.sh`, `m2_loopback_smoke_n_runs.sh`) +- `docs/` — design docs, wave reports, weak-point audits, plans +- `tests/` — Rust integration tests + +## Making a change + +1. **Branch**: never push to `main` directly. Branch names look like `feat/w--` or `fix/-`. + +2. **Test locally**: run `cargo test --release` before pushing. It must return `137 passed, 0 failed` (or more, if you added tests). If you touched routing or the mesh daemon, run `N=5 DURATION=10 ./smoke/m2_loopback_smoke_n_runs.sh` — it must return `5/5 PASS`. + +3. **Commit style**: conventional-commits (`feat:`, `fix:`, `docs:`, `refactor:`, `test:`). Include `phi^2 + phi^-2 = 3` in the body of substantive commits (project convention, see [`docs/AGENT_ONBOARDING.md`](docs/AGENT_ONBOARDING.md)). + +4. **Open a PR**: default to DRAFT (`gh pr create --draft`). Base is usually `main`. Include: + - What changed and why (one paragraph) + - How you verified (command + expected output) + - Cross-references to any related PR / doc / finding + +5. **Discipline rules to know**: + - **No fabricated metrics**: any pre-hardware number tagged `-sim`. See [`docs/WAVE_REPORT_2026-07-05.md`](docs/WAVE_REPORT_2026-07-05.md). + - **Numbers cite command + SHA**: any numeric claim in a doc must cite the exact command AND commit SHA it was measured on. + - **No-paste-review**: reviewers approve committed text, not pasted diffs. See PR #43. + - **SHA-advance re-review**: an approval binds to a cited SHA; branch advance requires explicit re-review. See PR #45. + - **Regression gates test invariants**: a gate tests the property the fix guarantees, not the asymptote the algorithm aspires to. See [`smoke/M2_LOOPBACK_FIX_RESULTS.md`](smoke/M2_LOOPBACK_FIX_RESULTS.md). + +## What you cannot do as a non-maintainer + +- **Merge PRs**: main is protected; only maintainers merge. This is a small-team policy, not a permanent rule. +- **Flash hardware**: physical P203 Mini boards live with one person; hardware operations require that person's presence with a JTAG cable. Software / docs / codegen contributions do not touch hardware. +- **Change token or economic parameters**: those live in the whitepaper (`README.md` §Tokenomics) and change requires governance. Doc improvements welcome; parameter changes do not. + +## Where to start + +Good first PRs by area: + +- **Docs**: fix typos, clarify a `-sim` boundary, add a cross-link between two related docs. +- **Tests**: add a property-test or fuzz case in `tests/` for an existing invariant. +- **Codegen**: pick a currently-non-compiling spec in [`docs/W6_CODEGEN_AUDIT_2026-07-05.md`](docs/W6_CODEGEN_AUDIT_2026-07-05.md) and make it compile in one backend. Requires the `t27c` compiler (separate repo, see `docs/AGENT_ONBOARDING.md`). +- **Smoke**: extend `m2_loopback_smoke.sh` to check additional invariants without breaking determinism (must still pass N=5 back-to-back). + +## Questions + +- Open a GitHub issue with `question:` prefix. +- The maintainer reads issues within 24-48 hours in most weeks; if urgent, note it in the issue title. + +## Code of conduct + +Standard: be direct, be honest, do not fabricate numbers, do not overclaim. If your change reduces a claim in the repo (e.g., "we tested this fewer times than the doc said"), that is welcome. See [`docs/WAVE_REPORT_2026-07-05.md`](docs/WAVE_REPORT_2026-07-05.md) §"Что не переживёт" for the culture on this. + +--- + +phi^2 + phi^-2 = 3 diff --git a/README.md b/README.md index 99829d6a..81c6331e 100644 --- a/README.md +++ b/README.md @@ -89,7 +89,7 @@ BitNet-ternary benchmark on returned silicon, publish the raw log. | Rust source lines | 4 463 | `find src -name '*.rs' \| xargs wc -l` | | AD9361 tune target | LO 5.8 GHz | `radio/README.md` | | AD9361 FFT peak (1 MHz tone, digital loopback) | +0.999 MHz | `radio/README.md` | -| AD9361 SNR over noise floor | 108.6 dB | `radio/README.md` | +| AD9361 SNR over noise floor | 108.6 dB (digital loopback only, not over-the-air) | `radio/README.md`; see [W7 finding #5](docs/W7_WEAK_POINTS_STRUCTURAL.md#находка-5) and [REGULATORY_STATUS](docs/REGULATORY_STATUS.md) | | AD9361 tuning range | 70 MHz … 6 GHz | `radio/README.md` | | Sample rate | 30.72 MHz | `radio/README.md` | | Capture length | 65 536 samples | `radio/README.md` | diff --git a/docs/PAPER_DELTA_v0.md b/docs/PAPER_DELTA_v0.md index 97be65a4..574eb03d 100644 --- a/docs/PAPER_DELTA_v0.md +++ b/docs/PAPER_DELTA_v0.md @@ -102,7 +102,9 @@ Contribution C1 (CI-enforced spec/impl equality) is only as strong as its covera 1. `t27c specs/.t27` produces output without emitting the literal `return ()` placeholder (used inside the compiler to mark unsupported constructs) and without emitting any `// unsupported: ...` marker. 2. The generated file byte-matches the file committed under `gen//.` (the diff-based enforcement that Contribution C1 rests on). -3. The parent workspace still passes its host-side sanity gate: `cargo test --all` on tri-net = 141 passed, 0 failed at the same tuple. +3. The parent workspace still passes its host-side sanity gate: `cargo test --release` on tri-net = 137 passed, 0 failed (measured on main @ `13e4692`, 2026-07-05). + +> **Errata 2026-07-05**: earlier drafts of this document listed `141 passed` for the same command. Investigation across seven SHAs in the 2026-06-29→2026-07-05 window showed the real number has always been 137 (135 before PR #32). The 141 figure was an anchor-class error; corrected in three places (this §4.5 gate, §4.5 reproduction, §4.5 checklist). See `docs/W8_WEAK_POINTS_AUDIT.md` A1. **Drift event.** Any single cell violating (1) or (2) after a merge is a drift event and fails the `spec-drift-guard` CI job, blocking merge. This is the operational definition of "drift" used throughout the paper: **byte-level divergence between spec-driven regeneration and committed artifact.** No semantic equivalence, no behavioural equivalence, no theorem — a byte diff. @@ -307,7 +309,7 @@ At tri-net `bf50ad64`, verified in-CI on [PR #39](https://github.com/gHashTag/tr - `t27c gen-c specs/wire.t27 | diff -u gen/c/wire.c -` → empty. - The same triple holds for the other 67 specs; §4.5.2 lists all 68 rows. - `grep -c 'unsupported: ExprCast' gen/{rust,zig,c}/*.{rs,zig,c}` → 0 across all 204 committed files. -- `cargo test --all` → 141 passed / 0 failed (includes `wire::tests::header_roundtrips` plus the extended per-spec test surface introduced during the 2026-07-04 flip loop). +- `cargo test --all` → 137 passed / 0 failed (includes `wire::tests::header_roundtrips` plus the extended per-spec test surface introduced during the 2026-07-04 flip loop). Sample of generated cast forms (extracted from the committed files, not fabricated): @@ -387,4 +389,4 @@ This is exactly what [`.github/workflows/spec-drift-guard.yml`](https://github.c 5. Rust: `../t27/target/release/t27c gen-rust specs/wire.t27 | diff -u gen/rust/wire.rs -`. Expected: empty diff. 6. Zig: `../t27/target/release/t27c gen specs/wire.t27 | diff -u gen/zig/wire.zig -`. Expected: empty diff. 7. C: `../t27/target/release/t27c gen-c specs/wire.t27 | diff -u gen/c/wire.c -`. Expected: empty diff. -8. Optional: `cargo test --all`. Expected: 141 passed / 0 failed. +8. Optional: `cargo test --all`. Expected: 137 passed / 0 failed. diff --git a/docs/REGULATORY_STATUS.md b/docs/REGULATORY_STATUS.md new file mode 100644 index 00000000..0d6e3e40 --- /dev/null +++ b/docs/REGULATORY_STATUS.md @@ -0,0 +1,57 @@ +# Regulatory status — 5.8 GHz mesh, single source of truth + +> phi^2 + phi^-2 = 3 + +**Purpose**: consolidate everything the project knows about legal ability to run +5.8 GHz over-the-air (OTA) mesh experiments. Previously scattered across three +docs; consolidated per W7 finding #6. + +**Date of this snapshot**: 2026-07-05, measured on main @ `13e4692`. + +**Do not** treat this document as legal advice. It is a status board for +internal go/no-go decisions. Actual OTA experiments require a licensed operator +and, in most jurisdictions, written authorization filed with the regulator. + +--- + +## Status table + +| Jurisdiction | 5.8 GHz OTA status for mesh | Power ceiling (unlicensed) | Path to licensed test | Next-step date | Source | +|---|---|---|---|---|---| +| Thailand (Phuket, primary dev location) | **CLOSED** for mesh use without NBTC license | 100 mW EIRP under Wi-Fi-like rules; mesh routing not covered | Requires NBTC individual radio license; no application filed | n.a. — blocked | [docs/WAVE_REPORT_2026-07-03.md:145](https://github.com/gHashTag/tri-net/blob/main/docs/WAVE_REPORT_2026-07-03.md) | +| Singapore | Similar to TH — licensed-by-rule 100 mW ceiling for point-to-point | 100 mW | IMDA test license process (~4-8 weeks) | not initiated | [docs/STRENGTHEN.md P8 BVLOS row](https://github.com/gHashTag/tri-net/blob/main/docs/STRENGTHEN.md) | +| UAE (ADGM / DIFC via Hub71+) | **OPEN** in principle via ADGM / DIFC RegLab sandbox | Case-by-case per sandbox admission | Hub71+ AI Cohort 20 application (deadline 2026-08-02) is prerequisite step | 2026-08-02 (application deadline) | [README.md:169](https://github.com/gHashTag/tri-net/blob/main/README.md); [docs/LOCAL_FLASH.md:413](https://github.com/gHashTag/tri-net/blob/main/docs/LOCAL_FLASH.md) | +| USA (FCC, hypothetical) | 5.725-5.850 GHz U-NII-3 unlicensed; mesh permitted with 802.11 rules | 1 W conducted / 4 W EIRP with cert | Would require FCC Part 15 subpart E cert for radio module | not on roadmap | n.a. — not the target market | +| EU (CEPT, hypothetical) | 5.725-5.875 GHz ISM; mesh permitted with SRD rules | 25-500 mW depending on band segment | ETSI EN 300 440 / EN 302 502 conformance | not on roadmap | n.a. — not the target market | + +## What can be done RIGHT NOW (no license, no OTA) + +1. **Digital loopback**: AD9361 internal TX→RX digital path. Already done, SNR 108.6 dB (`radio/README.md:7-14`). Note: this is **not an over-the-air measurement**, see [W7 finding #5](W7_WEAK_POINTS_STRUCTURAL.md#находка-5). + +2. **SMA RF loopback with attenuator**: TX SMA → attenuator → RX SMA, contained inside the lab. No radiation. Listed as "next (still greenfield)" in [`radio/README.md:26-29`](https://github.com/gHashTag/tri-net/blob/main/radio/README.md); the physically-next legal experiment. Planned in [`docs/LOCAL_FLASH.md §9.3`](https://github.com/gHashTag/tri-net/blob/main/docs/LOCAL_FLASH.md). + +3. **UDP transport dev** (current): mesh routing logic (`trios_meshd`) runs on loopback UDP without touching the radio front-end. This is what M2 gate v2 tests. Legal everywhere. + +## What is BLOCKED until further notice + +- **Any 5.8 GHz radiated experiment in Thailand**. No route to legal until NBTC license or Hub71+ ADGM sandbox admission. +- **Field flight tests with mesh in the air**. Requires both spectrum authorization AND drone flight authorization (separate BVLOS process; see `docs/STRENGTHEN.md` P8 row). +- **Public claims of "5.8 GHz mesh works"** based on digital loopback numbers. See W7 finding #5. + +## Contingency chain + +If Hub71+ 2026-08-02 application is **not** admitted: +- Fallback A: apply to IMDA (Singapore) sandbox — precedent for DePIN radio experiments exists. +- Fallback B: partnership with an existing licensed operator (defense contractor, university) — no candidate identified as of 2026-07-05. +- Fallback C: keep radio arm at digital + SMA loopback, ship remaining stack (T27 codegen, FPGA attestation, token protocol) which do not require spectrum. + +## Cross-references + +- Finding [W7 #6](W7_WEAK_POINTS_STRUCTURAL.md#находка-6) — this file addresses that finding. +- [`docs/LOCAL_FLASH.md`](LOCAL_FLASH.md) — hardware handling procedures. +- [`docs/BENCHMARK_VS_MANET_2026-07-04.md`](BENCHMARK_VS_MANET_2026-07-04.md) — regulatory row in the boundary table. +- [`README.md`](../README.md) — hardware matrix; this document should be linked next to the matrix. + +--- + +phi^2 + phi^-2 = 3 diff --git a/docs/SILICON_SLIP_CONTINGENCY.md b/docs/SILICON_SLIP_CONTINGENCY.md new file mode 100644 index 00000000..070fd215 --- /dev/null +++ b/docs/SILICON_SLIP_CONTINGENCY.md @@ -0,0 +1,85 @@ +# Silicon slip contingency — three scenarios + +> phi^2 + phi^-2 = 3 + +**Purpose**: address [W7 finding #1](W7_WEAK_POINTS_STRUCTURAL.md#находка-1). The +project's compute-arm and public roadmap both hang on a single date — TT SKY26b +Trinity tape-out 2026-12-16 ([`README.md:26,167`](../README.md)). Between +tape-out and returned silicon there is typically 8-16 weeks. This document +enumerates three explicit slip scenarios and the arms that continue in each. + +**Snapshot**: 2026-07-05, main @ `13e4692`. + +**Silicon-anchor score reference**: see [`docs/BENCHMARK_VS_MANET_2026-07-04.md`](BENCHMARK_VS_MANET_2026-07-04.md) §M7. Level 5 = "custom ASIC returned + on-chain verifier". Level 3 = "FPGA bitstream anchor + signed measurement". Level 2 = "TPM/secure-element attestation". + +--- + +## Scenario 1 — Slip 3 months (tape-out 2027-03-16, returned silicon ~2027-07) + +**Assumption**: fab schedule slips one quarter (foundry congestion, mask revision, or minor DRC issue). + +**Compute arm**: remains at **level 2** (TPM/HSM attestation as interim, per finding #2 mitigation) or **level 3** (FPGA bitstream anchor via Track B / Proof-of-FPGA arm) through 2027-07. + +**Transport / Coverage / Sensor arms**: unaffected. Continue to operate software-signed per [`README.md:67-70`](../README.md). + +**Token emission**: Era 0 rewards continue for Transport/Coverage/Sensor at software-signed level. Compute-arm rewards paused OR paid at reduced multiplier tied to attestation level. Explicit rule: **no Compute-arm reward > Transport reward until level 4+ attestation available**. + +**Public communication**: silicon-anchor score in README updates to `level 3 (FPGA + signed)` with dated note "level 5 target pushed to 2027 Q3". No headline claim revision needed. + +**Trigger for scenario 2 escalation**: if by 2027-05-01 no returned silicon confirmed, invoke scenario 2. + +--- + +## Scenario 2 — Slip 6 months (tape-out 2027-06-16, returned silicon ~2027-10) + +**Assumption**: major mask revision, or fab schedule + one bug-fix cycle. + +**All of scenario 1** plus: + +**Compute arm design change**: publish an amended whitepaper section explicitly moving Compute-arm sybil resistance to "level 3 FPGA-bitstream anchor + PUF measurement" as the **operating** baseline, with level 5 as future upgrade. This aligns with the [`M2_M4_FPGA_DECOMPOSED_PLAN.md`](M2_M4_FPGA_DECOMPOSED_PLAN.md) Track B monetization vectors (FPGA-attestation-as-a-Service). + +**Economic**: extend Era 0 emission curve or introduce a slower halving in Era 0 to compensate for delayed Compute-arm activation. Requires token governance decision by 2027-04-01. + +**Risk to Trinity narrative**: rename to "Trinity FPGA + Trinity ASIC (future)" everywhere in public materials. Do not drop the ASIC track; but reduce marketing weight until returned silicon is on the table. + +**Trigger for scenario 3 escalation**: if by 2027-09-01 no returned silicon confirmed, invoke scenario 3. + +--- + +## Scenario 3 — Slip 12+ months (tape-out 2027-12+, returned silicon 2028+ or indefinite) + +**Assumption**: fundamental redesign, fab loss, funding constraint on tape-out. + +**Options** (must pick one by 2027-09-01): + +**3A — pure FPGA network**: promote Proof-of-FPGA (Track B) from parallel arm to primary. Silicon-anchor score at level 3, permanent until further notice. Whitepaper amended. The advantage: real product, real hardware, real sybil resistance. Loss: no longer a "silicon-anchor DePIN", positioning shift required. + +**3B — partner with existing PUF vendor**: license Intrinsic ID (Synopsys since 2024) SRAM-PUF IP OR PUFsecurity IP, integrate into an off-the-shelf SoC (RISC-V), skip in-house Trinity ASIC entirely. Silicon-anchor score reaches level 4 via partner-attested chip. Loss: dependence on external IP vendor; economic model needs adjustment for royalty flow. + +**3C — kill Compute arm cleanly**: publicly retire Compute-arm from the whitepaper. Continue as three-arm DePIN (Transport/Coverage/Sensor). Loss: half the whitepaper structure gone; refund/burn any pre-committed reserves earmarked for Compute-arm. Preserve project integrity by clean deprecation rather than indefinite promise. + +**In all three 3-options**: token supply / halving schedule remains unchanged. What changes is which arm can claim proof-of-work. + +--- + +## What is decided vs deferred + +**Decided now** (documented in this file): +- Slip 3 months → continue on FPGA-anchor without whitepaper change (scenario 1) +- Slip 6 months → whitepaper amendment moving compute baseline to FPGA (scenario 2) +- Trigger dates: 2027-05-01 (scenario 2 check), 2027-09-01 (scenario 3 check) + +**Deferred** (requires governance / community vote when triggered): +- Choice between 3A / 3B / 3C +- Economic curve adjustment specifics for scenario 2 + +## Cross-references + +- [W7 finding #1](W7_WEAK_POINTS_STRUCTURAL.md#находка-1) — this file addresses that finding. +- [`docs/BENCHMARK_VS_MANET_2026-07-04.md`](BENCHMARK_VS_MANET_2026-07-04.md) §M7 — silicon-anchor score definition. +- [`docs/M2_M4_FPGA_DECOMPOSED_PLAN.md`](M2_M4_FPGA_DECOMPOSED_PLAN.md) — Track B (FPGA-attestation) is the operational backup in scenarios 1 and 2. +- [`README.md:26,167`](../README.md) — tape-out date and roadmap. + +--- + +phi^2 + phi^-2 = 3 diff --git a/docs/W8_COMPETITOR_WATCH_2026-07-05.md b/docs/W8_COMPETITOR_WATCH_2026-07-05.md new file mode 100644 index 00000000..56deddc4 --- /dev/null +++ b/docs/W8_COMPETITOR_WATCH_2026-07-05.md @@ -0,0 +1,63 @@ +# W8 — Competitor watch (DePIN mesh + PUF/FPGA silicon) +> phi^2 + phi^-2 = 3 +Date: 2026-07-05 + +Scope: source-cited competitor watch across two axes. Axis A bounds Tri-Net's Transport/Coverage (DePIN mesh / decentralized wireless) arm; Axis B bounds Tri-Net's Proof-of-FPGA / silicon-anchor arm. Every value carries a markdown link to a source fetched this session. Values that could not be confirmed from a fetched primary/secondary source are marked `n.a.` + +--- + +## Axis A — DePIN mesh / decentralized wireless + +| # | Entity | Primary product | Most recent public datapoint (date + what) | Token / business model | Differentiator from Tri-Net (overlapping arm) | Open threat to Tri-Net (specific mechanism) | Source (best support for datapoint) | +|---|--------|-----------------|--------------------------------------------|------------------------|----------------------------------------------|---------------------------------------------|-------------------------------------| +| 1 | **Helium Network (Nova Labs)** | Crypto-incentivized "patchwork" of cellular/IoT hotspots; carrier data-offload service ([Fortune](https://fortune.com/2026/06/02/andrew-yang-business-acquires-helium-mobile/)) | **2026-06-02:** Noble Mobile (Andrew Yang) acquiring Helium Mobile; Nova Labs retains the data-offloading business and pivots to carrier offload after closing a multi-year deal with a large U.S. carrier at end of 2025 ([Fortune](https://fortune.com/2026/06/02/andrew-yang-business-acquires-helium-mobile/)) | HNT/MOBILE token rewards to hotspot operators, under Helium DAO; Nova Labs monetizes via B2B data-offload deals with mobile network operators ([Fortune](https://fortune.com/2026/06/02/andrew-yang-business-acquires-helium-mobile/)); Helium Mobile posting ~$2.2M/mo revenue ([Syndica](https://blog.syndica.io/deep-dive-solana-depin-february-2026/)) | Helium is licensed-spectrum cellular + Wi-Fi offload for consumer phones; Tri-Net is 5.8 GHz UAV/drone mesh with SDR radios + silicon compute proof. Helium has no silicon-attestation anchor. | Proven carrier-offload PMF (multi-year U.S. carrier deal, $14M cumulative Helium Mobile revenue since Jan 2025) means Helium already monetizes real coverage at scale; it could extend offload/coverage incentives into edge-compute DePIN and out-distribute Tri-Net on operator relationships and node density before Tri-Net's mesh reaches critical mass ([Fortune](https://fortune.com/2026/06/02/andrew-yang-business-acquires-helium-mobile/), [Syndica](https://blog.syndica.io/deep-dive-solana-depin-february-2026/)) | [Fortune, 2026-06-02](https://fortune.com/2026/06/02/andrew-yang-business-acquires-helium-mobile/) | +| 2 | **Althea Network** | Althea L1 blockchain for machine-to-machine (M2M) micro-payments; router firmware for telecom routing/billing on mesh/last-mile ISPs ([Althea forum](https://forum.althea.net/t/development-update-althea-l1-token-unlock/729)) | **2025-10-14:** "Cardinal" upgrade adds stablecoin-only fee path + iFi DEX governance for M2M devices; follows **2025-09-08** governance vote enabling ALTHEA transfers/EVM gas (chain "unlocked") ([Althea blog](https://blog.althea.net/althea-update-cardinal/), [Althea forum](https://forum.althea.net/t/development-update-althea-l1-token-unlock/729)) | ALTHEA gas token + per-bandwidth M2M micro-payments between routers; "Liquid Infrastructure" brings ISP revenue on-chain; iFi DEX fees via governance ([Althea forum](https://forum.althea.net/t/development-update-althea-l1-token-unlock/729), [Althea blog](https://blog.althea.net/althea-update-cardinal/)) | Althea is a per-packet billing/settlement layer for last-mile ISP routers (fiber/Wi-Fi), not a physical RF mesh; it sells the payment rails, not the radio or silicon-proof. Tri-Net owns the RF+silicon stack. | Althea's out-of-the-box "appliance exit" firmware and stablecoin M2M rails could become the default settlement layer any mesh (incl. Tri-Net-style networks) plugs into — capturing the economic/billing slice of decentralized wireless without owning hardware, undercutting Tri-Net's need for a bespoke token economy ([Althea forum](https://forum.althea.net/t/development-update-althea-l1-token-unlock/729)) | [Althea blog "Cardinal", 2025-10-14](https://blog.althea.net/althea-update-cardinal/) | +| 3 | **WeatherXM** | Community-powered weather-sensor DePIN; hyperlocal weather data sold to enterprises ([WeatherXM docs](https://docs.weatherxm.com/tokenomics)) | **Nov 2025:** "Targeted Rollouts" crowdfunding launched — 1,500 NFTs on Base (1 station = 4 NFTs, $100 mint) to fund/deploy new stations; 933 NFTs minted by 203 holders raising ~$81k in the referenced rollout ([WeatherXM Rollouts](https://rollouts.weatherxm.com/)) | WXM ERC-20 (100M capped supply, 10-yr emissions, 55% station rewards); enterprises must acquire WXM to license data; annual Commercial Data License auctions paid in WXM (100,000 WXM per license) ([WeatherXM docs](https://docs.weatherxm.com/tokenomics), [WeatherXM blog](https://blog.weatherxm.com/we-acquired-one-of-the-2025-weatherxm-commercial-data-licenses-bb9487bf33f0)) | WeatherXM's sensor arm is passive environmental telemetry (weather), not an active RF transport/coverage mesh; no drone/UAV mobility and no silicon-attestation. Overlaps Tri-Net only as a "sensor-arm analogue." | Its NFT-crowdfunded station-deployment playbook and data-license auction model are a proven template for bootstrapping physical-sensor DePIN density and enterprise demand; if extended to RF/coverage sensing it could occupy the "verifiable physical-data" market slot Tri-Net wants for edge compute ([WeatherXM Rollouts](https://rollouts.weatherxm.com/), [WeatherXM blog](https://blog.weatherxm.com/we-acquired-one-of-the-2025-weatherxm-commercial-data-licenses-bb9487bf33f0)) | [WeatherXM Targeted Rollouts](https://rollouts.weatherxm.com/) | +| 4 | **XNET** | Neutral-host, carrier-grade decentralized Wi-Fi / 5G offload network (Passpoint) for MSPs/ISPs ([XNET blog](https://xnetmobile.com/blog)) | **Feb 2026:** data offload jumped 32% to 107 TB — first month above 100 TB — per Syndica; AT&T customers can access XNET's 1,300+ commercial-location Passpoint Wi-Fi network ([Syndica](https://blog.syndica.io/deep-dive-solana-depin-february-2026/), [XNET blog](https://xnetmobile.com/blog)) | $XNET token rewards deployers/node operators; deflationary tokenomics (XIP-10/XIP-11 mint-and-burn from offload revenue); enterprise offload contracts with carriers ([Syndica](https://blog.syndica.io/deep-dive-solana-depin-february-2026/)) | XNET is fixed-venue carrier-grade Wi-Fi/CBRS offload (hotels, stadiums, campuses) via Passpoint; Tri-Net is mobile 5.8 GHz drone mesh with silicon compute proof. XNET has no PUF/attestation identity layer. | XNET's "flip a switch" activation on existing venue infrastructure (Cambium partnership) plus AT&T reach lets it scale coverage nodes far faster and cheaper than Tri-Net's bespoke SDR hardware, capturing the neutral-host coverage slot with real carrier offload revenue ([Syndica](https://blog.syndica.io/deep-dive-solana-depin-february-2026/), [XNET blog](https://xnetmobile.com/blog)) | [Syndica Solana DePIN Feb 2026](https://blog.syndica.io/deep-dive-solana-depin-february-2026/) | +| 5 | **Pollen Mobile / DIMO** | Pollen: plug-and-play decentralized private cellular (small-cell radios, up to 170 Mbps DL). DIMO: decentralized automotive/vehicle data protocol ([Pollen Mobile](https://www.pollenmobile.io), [DIMO news](https://dimo.org/news)) | **DIMO 2025-11-07:** bridge exploit drained ~30M DIMO (~3% supply) via compromised dev key; core network unaffected. Pollen freshest verifiable item: "The Next Phase For Pollen Mobile: Paid Data" (no dated primary source; date `n.a.`) ([CoinMarketCap DIMO](https://coinmarketcap.com/cmc-ai/dimo/latest-updates/), [Pollen Mobile](https://www.pollenmobile.io)) | Pollen: mobile-coverage DePIN (own/operate radios, "coverage on demand"), token rewards for deployers (details `n.a.` from primary). DIMO: DIMO token rewards drivers for vehicle data; API/data-licensing to enterprises; developer console/WaaS ([Pollen Mobile](https://www.pollenmobile.io), [CoinMarketCap DIMO](https://coinmarketcap.com/cmc-ai/dimo/latest-updates/)) | Pollen is user-owned private small-cell coverage (no silicon-proof); DIMO is a vehicle-data DePIN (telematics, not RF transport). Neither has UAV mesh, ETX routing, or FPGA/PUF attestation. | DIMO's automaker courtship + developer console/API monetization could lock up the "verified physical-device data + on-chain identity" market for vehicles; combined with Pollen's cheap plug-and-play coverage radios, they normalize "own your node + monetize data" DePIN UX and set buyer expectations Tri-Net must beat — but DIMO's Nov-2025 bridge exploit shows the same key-compromise/sybil risk Tri-Net's PUF identity is meant to solve ([CoinMarketCap DIMO](https://coinmarketcap.com/cmc-ai/dimo/latest-updates/), [Pollen Mobile](https://www.pollenmobile.io)) | [CoinMarketCap DIMO updates](https://coinmarketcap.com/cmc-ai/dimo/latest-updates/) | +| 6 | **GEODNET** | Decentralized GNSS/RTK network — centimeter-accurate positioning from 21,000+ community base stations across 160 countries ([CoinGabbar](https://www.coingabbar.com/en/crypto-currency-news/geodnet-token-listing-coinbase-june-2026-geod-price-today)) | **2026-06-23:** GEOD spot trading went live on Coinbase (GEOD-USD, 9 AM PT); network at 20,000+ base stations, ~$200K weekly on-chain revenue; $8M GEOD purchase led by Multicoin ([CoinGabbar](https://www.coingabbar.com/en/crypto-currency-news/geodnet-token-listing-coinbase-june-2026-geod-price-today), [Distill](https://www.distillintelligence.com/news/geodnet)) | GEOD token: operators earn GEOD for validated correction data; **80% of network revenue funds GEOD buyback-and-burn** (deflationary); ~$7.8M annualized revenue; RTK hardware sales + subscriptions via HYFIX store ([CoinGabbar](https://www.coingabbar.com/en/crypto-currency-news/geodnet-token-listing-coinbase-june-2026-geod-price-today), [Our Crypto Talk](https://ourcryptotalk.com/news/geodnet-official-store-launch-rtk)) | GEODNET is a positioning/correction-data DePIN (GNSS RTK), not RF transport or compute; no drone mesh, no silicon-attestation. Overlaps Tri-Net only as a mature "physical-infrastructure with real revenue" benchmark. | GEODNET is the clearest proof that a DePIN with genuine enterprise revenue + revenue-funded token buyback/burn can list on a Tier-1 exchange and scale to 20k+ nodes; it sets the bar for "real utility + sustainable tokenomics" that Tri-Net's fair-launch/halving model will be judged against, and could bundle precise-positioning into drone/UAV navigation — Tri-Net's own domain ([CoinGabbar](https://www.coingabbar.com/en/crypto-currency-news/geodnet-token-listing-coinbase-june-2026-geod-price-today), [Distill](https://www.distillintelligence.com/news/geodnet)) | [CoinGabbar GEOD Coinbase, 2026-06-23](https://www.coingabbar.com/en/crypto-currency-news/geodnet-token-listing-coinbase-june-2026-geod-price-today) | + +### Read-outs — Axis A (biggest threat vector) + +The sharpest threat to Tri-Net's Transport/Coverage arm is **Helium/Nova Labs' proven carrier data-offload business** ([Fortune](https://fortune.com/2026/06/02/andrew-yang-business-acquires-helium-mobile/)). By spinning off consumer Helium Mobile to Noble Mobile and focusing on B2B offload deals with large U.S. carriers, Nova Labs has demonstrated the one thing Tri-Net has not: that a decentralized coverage network can sign real, multi-year revenue contracts with incumbent operators, on top of ~$14M cumulative Helium Mobile revenue since Jan 2025 ([Fortune](https://fortune.com/2026/06/02/andrew-yang-business-acquires-helium-mobile/), [Syndica](https://blog.syndica.io/deep-dive-solana-depin-february-2026/)). The secondary threat is **XNET's asset-light "flip a switch" venue activation** ([XNET blog](https://xnetmobile.com/blog)), which scales coverage nodes far faster and cheaper than Tri-Net's custom AD9361 SDR hardware, while **GEODNET** proves the market rewards DePIN with actual enterprise revenue and revenue-funded token burns — the exact economic legitimacy test Tri-Net's 0%-premine/halving token must pass ([CoinGabbar](https://www.coingabbar.com/en/crypto-currency-news/geodnet-token-listing-coinbase-june-2026-geod-price-today)). None of these competitors have a silicon-attestation moat, which remains Tri-Net's clearest differentiator on this axis. + +--- + +## Axis B — FPGA / PUF / silicon-attestation vendors + +| # | Entity | Primary product | Most recent public datapoint (date + what) | Token / business model | Differentiator from Tri-Net (overlapping arm) | Open threat to Tri-Net (specific mechanism) | Source (best support for datapoint) | +|---|--------|-----------------|--------------------------------------------|------------------------|----------------------------------------------|---------------------------------------------|-------------------------------------| +| 7 | **Intrinsic ID (now Synopsys)** | SRAM-PUF IP for generating on-chip unique identifiers / root keys in SoCs ([Synopsys](https://news.synopsys.com/2024-03-20-Synopsys-Expands-Semiconductor-IP-Portfolio-With-Acquisition-of-Intrinsic-ID)) | **2024-03-20:** Synopsys completed acquisition of Intrinsic ID; PUF IP folded into Synopsys' semiconductor IP portfolio; PUF center of excellence established in Eindhoven ([Synopsys](https://news.synopsys.com/2024-03-20-Synopsys-Expands-Semiconductor-IP-Portfolio-With-Acquisition-of-Intrinsic-ID)) | Semiconductor IP licensing (license fees + royalties), now inside Synopsys' DesignWare/IP business; deal terms undisclosed, "not material" to Synopsys ([Synopsys](https://news.synopsys.com/2024-03-20-Synopsys-Expands-Semiconductor-IP-Portfolio-With-Acquisition-of-Intrinsic-ID)) | Intrinsic ID/Synopsys sells PUF as licensable SoC IP to chipmakers for device identity/key gen — a component sold to silicon vendors. Tri-Net uses FPGA-PUF attestation as a network-level sybil-resistance primitive with a token economy, not as IP for sale. | As part of Synopsys (the dominant EDA/IP vendor), SRAM-PUF becomes a near-default, broadly-licensed identity primitive in commodity SoCs; if PUF-based device identity ships ubiquitously in standard chips, Tri-Net's "Proof-of-FPGA" ceases to be a differentiator and its custom FPGA-attestation could be undercut by cheaper, standardized silicon identity already in every device ([Synopsys](https://news.synopsys.com/2024-03-20-Synopsys-Expands-Semiconductor-IP-Portfolio-With-Acquisition-of-Intrinsic-ID)) | [Synopsys press, 2024-03-20](https://news.synopsys.com/2024-03-20-Synopsys-Expands-Semiconductor-IP-Portfolio-With-Acquisition-of-Intrinsic-ID) | +| 8 | **PUFsecurity** | PUF-based hardware root-of-trust IP: PUFrt (Root of Trust), PUFcc (crypto coprocessor), PUFhsm, PUF-PQC (subsidiary of eMemory) ([PUFsecurity](https://www.pufsecurity.com/about-us/)) | **2026-01-16:** PUF-PQC (with eMemory) achieved NIST FIPS 205 (SLH-DSA) + SP 800-208 certification, completing full coverage of NIST PQC standards (adds to prior FIPS 203/204) ([eMemory](https://www.ememory.com.tw/en-US/News/News?guid=26011610540360), [PUFsecurity](https://www.pufsecurity.com/category/company-news/)) | Security IP licensing (license + royalty) built on eMemory's NeoPUF; embeds into third-party SoCs; **2025-10-31** PUFrt anchored Silicon Labs Series 3 SoC to industry-first PSA Certified Level 4 ([PUFsecurity](https://www.pufsecurity.com/category/company-news/)) | PUFsecurity licenses NeoPUF root-of-trust + PQC IP into chips (BMC SoCs, SSD controllers, IoT); it sells attestation-as-IP. Tri-Net builds a DePIN sybil-resistance layer + Trinity ASIC on top of PUF, not IP-for-license. | PUFsecurity's NIST-certified PUF-PQC + PSA-L4 root-of-trust makes standardized, quantum-safe silicon identity available off-the-shelf to any chipmaker; a competing DePIN could license PUFrt/PUF-PQC and reach certified, quantum-resilient device attestation faster than Tri-Net can tape out its custom Trinity ASIC (projected 2026-12-16), neutralizing Tri-Net's silicon-anchor lead ([eMemory](https://www.ememory.com.tw/en-US/News/News?guid=26011610540360), [PUFsecurity](https://www.pufsecurity.com/category/company-news/)) | [eMemory/PUFsecurity PUF-PQC NIST, 2026-01-16](https://www.ememory.com.tw/en-US/News/News?guid=26011610540360) | +| 9 | **Verayo** | (Historical) Silicon-PUF ("Silicon DNA") authentication/key-generation IP, incl. FPGA/ASIC/RFID; PUF invented at MIT by Srini Devadas ([PR Newswire](https://www.prnewswire.com/news-releases/verayo-puf-ip-on-xilinx-zynq-ultrascale-mpsoc-devices-addresses-security-demands-300357805.html)) | **Status: OUT OF BUSINESS** — PitchBook lists Verayo as "Out of Business" (out-of-business event dated 01-Jan-2019); Semiconductor Engineering (2020) reports the company "appears to have closed down," website blank ([PitchBook](https://pitchbook.com/profiles/company/55111-87), [Semiconductor Engineering](https://semiengineering.com/pufs-promise-better-security/)) | (Historical) PUF IP licensing + PUF-enabled RFID chip sales; funded by Khosla Ventures, raised ~$3.05M; had licensed PUF IP into Xilinx Zynq UltraScale+ MPSoC ([PitchBook](https://pitchbook.com/profiles/company/55111-87), [PR Newswire](https://www.prnewswire.com/news-releases/verayo-puf-ip-on-xilinx-zynq-ultrascale-mpsoc-devices-addresses-security-demands-300357805.html)) | Verayo pioneered arbiter/"strong" PUF for FPGAs and RFID authentication, closest in spirit to Tri-Net's FPGA-PUF concept — but it is defunct, so it is a cautionary precedent, not an active competitor. Strong-PUF never proved commercially secure enough at scale ([Semiconductor Engineering](https://semiengineering.com/pufs-promise-better-security/)). | Minimal direct threat (defunct). The relevant lesson: Verayo's failure shows FPGA/strong-PUF authentication as a standalone business is hard to sustain commercially — a risk flag for Tri-Net if Proof-of-FPGA is treated as the product rather than as one primitive inside a broader DePIN economy ([PitchBook](https://pitchbook.com/profiles/company/55111-87), [Semiconductor Engineering](https://semiengineering.com/pufs-promise-better-security/)) | [PitchBook Verayo (Out of Business)](https://pitchbook.com/profiles/company/55111-87) | +| 10 | **eMemory Technology** | Logic-based NVM IP (NeoFuse OTP, NeoBit) + PUF security IP (NeoPUF); parent of PUFsecurity; supplies 2,400+ foundries/fabless firms ([eMemory](https://www.ememory.com.tw/en-US/News/News?guid=26011610540360)) | **2026-05:** Q1 2026 earnings — PUF-based revenue licensing up 21.5% QoQ / **606.9% YoY**; partnering with **Intel Foundry to implement PUF-based IP on Intel 18A** for U.S. gov't supply-chain security ([Quartr](https://quartr.com/companies/ememory-technology-inc_15790), [Yahoo Finance](https://finance.yahoo.com/markets/stocks/articles/ememory-technology-inc-roco-3529-030030531.html)) | Semiconductor IP licensing + per-chip royalties (NeoFuse 59.8% of Q1 rev, NeoBit 20%, PUF-based 12.2%, MTP 8%); publicly traded (TPEx/ROCO:3529) ([Quartr](https://quartr.com/companies/ememory-technology-inc_15790)) | eMemory is the foundational NVM+PUF IP licensor whose NeoPUF underpins PUFsecurity; it sells silicon-identity IP to the entire foundry ecosystem. Tri-Net consumes PUF as a network primitive; eMemory would be a supplier/rival at the IP layer, not a DePIN. | With PUF-based IP already in 20+ SSD controllers, mainstream BMC chips, and now targeting Intel 18A, eMemory is making hardware root-of-trust a ubiquitous, foundry-standard feature; if silicon identity is baked into virtually all advanced-node chips, Tri-Net's bespoke Proof-of-FPGA/Trinity ASIC loses scarcity value and any competitor can source certified silicon identity as a commodity ([Quartr](https://quartr.com/companies/ememory-technology-inc_15790), [Yahoo Finance](https://finance.yahoo.com/markets/stocks/articles/ememory-technology-inc-roco-3529-030030531.html)) | [Quartr eMemory Q1 2026](https://quartr.com/companies/ememory-technology-inc_15790) | + +### Read-outs — Axis B (biggest threat vector) + +The dominant threat to Tri-Net's silicon-anchor arm is **the commoditization of PUF-based device identity by the eMemory / PUFsecurity / Synopsys(Intrinsic ID) bloc** ([eMemory](https://www.ememory.com.tw/en-US/News/News?guid=26011610540360), [Synopsys](https://news.synopsys.com/2024-03-20-Synopsys-Expands-Semiconductor-IP-Portfolio-With-Acquisition-of-Intrinsic-ID)). eMemory's PUF licensing grew ~607% YoY and is now targeting Intel 18A, while PUFsecurity's PUF-PQC holds full NIST PQC certification (FIPS 203/204/205 + SP 800-208) and PSA Level 4 ([Quartr](https://quartr.com/companies/ememory-technology-inc_15790), [eMemory](https://www.ememory.com.tw/en-US/News/News?guid=26011610540360)). The mechanism of harm is standardization: if certified, quantum-safe silicon root-of-trust ships as a licensable, foundry-standard block in commodity SoCs, then any rival DePIN can license the same attestation off-the-shelf and reach it *before* Tri-Net's custom Trinity ASIC tapes out (projected 2026-12-16) — collapsing Tri-Net's "silicon anchor for compute proof" from a moat into a table-stakes feature. **Verayo** is the cautionary tail: the original FPGA/strong-PUF authentication startup is defunct ([PitchBook](https://pitchbook.com/profiles/company/55111-87)), underscoring that Proof-of-FPGA survives only as one primitive inside Tri-Net's broader DePIN economy, not as a standalone product. + +--- + +## Method + +**URLs fetched (this session):** +- https://fortune.com/2026/06/02/andrew-yang-business-acquires-helium-mobile/ — Helium/Nova Labs/Noble Mobile acquisition (fetched OK) +- https://www.coingabbar.com/en/crypto-currency-news/geodnet-token-listing-coinbase-june-2026-geod-price-today — GEODNET Coinbase listing (fetched OK) +- https://www.distillintelligence.com/news/geodnet — GEODNET funding/base stations/revenue (fetched OK) +- https://blog.althea.net/althea-update-cardinal/ — Althea Cardinal upgrade (fetched OK) +- https://announcements.weatherxm.com/ — WeatherXM announcements (fetched OK; no 2026 items on index) +- https://www.pollenmobile.io — Pollen Mobile product/status (fetched OK; no dated news) +- https://blog.weatherxm.com/ — WeatherXM blog index (fetched OK; latest post "Preparing for the Next Era of $WXM," May 20) +- https://xnetmobile.com/blog — XNET blog (fetched OK; post dates not exposed on page) +- https://dimo.org/news — DIMO news (fetched OK; latest visible item July 2025) +- https://www.ememory.com.tw/en-US/News/News?guid=26011610540360 — eMemory/PUFsecurity PUF-PQC NIST FIPS 205 (fetched OK) +- https://www.pufsecurity.com/category/company-news/ — PUFsecurity company news list (fetched OK) +- Search-surfaced content used with in-text citation (via search_web result bodies, then corroborated): Synopsys press release (news.synopsys.com/2024-03-20...), PitchBook Verayo profile, Semiconductor Engineering PUF article, Syndica Solana DePIN Feb 2026, CoinMarketCap DIMO updates, Quartr eMemory Q1 2026, Yahoo Finance eMemory Q1 2026 call, WeatherXM Rollouts (rollouts.weatherxm.com), WeatherXM docs/blog data-license posts, PR Newswire Verayo/Xilinx. + +**Could not fetch / not confirmed:** +- https://blog.weatherxm.com/preparing-for-the-next-era-of-wxm/ — returned 404 (Medium). WeatherXM's freshest fully-primary datapoint was taken from the Rollouts site (Nov 2025) and docs instead. +- WeatherXM "2026 Data License Auction Winners" precise winners — only surfaced via a Reddit thread (not cited per rules); the auction *mechanism* and WXM licensing model were confirmed from WeatherXM docs and the company's own 2025 license-acquisition blog post. Exact 2026 winner list: `n.a.` from primary. +- Pollen Mobile token/tokenomics and a dated 2026 news item — no dated primary source located; marked `n.a.` +- XNET exact publication dates for individual blog posts — not exposed on the blog page; offload metrics/date sourced from Syndica (Feb 2026) instead. + +phi^2 + phi^-2 = 3 diff --git a/docs/W8_DECOMPOSED_PLAN.md b/docs/W8_DECOMPOSED_PLAN.md new file mode 100644 index 00000000..c119f65d --- /dev/null +++ b/docs/W8_DECOMPOSED_PLAN.md @@ -0,0 +1,91 @@ +# W8 — decomposed plan (weak-points × competitor threats) + +> phi^2 + phi^-2 = 3 + +Дата: 2026-07-05, main @ `13e4692`. + +**Синтез двух источников**: +- [`W8_WEAK_POINTS_AUDIT.md`](W8_WEAK_POINTS_AUDIT.md) — ранжирование 8 W7-находок + audit-tail A1 +- [`W8_COMPETITOR_WATCH_2026-07-05.md`](W8_COMPETITOR_WATCH_2026-07-05.md) — 10 конкурентов по 2 осям + +## 0. Одна фраза + +Слабые места и конкуренты **сходятся на одной точке давления**: Tri-Net должен показать *реальную денежную* или *реальную функциональную* легитимность до 2026-12-16 tape-out, потому что (a) экономика без Compute-arm 6+ месяцев уязвима (finding #7), (b) PUF-identity commodifиzируется через Synopsys/eMemory/PUFsecurity быстрее чем Trinity ASIC приезжает ([W8_COMPETITOR_WATCH](W8_COMPETITOR_WATCH_2026-07-05.md#axis-b-fpga--puf--silicon-attestation-vendors) Axis B read-out), (c) GEODNET/Helium/XNET уже показывают "real revenue + tier-1 listing" стандарт по которому будет судиться fair-launch модель Tri-Net ([W8_COMPETITOR_WATCH](W8_COMPETITOR_WATCH_2026-07-05.md#axis-a-depin-mesh--decentralized-wireless) Axis A read-out). + +## 1. Матрица давления — weakness × threat + +| Weakness (W7) | Совпадающий competitor threat | Приоритет | +|---|---|---| +| #1 Silicon single-date | eMemory PUF-PQC на Intel 18A уже сегодня; PUFsecurity PSA-L4 сегодня; Trinity — только в декабре | **CRITICAL** | +| #2 Compute arm blocked pre-silicon | Синопсис/PUFsecurity могут licence PUF-attestation любому конкуренту-DePIN, тот придёт с "рабочим silicon-anchor" раньше | **CRITICAL** | +| #3 3-node self-heal не работает | Helium 100k+ hotspots, XNET 1300+ locations, GEODNET 20k+ базовых станций — 3 узла на этом фоне выглядят как lab experiment, не network | MAJOR (нет денег на 4-й узел) | +| #4 Tri-backend ∩ = ∅ | Не пересекается с competitor threat напрямую | MAJOR (структурный, не рыночный) | +| #5 108.6 dB — digital loopback | XNET/Pollen уже имеют реальную OTA-передачу с carriers; наши цифры без OTA — не сопоставимы | MAJOR | +| #6 Regulatory 5.8 GHz TH closed | Helium имеет FCC licensed spectrum + carrier deals; мы ещё не в Hub71+ | MAJOR | +| #7 Экономика 0% premine + Compute blocked | GEODNET показывает эталон "real revenue → buyback burn" (80% revenue → burn), нам нечего показать; DIMO/WeatherXM subsidize deployment через NFT/token — у нас нет subsidy механизма | **CRITICAL** | +| #8 Bus factor | Не совпадает с прямой competitor threat, но при появлении внешнего contributor это будет первый вопрос | MAJOR | + +**Верхняя тройка (совпадение weakness+threat, оба critical)**: #1, #2, #7. Все три — экономика/timeline, не код. + +## 2. Что закрыто в этом лупе (W8, уже реализовано в PR #51) + +Один DRAFT PR [#51](https://github.com/gHashTag/tri-net/pull/51) `feat/w8-weak-points-mitigations-2026-07-05` `ea8f4db`: + +1. **A1** paper-delta `141 → 137` в трёх местах + errata note (audit-tail из W7.5 закрыт) +2. **#1 mitigation** — `docs/SILICON_SLIP_CONTINGENCY.md`: явные сценарии slip 3/6/12 мес, trigger dates 2027-05-01 и 2027-09-01, три развилки (3A pure FPGA / 3B partner PUF / 3C kill Compute clean) +3. **#5 mitigation** — README Metrics disclaimer: 108.6 dB помечен `digital loopback only, not over-the-air` +4. **#6 mitigation** — `docs/REGULATORY_STATUS.md`: single source of truth, таблица TH/SG/UAE/US/EU, contingency chain если Hub71+ не примут +5. **#8 mitigation** — `CONTRIBUTING.md`: 15-минутный quickstart для человеческого контрибьютора + +Verified: 137 tests pass on `ea8f4db`; gate v2 N=5 → 5/5 PASS on branch. + +## 3. Что декомпозировано на W9 (design docs, ещё не реализовано) + +Два design doc'а, оба сходятся на critical-triangle #1+#2+#7: + +### W9-D1 — Compute-arm interim attestation path (finding #2) + +**Motivation** ← competitor threat: eMemory PUF-PQC + Intel 18A + PSA-L4 доступны конкуренту-DePIN уже сегодня. Мы теряем окно "silicon-anchor moat" быстрее чем закрывается tape-out. + +**Deliverable**: `docs/COMPUTE_INTERIM_ATTESTATION.md` — дизайн уровня "level 2 TPM/HSM attestation" (по собственной шкале M7) как временного, помеченного `low-security` пути для Compute arm до silicon. Ссылки на: +- TPM 2.0 spec для generic TPM attestation +- PUFsecurity PUFrt as licensable interim option (buy vs build анализ) +- Помеченный `-sim` disclaimer: этот путь не даёт полной sybil-resistance, только "лучше чем ничего" + +**Non-goal**: implementation. Только design doc + explicit trade-off table. + +**Effort**: 1 день cloud agent, 0.5 дня human review. + +### W9-D2 — Bootstrap operator program (finding #7) + +**Motivation** ← competitor threat: GEODNET показывает эталон real revenue + buyback burn; WeatherXM показывает NFT-crowdfunded station deployment; DIMO subsidize через partnership с automakers. У нас — 0% treasury, значит нет капитала для subsidy P203 Mini boards, но нельзя нарушать 0% premine принцип. + +**Deliverable**: `docs/BOOTSTRAP_OPERATOR_PROGRAM.md` — дизайн "first-N-operators получают повышенный Era-0 reward multiplier без нарушения 0% premine". Curve скошена в начале, эмиссия всё ещё через proof. Явно контрастирует с Helium equity-based subsidy (Nova Labs) и WeatherXM NFT-crowdfunding. Экономический моделирование: если N=100 operators получают 3x multiplier в первые 6 месяцев, сколько это TRI, какая dilution против long-term supply. + +**Non-goal**: governance vote. Только design doc + calibration table. + +**Effort**: 1-2 дня cloud agent + human review. + +## 4. Что НЕ в W8/W9 (структурные, не документные) + +- **#3 hardware** — 4-я плата: $2-3k, procurement, не в этом квартале. +- **#4 execution** — E0425 root cause: отдельный трек, PR #44 in-flight. +- **Sensor/Coverage arms operational**: требует железа и regulatory. + +## 5. Дисциплина применения (напоминание для W9) + +- **v1.2 numbers-without-realm-check**: любое число в W9-D1/W9-D2 → команда + SHA +- **v1.3 aspiration-vs-property**: если появится regression gate — тестировать инвариант, не асимптоту, N=5 обязательно +- **v1.4 stacked-PR-after-squash-check**: W9-D1 и W9-D2 — независимые PRs, оба base=main. Никаких стеков. + +## 6. Что-если сценарии для W9 + +**Если Hub71+ 2026-08-02 не принят**: W9-D2 (bootstrap operator program) становится **обязательным** — без grant и без treasury единственный путь bootstrap это правильная кривая emission. + +**Если PR #44 (E0425 root cause) сходится**: измеримый gate для #4 (tri-backend) становится achievable → добавляется как W10 item. + +**Если competitor watch cron (Friday 2026-07-10) поймает новую angle**: adaptive re-prioritization для W9 findings. + +--- + +phi^2 + phi^-2 = 3 diff --git a/docs/W8_WEAK_POINTS_AUDIT.md b/docs/W8_WEAK_POINTS_AUDIT.md new file mode 100644 index 00000000..d127c512 --- /dev/null +++ b/docs/W8_WEAK_POINTS_AUDIT.md @@ -0,0 +1,51 @@ +# W8 — аудит слабых мест (rank + cycle-fit) + +> phi^2 + phi^-2 = 3 + +Дата: 2026-07-05. Основано на: [W7_WEAK_POINTS_STRUCTURAL.md](W7_WEAK_POINTS_STRUCTURAL.md) + audit-tail из session log W7.5. + +Формат: одна строка на находку. Severity — из W7-документа. Cost-to-fix — оценка человеко-часов и/или $. Cycle-fit — можно ли закрыть в W8 (7 дней) при текущей команде. + +## Ранжирование + +| # | Weakness | Sev | Cost | Cycle-fit W8 | Owner tier | +|---|---|---|---|---|---| +| 1 | Silicon timeline slip (single date 2026-12-16, no slip contingency doc) | CRIT | 0.5 дня (написать `docs/SILICON_SLIP_CONTINGENCY.md`, 3 сценария) | **YES** | cloud+human | +| 2 | Compute arm blocked pre-silicon, no interim TPM/HSM attestation path documented | CRIT | 1 день (design doc, не реализация) | partial — только design doc | cloud | +| 3 | 3-node triangle не показывает self-heal (path diversity ≥ 2) | MAJOR | 2-3 дня (rename M4/M5 в док-ах) ИЛИ $2-3k (4-я плата) | rename **YES**, hardware **NO** | cloud+human | +| 4 | codegen tri-backend ∩ = ∅, ценность архитектуры не эмпирична | MAJOR | 3-5 дней (fix E0425 root cause, PR #44 в процессе) | partial — attach measurable gate, реализация не в W8 | cloud | +| 5 | 108.6 dB SNR — digital loopback, не эфир; SMA RF loopback не сделан | MAJOR | 0.3 дня (disclaimer в Metrics table) + hardware experiment (human) | disclaimer **YES** | cloud | +| 6 | Regulatory 5.8 GHz — знание разбросано, нет единого `REGULATORY_STATUS.md` | MAJOR | 0.5 дня | **YES** | cloud | +| 7 | Экономика: 0% premine + Compute blocked → нет капитала для bootstrap operators | CRIT | 1 день (design bootstrap operator program без нарушения 0%) | design doc **YES**, execution нет | cloud | +| 8 | Bus factor — один человек: hardware + merge + legal | MAJOR | 0.5 дня (`CONTRIBUTING.md` + delegate docs-only merge) | **YES** | cloud+human | +| A1 | Audit-tail v1.2: paper-delta `141 tests` в 3 местах, реальность 137 | MINOR | 15 минут (3 sed) | **YES** | cloud | + +## Итог по cycle-fit W8 + +Закрываются в этом лупе документами (без hardware, без $): +- **A1** — paper-delta 141→137 (тривиальный audit-tail) +- **1** — SILICON_SLIP_CONTINGENCY doc +- **5** — SNR disclaimer в Metrics table +- **6** — REGULATORY_STATUS.md (сбор существующего знания в один файл) +- **8** — CONTRIBUTING.md (15-мин quick-start для человеческого контрибьютора) + +Требуют design-work (можно в W8 как ONE design doc, exec позже): +- **2** — Compute interim attestation path +- **7** — Bootstrap operator program без 0%-premine нарушения + +Не в W8 (нужно железо / деньги / внешние люди): +- **3** hardware — покупка 4-й платы +- **4** реализация — фикс E0425 root cause через PR #44 (уже отдельный трек) + +## Приоритет реализации в W8 + +Порядок (по «cost / risk-reduction» ratio): +1. **A1** paper-delta fix (15 мин, closes audit-tail from W7.5) +2. **6** REGULATORY_STATUS.md (0.5 дня, single-file синтез) +3. **1** SILICON_SLIP_CONTINGENCY (0.5 дня) +4. **8** CONTRIBUTING.md (0.5 дня, снижает bus factor) +5. **5** SNR disclaimer правка (15 мин) + +Один DRAFT PR `feat/w8-weak-points-mitigations-2026-07-05` содержит все пять правок — они мелкие, документные, тематически связаны, review одним куском проще чем пять отдельных. + +phi^2 + phi^-2 = 3