docs(TRI-NET): cross-line package -- P0 NMSE / P1 API+whitepaper / P2 22FDX + Zenodo#697
Merged
Merged
Conversation
… 22FDX + Zenodo Adds the TRI-NET cross-line package documents and machine-readable specs/schemas, plus traceability updates. Docs-only; no gen/, coq/, bootstrap/ edits; no new *.sh; R5-HONEST preserved. NEW docs: - docs/GF16_BFLOAT16_NMSE_PROTOCOL.md (P0) - docs/TRI_NET_API.md (P1) - docs/TRI_NET_WHITEPAPER.md (P1) - docs/22FDX_TOPS_W_PROJECTION.md (P2) - docs/ZENODO_BUNDLES.md (P2) NEW specs (L4 TESTABILITY: test + invariant + bench): - specs/benchmarks/gf16_bfloat16_nmse.t27 - specs/api/tri_net_api.t27 NEW JSON schemas (draft-07): - schemas/nmse-protocol-v1.json - schemas/tri-net-api-v1.json Law compliance: L1 Closes #696, L2 no gen/ edits, L3 pure ASCII/English, L4 specs have test+invariant+bench, L5 phi^2 + 1/phi^2 = 3 verbatim, L6 FORMAT-SPEC-001.json + gf16.t27 referenced as SSOT, L7 zero new *.sh. Validation: scripts/check_first_party_doc_language.py PASS; JSON sanity PASS; draft-07 schema validity PASS; golden round-trip + mutation negative test PASS. ./scripts/tri test not run locally (no cargo in env) -- CI is authoritative. Closes #696
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
…map) t27-side projection of the TRI-NET 2026 scientific improvement plan. Toolchain-only deliverables: NMSE harness, Python SDK (read-only), Coq export, Zenodo manifests, conformance contribution path. R5-HONEST. NEW: docs/SCIENTIFIC_IMPROVEMENT_PLAN.md - CL-01..CL-04 DARPA CLARA alignment (technical only; no funding claim) - EN-01..EN-03 energy efficiency (Triple-Deck Coq lemmas + 22FDX projection; no `1000x` / `4000 TOPS/W` claim restated) - SN-01..SN-03 SNN-TRI fusion (NMSE distributions, theta gate, INT2 codebook; no `Delta_dB` quoted before manifest lands) - PUB-01..PUB-03 publication path (draft-and-submit; no acceptance claim) - OS-01..OS-03 open-source community (Python SDK target, Coq export target, contribution path) - Section 7 timeline: Q2..Q4 2026 + open rows for silicon / paper acceptance / Zenodo upload - Section 8 success metrics: only CI-green workflows and committed artefact counts -- no silicon-bound metric - Section 9 references: in-repo (authoritative) + external (VERIFY) - Section 10 anti-claims: no funding, no tape-out date, no paper acceptance, no 1000x / 4000 TOPS/W claim, no new DOI, no hosted service, no NPU parity Every row in every table labelled `VERIFY`, `projection`, or `target`. Cross-links added in: - docs/TRI_NET_WHITEPAPER.md (Cross-links section) - docs/TRI_NET_API.md (Cross-links section -- OS-01 SDK target) - docs/22FDX_TOPS_W_PROJECTION.md (Cross-links section -- EN-02) - docs/GF16_BFLOAT16_NMSE_PROTOCOL.md (Cross-links section -- PUB-02) - docs/ZENODO_BUNDLES.md (Cross-links section -- OS-02 / PUB-02) - docs/README.md (new "TRI-NET cross-line package" table including the SIP entry) - docs/NOW.md (extended package entry) - NOW.md (extended package entry) Law compliance: - L1: still Closes #696 (same PR) - L2: zero gen/ / coq/ / bootstrap/ edits - L3: new doc is pure ASCII; pre-existing non-ASCII in docs/README.md / docs/NOW.md / NOW.md left untouched - L4: no new .t27 specs in this commit - L5: phi^2 + 1/phi^2 = 3 cited verbatim - L6: numeric SSOT unchanged - L7: zero new *.sh Validation: scripts/check_first_party_doc_language.py PASS; ASCII purity verified on docs/SCIENTIFIC_IMPROVEMENT_PLAN.md and on every new cross-link line. Refs #696
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
PR DashboardGenerated at: 2026-05-18 05:28:04 UTC
Summary
|
Owner
Author
Follow-up commit
|
| Section | IDs | Content |
|---|---|---|
| 2 | CL-01..CL-04 | DARPA CLARA alignment (technical, NOT funding) |
| 3 | EN-01..EN-03 | Energy efficiency (Triple-Deck Coq + 22FDX projection) |
| 4 | SN-01..SN-03 | SNN-TRI fusion surface (NMSE / theta / INT2) |
| 5 | PUB-01..PUB-03 | Publication path (draft and submit) |
| 6 | OS-01..OS-03 | Open-source SDK / Coq export / contribution path |
| 7 | -- | Timeline (Q2..Q4 2026 + open rows for silicon / paper / DOI) |
| 8 | -- | Success metrics (CI-green workflows + committed artefacts only) |
| 9 | -- | References (in-repo authoritative + external VERIFY) |
| 10 | -- | What this is NOT (explicit anti-claims) |
R5-honest gating. Every row carries one of three labels:
VERIFY-- external claim; integrator must verify source.projection-- architecture estimate, not measured silicon.target-- programmatic goal, not achieved outcome.
Explicit anti-claims in the doc:
- No funding claim. CL-01..CL-04 are technical alignment, not funding.
- No silicon arrival date. Timeline marks silicon as
open. - No paper acceptance. PUB-01..PUB-03 are draft-and-submit.
- No
1000xor4000 TOPS/Wclaim restated. Such figures are
VERIFYexternal press only. - Existing
28-120 TOPS/Wband restated asprojection, with
back-links toBENCHMARKS.mdanddocs/22FDX_TOPS_W_PROJECTION.md. - No new DOI minted. Only existing
10.5281/zenodo.19227877is
referenced (perdocs/ZENODO.md). - No
Delta_dBintroduced before a sealedbench/results/nmse-*.json
manifest lands.
Cross-links added in (+1 line each, ASCII):
docs/TRI_NET_WHITEPAPER.md(Cross-links section)docs/TRI_NET_API.md(Cross-links section -- OS-01 SDK target)docs/22FDX_TOPS_W_PROJECTION.md(Cross-links section -- EN-02)docs/GF16_BFLOAT16_NMSE_PROTOCOL.md(Cross-links section -- PUB-02)docs/ZENODO_BUNDLES.md(Cross-links section -- OS-02 / PUB-02)docs/README.md(new "TRI-NET cross-line package" index table)docs/NOW.md(extended package entry)NOW.md(extended package entry)
Law compliance preserved. L1 (still Closes #696), L2 (zero gen/ /
coq/ / bootstrap/ edits), L3 (new file pure ASCII; gate exit 0),
L5 (phi^2 + 1/phi^2 = 3 verbatim), L6 (numeric SSOT untouched), L7
(zero new *.sh).
Validation. scripts/check_first_party_doc_language.py PASS (exit
0); ASCII purity verified on the new file and every cross-link
addition.
PR remains open, unmerged, as instructed.
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
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cross-line TRI-NET package -- P0 NMSE protocol, P1 TRI-NET API and
whitepaper, P2 22FDX TOPS/W projection methodology and Zenodo bundles plan.
Docs-and-specs only in
t27; the chip-side D2D protocol and Triple-Deckimplementation live in
tt-trinity-euler/tt-trinity-gammaand arecross-linked, not duplicated.
Five new docs, two new
.t27specs (each withtest+invariant+benchper L4 TESTABILITY), and two new draft-07 JSON schemas. R5-HONESTposture preserved throughout: every 22FDX number is labelled
projection, not measured silicon; no DOI is quoted for v1/v2/v3
before upload; no parity claim is made against any commercial NPU.
Deliverables
P0 -- GF16 vs bfloat16 NMSE protocol
docs/GF16_BFLOAT16_NMSE_PROTOCOL.mdspecs/benchmarks/gf16_bfloat16_nmse.t27schemas/nmse-protocol-v1.jsonDistribution-explicit (D_NORM / D_LOG / D_RELU / D_PHI / D_DEEP). L5
IDENTITY witness (
|phi^2 + 1/phi^2 - 3| < 1e-15in f64) gates everyrun. BF16 subnormal policy must be declared in the manifest. Seal hash
must match
bootstrap/stage0/FROZEN_HASHor the manifest is informationalonly.
P1 -- TRI-NET API for external integration
docs/TRI_NET_API.mdspecs/api/tri_net_api.t27schemas/tri-net-api-v1.jsonFile-based, read-only contract over the JSON artefacts this repo (and the
sibling chip repos) emit. Explicitly NOT a hosted endpoint. Fail-closed
validation. Extensions confined to a reserved
x_extensionnamespace.Schema fragments:
RepoIdentity,Readiness,ArtefactIndex.P1 -- Whitepaper
docs/TRI_NET_WHITEPAPER.mdPosition paper. Frames TRI-NET as open high-assurance ternary AI
silicon substrate, not a TOPS race. Every silicon-readiness statement
mirrors
STATUS.md; nothing outruns the ladder. Cross-links the fourproducts (
t27+ the three chip repostt-trinity-phi,tt-trinity-euler,tt-trinity-gamma).P2 -- 22FDX TOPS/W projection methodology
docs/22FDX_TOPS_W_PROJECTION.mdEvery row tagged with a confidence band C1..C5.
C1rows trace toexisting Coq lemmas in
trios-coq/Physics/(W34..W49 ledger). Nomeasured silicon number appears. A falsification policy is enumerated so
that, when 22FDX silicon eventually exists, the table can be falsified
line-by-line.
P2 -- Zenodo bundles plan v1/v2/v3
docs/ZENODO_BUNDLES.mdThree role-based bundles: v1 toolchain, v2 silicon substrate, v3 proofs +
conformance. No DOI is quoted before upload. Existing canonical
B001..B007 + v5.0 parent records (in
docs/ZENODO.md) are predecessorrecords, not the v1/v2/v3 line.
Cross-links to chip repos
tt-trinity-euler/tt-trinity-gamma; t27surfaces only the toolchain-side hooks via the file-based API.
in
trios-coq/Physics/(existing NOW entries). Chip-side implementationlives in the chip repos and is referenced, not duplicated, here.
Law compliance
Closes #696.gen/,coq/,trios-coq/,proofs/,bootstrap/.scripts/check_first_party_doc_language.pyPASS..t27spec containstest+invariant+benchblocks.phi^2 + 1/phi^2 = 3cited verbatim in every new docand witnessed at the NMSE protocol boundary.
conformance/FORMAT-SPEC-001.json+specs/numeric/gf16.t27referenced as numeric SSOT; no kernel changes.
*.sh.Test plan
scripts/check_first_party_doc_language.py-- exit 0FORMAT-SPEC-001.json-- PASSjsonschema.Draft7Validator.check_schemaon
schemas/nmse-protocol-v1.jsonandschemas/tri-net-api-v1.json-- PASSRepoIdentityandminimal valid NMSE manifest both validate against their schemas -- PASS
bf16_subnormal_policyfrom theNMSE manifest correctly fails validation -- PASS
L3 PURITY)./scripts/tri test(full t27c suite) -- not run locally (nocargo in env). CI is authoritative.
Non-claims (R5-HONEST)
Caveats
./scripts/tri testwas not run locally because the environment lackscargo; CI must verify.arrows) in existing NOW.md ledger entries; this PR keeps the
existing entries verbatim and only writes pure-ASCII content in the
new entries and new files, matching the strictly-ASCII profile of
STATUS.md,LINEUP.md,FORMAT_REGISTRY.md,COMPETITORS.md,BENCHMARKS.md, andCLARA_TRACEABILITY.md.Closes #696