Bootstrap repo: State Hub registration, agent docs, TEN-WP-0001/0002

statehub register + repo-seed template scaffold (CLAUDE.md, .claude/rules/,
registry/). INTENT.md and SCOPE.md rewritten from the generated stub to
match net-kingdom's ratified tenant-engine-boundary-contract_v0.1.md
(Purpose, Responsibility Boundary, Non-Goals). topic_slug corrected from
the auto-assigned custodian default to netkingdom, matching key-cape and
user-engine.

TEN-WP-0001 (bootstrap) complete: files reviewed/refined, stack decided
(Python 3.12 + FastAPI, matching qonto-assistant's convention), first real
workplan seeded.

TEN-WP-0002 drafted: service skeleton, domain model (tenant/grouping/
capability-role/plan-grant), storage layer, and the three boundary-contract
API surfaces (cache-read for key-cape, live-lookup for flex-auth with an
explicit fail-closed requirement, write API behind a WriteAuthorizer seam
since real flex-auth integration is a declared non-goal for this pass).

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

.repo-classification.yaml

@@ -0,0 +1,26 @@
+repo_classification:
+  standard: Repo Classification Standard
+  version: '1.0'
+  classified_at: '2026-07-23'
+  classified_by: agent
+  category: product
+  domain: infotech
+  secondary_domains:
+  - financials
+  capability_tags:
+  - identity
+  - access-control
+  - tenancy
+  - platform
+  - operations
+  business_stake:
+  - technology
+  - operations
+  - legal
+  - product
+  business_mechanics:
+  - control
+  - operation
+  notes: Canonical owner of tenant-as-an-entity facts for NetKingdom -- tenant
+    existence, onboarding grouping, capability roles, and plan/subscription
+    assignment. See net-kingdom canon/standards/tenant-engine-boundary-contract_v0.1.md.