SENEX documentation
SENEX Intelligent Chain is a human-owned intelligence ecosystem. Personal AIA (AIA — Artificial Intelligent Assistant) software works with owner-approved context on the owner's own devices. Future network components are intended to let independently owned agents cooperate under each data owner's control, and to recognize the value that data and computation actually contribute.
SENEX is a local-first desktop foundation under active development. The current milestone is M0 — Trust foundations: every public statement must match the software, keys must be protected by default, and the full test suite must pass. There is no public network yet, and ASHA exists in the software only as simulated accounting. See Current status.
Product direction
| Horizon | Purpose | Status |
|---|---|---|
| AIA foundation | A private, controllable assistant that works with the owner's local context | Working foundation |
| Proof of Data kernel | Governed data access across owners, with value measured at the moment data is used | Research direction |
| V1-testnet | The complete V1 product and protocol, run as a production candidate with test-only ASHA | V1-testnet target |
| V1 | The planned production network, launched from a fresh genesis only after V1-testnet evidence and external review | External validation required |
| GENOME | Collective intelligence formed by connected agents, governed data, computation, proofs, and outcomes | Research direction |
V1 is one integrated product: desktop, mobile, wallet and devices, governed data, local inference, networking, proofs, a permissioned contribution chain, accounting, marketplace, security, operations, and release. No single component is the product on its own, and no milestone exit is a V1 claim.
Design principles
- Local first: sensitive context stays in the owner's environment unless the owner authorizes a specific exchange.
- Owner governs every hop: when one agent asks another, each data owner on the path decides what may be used.
- Explicit purpose: a request states what is needed, why, and what result will be returned.
- Minimum disclosure: cooperation uses the smallest useful amount of information.
- Revocable control: ongoing permissions are visible and removable.
- Proof before value: contribution is recognized only after it has been verified.
- Verifiable progress: roadmap language is not a substitute for implementation evidence, testing, or independent assessment.
Security, privacy, performance, governance, and economic claims remain subject to independent testing and review. No page in these docs should be read as a certification, a formal privacy guarantee, a financial offer, or an assurance that a production launch will occur.
Explore the documentation
- Current status: what works today, what is partial, and what is simulated.
- Key concepts: AIA, GENOME, ASHA, V1-testnet, V1, and the other terms these docs use.
- Roadmap: milestones M0 to M5 and the evidence each must produce.
- Architecture overview: trust boundaries between AIA, the network, and GENOME.
- Wallet, devices, and contribution roles: one owner wallet, many devices, and contribution roles.
- Privacy and security: user controls, data flows, threats, and assurance limits.
- Proof of Data: the research thesis and how each hypothesis will be tested.
- ASHA and contribution accounting: how contribution is accounted for today and what gates stand before any live use.
The SENEX whitepaper
The current edition of the SENEX whitepaper is Edition 2026.1 (September 2026), published on senexic.com. These docs track the software as it is; where they differ from the whitepaper on what exists today, Current status is the reference.
These public docs explain outcomes, trust boundaries, and status. They intentionally leave out implementation details that could weaken security or enable reconstruction.