Verusai Ltd · Confidential

Design documentation status

A living index of the technical, security, and product documentation set behind Fignature and Verusai PoLE — what exists, what's in progress, and what's still to be written.

Last updated manually by Jon · republish after each doc set revision
VADR Core Service API reference →
6
Core specs drafted
2
Level 0–2 docs drafted
6
Documents still needed
2
Proposed cross-cutting registers

Document hierarchy

Six tiers, strategy down to implementation-level component and API specs, plus two cross-cutting registers that index status and open issues across the whole set.

Level 0 — Strategy
Why the company and products exist
VS-001
Exists
Level 1 — Product requirements
Strategy translated into testable requirements
PRD-001
Needed
Level 1.5 — Core protocol & security
Shared cryptographic and security foundation
GSM · GCP · GGL · GHP · GPP · GSA
Exists
Level 2 — Technical architecture
System components, trust boundaries, sequences
TAD-001
Exists
Level 3 — Component & API specs
Implementation detail per component, OpenAPI contracts
TS-001…004 · API-IAM-001 · API-VADR-001
Needed
Cross-cutting — Registers
One place to see everything tracked, everywhere
SEQ-001 · REG-001
Proposed
Exists drafted and available today Needed not yet drafted Proposed new document type, not yet agreed

Master index

Every document in the hierarchy, its status, what it depends on, and — where relevant — a link to its published reference (OpenAPI pages will appear here once drafted).

ID Name Level Status Depends on Purpose Reference
VS-001 Verusai Strategy Overview 0 — Strategy Exists — Why the company exists, why the two products pair, target outcome Internal doc
PRD-001 Product Requirements Document 1 — Product Needed VS-001 Translates strategy into testable requirements, traced to the spec set below Not yet drafted
GGL-001 Glossary and Terminology 1.5 — Core Exists PRD-001 Single source of truth for every term; all other docs reference it Internal doc
GSM-001 Mathematical Model and Security Proof 1.5 — Core Exists PRD-001 Formal proofs the protocol relies on Internal doc
GCP-001 Core Protocol Specification 1.5 — Core Exists PRD-001 Protocol behaviour — participants, state, message exchange Internal doc
GHP-001 Human Profile (Fignature) 1.5 — Core Exists PRD-001 Human-authentication parameterisation of the shared core model Internal doc
GPP-001 Verusai PoLE Profile 1.5 — Core Exists PRD-001 Agent-authentication parameterisation of the shared core model Internal doc
GSA-001 Security Architecture 1.5 — Core Exists PRD-001 Consolidates trust assumptions and the ranked attack-tier table Internal doc
TAD-001 VADR Technical Architecture Document 2 — Architecture Exists (predates PRD-001) PRD-001 Component map, trust boundaries, the six VADR request sequences Internal doc
TS-001 Agent Shim Technical Specification 3 — Component Needed TAD-001 Implementation detail for the agent-side component Not yet drafted
TS-002 IAM Plugin Technical Specification 3 — Component Needed TAD-001 Implementation detail for the IAM-side component Not yet drafted
TS-003 VADR Core Service Technical Specification 3 — Component Needed TAD-001 Implementation detail for the shared backend service Not yet drafted
TS-004 DynamoDB Data Model & Access Pattern Spec 3 — Component Needed TAD-001 Schema, keys, access patterns Not yet drafted
API-IAM-001 IAM Plugin OpenAPI Spec 3 — API Needed TS-002 Machine-readable contract for every IAM-facing endpoint Not yet published
API-VADR-001 VADR Core Service OpenAPI Spec 3 — API Exists TS-003 Machine-readable contract for IAM↔VADR internal calls View docs →
SEQ-001 Sequence Diagram Catalog Cross-cutting Proposed TAD-001 Master index of every sequence needed system-wide, owner, and status Not yet agreed
REG-001 Open Items & Security Issue Register Cross-cutting Proposed GSA-001 Single living table of every open item across the doc set, owner, target doc Not yet agreed

Open decisions

Structural points that need a decision before the Level 3 tier gets drafted.

TAD-001 predates its stated parent
TAD-001 declares it derives from PRD-001, which doesn't exist yet. Decide whether PRD-001 is now written to document decisions TAD-001 already made, or whether TAD-001 gets revisited once PRD-001 exists.
MCP Gateway scoping
TAD-001 treats the MCP Gateway as external infrastructure with no TS-00x document of its own. Flagged in the source document as needing confirmation before TS-001 is drafted.
Tier 8b — false ancestry
Named as a pending concern in GPP-001 but not yet analysed at the mechanism level, unlike Tiers 4/7/2b where a design exists but is unbuilt.