Bernd Worsch
b5d73aa18b
Implements IHUB-WP-0009: closes four GAAF-2026 gaps before domain hub work begins. - TypeRegistry helper + controllers/views (hub_kind, hub_capability_manifest) - HubCapabilityManifest entity with validation and registry linkage - ARCHITECTURE-LAYERS.md + CI-enforced boundary contracts - Alembic migration 1743724800, fitness tests (Test/Architecture/) - GAAF spec, Operational Architecture spec, domain hub extension guide - Updates to CLAUDE.md, SCOPE.md, Schema.sql, Routes, FrontController, Types state_hub_sync: pending (tunnel was STALE at completion time; run fix-consistency) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
955 B
name, description, type
| name | description | type |
|---|---|---|
| IHF current phase | Current phase and workplan status for inter-hub IHF implementation | project |
Phases 1–8 complete. GAAF Compliance Foundation (IHUB-WP-0009) complete.
Why: All 8 phases of IHF v0.1 spec delivered. GAAF-2026 review identified critical gaps (no extension layer, no type registries, no hub kind classification, no fitness functions). IHUB-WP-0009 addressed all gaps as a prerequisite to Phase 9.
How to apply: Active workplan is IHUB-WP-0010 (Phase 9 — External API). Start with /ralph-workplan workplans/IHUB-WP-0010-ihf-phase9-external-api.md when ready. Type registries must remain seeded; all new type discriminators must reference a registry (enforced by fitness function Test 4 in CI). Domain hubs must register via HubCapabilityManifest before creating hub-owned types.
GAAF scorecard post-WP-0009: 3.34/5.0 (Usable but vulnerable — Phase 9 ready). Target ≥3.5 at Phase 10 exit.