Add retrieval agent briefs and interface cards

infospace/agent/global-agent-brief.md

@@ -6,8 +6,10 @@ This brief summarizes the current canon service surface for agents.
 
 - Infospace slug: `canon`
 - Artifact count: 29
+- Retrieval index items: 29
 - 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
 
@@ -15,6 +17,22 @@ This brief summarizes the current canon service surface for agents.
 - `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
+
+- **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 an actor wants something, scope bounds what is included, and purpose captures consumer demand or use case pressure on the repo.
 
 ## Consumption Notes