ReferenceStrong architectural inferencev1.22.1
In plain English
This page is reference material: definitions, schemas, catalogs, templates, and implementation records.
- Why this matters: AI risk can come from the whole arrangement, not one obvious model.
- What to look for: data, memory, routes, adapters, tools, evaluators, updates, and rollback paths.
- Technical version below: the expert terminology remains available and is linked through the glossary.
Reference FAQ
Are schema files normative standards?
No. They are reusable starting points for composition manifests, rollbackReturning a system to an earlier known state. Open glossary definition packets, evidence cards, lineage records, evaluation records, retirement records, and behavioral-extinction reviews.
Can the threat catalog be used as an incident playbook?
It is a planning reference, not an operational exploit or response manual. Organizations should adapt it to their own legal, security, and safety processes.
Why so many UTC timestamps?
UTC timestamps avoid ambiguity when evidence, release aliases, memory snapshots, and review records cross jurisdictions.