tegwick
1ac4f56783
Scaffold the repository to the repo-manager standard and establish its governance surface: INTENT declaring the Taxonomy-layer claim and boundary against NetKingdom, flex-auth, key-cape, OpenBao and whitehat-security; GOAL with migration invariants and success gates; SCOPE listing the extraction candidates and the unresolved boundary questions; AGENTS repo identity; repo classification. Add SECURITY-WP-0001 covering registration, the disposition review of InfoTechCanon's security material, the reference-impact survey, the federation interface card, and the handoff to a migration workplan. No canon content is moved yet — the migration waits on the reviewed disposition. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUkN13CAqtXWPXuEiEtmJj Assistant: claude-code Assistant-Model: opus Assistant-Process: 36656@bnt-lap001 Assistant-Session: 66d6eece-d245-43ca-85e8-68a1b5970a67
1.1 KiB
1.1 KiB
Agent instructions — security-canon
Repo Identity
Purpose: Orthogonal vocabulary and canonical model for security-related concepts, extending InfoTechCanon.
Domain: infotech
Repo slug: security-canon
Topic ID: fe2aaa78-9c20-4feb-b3d2-4fe0529572a3
Workplan prefix: SECURITY-WP-
Upstream canon: info-tech-canon
Orient: INTENT.md → GOAL.md → SCOPE.md → workplans/.
State Hub Integration
| Context | URL |
|---|---|
| Local workstation | http://127.0.0.1:8000 |
| Remote (railiance01, in-cluster) | http://10.43.68.154:8000 |
| Optional local edge relay | http://127.0.0.1:18080 |
Do not instruct a remote agent to use http://127.0.0.1:18000. That reverse tunnel is retired; on railiance01 reach the hub at the in-cluster address above.
Cross-repo waits
If blocked on another repo, look for a prj- driver workplan and follow coordination-engine spec/cross-owner-wait-mode-v0.1.md. Do not mint a stranded wait, implement flavor: residual, or message ops-warden for secrets.