Capability register · reviewed 2026-08-23
What works today. And where it stops.
6 capabilities sit on the public register. Each row states the scope it covers, the limit it does not cross, and the evidence behind its status.
- Rows on the capability register 6 rows
- Implemented, inside the stated scope 5 rows
- Roadmap, not a product capability 1 row
- Rows carrying a dated receipt 4 of 6
“What can we rely on today?”
Implemented, inside the stated scope
5 of 6capabilities
| Capability | Lifecycle | Evidence |
|---|---|---|
| Self-hosted memory store | Implemented | Verified 2026-07-14 |
| Named agent surfaces | Implemented | Verified 2026-07-28 |
| Supersession and addressable history | Implemented | Verified 2026-07-14 |
| Principal and scoped access controls | Implemented | Verified 2026-07-14 |
| Typed N-ary relationships and graph traversal | Implemented | Scope differs · reviewed 2026-08-23 |
| Automated causal discovery | Roadmap | Roadmap |
Every field on this page renders from capabilities-public.json at build time
- Capabilities
- 6
- Implemented
- 5
- Experimental
- 0
- Roadmap
- 1
- Dated receipts
- 4
Counted from capabilities-public.json at build time · reviewed 2026-08-23
01 · Lifecycle
Three states. One meaning each.
A state says how far a capability got, not how useful it is. Solid amber means a dated receipt stands behind the row. Dashed means in build: the work exists, the receipt does not.
Implemented
5 of 6
In source and tests, inside the scope the row states.
- Self-hosted memory store
- Named agent surfaces
- Supersession and addressable history
- Principal and scoped access controls
- Typed N-ary relationships and graph traversal
Experimental
0 of 6
In build. The work runs, no dated receipt stands behind it yet.
- No rows listed in this state
Roadmap
1 of 6
A direction. Not a current product capability, and not a date.
- Automated causal discovery
02 · The register
Each row states its scope. And what it does not cover.
Rows are manually reviewed and statically validated; source changes can still make a row stale. Public release references remain pending.
| Capability and scope | Evidence | Reviewed |
|---|---|---|
| Self-hosted memory store The default self-hosted product path keeps stored product data on operator-controlled machines. Limit Implemented in ax0s-memory 0.5.0; a public release record is pending. The scope applies to default product storage, not optional product egress or website services. | Verified 2026-07-14 | 2026-07-14 |
| Named agent surfaces One bounded same-store write-and-recall check was verified on 2026-07-28 across the four named configured surfaces. Limit Not simultaneous, continuous runtime, endorsement, or current health; provider identity per leg comes from the operating surface and store-side source stamp. | Verified 2026-07-28 | 2026-08-23 |
| Supersession and addressable history Stale facts can be superseded without deletion, and superseded history remains addressable. Limit Implemented and test-covered in ax0s-memory 0.5.0, with one recorded 2026-07-14 product round trip; a public release record is pending. This row does not claim that every contradiction is resolved automatically. | Verified 2026-07-14 | 2026-07-14 |
| Principal and scoped access controls Per-principal tokens and slug/capability grants, expiry, revocation, rate limits, default-deny enforcement, and access-audit records are implemented; record-level authorization, hardened multi-tenant isolation, and externally validated identity controls are not established. Limit Record-level authorization, hardened multi-tenant isolation, and externally validated identity controls are not established. Legacy shared-bearer compatibility remains until registry cutover. | Verified 2026-07-14 | 2026-07-14 |
| Typed N-ary relationships and graph traversal Typed N-ary relationships, role-bearing participants, fabric entities, one-hop expansion, and multi-hop graph walk for declared connector facts. Limit This capability review is narrower than the broader live-unified-fabric claim, which remains In build. It does not claim full connector migration, automatic causal discovery, or a public graph visualization product. | Scope differs · reviewed 2026-08-23 Capability scope: Typed N-ary relationships and graph traversal | 2026-08-23 |
No rows listed in this state.
| Capability and scope | Evidence | Reviewed |
|---|---|---|
| Automated causal discovery Research work only; it is not a current product capability. Limit Automated causal discovery is not available in the current product. | Roadmap | 2026-07-14 |
03 · Boundaries
What each limit costs you.
A limit only matters when it changes what you do. Each row names the consequence, the safe way around it, and the gate that would move it.
- 01
Self-hosted memory store
Verified 2026-07-14- Consequence
- The operator is responsible for the machines that run and retain the memory store.
- Safe workaround
- Review optional product egress and website egress separately before deployment.
- Next gate
- Publish a release record with date, artifact, supported environments, interface contract, and acceptance receipt.
- 02
Named agent surfaces
Verified 2026-07-28- Consequence
- The receipt applies only to the named bounded checks.
- Safe workaround
- Validate the selected path in the operator environment before relying on it.
- Next gate
- Publish a refreshed dated receipt when the configured surface or scope changes.
- 03
Supersession and addressable history
Verified 2026-07-14- Consequence
- A correction can become current while the prior record remains available for inspection.
- Safe workaround
- Inspect the addressable history when the prior state matters.
- Next gate
- Publish a release record and broader compatibility, concurrency, and durability receipts.
- 04
Principal and scoped access controls
Verified 2026-07-14- Consequence
- Do not rely on the current product where record-level authorization, hardened tenant isolation, or externally validated identity controls are required.
- Safe workaround
- No public workaround is claimed for the unestablished controls.
- Next gate
- Publish record-level authorization, tenant-isolation, and external identity-validation artifacts before extending this scope.
- 05
Typed N-ary relationships and graph traversal
Scope differs · reviewed 2026-08-23- Consequence
- Current workflows can use declared relationships and traversal within the stated capability-review scope, but must not infer completion of the broader unified fabric.
- Safe workaround
- Treat the capability row as a scoped review and the broader unified-fabric claim as In build.
- Next gate
- Publish a bounded traversal receipt on an allowed public claim surface before replacing this scope-difference label.
- 06
Automated causal discovery
Roadmap- Consequence
- Current workflows must not depend on automated causal discovery.
- Safe workaround
- Use only the implemented memory, typed relationships, and graph traversal described in this matrix.
- Next gate
- Publish an approved implementation artifact before changing the lifecycle state.
Behind the statuses