Schema Intake
- Identify producers, consumers, storage and transport boundaries.
- Collect two valid examples, invalid/edge examples, ownership, sensitivity, retention, and expected evolution.
- A schema is required by default when data is persisted, exchanged, configured, queued, emitted, imported/exported, or authored as structured content.
- An opt-out is valid only for ephemeral internal values with no durable or cross-component contract; record owner, rationale, boundary, and review date.
- Create
.aiwg/architecture/schema-briefs/<logical-name>.mdfrom the addon template, then route required contracts toschema-author.