Skip to content

TRUST-ARTIFACTS.md

Latest commit

 

History

History
135 lines (112 loc) · 6.98 KB

TRUST-ARTIFACTS.md

File metadata and controls

135 lines (112 loc) · 6.98 KB

Trust artifacts

The single index over PEAC's trust artifacts. Each artifact below has one canonical home; this page points at all of them and normalizes the reference-verifier versus Hosted Verify distinction once so the rest of the documentation can link here.

Engineering trust

  • SLO: operator-facing service-level objectives with versioned baseline stamps.
  • Benchmark methodology: machine profile, fixture set, measurement protocol, and reproduction commands.
  • Stability contract: every public surface classified stable, experimental, deprecated, archived, or internal-only.
  • Threat model: consolidated threat catalog with per-threat test-coverage links.

Disclosure and supply chain

  • SECURITY.md: coordinated disclosure contact, supported versions, supply-chain controls, external review cadence.
  • Security operations: support windows, runtime support, incident handling SLAs, supply-chain provenance, logging boundaries, tenant isolation, data residency.
  • Key custody and tenancy: key custody, tenancy, procurement, stewardship.

Architecture and deep detail

Reference verifier versus Hosted Verify

PEAC ships two distinct verification surfaces. The stability contract, SLO, threat model, and security operations apply to the reference verifier unless a row is explicitly scoped to Hosted Verify.

Aspect Reference verifier Hosted Verify
Location apps/api in this repository Operated separately; not part of this repository
Hosting model Self-hostable, tenantless Managed, multi-tenant
Deployment recipes surfaces/reference-verifier/ Not published here
SLA None (operator-managed availability) Per-contract
Contract packages/schema/openapi/verify.yaml Hosted Verify contract
Threat model docs/THREAT_MODEL.md Operated under its own threat model
SLO scope docs/SLO.md Published by the Hosted Verify operator

Machine-readable and conformance artifacts

Compatibility

Compliance mappings

  • ISO/IEC 42001:2023 Clause 8 mapping: operational planning and control objectives mapped to supporting PEAC artifacts.
  • EU AI Act Annex IV mapping: technical-documentation points 1(a) through 5 mapped to supporting PEAC artifacts. Applicability context: Regulation (EU) 2024/1689 applies from 2 August 2026, with exceptions under Article 113.
  • Compliance index: framing, non-claim statement, companion framework guides.

Privacy-aware verification (deployment guidance)

Operator-facing privacy guidance for PEAC deployments. Complements the normative receipt-side privacy profile. Each document leads with a boundary-first block (what PEAC does / what PEAC does not do / what deployers still own).

  • Data classification: which PEAC surfaces likely hold personal data, pseudonymous data, or operator-controlled content.
  • Retention and deletion: retention classes, the evidence-vs-derived deletion model, and linked-index purge.
  • Deployment roles: controller / processor posture for each of the four common deployment shapes.
  • Data-subject rights: access, rectification, erasure, restriction, objection, portability, automated-decision-making; AIPREF is not consent.
  • DPIA starter: risk-tier starter and PEAC-specific mitigation levers.
  • Privacy directory index: boundary-first discipline plus preferred / avoided public wording.

PEAC supports privacy-aware verification and GDPR-aligned deployments. PEAC does not replace operator legal review, lawful-basis decisions, or controller obligations.

Carrier surfaces

Execution-surface carriers shipped in v0.14.1 and provisioning lifecycle carriers shipped in v0.14.2 are classified stable in Stability contract and have CLI surfaces under @peac/cli (peac observe command, peac record command, peac emit lifecycle). The earlier forward-looking security controls described for these carriers are now superseded by their shipped specs: