Pilot
AXIS reached v0.6 Pilot Readiness: controlled demos, local review and a non-production pilot. This milestone is explicitly not compliance-certified enterprise production.
Pilot scope
| In scope | Out of scope |
|---|---|
| Controlled demos with reviewer environments | Production enterprise deployment |
| Local review of the HTTP integration path | Native wire protocol in production |
| Policy, approval and audit workflows with real drivers | RBAC/SSO, KMS, external ledger |
| Operational drills (health, evidence verify, recovery) | Compliance certification |
Pilot acceptance criteria
- Startup chain passes with no warnings: WAL continuity, manifest SHA-256, policy validation, dry-run corpus.
/healthreturnsstatus: ok;/policy/statusshows the expected version.- ALLOW / BLOCK / REQUIRE_APPROVAL drill passes end-to-end (including resolve + explicit retry).
/evidence/verifyreturnsstatus: okbefore and after restart.- Driver smoke tests pass (psycopg3 / asyncpg / Prisma / pgJDBC single-statement).
- Bypass checks: direct DB writes, COPY, batch, and wire prepared statements fail closed.
Operator checklist
Run the stack: docker compose up --build; verify health and policy status.
Run the verification drill.
Set a real AXIS_OPERATOR_TOKEN; confirm operator_auth_enabled: true.
Close direct DB access (network/roles) — the documented bypass.
Persist and back up /data (WAL, JSONL, approvals) and policies.
Document accepted pilot risks (plaintext lab traffic, unverified identity, single operator).
Demo scenarios
- ALLOW: a normal table UPDATE executes and returns 200 with evidence.
- BLOCK: a dangerous UPDATE without WHERE returns 403, never reaching PostgreSQL.
- REQUIRE_APPROVAL: DDL or guarded DML returns 202 with
approval_id; resolve; explicit retry executes. - Policy lifecycle: validate, diff, dry-run, candidate, activate, rollback.
- Evidence:
/evidence/verify, bundle export, hash chain inspection in the WAL. - Modes: same corpus under shadow vs enforce produces identical decisions.
Exit criteria to leave the pilot
- Complete the production review gates (mTLS, TLS to PostgreSQL, token policy, identity/JWT adoption, external evidence handling).
- Third-party security review and compliance assessment.
- Extended Query shipped and verified with real OLTP clients.
- Approval workflow reviewed for multi-person approval if required.
Use shadow mode during integration weeks, then approval_first, then enforce — the decisions are identical in all modes, so the switch is a confidence step, not a behavior change.
Related: Testing & Verification · Limitations · FAQ