ARCHITECTURE VIEW

Data and provenance

This view distinguishes public static records, bounded observation fields, agreement-specific information, and protected operational material. Public evidence is point-in-time and limitation-aware.

SEMANTIC SYSTEM VIEW

Data and provenance map

Each step carries its state in text. The diagram remains readable without colour or client JavaScript.

01
Public records
Schemas, source-controlled JSON, documentation, release manifests, and public evidence references.
Current
02
Local files
A future local workflow can evaluate user-supplied artifacts without sending them to the public website.
Reference
03
Client information
Exists only in the applicable delivery context and is not published in public records.
Agreement-specific
04
Tenancy and isolation boundary
Client work remains in a separate agreement-specific delivery context; no multi-tenant public control plane is claimed.
Agreement-specific
05
Private operations
Credentials, protected topology, signing material, and raw witness material are excluded from the public estate.
Protected

Text equivalent: Public records is current; Local files is reference; Client information is agreement-specific; Tenancy and isolation boundary is agreement-specific; Private operations is protected.

CURRENT IMPLEMENTATION BOUNDARY

What this view does and does not state

A published hash, record, or signed observation supports only its stated integrity and provenance scope; it does not disclose or prove protected systems.

Inspect the claim register and evidence classes for the records that govern public assurance language.