an axiarium platform · access layer
one console for every product we build.
Axordium is the layer that sits in front of Axiarium's products: a single sign-in, a tree scoped to exactly what each person is allowed to open, and a record of who saw what.
- identityONE ACCOUNT, EMAIL SIGN-IN
- visibilitySCOPED BY ROLE
- revocationNO REDEPLOY
- recordSERVER-SIDE AUDIT TRAIL
- 09:12:04openchargeback win probabilitygranted · read and run
- 09:12:19grantcontract renewal trackergranted · read only
- 09:13:02denyeverything else in the estatenot granted — not listed
access on record
01 — what it is
an access layer, not another product.
Axordium does not analyse anything. It decides who may open what, and keeps the record.
does
Holds one sign-in for the whole portfolio, renders a tree scoped to each person's grants, puts each product behind one authenticated address, and records every launch. Adding a product is a registry entry and a reviewed change — not a new auth decision taken from scratch.
does not
It does not build use cases, route between them with a model, or reach into their data. Each product keeps its own logic and its own database; to Axordium they are opaque. There is no cross-product data sharing and no shared data model.
access is granted by axiarium, not by signup. there is no self-service tier today.
02 — how it works
onboard. grant. open.
Three steps, each one reviewable, none of them requiring a product's code to change.
The product declares itself in a manifest and is registered against an owning domain
A route exists; nobody can reach it yet
A named person is given a role scoped to that product, or to a whole domain
It appears in their tree, and in nobody else's
They sign in once and launch it from the console
A scoped, time-limited session — and an audit entry
revoking reverses step 2 alone. no redeploy, no change to the product.
03 — access & control
built so that access can be proven, not asserted.
The same standard Axiarium applies to its numbers, applied to its permissions.
least privilege by default
Nothing is visible until it is granted. A role is scoped to a product or to a domain, never global by accident, and the console tree is pruned to match before it is ever rendered.
- seven fixed roles, including a view-only auditor
- a product still in draft is not listed, even to an admin's grantees
- grants are revocable in place
an audit trail that is the record
Grants, revocations, onboarding approvals and sign-ins are written to a server-side audit table, and every launch is recorded against the person who made it. The auditor role reads that trail and holds no launch, grant, reseed or deploy rights anywhere — the point is that someone can check without being able to alter what they are checking.
- who opened what, and when
- read-only access is a real role, not an honour system
- the token that opens a product expires in minutes and is re-minted, not held open
04 — status
in build. stated plainly.
Axordium is an Axiarium platform under active construction. The console runs, the access model is implemented and covered by an automated test suite, and it is being used to front Axiarium's own products first.
8 use cases run today on the console.
It is not open for self-service signup, and access today is granted directly by Axiarium.