tegwick
5a1ea90f64
The canon owner disposed coordination-engine's candidate practice pattern as adapt, which unblocks COORDINATION-WP-0004-T01. Preserve the source, record the DecisionRecord, and register the assimilation. The TAMQ known use is implemented and tested, so the pattern enters at candidate. Canon placement is planned as proposed workplan INFO-WP-0030. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 121421@bnt-lap001 Assistant-Session: 36f8657c-ebfa-4a2e-9ba0-bff06738f233
43 lines
2.3 KiB
Markdown
43 lines
2.3 KiB
Markdown
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
|
|
|
|
# Global Agent Brief
|
|
|
|
This brief summarizes the current canon service surface for agents.
|
|
|
|
- Infospace slug: `canon`
|
|
- Artifact count: 82
|
|
- Retrieval index items: 82
|
|
- Primary confidence command: `make validate`
|
|
- Refresh generated indexes and views with: `make index`
|
|
- Refresh agent briefs and interface templates with: `make agent-briefs`
|
|
|
|
## Useful Commands
|
|
|
|
- `PYTHONPATH=src python3 -m info_tech_canon inspect`
|
|
- `PYTHONPATH=src python3 -m info_tech_canon validate`
|
|
- `PYTHONPATH=src python3 -m info_tech_canon graph`
|
|
- `PYTHONPATH=src python3 -m info_tech_canon index`
|
|
- `PYTHONPATH=src python3 -m info_tech_canon profile validate small-saas`
|
|
|
|
## Retrieval Entry Points
|
|
|
|
- `agent/retrieval-index.md`
|
|
- `agent/retrieval-index.yaml`
|
|
- `agent/retrieval-index.json`
|
|
- `agent/briefs/` for per-artifact briefs
|
|
- `agent/templates/canon-interface-card.template.yaml`
|
|
|
|
## Common Distinctions
|
|
|
|
- **Agentic fallback vs direct functional interface**: Use cross-repository agentic work to interpret novel demand; use an owned API, CLI, or MCP surface when the outcome is stable and recurring.
|
|
- **Interface deprecation vs retirement vs removal**: Deprecation guides and observes callers, retirement ends legacy behavior while retaining a metered tombstone, and removal deletes that tombstone only after the evidence gate passes.
|
|
- **Actor vs Subject vs Principal**: Use actor for the acting entity in a context, subject for the entity a policy evaluates, and principal for the authenticated identity bound to access decisions.
|
|
- **Organization Role vs AccessRole vs CARING role**: Organization roles describe responsibility or position; access roles describe permissions; CARING roles classify access-governance needs and analysis.
|
|
- **Policy vs Control vs Evidence**: Governance owns policy and control; ITC-EVID owns the distinct evidence assertion and its addressable source. Evidence supports a stated interest without guaranteeing truth.
|
|
- **Intent vs Scope vs Purpose**: Intent captures why a producer or consumer exists, scope bounds producer ownership and promises, and purpose captures consumer demand anchored in consumer intent.
|
|
|
|
## Consumption Notes
|
|
|
|
- Treat `seeds/` as provenance.
|
|
- Treat `infospace/` as the service-consumable canon root.
|
|
- Generated files are marked and can be refreshed deterministically.
|