the soft3 stack
the component registry: every repo, its verb, its release, its role. soft3 is the cyber component of the cybics WORK triad — and internally it unfolds the same seven-triad spiral that cybics uses for all knowledge. form defines the primitive rules. mass is what knowledge is literally made of. space is where it exists at scale. life is where it becomes intelligent. word is what it means. work is how it runs. play is where we act together. each group earns its place: remove any one and a class of reasoning becomes impossible.
| repo |
verb |
release |
what it does |
| honeycrisp |
accelerate |
— |
NEON/AMX/SME · Metal GPU · ANE · zero-copy unimem |
| strata |
math |
— |
nebu 𝔽_p · genies 𝔽_q · jali R_q |
| hemera |
hash |
v0.2.0 |
Poseidon2 sponge · identity · trees · verified streaming |
| lens |
commit |
— |
5 PCS backends, one per algebra |
| repo |
verb |
release |
what it does |
| cybergraph |
link |
— |
jets · memos · types · knowledge |
| bbg |
store |
— |
1 polynomial · 10 dims · ~200B proofs |
| cell |
hold |
— |
local node · graph slice · signal chain · apply/prove loop |
| fs |
mount |
— |
particles · patches · sync |
| tok |
pay |
— |
Coin · Card · conservation |
| repo |
verb |
release |
what it does |
| mudra |
encrypt |
— |
KEM · dCTIDH · AEAD · TFHE · threshold |
| radio |
transmit |
— |
QUIC · BAO streaming · gossip |
| tape |
frame |
— |
typed particle framing over any byte stream |
| foculus |
sync |
— |
chain · VDF · equivocation · DAS · erasure · CRDT |
| ward |
authorize |
spec |
effect router · emit/query/link/seal/host |
| repo |
verb |
release |
what it does |
| neural |
mean |
— |
sigil → word → link → sentence → motif → dialect |
| rune |
eval |
— |
Rs · hint · host · eval · async |
| inf |
query |
— |
datalog · fixed-point over BBG |
| repo |
verb |
release |
what it does |
| trident |
compile |
v0.1.0 |
.tri → .nox |
| nox |
run |
— |
18 patterns + jets · unconditional proof |
| wysm |
sandbox |
— |
WASM souls · gas-metered · cond/host |
| glia |
infer |
— |
.model runtime · cond/model |
| kern |
shade |
— |
Metal/Vulkan/WebGPU shaders · cond/host |
| zheng |
prove |
— |
SuperSpartan · Brakedown · sumcheck |
| eidos |
certify |
— |
CIC type-checker · theorem → cyberlink |
| repo |
verb |
release |
what it does |
| mir |
render |
— |
positions + features → R-1.0 world |
| prysm |
paint |
— |
tape dialect · chunks → UI |
| cyb |
embody |
— |
Bevy worlds · terminal · live cells |
| lytics |
measure |
— |
signed visitor events · PoW-priced · retention · cohorts · funnels |
stability
| repo |
verb |
release |
what it does |
| conformance |
snapshot |
scaffold |
hemera fingerprint per encoding · stability harness |
the four runtimes in work — nox · glia · wysm · kern — form a proof-contract ladder from unconditional down to conditional-on-host; the long-term arc lowers every soul toward nox through trident LIR. kern wraps wgpu into an authored component; nu (vendored Nushell) is the external piece outside the authored-verb table. the boundary analysis for the network tier lives in component-boundaries.
the SDK
| dir |
what |
status |
| js/ |
JavaScript/TypeScript SDK (current Bostrom chain) |
active |
| schema/ |
canonical wire format definitions |
draft |
| cli/ |
soft3 command-line tool |
scaffold |
| mcp/ |
MCP server — cybergraph tools for AI assistants |
scaffold |
| py/ |
Python SDK |
scaffold |
every SDK exposes the same five operations regardless of language:
particle(content) → particle hemera hash of bytes
cyberlink(from, to, neuron) → signal construct + sign a cyberlink
query(particle, dimension) → value+proof BBG Lens opening
verify(root, proof) → bool proof verification
submit(signal) → receipt send signal to network
import { CyberClient } from '@cybercongress/cyber-js'
const client = await CyberClient.connect('https://rpc.bostrom.cybernode.ai')
const result = await client.rank.search('cyber')
dependencies not yet stabilised — full implementation is blocked on wire format finalisation (schema/), BBG proof serialisation (lens Commitment/Opening serde), and the query RPC protocol. the scaffold is in place; implementations land per component as deps stabilise.
see the whitepaper for the foundations — the methods behind one mind, many languages, open world.