neural/trident/docs.md

πŸ”± Trident Documentation

← Project Root

Organized following the Diataxis framework: tutorials, how-to guides, reference, and explanation.


πŸŽ“ Tutorials: learning-oriented

The Builder's Journey β€” six chapters that build one complete private application, from a four-line proof to a sovereign DAO.

# Document You Build
1 Prove a Secret A hash-locked proof β€” the primitive behind everything else
2 Build a Coin A private token with pay, mint, and burn
3 Build a Name Service An ENS-like registry of unique assets
4 Build a Liquidity Strategy A constant-product AMM for TIDE
5 Auction Names with Hidden Bids A Vickrey auction β€” sealed bids, honest pricing
6 Upgrade to a DAO Private coin-weighted voting that governs the name service

Foundations

Document Description
Tutorial Language walkthrough β€” types, functions, modules, inline asm

πŸ”§ Guides: task-oriented

Document Description
Compiling a Program Build, check, cost analysis
Running a Program Execute, test, debug
Deploying a Program Neptune scripts, multi-target deployment
Generating Proofs Execution trace to STARK proof
Verifying Proofs Proof checking, on-chain verification
Optimization Cost reduction strategies
Prompt Templates AI-assisted development prompts

πŸ“– Reference: information-oriented

Document Description
Language Reference Types, operators, builtins, sponge, Merkle, proof composition
Grammar (EBNF) Complete formal specification
IR Design TIR operations, tiers, lowering
Target Reference OS model, target profiles, cost models
VM Reference Virtual machine architecture
OS Reference Operating system model
Standard Library std.* module reference
CLI Reference Command-line interface
Error Catalog Every error message explained
Agent Briefing Compact format for AI code generation

Per-target documentation lives alongside its config:

πŸ’‘ Explanation: understanding-oriented

Document Description
Vision Three revolutions, one field β€” why Trident exists
Multi-Target Compilation One source, every chain
Programming Model Execution model, OS abstraction, six concerns
How STARK Proofs Work From traces to quantum-safe proofs
Provable Computing Comparative analysis of ZK systems
Formal Verification Symbolic execution, SMT, invariant synthesis
Content-Addressed Code Hashing, caching, registry, equivalence
The Gold Standard PLUMB framework, TSP-1 (Coin), TSP-2 (Card)
Skill Library 23 composable token capabilities
For Offchain Devs Zero-knowledge from scratch
For Onchain Devs Mental model migration from Solidity/Anchor/CosmWasm
Privacy The privacy trilateral: ZK + FHE + MPC over one field
Quantum Computing Why prime field arithmetic is quantum-native
Verifiable AI Why the next generation of zkML starts from prime fields
Cyber License Don't trust. Don't fear. Don't beg.

πŸ—ΊοΈ Project

Document Description
Development Plan Roadmap and status

Folder

Homonyms

cyb/docs
docs
soft3/mir/docs
docs
neural/rs/docs
docs
soft3/cybergraph/docs
cybergraph a knowledge graph where every change is a proven computation. not "someone wrote a fact and we trust them," and not "a contract moved tokens and we re-execute to check." instead: a neuron declares what it will do, runs it, and publishes a proof that it did exactly that β€” and anyone…
soft3/hemera/docs
Hemera documentation explanation why Hemera works the way it does β€” design decisions and rationale. see explanation/ for the full index. guides task-oriented how-tos (phase 2 β€” not yet written). cli.md β€” hash files, check sums, encode/decode streams streaming.md β€” verified streaming for large files…
soft3/foculus/docs
docs
soft3/tru/docs
tru docs teaching and explanation for tru β€” the convergence VM. the normative contracts live in [specs/](/soft3/tru/specs); this tree explains and references them, it never duplicates them. explanation why tru works the way it does β€” narrative, derivations, background. see…
cyb/cyb/docs
docs
warriors/trisha/docs
Trisha documentation explanation why Trisha works the way it does β€” design decisions and rationale. architecture β€” how trisha fits in the soft3 stack gpu-backend β€” seven shaders, one pipeline, Metal/Vulkan/DX12 proof-file-format β€” TOML envelope + bincode proof bytes patching β€” vendor patching…
soft3/radio/docs
docs
cyb/wysm/docs
docs
soft3/nox/docs
docs
bootloader/space-pussy/docs
Documentation [WIP] Contents 1. **[Run validator guide](/bootloader/space-pussy/docs/run-validator)** 2. **[Use CLI guide](/bootloader/space-pussy/docs/ultimate-commands-guide)** 3. **[Setup daemon config guide](/bootloader/space-pussy/docs/setup-pussy-configuration)** 4. **[Setup local dev…
bootloader/go-cyber/docs
Concepts (WIP) soft2 and soft3 [soft2 and soft3](/bootloader/go-cyber/docs/soft2-soft3-concepts) content from presentation knowledge graph content oracle particle cyberlink neuron consensus computer [cyber-sdk](#cyber-sdk-modules-documentation) resources tendermint abci ibc ikp sequential…
soft3/zheng/docs
docs
soft3/bbg/docs
docs
neural/rune/docs
rune documentation Documentation follows [Diataxis](https://diataxis.fr) β€” four kinds, each serving a different need. The [specs](/neural/rune/specs) are the canonical reference (the fourth quadrant); this directory holds the other three. | | learning | working | |---|---|---| | **practical** |…
neural/inf/docs
inf β€” a whitepaper inf is the language of a provable graph. you ask the cybergraph a question and get an answer; you state a change and the graph takes it. both come with a zheng proof that the result follows from the graph's committed state, and anyone holding the 32-byte graph root checks that…
soft3/glia/docs
docs
cyb/honeycrisp/aruminium/docs
docs/ documentation for humans. three levels of depth. | file | audience | what's inside | |------|----------|--------------| | `tutorial.md` | newcomers | step-by-step first GPU program | | `guide.md` | practitioners | patterns, best practices, real workflows | | `explanations.md` | curious minds…
soft3/strata/kuro/docs
docs
bootloader/go-cyber/client/docs
docs
soft3/strata/jali/docs
docs
soft3/radio/docs/docs
docs eventually-consistent multi-dimensional key-value documents replica a document instance identified by a NamespaceId (public key). contains unlimited entries. the namespace private key grants write authority over the entire document entries and authors an entry is identified by the tuple…
soft3/radio/iroh-willow/docs
docs
cyb/honeycrisp/unimem/docs
docs
soft3/strata/trop/docs
docs
soft3/radio/iroh-blobs/docs
docs
cyb/honeycrisp/acpu/docs
docs
cyb/honeycrisp/rane/docs
docs
bootloader/space-pussy/ts/docs
docs
bootloader/space-pussy/client/docs
docs
soft3/strata/nebu/docs
docs
soft3/strata/genies/docs
docs
soft3/radio/iroh/docs
docs

Graph