<aside> 🗺️

Roadmap status: ISAC implementation is defined from Stage 31 through Stage 55. This page is the controlled execution baseline for the Core v1 programme. Stage purpose, dependency order, release gates and merge discipline remain stable unless changed through explicit architecture review.

</aside>

<aside> 🟢

Current position: 25 September 2026: Stage 35 is complete. Foundation Stability Audit Phase 3 is in progress before implementation moves to Stage 36: External & Custom Providers. Completed-stage history remains immutable except through documented maintenance or correction.

</aside>

Development Controls

<aside> 🔒

Merge control: Each stage is implemented and validated in isolation. Subpart completion does not authorize merge. Merge occurs only after the full stage passes testing, documentation, performance/resource checks, governance review and formal closeout.

</aside>

Each stage begins from the last approved merged baseline. GCF 2.0 remains the frozen cognitive-framework dependency unless a separate GCF maintenance release is explicitly approved. ISAC stage work must not modify GCF outside the approved maintenance and change-control process.

Every stage closeout must answer five questions: Does it work? Is it governed? Is it resource-safe? Is it testable and reproducible? Did it preserve earlier behaviour?

Release Milestones

Milestone Stages Meaning
Foundation 31–35 Runnable ISAC core, terminal bootstrap, GCF resource adaptation, local model acquisition/runtime and adaptive local model layouts.
Personal ISAC 36–42 Optional external providers, stable identity, encrypted memory, user relationships, goals/initiative, skills and offline knowledge.
Aware & Connected ISAC 43–49 Environment awareness, voice/accessibility, Guardian Node, multi-user profiles, smart-home/physical awareness, sustainability and add-on platform.
Product Integration 50–53 Consumer setup, system-wide cognition integration, benchmark suite and failure/adversarial validation.
Release 54–55 Release candidate, final validation and ISAC Core v1.0 freeze.

Stage 31 - ISAC Core Foundation

Objective: Establish the first real ISAC executable and the architectural boundary between ISAC and frozen GCF 2.0. Stage 31 must create a small, testable runtime skeleton without prematurely implementing models, memory, skills or autonomy.

Work Packages

  1. 31A - Repository & Workspace Structure - Define crate/module layout, naming, dependency ownership, build profiles, feature flags and test organization.
  2. 31B - ISAC ↔ GCF Boundary - Introduce the narrow integration interface through which ISAC requests cognition/governance/resource information without reaching into GCF internals.
  3. 31C - Runtime Lifecycle - Define bootstrap, initialize, ready, degraded, shutting-down and failed lifecycle states with deterministic transitions.
  4. 31D - Configuration Foundation - Layer defaults, user configuration, environment overrides and validation without putting secrets into ordinary config.
  5. 31E - Filesystem & State Paths - Establish cross-platform application-data, config, cache, log, temporary and future model/memory locations.
  6. 31F - Diagnostics & Audit Bootstrap - Structured logs, startup diagnostics, version/build identifiers and GCF integration status.
  7. 31G - Terminal Bootstrap - Minimal isac process with logo/banner, status and a clean command-loop placeholder; no simulated or placeholder intelligence behaviour.
  8. 31H - Test Harness - Unit/integration test structure and deterministic GCF boundary mocks where appropriate.
  9. 31I - Stage Closeout - Clean build, clean shutdown, config validation, failure-path tests, documentation and architecture review.