info-tech-canon/workplans/ITC-WP-0005-retrieval-agent-briefs-and-interface-cards.md

id, type, title, domain, repo, status, priority, created, updated, depends_on_workplans, state_hub_workstream_id

id	type	title	domain	repo	status	priority	created	updated	depends_on_workplans	state_hub_workstream_id
ITC-WP-0005	workplan	Retrieval Agent Briefs And Interface Cards	canon	info-tech-canon	proposed	medium	2026-05-23	2026-05-23	ITC-WP-0003 ITC-WP-0004	1dc61e3a-7451-42ac-bba7-1c6fa30c826c

ITC-WP-0005 - Retrieval Agent Briefs And Interface Cards

Goal

Make InfoTechCanon retrievable and usable by agents, tools, and consumer repositories without requiring them to read every full standard.

Intent

The canon needs compact, source-linked retrieval artifacts that preserve the important distinctions: Actor vs Subject vs Principal, Organization Role vs AccessRole vs CARING role, Policy vs Control vs Evidence, and similar rules.

Tasks

T01 - Agent briefs

id: ITC-WP-0005-T01
status: todo
priority: high
state_hub_task_id: "3e509e68-2f6d-43fb-a4da-a0289f38960c"

• Place the global agent brief under infospace/agent/.
• Add per-standard and per-model agent briefs.
• Validate that agent briefs point back to full source artifacts.

T02 - Retrieval index

id: ITC-WP-0005-T02
status: todo
priority: high
state_hub_task_id: "12f350a2-d6d2-402e-820a-5ef86478a562"

• Generate infospace/agent/retrieval-index.md and a JSON/YAML equivalent.
• Include stable IDs, canonical paths, summary, owned concepts, imports, warnings, and common distinctions.

T03 - Canon Interface Card template

id: ITC-WP-0005-T03
status: todo
priority: medium
state_hub_task_id: "12c17aeb-1da2-4a6f-b71d-cc8614a53394"

• Define a Canon Interface Card template.
• Include fields for owned concepts, produced concepts, consumed concepts, implemented profiles, mappings, validation expectations, and consumer needs.

T04 - Consumer brief templates

id: ITC-WP-0005-T04
status: todo
priority: medium
state_hub_task_id: "c504ffe6-1a4c-4ce6-85b4-4c455edaa461"

• Create brief templates for user-engine, railiance-fabric, and repo-scoping.
• Keep actual adoption workplans in those repos.

Acceptance

• Agents can start from compact briefs and retrieve full standards when needed.
• Interface Card templates are ready for first consumers.
• The retrieval index is generated and validated.