tegwick
e0ca7de63b
INFO-WP-0030: register practice-pattern/explicit-unsafe-diagnostic-mode (adapted from coordination-engine's OrwellLoggingDiagnostics candidate, INFO-DEC-2026-003) at canon 0.13.0, close the assimilation, and notify coordination-engine for COORDINATION-WP-0004-T02. Workplan finished. INFO-WP-0029: record activity-core's source-owned declaration (T03/T04 done) with its expected-rate/calendar-schedule incompatibility as demand/EmissionExpectedRateCalendar.md, and record audit-core's structural-only observer evaluation of net-kingdom's declaration as a steward note. No party has yet produced a real observer result against traffic, so T05 and the workplan stay blocked on external action. Updated artifact-count and practice-pattern-count assertions in tests/test_cli.py and tests/test_service.py for the new artifact. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: sonnet Assistant-Process: 317218@bnt-lap001 Assistant-Session: a8d6c0ab-c70f-4610-a288-576f44d747d4
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: 83
|
|
- Retrieval index items: 83
|
|
- 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.
|