SPINE · the assurance system of record
Continuous Assurance. Evidence That Holds Together.
Why SPINE
Findings fade. Claims are kept honest.
- 01
Bound to a configuration
Every claim is tied to a system fingerprint, a policy version and an environment — never to a vague “the system.”
- 02
Gaps are named
What was not measured is recorded as not measured — never turned into a green result.
- 03
Change-aware
When the system moves, SPINE works out which conclusions moved with it — and only those are retested.
The assurance graph
Everything a claim depends on, connected.
- Identities
- Tools
- Actions
- Effects
- Claims
- Evidence
IllustrativeWho the assistant acts as, what it can call, what it did and what happened — tied to the claim and the evidence behind it.
The claim state machine
Declared, observed and verified are never merged.
Declared
Stated by the customer or a vendor; not yet observed.
Observed
Seen by Mythos AI Security in the running system.
Verified
Confirmed by testing, with evidence behind it.
Unknown
Not enough evidence yet — never shown as a pass.
Stale
Was verified, but a change means it must be revalidated.
Contradicted
The evidence conflicts with the claim.
- Technically verified
- Configuration verified
- Document supported
- Contractually stated
- Vendor assertedcaps at supported
- Partially verified
- Unknown
- Not documented
Confidence is the weakest evidence class — never a probability, and null when unknown.
Two clocks, nothing overwritten
SPINE keeps when a source saw a fact apart from when that fact was held current — so you can ask what was true on any date, and what was known at the time.
- Why it matters
- Customer data could persist outside your boundary.
- Evidence needed
- The provider’s data-processing terms, or an observed retention test.
- Coverage manifest
- Recorded as not measured in the coverage manifest. If coverage falls short, the decision reads Audit incomplete — never Ready.
Authority and action lineage
Who allowed this, and did the effect match?
- 01
Deny
Blocked. Policy denies by default.
- 02
Escalate
Sent up for a person to decide.
- 03
Hold for approval
Waits for the approval in force.
- 04
Permit
Bound to the action, policy and authority epoch; spent once, at dispatch.
Illustrative example · a support assistant issues a refund
- 01PersonWho is accountable?Support lead
- 02UserWhich identity asked?Her session
- 03AgentWhich AI acted?Support assistant
- 04PolicyWhich rule allowed it?Refunds up to $500
- 05ToolWhat did it call?payments.refund
- 06AccountUnder whose credentials?Service account
- 07ActionWhat was requested?Refund $4,800
- 08EffectWhat actually happened?Funds moved
SPINE verdict: Contradicted. The effect exceeded the policy that authorized it. SPINE marks the approval claim Contradicted and holds the deployment decision until it is fixed and retested.
Change intelligence
The loop that keeps evidence current.
SUPERSEDES
A fresher observation of the same fact replaces the old one. Nothing breaks, and the history is kept.
INVALIDATES
A contradiction or expiry closes the claim and recalculates the decision. Cleared is not fixed: the claim stays closed until a retest restores it.
- System fingerprints
- Per-claim input fingerprints
- Pinned policy versions
- A revalidation planner
- Legal staleness set by a person
Deployment decisions
A recommendation backed by evidence. Your team decides.
- Ready
Current evidence supports release within the assessed scope.
- Ready with restrictions
Supported, but only within stated limits.
- Needs more evidence
A claim lacks the evidence a decision needs.
- Audit incomplete
Coverage fell short of what was expected.
- Needs remediation
Failures must be fixed and retested first.
- Not recommended
The evidence does not support release.
- Paused
Held by a pause; nothing proceeds until it lifts.
Receipts and dispatch
Evidence you can hand to someone else.
Signed engine evidence packs
Athena evidence packs are signed with Ed25519 and carry Merkle inclusion proofs, checked offline by a standalone tool.
Vendor-asserted claims
What a vendor declares about a third-party AI caps at supported. Verified needs non-vendor technical evidence.
Findings dispatch
Findings go to Jira, GitHub, ServiceNow and Splunk. A lost answer is looked for, not re-pushed, and a stop never waits on a connector.
Assurance Receipt
Sample · fictional data
- Subject
- Support assistant · refund path
- Configuration
- fingerprint 7f3a…c91e
- Policy
- refunds-policy · v12
- Evaluator
- Achilles · approval-boundary tests
- Evidence
- 14 artifacts · 3 observed effects
- Result
- Verified
- Issued
- 14 Oct 2026, 09:12 UTC · inside the signature
- Validity
- Until configuration or policy changes
- Invalidators
- New tool · policy edit · model change
- Approval
- Security lead
- Signature
- DSSE envelope · verifies offline (sample)
SPINE Economic Exposure
A verified effect, in business terms.
Assurance teams and validity
Four roles, one evidence loop.
Red Team · Adversarial challenge
Authorized adversarial testing of an agreed objective and its technical paths.
Delivers
Reproducible failure evidence, attempted paths and observed effects.
Boundary
Never reads the answer key; cannot expand scope or waive a stop.
Mythos AI Security
See what SPINE keeps true about your AI.
Bring a workflow that changes often, and we will show how its claims, evidence and decisions would stay current.













