TRUST — OPEN BY DESIGN, ONE SEALED SEAM
In a record, trust is the entire product. So almost all of Askora is open — the binding lifecycle, the state machine, the immutable aska, every grade. Exactly one seam is sealed. This page draws the line precisely, and stays honest about where every claim stops.
THE WITNESS — TRUSTED BECAUSE IT WILL NOT REACH IN
A log records keystrokes. Observability watches a running system so you can fix it — it exists to intervene. A witness does the opposite. It binds the promise before the deed, grades it against the truth when reality resolves, keeps the misses as loudly as the wins — and then refuses to act on what it saw. The thing that grades your record has no hand in how it reads.
So non-intervention is not a limitation to apologize for — it is the whole argument. The witness keeps faith with a thing without touching it; and against every keeping stands its shadow — a reach it refuses, because the reach would undo the keep. Held together and entered neither, they are the charter, and each is stated plainly.
The refusals — the trust charter
Don't fix. Witness.
OPEN BY DESIGN — THE DISCIPLINE IS THE PRODUCT
The binding lifecycle, the state machine, the immutable record, the goal tree and its gates, grades — all of it is open, on purpose. We want customers, auditors, and regulators to see exactly how a commitment is stated, moved through its states, graded, and kept.
A ledger is only worth trusting if you can watch it work, so the mechanics are a selling point, not a secret. The shape of the atomic unit — a commitment, its conditions, the falsifiable test that would prove it wrong, a satisfier pointer, and a grade — is published, because the legibility is the whole pitch.
declared → claimed → satisfying → graded · satisfied · graded · violated · graded · indeterminate · retracted — the lifecycle is open, by design
Openness is the feature.
The record grades every commitment against the truth and has no stake in the verdict — no side to protect, nothing to sell you in the reading. That is what makes the reading worth trusting.
THE DOGFOOD — THE HOUSE'S OWN R&D RUNS ON ASKORA
GRADED · DOGFOODED The grading runs daily on the house's own work — computed from the ledger, not asserted.
Every Vulcora product is planned, built, and graded through Askora — including Askora itself. A unit of work does not start until its intent is bound in falsifiable form; it does not land until the gate in the repository finds a commit naming that intent and the guard finds a signed receipt for it; and it is never finished quietly — it is graded, and the grade is kept, misses included. So you are not the first tenant: the sharp edges are found by the makers first, on load-bearing work, under the same discipline being sold.
And the credibility on offer is the discipline, not a feed. A record of intent belongs to the tenant that wrote it — and the house holds its own record to the same law: Askora keeps the ash; it does not get to mine it. Vulcora's ledger is a working instrument, not a publication; it is never published — ours or yours. What proves the substrate is that it is lived on daily, and walked live in controlled demos, never a record you scroll.
Not claimed, not implied
THE ONE SEALED SEAM — ONLY THE INTELLIGENCE
Everything above runs on the ledger and its projections. Sealed behind a narrow interface is only the intelligence, described by what it does and never by how it does it. Referenced only through the interface: what goes in, what comes out.
The rest of the apparatus never needs what is behind that interface: bind, grade, keep and render all run against the open record. One capability crosses that seam today. The other two are written down here as declared, because a seam described as sealed reads to a buyer as shipped-but-secret, and that is the one thing this page may not let stand.
That a goal is placed and moved on the orrery by a judgement about the whole tree — five plain numbers per goal: spin, size, brightness, acceleration, phase. The queue, the ranges, and the door that refuses anything else are open; the judgement that produces the numbers is sealed. The engine dials in and leases; nothing here dials out.
That two commitments contradict on meaning — beyond merely touching the same file — read at bind-time with a human-readable reason. Nothing computes this today, sealed or open: no request of this kind is queued and the ledger has no clash state to write.
That a natural-language promise becomes a falsifiable test spec. Today the maker writes the test_spec themselves, and an intent bound without one records that nobody stated a test — which is honest, and different from an empty one.
The interface is small on purpose. One kind of request goes out to the engine and five bounded numbers come back, scrubbed at the door: an extra key at any level, a value outside its range, or a goal the lease did not name and the whole submission is refused, with nothing partial stored. Walk the lenses →
And the seal is not a single point of failure for your record. The Engine travels separately from the ledger. If it is ever unavailable, the ledger, the state machine, the immutable aska, and every graded outcome stay fully readable, and the orrery still draws every goal from the ledger's own state — only the physics stop refreshing, and the ledger can be asked whether the numbers it holds are still a reading at all. Your record never depends on the sealed core to be read.
DATA & PRIVACY — A CUSTOMER'S RECORD OF INTENT IS THEIRS
The governing principle is one line. Askora's whole job is to keep that record faithfully — append-only, graded against the truth, misses kept, nothing quietly forgotten — and its whole discipline is to keep it only for them.
Askora keeps the ash; it does not get to mine it.
WHERE IT RUNS — TWO SHAPES
The default — Askora-hosted, tenant-isolated as above. Region pinning for data-residency customers.
Isolated infrastructure per organization, for a customer that will not share a substrate.
INTEGRITY, STATED HONESTLY — NO MORE THAN IS TRUE
The record's trustworthiness is the product, so its integrity claims are stated exactly. It is append-only by construction — new versioned rows, no edit-in-place path for a binding's history — and fully audit-trailed: every transition, including a retraction, a correction, a re-grade, or a deletion, is itself a recorded row. There is no off-ledger change to a binding's lifecycle.
What it is not: tamper-proof against a hostile insider with database access. Askora claims the narrower, true thing — every change is itself recorded, so tampering is not invisible. For customers who need cryptographic assurance beyond that, tamper-evident signing and external anchoring of the aska trail are a hardening option — offered as what they are, never dressed up as "unforgeable." The signed dossier →
| Subject | What Askora claims | What Askora will never say |
|---|---|---|
| The record | append-only by construction, fully audit-trailed — every change itself recorded | "tamper-proof · unforgeable against a hostile insider" |
| A green grade | this falsifiable test held — what was committed to, and whether the bound test passed | "this proves the agents did the right thing" |
| Clash coverage | none — no clash check runs today, and no coverage has been measured | "catches every contradiction · your agents never conflict" |
| Compliance | evidence the EU AI Act / NIST frameworks expect | "guarantees or certifies your compliance" |
The record is faithful, not omniscient. What it gives a risk function is evidence — graded, timestamped, immutable — not legal advice or certification. What this gives your risk function →
CLIENT INTEGRITY — THE LEDGER VOUCHES FOR THE RITUAL
The discipline that makes the ledger trustworthy — bind before you edit, route code queries to the forge tools, respect scope, never bypass the verifier, never force the main line — is enforced by hooks that run inside the maker's client. But those hooks run on the maker's machine. A key proves who is calling, not that their client is enforcing the ritual. In a shared workspace, one unhooked client could corrupt the record for everyone.
So the backend proves it cryptographically and writes the answer to the ledger. "Hooked and current" is a signed manifest hash: canonicalize the required hook set into a hash, and a missing hook, a stale hook, or a tampered hook all change it — so not-installed and tampered are the same detectable event. On connect the client signs a fresh challenge; each ledger-affecting call carries a per-action attestation token. It is all standard cryptography and paper-trail.
| Verdict | Meaning | Response |
|---|---|---|
| attested | hooks present, manifest matches, signatures valid | full write path — bind / satisfy / advance land normally |
| unattested | no valid attestation — no hooks, or a raw client calling MCP directly | refused, or quarantined to a low-trust tier that must re-attest before it can land; the read path stays open |
| manifest_drift | hooks stale, partial, or tampered — hash mismatch | flagged; prompt a re-install; degrade to low-trust until the hash matches again |
The invariant is simple: no un-attested action silently lands as if it were attested. The online observatory renders the attestation state alongside the work, so a superior sees the team's clients honoring the discipline — without inspecting anyone's machine or watching anyone work. The ledger vouches for the ritual, so people don't have to watch people.
Honest status: the foundation is shipping GRADED · LIVE — the key-based MCP auth that stamps every binding, the hook installers, the access-hook enforcement, and the immutable paper-trail. The attestation layer on top — the manifest hash, challenge/response, per-action tokens, and the trust tiers — is DECLARED · FRONTIER, a build ahead. The one part that had to be real, the manifest hash, is validated: a canonical hash over the installed hook set is deterministic today (recompute → identical).
THE CHARTER — WHAT ASKORA NEVER DOES
Held in the contract and in the marketing alike: the lines around your record, and the lines around our own claims.
The nevers
That honesty is the whole product: a ledger is only worth trusting if it does not flatter itself.
What the witness keeps · what it refuses · the keeper enters neither
It sets down what happened, and stands by it.
grades each commitment against ground truth — read from what happened, never asserted from prose
To change the thing is to stop witnessing it.
surfaces a verdict for a human to resolve — it does not act on what it witnessed
It keeps the thing whole — both sides held together, neither let go.
append-only and fully audit-trailed — nothing edited in place, the miss kept beside the win
To pry it open is to break its keeping.
keeps the ash; it does not get to mine it — the record of intent stays its maker’s own
It names the thing exactly — a word cut to fit the deed, not to please.
each load-bearing intent bound as a falsifiable commitment before the work — or refused at bind-time
To gild it is to lie about it.
keeps its failures as loudly as its wins — a graded_violated binding is retained, never deleted to flatter
Where its sight ends, it says so, and marks the edge.
a check that did not settle the question is filed as indeterminate, never rounded to either side — and an aim gated on one is not called met
To claim the future is to overrun the edge of what was seen.
records what was committed to and whether the bound test held — never what will happen
A scale reads true because it weighs nothing itself. witness ≠ lock
Two witnesses stand in the house, one theorem between them: Proofora, the proof that will not look away — machine-checked; and Askora, the keeper that will not intervene. The theorem is the one marked above — witness ≠ lock — which Proofora settles and Askora is built to embody.
Read the whole record, walk the state machine, audit every grade — your record never depends on the one proprietary layer to be read.
PUBLIC ACCESS · SOON The apparatus is live inside the house today; this is how it works.
