soft3 status

the component registry and its honest state: every repo, its verb, its release, and where it actually stands. 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 component is in one of six states. live — carries real traffic today. published — released and correct, but not yet in the live loop. unwired — built, released, and not connected to the thing that needs it. spec — paper only. dormant — no commits in months while holding a named seat. blocked — waiting on another component's gap.

the stack has a heart, and products grow on its skin. at the centre sits the trinity the whole stack exists to turn: cyb the body, cyber the mind, cyberia the state — a cycle (bodies feed the mind, the mind guides the state, citizens embody). they are not seats in the registry; the registry is what they are made of. listing cyb inside the stack it depends on was a structural error, corrected 2026-09-02. lytics however IS a seat — measurement is how cybernetics closes its loop — and returned to play. the stack's own top-tier seats are cell (hold), ward (authorize), vault (keep) and sigma (evaluate). the full interaction graph, with every concrete input and output, is drawn at soft3.org/chart; the boundary rule and the loop — four motions, two guarantees, one attractor, every verb from this table — live in crystallization and are drawn at soft3.org/scheme.

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 layered map and the five architectural gaps live in stack-completeness; the network-tier borders in component-boundaries.

the verdict

the stack is complete in principle and peer-pair in fact. lytics remains the strongest single-node evidence: cybergraph + bbg + hemera + mudra + inf holding real, adversarial-facing traffic in production. and as of 2026-09-01 the wire exists, and the graph routes it: cy wire up converges cells over radio QUIC with no cybernode between them — and following is a cyberlink. FOLLOW → neuron on my chain is the subscription; ANTENNA → endpoint and SOCKET → ip:port on a node's own chain are its address record; the wire obeys those links, syncing exactly the followed chains and dialing any followed neuron whose antenna the cell holds. proven with three nodes on one machine: a cell that knew only one peer followed a stranger's neuron, received its chain through the friend, unpacked the address from graph content, and dialed the stranger directly — discovery, subscription and routing as signals, replicated by the mechanism they route.

milestone №1 is crossed in its first form; the next three are named: the same wire across two machines (relay / hole-punching, which radio already carries); gossip beyond a pair (fan-out is foculus's reconciliation seat, not a pair's rebroadcast); and the cyb shell app speaking the protocol its own cy already speaks — with mudra keys instead of endpoint-derived neurons. the fork-choice has still never chosen a fork; that remains foculus's unproven half.

critical, and out of scope

seven questions no roadmap in the stack currently owns. each one is ignorable today and existential at the first real scale.

1. the economics of writing. φ* ranks particles, but who may write, and at what cost? lytics prices a signal at 0.042 s of PoW — one app's local answer. an open cybergraph with free writes drowns in spam on day one. tok is published; a live economy, and the bridge from the bostrom snapshot to it, is nowhere.
2. key lifecycle. mudra derives and claims; nothing recovers, rotates, or revokes. a lost seed is a lost neuron forever, and one person on two devices is formally two neurons. for a state whose citizens are keys, identity loss is not a bug — it is a constitutional crisis without a constitution.
3. protocol upgrade. foculus's parameters are derived and documented; the procedure for changing them on a running network does not exist. a hard fork of a φ*-converged network is undefined behavior.
4. deletion and liability. an append-only content-addressed graph will be handed illegal bytes — every such network has been. right-to-be-forgotten versus content addressing, moderation versus censorship: the hardest political question, currently unasked.
5. storage economics. state grows forever; bbg makes reads provable but gives nobody a reason to hold the bytes. a filecoin-shaped hole between bbg and tok.
6. adversarial audit. the consensus theorem is conditional, the truth-serum unaudited, and mudra's cryptography is self-built. before real value moves, someone paid to break it must try. no roadmap budgets this.
7. operations. one duplicated launchd job recently ate the strongest dev machine for hours. a network of nodes needs health, metrics and alerting as protocol citizens, not as an afterthought — networks die of boring things.

the SDK

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.