Register with repo-manager and add agent guidance

Register gate-house as category: tooling, domain: infotech, workplan
prefix GH-WP, via rmgr scaffold. Baseline files: .repo-classification.yaml,
SCOPE.md, AGENTS.md, workplans/GH-WP-0001-foundation.md. rmgr conform
passes with no findings.

SCOPE.md is derived from INTENT.md; GH-WP-0001 targets milestone M0
(executable skeleton) from ArchitectureBlueprint.md §41.

Move ArchitectureBlueprint.md to the repository root, matching its own
reference layout (§32). spec/ retains the Active Secrets Management Canon,
the external standard Gate House conforms to.

Add CLAUDE.md documenting the document precedence (Canon → INTENT →
Blueprint → README), the load-bearing security invariants, the fixed
domain vocabulary, and the stable identifier scheme.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2564823@bnt-lap001
Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9

.repo-classification.yaml

@@ -0,0 +1,26 @@
+repo_classification:
+  standard: Repo Classification Standard
+  version: "1.0"
+  classified_at: "2026-08-24"
+  classified_by: human
+  category: tooling
+  domain: infotech
+  secondary_domains:
+    - agents
+  capability_tags:
+    - access-control
+    - identity
+    - governance
+    - platform
+    - evidence
+  business_stake:
+    - technology
+    - operations
+  business_mechanics:
+    - control
+    - operation
+  notes: >-
+    Deterministic authority plane for human, workload, and agent actions
+    across NetKingdom, and the reference implementation of the Active
+    Secrets Management (ASM) Plane. Long-lived control-plane component
+    reused across the ecosystem; not a domain hub, not a secrets manager.