Records

The unit of record is a risk register entry: a risk, control, or policy (and related incident/evidence metadata) that Arbiter stores with lifecycle state and framework mapping.

This page describes fields partners and agents can rely on publicly. It is not a dump of every Firestore document.

Unit of record

Concept	In Arbiter
Unit of record	Risk register entry (risk / control / policy)
Shared across	Dashboard, REST, MCP
Integrity at rest (evidence)	SHA-256 fingerprint — Verification
Optional seal	Metadata-only Stratum seal when entitled

Core record types

Type	Typical public fields	Lifecycle
Risk	id, title, status, severity/likelihood signals, framework refs	Lifecycle § Risks
Control	id, title, implementation status, framework refs	Lifecycle § Controls
Policy	id, title, version, status, framework refs	Lifecycle § Policies
Evidence (metadata)	id, content type, evidence_hash, attachment metadata	Hash-chained layer

Exact REST field names live in the API reference OpenAPI. Prefer the generated schemas over inventing synonyms.

Partner Read envelope

Partner-oriented payloads emphasize metadata and integrity signals, not full NPI or free-text review notes.

Field (conceptual)	Purpose
evidence_hash	SHA-256 of evidence content (when applicable)
body_hash	SHA-256 of a published body / package segment (when applicable)
verified_no_npi	Affirms the outbound package path excluded NPI for that emission

Treat these as integrity and disclosure signals. They do not mean Arbiter scored the record or that a seal exists.

Evidence metadata

What is typically metadata-only on partner and seal paths:

Included	Excluded
Hashes, ids, timestamps, status	Raw evidence file bytes on Partner Read
Framework references	Free-text assessor workpapers (unless explicitly exported)
Package / seal references when present	NPI and secrets

NPI never rides the on-chain path. See Verification, Disclosure Boundary, and Integration Surfaces.