Principles

The commitments we are building into the software platform and the commons layer around it. If we drift, tell us.

Preserve attentionHelp people think without capturing their time.
Public structureMake shared memory inspectable and correctable.
Start on deviceKeep private work local by default.
Clear red linesName the directions Syxon refuses.
Evolve in publicPublish major decisions and changes where possible.
Attention promise

1. Preserve attention

Syxon is built to help you think, not to capture your time.

  • No infinite feed. Spaces and fracta should stay navigable, not addictive.
  • When something shows up, you should be able to see where it came from.
  • Sessions are finite. “Done for now” is a first‑class action.
  • We prefer calm visuals and keyboard‑first flows over constant motion.

Explainable outcomes

When Emerga or any local model influences what you see, you should be able to understand why.

  • If we rank items, we show the main reasons in plain language.
  • Assists and decision briefs should keep sources and uncertainty when it matters.
  • We treat unexplained automation as a bug, not a feature.

Proofs, not slogans

Big claims should come with things you can inspect and measure, including the public proof surfaces in Ion Commons/Xray.

  • Measure time‑to‑first‑useful and minutes saved in real workflows (opt‑in).
  • Publish honest ranges instead of vanity charts.
  • Ship demos you can inspect.
Ownership & governance

2. Public memory needs public structure

If we build a shared layer, it should benefit the people who maintain it, and it should move toward Ion Commons ownership and governance rather than only company control.

  • Claims, corrections, votes, and challenges should be explicit objects, not invisible moderation.
  • Attestation should be a simple civic verb used across multiple governance regimes.
  • Credit, reputation, and eventual upside should come from useful contribution.

Open does not mean reckless or vague. Ion Commons is the decentralized, federated, open, and inspectable stewardship path around the shared layer; the first public source promises are the shell Ion, protocol/app structure, public records, and governance-facing surfaces. We should not claim every Syxon internal system is open source before it is actually clean enough to release.

How decisions scale

Bigger decisions require more consensus.

  • Low‑risk fixes, like obvious dedupe, can move fast.
  • High‑risk changes (like policy and safety) require stronger thresholds.
  • Founders keep narrow reserve powers for security, privacy, and legal obligations—with public explanations where possible.
Privacy by default

3. Start on your device

We assume your work belongs on your device first. Cloud is an optional extension, not the default.

  • By default, capture, save, search, and private ion authoring run on your device.
  • Cloud help is explicit, redacted, and opt‑in. The UI shows when something leaves your device.
  • Encrypted backups are optional, with keys kept separate from stored data.
  • Telemetry is opt‑in, minimal, and never includes content.
  • When there’s a tradeoff, we prefer slower but local and explainable over faster but opaque.

Memora posture

Hardware should narrow risk, not become another wearable extraction surface.

  • Memora is being designed as an encrypted archive, consent gate, trust token, and identity wallet, in that order.
  • Private keys should not be exportable, and broad archive extraction should be the hardest operation.
  • Verified software interprets intent; the user's intent remains the highest authority.
What We Won't Do

4. Clear red lines

There are directions we choose not to take, even if they might be profitable.

  • No dark patterns to drive engagement (no infinite feeds, no fake urgency).
  • No selling or trading of personal data.
  • No hidden content‑level telemetry or opaque personalization based on things you read or write.
  • No unexplainable ranking modes. If we cannot explain it, we should not ship it.
  • No token-plutocracy dressed up as governance.
Evolution

5. Evolving in public

These principles will need to evolve as Syxon grows and as the world around us changes.

  • We will record major product and governance decisions in Ion Commons public notes where possible.
  • We will refine governance with real use, not with fantasy constitutions.
  • If we override the usual rules for safety or legal reasons, we will say so and aim to restore normal operation quickly.

How to hold us to this

If the point should be private product feedback, use the site feedback form or email us. If it should be public and reviewable, raise it through Ion Commons.

Private feedback Raise a public point Inspect public records principles@syxon.org

Last reviewed: May 13, 2026.

← Back to Syxon