02 · Specifications

All twelve specs

An exploratory map of the same 12 specs below. Click a vertical to filter both. Tab through with a keyboard; Enter/Space activates a node like a click.

Filter by vertical
Spec What it declares Detect via Well-known path
AEO Protocol Entity declaration · authoritative claims · citation preferences aeo_version /.well-known/aeo.json
Prompt Provenance Versioned, lineaged, reviewable LLM prompt records provenance_version —
Agent Cards Declarative agent capability + refusal disclosure agent_card_version /.well-known/agents/<id>.json
AI Evidence Format Structured citations for LLM-generated claims evidence_version —
MCP Tool Cards Per-tool disclosure for MCP servers tool_card_version /.well-known/mcp-tools/<name>.json
AI Tutor Cards EdTech EdTech vendor-side · pedagogy · FERPA/COPPA/GDPR posture tutor_card_version /.well-known/tutors/<id>.json
Student AI Disclosure EdTech Student-side · roles · prompt evidence · artifact-hash binding disclosure_version — (travels with artifact)
Classroom AI AUP EdTech District / school / course AI policy aup_version /.well-known/ai-aup.json
Clinical AI Disclosure HealthTech HIPAA / FDA / SaMD posture · bias audits · EHR integration clinical_ai_card_version /.well-known/clinical-ai/<id>.json
AI Incident Card cross-cutting · vendor-side "CVE for AI agents" · references every other document incident_card_version /.well-known/ai-incidents/<id>.json
AI Procurement Decision Card cross-cutting · buyer-side Buyer's procurement review outcome · documents reviewed · conditions · rationale · v0.2 adds data_vault_targets[] (Skyyflow-shaped field-level vault contract) powering rag-sentinel, deal-desk-workspace, kg-skyyflow-klaviyo-bridge, and the bridge console · v0.3 adds retention_envelope[] — per-field TTL + redaction action + ed25519-signed deletion-proof endpoint decision_card_version /.well-known/decisions/<id>.json
AI Claims Decision Card InsurTech · insurer-side Insurer/adjudicator record that an AI system decided an insurance claim · outcome · underwriting rules applied · content-hashed evidence bundle · human-in-loop · ed25519-signed, hash-chained claims_card_version — (document-embedded)
02b · Regulatory mapping

NIST AI RMF crosswalk

This May 2026 crosswalk is a historical mapping of the first eleven Suite specs to selected NIST AI RMF subcategories. It does not yet assess the twelfth spec. Its implementation examples show possible controls, not evidence of a deployed buyer policy, complete audit, or RMF conformance. The AI Procurement Decision Card (spec #11) can carry a buyer's rubric and recorded outcome.

Three historical repo-to-control examples from Crosswalk v0.2 §7. These are design mappings, not deployed-control evidence. Tab, click, or hover for detail.

Default Tab, click, or hover a node to see a possible control mapping. A buyer can record an outcome in the AI Procurement Decision Card (spec #11); the diagram does not verify that a buyer did so.

1 policy-as-code-engine → MANAGE 1.3 · 2 audit-stream-py → GOVERN 1.5 · 3 aeo-validator-service → MEASURE 3.1 · 4 slo-budget-tracker → MEASURE 3.1