One system · two levels of explanation
The whole ship, without the fog.
Syxon is a place to learn across scale, think in connected structures, publish deliberately, and coordinate around public knowledge. These docs explain the five-minute idea first—then let you recurse all the way down to protocols, routes, threat models, and release gates.
The five-minute version
Think privately. Share intentionally. Trust a process, not a popularity score.
Most software collapses private thought, public identity, source material, algorithmic recommendations, and social approval into one feed. Syxon keeps them apart, then makes every transition visible.
Publishing is not a fifth space. It is an explicit doorway from a private local ion in Think to a distinct public artifact with a new global identity.
Public records do not end as posts. They can keep their sources, history, relationships, challenges, witnesses, review, decisions, and later outcomes. The network becomes shared memory with an inspectable public process around it.
Three names, three jobs
Who and what does what?
Syxon
The human interface: Learn, Think, Explore, and Connect. It is the first client for the system.
Ion Commons
The nonprofit steward building the first public infrastructure and constitutional process.
Ion Protocol
The public rules and network: data boundaries, record lifecycles, identity, trust, cases, governance, and replication.
A published ION is one compositional public artifact type inside that architecture. Claims, attestations, cases, findings, policies, and mandates remain distinct public types. Fracta is the scale-aware interface language used to navigate nested structures without losing the larger world.
The shared runtime
One mental model holds the four spaces together.
Think is the mature reference for recursive interaction. Learn keeps its Venn atlas, but inherits the same laws of stable labels, predictable child emergence, orientation, connection traversal, and accessible navigation. The shared shell compresses complexity into finite Next steps, dependable Record details, and an action route that names scope and persistence before action.
The most important boundary
Syxon is not one enormous database.
The system has five planes. Their separation is a security property, not a visual preference.
The public layer
Three structures make the complexity legible.
Shared memory
Ideas, sources, claims, events, proposals, decisions, outcomes, and change through time.
Web of trust
Domain-specific evidence around work, witnesses, disputes, freshness, and concentration—never a score of a human.
Public process
Reply, evidence, field review, live questions, selected assemblies, findings, appeals, and bounded mandates.
The web of trust can help determine who is eligible for a bounded duty. It cannot replace public process, create another civic vote, or turn historic reputation into permanent office.
Choose your depth
Where should I go next?
I want to use Syxon
Learn the four spaces, publishing flow, profiles, Local AI, links, and mobile posture.
Open the product guide →I want the interface model
Understand permissions, current context, views, the Fracta Canvas, connections, Next steps, Record details, and action routes.
Read the runtime guide →I want the whole idea
Read the public contract behind IONs, shared memory, verification, review, and forkable coordination.
Read the protocol guide →I care about trust
See how claims, attestations, track records, capabilities, and anti-capture safeguards fit together.
Explore community trust →I care about accountability
Follow consequential claims and resource requests through evidence, town halls, assemblies, and mandates.
Explore civic cases →I want the system design
Inspect data planes, clients, the Global Server, stores, signatures, AI lanes, and decentralization.
Open architecture →I want the honest status
See what is available, what has a tested foundation, what is designed, and what is forbidden.
Check implementation status →How to read these docs
Status is part of the meaning.
Implemented in the current product or server and covered by proportionate checks.
The substrate, contracts, or routes exist, but the full institution or user journey is not ready.
A documented direction with unresolved engineering, safety, legal, operational, or community work.
A boundary the protocol rejects: universal scoring, paid verdicts, secret AI authority, or automatic resource execution.
The implementation documents inside the repository remain authoritative for exact code behavior. This site translates them; it does not outrank tested reality.
The compact public contract
What the system promises not to blur.
- Your private work does not become public because you wrote it.
- Publishing creates a distinct public record with a visible lifecycle.
- A source, signature, witness, track record, finding, and mandate each mean different things.
- No universal human score, transferable reputation token, paid verdict, or wealth-weighted civic voice.
- AI may organize evidence and prepare questions; accountable humans reach consequential findings.
- Public history should be inspectable, mirrorable, contestable, appealable, and ultimately forkable.