You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No Linux in compute core. The FPGA node is a bare RTL computer: packet fabric, GF16/ternary compute tiles, receipt engine, host/mesh ingress. No Linux, no soft CPU, no AXI/IP Integrator in the core path.
No new hardware multipliers. Do not introduce arithmetic * in synthesizable RTL. Existing legacy gf16_mul.v is tolerated only as pre-existing substrate; new ternary/GF16 mesh logic must be XOR/popcount/add/FSM/ready-valid only.
USB-3 is a boundary, not a processor. Use FT60x-style FIFO boundary for host streaming/programming/readout. Do not pull in vendor black-box IP.
Mesh is off-chip at G1/G2. Radio/Wi-Fi/LoRa/Ethernet modules feed packets into FPGA ingress. FPGA does not implement LoRa/Wi-Fi PHY in this mission.
TRI settlement is off-chip at G1/G2. FPGA emits deterministic compute receipts; token accounting/verifier/network settlement are separate layers.
R5 honesty. Do not claim “Helium competitor complete” until at least two physical nodes exchange jobs and receipts over an external mesh/backhaul.
1. Background
tt-trinity-gf16 was originally a combinational GF16 dot4 demonstrator. PR #2 upgrades it into a CPU-less RTL packet fabric v0: host FSM, 2x2 tile fabric, four gf16_dot4 tiles, packetized LOAD_A, LOAD_B, COMPUTE, READ_RES, and RESULT output. The new DePIN extension adds docs/TRINITY_DEPIN_NODE.md, trinity_usb3_fifo_bridge.v, trinity_mesh_adapter_stub.v, and receipt constants without touching TT die pinout.
The product target is a Trinity node: an FPGA that can be programmed/streamed through USB-3, joined to a physical mesh/backhaul, execute Trinity GF16/ternary compute jobs, and emit receipts that can later be settled in TRI. This competes with the incentive pattern of Helium, but changes the unit of value from wireless coverage only to useful ternary compute plus mesh transport.
2. Hypothesis
H1: A Trinity FPGA node can act as a CPU-less packet-compute endpoint if a PC sends one 32-bit job packet stream over USB-3 FIFO, the FPGA routes it through the on-chip mesh to a GF16/ternary tile, and returns a deterministic RESULT/RECEIPT packet without Linux, soft CPU, or AXI.
Falsification witness: H1 is false if any G1 loopback run cannot reproduce the canonical result 0x47C0 through the packet path, or if the path requires Linux/soft CPU/AXI/new arithmetic multipliers inside the compute core.
3. Mission Scope
In Scope
Implement and validate a USB-3 FIFO boundary for Trinity 32-bit packets.
The FPGA must see both USB and mesh as packet sources. The packet protocol is the stable boundary; the future Trinity CPU can later replace trinity_master_fsm or act as another packet master without changing tile interfaces.
7. Packet and Receipt Contract
Base packet format:
[31:28] op
[27:26] dst
[25:24] src
[23:20] lane
[19:16] reserved
[15:0] payload
Receipt extension:
Field
Width
Purpose
compute_job_id
16
Job identity from host/network
tile_id
2
Tile that executed job
op_code
4
GF16/ternary operation
result
16
Computed result
nonce
16
Replay resistance placeholder
checksum
8
Lightweight integrity placeholder
G4 must replace checksum placeholder with a real verifier contract. Until then, receipts are deterministic engineering artifacts, not final TRI payment proofs.
🎯 ONE SHOT — TRINITY TERNARY INTERNET NODE
Mission Codename:
TRI-NET-G1Owner Repo:
gHashTag/trinity-fpgaImplementation Repo:
gHashTag/tt-trinity-gf16Parent EPIC: #19
AGI Layer: gHashTag/t27#583
Base PR: gHashTag/tt-trinity-gf16#2
Base Branch:
feat/trinity-mesh-v0Current HEAD:
702559bPriority:
P0Mission Type: FPGA / RTL / DePIN / USB-3 / Mesh
Anchor:
phi^2 + phi^-2 = 30. Hard Rules
*in synthesizable RTL. Existing legacygf16_mul.vis tolerated only as pre-existing substrate; new ternary/GF16 mesh logic must be XOR/popcount/add/FSM/ready-valid only.1. Background
tt-trinity-gf16was originally a combinational GF16 dot4 demonstrator. PR #2 upgrades it into a CPU-less RTL packet fabric v0: host FSM, 2x2 tile fabric, fourgf16_dot4tiles, packetizedLOAD_A,LOAD_B,COMPUTE,READ_RES, and RESULT output. The new DePIN extension addsdocs/TRINITY_DEPIN_NODE.md,trinity_usb3_fifo_bridge.v,trinity_mesh_adapter_stub.v, and receipt constants without touching TT die pinout.The product target is a Trinity node: an FPGA that can be programmed/streamed through USB-3, joined to a physical mesh/backhaul, execute Trinity GF16/ternary compute jobs, and emit receipts that can later be settled in TRI. This competes with the incentive pattern of Helium, but changes the unit of value from wireless coverage only to useful ternary compute plus mesh transport.
2. Hypothesis
H1: A Trinity FPGA node can act as a CPU-less packet-compute endpoint if a PC sends one 32-bit job packet stream over USB-3 FIFO, the FPGA routes it through the on-chip mesh to a GF16/ternary tile, and returns a deterministic RESULT/RECEIPT packet without Linux, soft CPU, or AXI.
Falsification witness: H1 is false if any G1 loopback run cannot reproduce the canonical result
0x47C0through the packet path, or if the path requires Linux/soft CPU/AXI/new arithmetic multipliers inside the compute core.3. Mission Scope
In Scope
Out of Scope
gf16_dot4with full ternary matmul unless G1 is already green.4. Lane Map
feat/trinity-mesh-v0green CItrinity_usb3_fifo_bridgewired to board-top0x47C0LOAD_A/LOAD_B/COMPUTE/READ_RES5. Pre-Registration
0x47C0from FPGA packet path6. Technical Architecture
External mesh is parallel to USB host ingress:
The FPGA must see both USB and mesh as packet sources. The packet protocol is the stable boundary; the future Trinity CPU can later replace
trinity_master_fsmor act as another packet master without changing tile interfaces.7. Packet and Receipt Contract
Base packet format:
Receipt extension:
compute_job_idtile_idop_coderesultnoncechecksumG4 must replace checksum placeholder with a real verifier contract. Until then, receipts are deterministic engineering artifacts, not final TRI payment proofs.
8. Quality Gates
gdsgreen, no failing checks0x47C0No gate may be marked green from intention. Each gate requires logs, commit SHA, and a repeatable command or hardware test recipe.
9. Implementation Orders
Order A — Close PR #2
Order B — G1 USB-3 FIFO Loopback
boards/qmtech_a100t/top_usb3_loopback.v.Order C — G2 Host Packet Tool
{"job_id":1,"tile_id":0,"op":"GF16_DOT4","expected":"0x47C0","observed":"0x47C0","status":"pass"}Order D — G3 Mesh Adapter
Order E — G4 TRI Receipt Verifier
10. Forbidden Actions
11. Active Artifacts
feat/trinity-mesh-v0702559bsrc/trinity_packet.vhsrc/trinity_gf16_tile.vsrc/trinity_router_2x2.vsrc/trinity_mesh_2x2.vsrc/trinity_master_fsm.vdocs/TRINITY_DEPIN_NODE.mdsrc/trinity_usb3_fifo_bridge.vsrc/trinity_mesh_adapter_stub.v12. GO / NO-GO Poll
Final Call:
GO for G1 USB-3 loopback; HOLD for product/custom PCB until G1/G2 pass.13. Battle Cry
Coq anchors it. FPGA routes it. USB-3 feeds it. Mesh carries it. TRI pays only for receipts.
phi^2 + phi^-2 = 3 · TRINITY TERNARY INTERNET · NO LINUX IN THE CORE