Define the intake and assimilation practice (incoming/ drop zone -> frozen source snapshot -> Minimal Assimilation Profile -> disposition gate -> canon transformation -> versioned change notes) and run it on the first inputs. - infospace/assimilation/intake-and-assimilation-practice.md, incoming/README.md - assimilation/it-capability-canon: frozen source, comparison matrix, 26 mappings, 8 proposed changes, 7 open questions, decision record (adapt) - new model ITC-CAP with 41-capability machine-readable catalog, anchored to owning canon models; CILM rejected, Profile renamed, Provision made explicit - registered in canon.yaml / artifacts index / infospace.yaml; regenerated briefs, indexes, views; canon version 0.1.0-scaffold -> 0.2.0 + CHANGELOG - ITC-WP-0014 for promotion work; ITC-WP-0013 added to the workplan registry make validate: ok (65 artifacts, 0 errors/warnings). make test: 22 passed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.9 KiB
1.9 KiB
Global Agent Brief
This brief summarizes the current canon service surface for agents.
- Infospace slug:
canon - Artifact count: 65
- Retrieval index items: 65
- 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 inspectPYTHONPATH=src python3 -m info_tech_canon validatePYTHONPATH=src python3 -m info_tech_canon graphPYTHONPATH=src python3 -m info_tech_canon indexPYTHONPATH=src python3 -m info_tech_canon profile validate small-saas
Retrieval Entry Points
agent/retrieval-index.mdagent/retrieval-index.yamlagent/retrieval-index.jsonagent/briefs/for per-artifact briefsagent/templates/canon-interface-card.template.yaml
Common Distinctions
- 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: Policy states intent or rule, control implements or enforces that rule, and evidence records why the claim should be trusted.
- 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.