File size: 3,685 Bytes
a6a5d8e
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
# A11oy showcase — proof-backed governed execution

A11oy is the governed execution hub for the SZL Holdings substrate. It is the
layer that turns AI or agent work into policy-checked, receipt-backed, replayable
operations with payload provenance.

## Capability graph

```mermaid
flowchart TD
    A[A11oy<br/>governed execution hub]
    D[Doctrine package lane<br/>tests · typecheck · build]
    R[Receipt substrate<br/>hash chain · quorum · QEC witness]
    P[Payload discipline<br/>MANIFEST · attestation · bundle]
    HF[Hugging Face mirror<br/>generated diligence packet]
    UDS[UDS/Zarf lane<br/>operator proof point]
    V[Vessels<br/>active vertical demo]
    S[Sentra<br/>drift + incident telemetry]
    AM[Amaru<br/>receipt minting / anchoring]
    RO[Rosie<br/>receipt DAG / CSS ingress]
    O[Ouroboros<br/>bounded loop runtime]
    L[Lutar Lean<br/>proof substrate]
    T[Ouroboros Thesis<br/>DOI-pinned claim taxonomy]

    T --> A
    L --> A
    O --> A
    A --> D
    A --> R
    A --> P
    P --> HF
    P --> UDS
    R --> RO
    R --> AM
    A --> S
    A --> V
```

## What A11oy can demonstrate today

| Capability | Evidence in this payload |
| --- | --- |
| Doctrine runtime checks | `source/README.md`, `build/package.json`, `source/docs/PROVENANCE.md` |
| KS-18 / governance math test lane | `source/docs/PROVENANCE.md` and GitHub `web/packages/a11oy-core/src/**/__tests__` |
| Operational receipt chain | `DEMO_RECEIPT_SAMPLE.jsonl` and GitHub `packages/receipt-substrate` |
| Deploy manifest verification | `payloads/deploy/MANIFEST.json` |
| UDS/Zarf operator handoff | `payloads/deploy/zarf.yaml`, `source/docs/WARHACKER_UDS_PROOF_POINT.md` |
| Ecosystem readiness | `source/docs/ecosystem-readiness-report.json` |
| Market evidence | `source/docs/SERIES_A_MARKET_EVIDENCE.md` |
| Substrate reality | `source/docs/SUBSTRATE_REALITY_MAP.md` |
| Series-A diligence | `source/docs/SERIES_A_DILIGENCE.md`, `INVESTOR_BRIEF.md` |

## Verification lane

```mermaid
sequenceDiagram
    participant Dev as Developer / CI
    participant Tests as Doctrine tests
    participant Manifest as Deploy manifest
    participant HF as Hugging Face payload
    participant Bundle as Operational bundle

    Dev->>Tests: pnpm test:doctrine
    Dev->>Tests: pnpm typecheck:doctrine && pnpm build:doctrine
    Dev->>Manifest: pnpm payload:verify
    Dev->>HF: pnpm payload:huggingface
    Dev->>Bundle: pnpm payload:bundle && pnpm payload:bundle:verify
```

## Naming cleanup

This showcase uses real GitHub repo names and excludes stale product copy. Do
not use KORA, LUMINA, PARAGON, or active Lyte framing for this A11oy packet.
Counsel, Terra, and Carlota Jo remain funded-roadmap scaffolds, not active demo
surfaces.

## Claim discipline

The strongest story is the evidence trail:

1. GitHub is canonical.
2. CI validates runtime/package lanes.
3. Manifests bind payload bytes.
4. Receipts bind actions.
5. Hugging Face mirrors the packet for public review.
6. Proof and thesis claims are scoped by `source/docs/PROVENANCE.md`.

## Live correction ledger

| Claim area | Current evidence-backed wording |
| --- | --- |
| A11oy gates | A11oy main currently exposes seven policy gate files and ten theorem-runtime manifest entries. G36-G40 and broader gate counts remain PR/roadmap until merged and validated. |
| UDS signed assets | A11oy `uds-v0.3.0` has SBOM release assets only; Vessels `uds-v0.3.0` has zero release assets. Use `uds-v0.2.0` when demonstrating signed Vessels assets. |
| GHCR | GHCR manifest checks returned an authentication challenge in this environment, so public package availability needs owner-side push or visibility confirmation. |