coulomb/info-tech-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
info-tech-canon/infospace/agent/global-agent-brief.md
tegwick 372f671eef
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Distribute frozen federation corpus by concept destination 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
2026-09-06 00:44:37 +02:00

2.3 KiB
Raw Blame History

Global Agent Brief

This brief summarizes the current canon service surface for agents.

  • Infospace slug: canon
  • Artifact count: 80
  • Retrieval index items: 80
  • 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.