Partner access
What runs in ONIOKO products today, what is prepared as partner contract, and what is open to partners. Read from the contract files, not written by hand.
ONIOKO's technology runs in production inside ONIOKO products today: Perception, Memory, sessions and consent handling. This page tracks a different question: Which parts of that technology are opened to partners through the public contract. Numbers and states come from public-api/STATUS.json, synced from the platform layer. When a resource opens, its operations lose their banner in the API reference and the counters change.
How to read the labels
| Label | Meaning |
|---|---|
| Open to partners | Part of the public contract. Partners call it today. Covered by the version policy. |
| In preparation | Code and contract exist, verified in CI. Partner keys are not issued for it yet. The contract can still change. Pages in the reference carry a banner. |
| Runs in products | The capability runs inside ONIOKO products. A partner contract for it has not been opened yet. |
| Planned | Defined as a partner resource. Does not exist as a partner capability yet. |
| Internal | Exists in the code and is deliberately not part of the public contract. |
Why a product can be live while partner access is 0
A partner contract is more than a working route. Before a resource opens, the platform guarantees for it: tenant isolation, scoped keys, consent enforcement on every call, rate limits, idempotent writes, documented error states and a rollback path. Products inside ONIOKO run on the same technology under one roof and do not need that boundary. Partners do. The boundary is built first, then the door opens.
Release order
- Subjects and consent, Sessions, Perception. Contract prepared, in preparation.
- Memory. Runs in products, partner contract after step 1.
- Export and deletion, Events.
The order follows one rule: nothing may be perceived or remembered on behalf of a partner before consent exists as a contract.
Open questions tracked here
- On-device: which parts of Perception and Memory can run without the cloud. Decides variant B in the robot flow chart.
- Sandbox: a separate environment with its own keys. Planned.
- Data location and subprocessors: fixed per contract; the public summary follows once the first contract is signed.
Changelog
A changelog starts with the first resource that opens to partners. Until then there is no release to list, and this page is the single source of the current state.