CHECKING FOR UPDATESAutomatic check every 5 seconds

THE SPARK · EVIDENCE CONTROL PLANE

The Spark DadaTracker

v1.0.0 PROTOTYPEPRODUCTION

Evidence-backed tracking, roadmaps, progress, migration, installations, questionnaires, release gates, and artifacts for The Spark and F.O.U.R.

Production tracker is live · roadmap sources are connected

The Spark33%Current evidence-based portfolio estimate

F.O.U.R. parent weight90%36.891875% exact official model

InstaDater parent weight10%Top-level lifecycle service

Tracker stateLIVEPlanning, evidence, and roadmap views

Automatic planning portfolio

Roadmaps

Roadmap files are discovered recursively, parsed, deduplicated, hashed, and connected automatically. Only each component's Current Status is manually maintained from accepted evidence.

23Roadmap source files

21Automatically parsed roadmaps

21Connected components

ManualCurrent Status only

F.O.U.R. → Forgey Foundry · v0.1.0

ADAPTER SDK Roadmap

Provide the supported safe developer kit for connecting applications, components, providers, evidence systems, and profiles to Foundry contracts without copying engine, router, updater, or control logic.

100%phase total

For the family

ADAPTER SDK ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC290–541 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestoneGenerate a fixture adapter that passes schema, permission, package, and end-to-end tests, then pause.

Phase	Weight	ETUC	Evidence / stop gate
01 · Scope and adapter taxonomy	10%	20–36 active hours	Owner-approved API scope. · HOLD if SDK becomes runtime or permission bypass.
02 · Contracts and public API	15%	40–75 active hours	Contract tests and API review. · Return if SDK copies private schemas.
03 · Scaffolding and templates	18%	50–90 active hours	Golden generation snapshots and reproducibility tests. · HOLD on business logic or hidden unsafe defaults.
04 · Validators and diagnostics	15%	40–75 active hours	Negative validation suite. · HOLD if syntax-only validation can pass unsafe adapters.
05 · Capability and permission model	12%	35–65 active hours	Permission escalation and denial tests. · HOLD on inherited broad authority.
06 · Packaging and lifecycle metadata	10%	30–60 active hours	Package integrity and fixture install tests. · HOLD on unbounded latest dependencies.
07 · Integration proof	12%	45–80 active hours	Schema, permission, package, and end-to-end PASS. · Return to contracts on divergent adapter behavior.
08 · Hardening, documentation, and release	8%	30–60 active hours	Target-PC generation/build tests and Owner release gate. · No release without reproducibility and negative tests. · CROSS-COMPONENT DEPENDENCIES · Shared Schemas · Forgey Foundry Platform · Watcher Profile SDK / Generator · Master Engine · Forgey Control · Top-level InstaDater · BLOCKERS AND PROTECTED RISKS · The public API and exact package format are not frozen. · The boundary with Watcher Profile SDK / Generator requires explicit contract mapping. · TypeScript support remains conditional. · SPECIAL RULES · Python is the v1 implementation language unless a proven TypeScript consumer requires parallel support. · ROADMAP APPROVAL GATE · This roadmap is ready for Owner review but is not yet approved for · implementation. · Owner review must decide: · 1. Whether the north star and 100% definition are correct. · 2. Whether the phase weights and ETUC are accepted. · 3. Whether the dependencies and blockers are complete. · 4. Whether the Green pause point is correct. · 5. Whether the component weight/parent placement is accepted. · 6. Whether a later implementation-planning phase may begin. · Until explicit Owner approval, no implementation prompt or source change is · authorized.

Bare Minimum

Generate and validate one component adapter and one profile adapter using fixtures and stable contracts.
Comfortably Functional / Purple:
A routine developer workflow provides docs, examples, migrations, diagnostics, approved languages, reliable packaging, and low-friction compatibility checks.
First Green work target / pause point:
Generate a fixture adapter that passes schema, permission, package, and end-to-end tests, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Scope and adapter taxonomy 10% 20–36h
02. Contracts and public API 15% 40–75h

Comfortable target

A routine developer workflow provides docs, examples, migrations, diagnostics, approved languages, reliable packaging, and low-friction compatibility checks.
First Green work target / pause point:
Generate a fixture adapter that passes schema, permission, package, and end-to-end tests, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Scope and adapter taxonomy 10% 20–36h
02. Contracts and public API 15% 40–75h
03. Scaffolding and templates 18% 50–90h
04. Validators and diagnostics 15% 40–75h

Green pause point

Generate a fixture adapter that passes schema, permission, package, and end-to-end tests, then pause.

Dependencies

: Platform component model.
Deliverables:
Adapter categories and ownership.
Python-first language decision.
SDK/non-SDK boundaries.
Evidence gate:
Owner-approved API scope.
Stop / return condition:
HOLD if SDK becomes runtime or permission bypass.
PHASE 02 — Contracts and public API
Weight: 15%
ETUC: 40–75 active hours
Dependencies: Shared Schemas core contracts.
Deliverables:
Stable interfaces, lifecycle hooks, error model, compatibility metadata.
Evidence gate:
Contract tests and API review.
Stop / return condition:
Return if SDK copies private schemas.
PHASE 03 — Scaffolding and templates

Blockers

The public API and exact package format are not frozen.
The boundary with Watcher Profile SDK / Generator requires explicit contract mapping.
TypeScript support remains conditional.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0006_Adapter_SDK_Roadmap_v0.1.0.txt
SHA-256 C52C1B701B1E8B331B2BEC186D3949967F6F78C072214362C0AD3ECCD8B5CBD6

100% completion definitionApproved adapter categories can be created with stable APIs, deterministic scaffolds, validated manifests, least-privilege capabilities, tests, packages, migration guidance, diagnostics, documentation, and proven compatibility.

F.O.U.R. → Forgey Foundry · v0.1.0

CROSS-DEVICE ROUTER Roadmap

Provide the secure transport-only fabric connecting authorized Forgey devices, synchronizing persistent inventory and carrying signed messages, heartbeats, receipts, results, and evidence references without deciding or executing work.

100%phase total

For the family

CROSS-DEVICE ROUTER ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC440–795 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestoneComplete two-device fixture transport and inventory synchronization without live watcher execution, then pause.

Phase	Weight	ETUC	Evidence / stop gate
01 · Goal, protocol, and transport boundary	10%	30–55 active hours	Owner-approved protocol specification. · HOLD if Router grants control or execution authority.
02 · Identity and device enrollment	12%	45–80 active hours	Enrollment, duplicate, revocation, and recovery tests. · HOLD on insecure or silent enrollment.
03 · Device client	13%	55–95 active hours	Client unit/integration and offline tests. · HOLD on inbound watcher ports or credential leakage.
04 · Deterministic fixture backend	12%	50–90 active hours	Two-device deterministic test environment. · Do not deploy cloud before fixture protocol proof.
05 · Persistence, queues, and idempotency	10%	45–80 active hours	Crash/restart/replay/duplicate/expiry tests. · HOLD if unsafe commands survive expiry or revalidation.
06 · Forgey Control and inventory integration	12%	55–95 active hours	Control↔Router two-device fixture PASS. · HOLD if status conflates connected, controllable, or executing.
07 · Cloud backend and domain deployment	12%	55–105 active hours	Preview/staging security, outage, and load tests. · No production DNS/domain activation without Owner authorization.
08 · Recovery, security, and disaster hardening	12%	60–110 active hours	Disaster and security exercises. · HOLD on irrecoverable identity or queue uncertainty.
09 · Production release and staged device enrollment	7%	45–85 active hours	Owner release gate and per-device acceptance. · No real Roy enrollment without separate authorization and rollback proof. · CROSS-COMPONENT DEPENDENCIES · Shared Schemas · Forgey Control · Master Engine · Forgey Foundry Platform · Top-level InstaDater · Device installation roadmap · BLOCKERS AND PROTECTED RISKS · Cloud deployment, domain activation, credential storage, persistence, and production topology are unresolved. · Real Roy-device enrollment is not authorized by this roadmap. · Automatic inventory synchronization and complete Control integration are not accepted. · SPECIAL RULES · Cloud deployment remains a later explicit authorization. · Transport delivery never proves target execution completion. · ROADMAP APPROVAL GATE · This roadmap is ready for Owner review but is not yet approved for · implementation. · Owner review must decide: · 1. Whether the north star and 100% definition are correct. · 2. Whether the phase weights and ETUC are accepted. · 3. Whether the dependencies and blockers are complete. · 4. Whether the Green pause point is correct. · 5. Whether the component weight/parent placement is accepted. · 6. Whether a later implementation-planning phase may begin. · Until explicit Owner approval, no implementation prompt or source change is · authorized.

Bare Minimum

Two fixture devices enroll, inventory synchronizes, signed safe messages deliver with receipts, outages/reconnect work, and dangerous offline commands are rejected.
Comfortably Functional / Purple:
Reliable daily multi-device operation with mature credential lifecycle, recovery, observability, bounded queues, portable backend, and low support burden.
First Green work target / pause point:
Complete two-device fixture transport and inventory synchronization without live watcher execution, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Goal, protocol, and transport boundary 10% 30–55h
02. Identity and device enrollment 12% 45–80h

Comfortable target

Reliable daily multi-device operation with mature credential lifecycle, recovery, observability, bounded queues, portable backend, and low support burden.
First Green work target / pause point:
Complete two-device fixture transport and inventory synchronization without live watcher execution, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Goal, protocol, and transport boundary 10% 30–55h
02. Identity and device enrollment 12% 45–80h
03. Device client 13% 55–95h
04. Deterministic fixture backend 12% 50–90h

Green pause point

Complete two-device fixture transport and inventory synchronization without live watcher execution, then pause.

Dependencies

: Shared Schemas direction.
Deliverables:
Transport-only architecture.
Message lifecycle and uncertainty model.
Threat and trust-boundary model.
Evidence gate:
Owner-approved protocol specification.
Stop / return condition:
HOLD if Router grants control or execution authority.
PHASE 02 — Identity and device enrollment
Weight: 12%
ETUC: 45–80 active hours
Dependencies: Identity schemas and Owner policy.
Deliverables:
Stable device IDs, credentials, roles, namespaces, revocation, rotation, recovery, and enrollment evidence.
Evidence gate:
Enrollment, duplicate, revocation, and recovery tests.
Stop / return condition:
HOLD on insecure or silent enrollment.
PHASE 03 — Device client

Blockers

Cloud deployment, domain activation, credential storage, persistence, and production topology are unresolved.
Real Roy-device enrollment is not authorized by this roadmap.
Automatic inventory synchronization and complete Control integration are not accepted.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0009_Cross_Device_Router_Roadmap_v0.1.0.txt
SHA-256 D5EC3CFFF9F38D8A0DC22C66284A221A894E2C9AD531A8472DC7AF621281E898

100% completion definitionApproved devices securely enroll, connect outbound, synchronize inventory, exchange durable/idempotent messages with truthful lifecycle and receipts, recover from outages, rotate/revoke credentials, and operate on a production-grade portable backend with Owner acceptance.

The Spark → F.O.U.R. · v1.0.0

F.O.U.R. — ARCHIVE AND CONTINUITY Roadmap

Build the complete preservation and continuity system for legacy roots, migration evidence, snapshots, superseded material, restoration, and safe future cleanup.

100%phase total

For the family

F.O.U.R. — ARCHIVE AND CONTINUITY ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC490–865 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Finish evidence-backed copy-first migration without deletion. - Pause for Owner and portfolio review before continuing.

Phase	Weight	ETUC	Evidence / stop gate
01 · Policy, verification taxonomy, retention, and deletion gates	12%	45–80 active hours	Owner approves policy. · Methods are never treated as equivalent. · HOLD on ambiguous verdicts or automatic cleanup.
02 · Authoritative inventory, source maps, and dependency discovery	12%	55–95 active hours	Inventory completeness report passes. · No overwrite guesses. · Return if unresolved material is not preserved honestly.
03 · Checkpointed copy, manifest, hashing, and verification tools	14%	75–130 active hours	Resume after interruption. · Successful copy work is not repeated unnecessarily. · HOLD on endless non-checkpointed hashing or destructive sync.
04 · Evidence-backed root archives and migration continuity	16%	90–155 active hours	Included roots are verified using declared methods. · No deletion. · Restore map complete. · Return on byte/count/hash conflict or lost staging.
05 · Searchable indexes, provenance, supersession, and handoffs	12%	55–95 active hours	A future maintainer can reconstruct origin and status. · HOLD if archives become indistinguishable from active source.
06 · Off-device backup and disaster protection	12%	60–110 active hours	Off-device copy is verified. · Same-drive archive is not called disaster backup. · Return if privacy or restore capability is unproven.
07 · Restore drills, repair, rollback, and observation	12%	65–115 active hours	Restored system/data is verified. · Prior working state is preserved. · No cleanup if restore or observation fails.
08 · Cleanup governance, legacy retirement, documentation, and release	10%	45–85 active hours	No unresolved dependencies. · Owner separately approves deletion. · Automatic cleanup remains rejected. · Total phase weight: 100% · Total provisional ETUC: 490–865 active hours · DEPENDENCIES · F.O.U.R. HQ. · Developer Tools. · Test/Fixture System. · Documentation. · Off-device storage. · InstaDater where applicable. · PROTECTED BLOCKERS · Unverified claims. · Destructive sync. · Infinite hashing. · Lost staging. · Premature deletion. · DEFERRED · Deletion of legacy roots. · EXPLICITLY REJECTED · Automatic cleanup after copy. · Calling tiered verification Full SHA-256. · SPECIAL OWNER RULES · Unresolved files remain preserved with original relative paths and reports. · Verification method is part of every verdict. · DADATRACKER RULES · Roadmap discovery, hash, version, source, and CONNECTED state are automatic. · Current Status and numerical Blue Current remain manually evidence-maintained. · A numerical tracker remains visible for this item. · Roadmap existence does not prove installed, running, runtime-connected, · controllable, released, or healthy state. · Family-facing UI shows `CONNECTED! · AUTOMATIC` and `CURRENT STATUS · MANUAL`. · Internal PASS WITH WARNINGS and implementation-authorization labels remain · technical artifacts, not family-facing badges. · ROADMAP APPROVAL GATE · Approved planning source. Implementation remains a separate explicit Owner · decision.

Bare Minimum

Verified intact archives and restore maps.
Declared verification methods.
Sources preserved.
No premature deletion.
Comfortably Functional / Purple:
Checkpointed archives.
Searchable indexes.
Off-device protection.
Restore drills and cleanup reviews.
First Green work target / pause point:
Finish evidence-backed copy-first migration without deletion.
Pause for Owner and portfolio review before continuing.

Comfortable target

Checkpointed archives.
Searchable indexes.
Off-device protection.
Restore drills and cleanup reviews.
First Green work target / pause point:
Finish evidence-backed copy-first migration without deletion.
Pause for Owner and portfolio review before continuing.

Green pause point

- Finish evidence-backed copy-first migration without deletion. - Pause for Owner and portfolio review before continuing.

Dependencies

F.O.U.R. HQ.
Developer Tools.
Test/Fixture System.
Documentation.
Off-device storage.
InstaDater where applicable.

Blockers

Unverified claims.
Destructive sync.
Infinite hashing.
Lost staging.
Premature deletion.
DEFERRED
Deletion of legacy roots.
EXPLICITLY REJECTED
Automatic cleanup after copy.
Calling tiered verification Full SHA-256.
SPECIAL OWNER RULES
Unresolved files remain preserved with original relative paths and reports.
Verification method is part of every verdict.
DADATRACKER RULES
Roadmap discovery, hash, version, source, and CONNECTED state are automatic.
Current Status and numerical Blue Current remain manually evidence-maintained.
A numerical tracker remains visible for this item.
Roadmap existence does not prove installed, running, runtime-connected,
controllable, released, or healthy state.
Family-facing UI shows `CONNECTED! · AUTOMATIC` and `CURRENT STATUS · MANUAL`.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/Batch_05/0021_FOUR_Archive_and_Continuity_Roadmap_v1.0.0.txt
SHA-256 43458FF1370D182253145F05D33A8EE0CC62F9C908DDD7948933480ED64A0F1B

100% completion definitionArchive policy, resumable tools, verified archives, indexes, off-device protection, restore drills, retention, cleanup gates, documentation, and Owner acceptance are complete.

The Spark → F.O.U.R. (cross-cutting program) · v1.0.0

F.O.U.R. — DEVICE INSTALLATION AND MULTI-PC DEPLOYMENT Roadmap

Build the repeatable secure process for installing, enrolling, configuring, updating, verifying, recovering, and retiring the correct F.O.U.R. systems on approved computers.

100%phase total

For the family

F.O.U.R. — DEVICE INSTALLATION AND MULTI-PC DEPLOYMENT ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC535–925 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Approve device-role/install matrices and complete a no-change preflight/dry-run. - Pause for Owner and portfolio review before continuing.

Phase	Weight	ETUC	Evidence / stop gate
01 · Device roles, identities, hardware profiles, and install matrices	12%	55–95 active hours	Owner approves matrices. · No identical-all-PC assumption. · HOLD on unknown hardware, roles, paths, or install sets.
02 · Website installer, Resend verification, and onboarding choice	14%	65–110 active hours	Verified-email and failure tests pass. · No installation starts before route confirmation. · Return if verification, privacy, or account recovery is unclear.
03 · InstaDater bootstrap and F.O.U.R. Desktop authority	16%	80–135 active hours	Clean fixture install and rollback pass. · F.O.U.R. Desktop can authorize/initiate lifecycle transactions. · InstaDater executes them deterministically. · HOLD if F.O.U.R. Desktop bypasses InstaDater execution or InstaDater makes user-facing authority decisions.
04 · Manual and AI-guided catalog selection and dependency planning	14%	75–130 active hours	Manual and AI routes produce reviewable manifests. · AI cannot silently install unsupported apps. · Return if AI selection is opaque or conflicts with device role.
05 · Forgey Foundry installation sequence	14%	80–145 active hours	Dependency and partial-failure tests pass. · No component is marked ready before verification. · HOLD on unsupported component release state.
06 · Enrollment, Router/Control visibility, data placement, and offline behavior	12%	70–120 active hours	No invented connectivity. · No broad data sync. · Credential rotation/revocation pass. · HOLD on hidden remote shell or mixed family data.
07 · Update rings, repair, rollback, recovery, and acceptance	10%	65–110 active hours	Acceptance gate passes. · Installed is not treated as accepted without evidence. · No cutover on failed recovery or unresolved warnings.
08 · Expansion, retirement, documentation, and support	8%	45–80 active hours	Expansion and retirement drills pass. · Artifact index is complete. · No device retirement without verified data disposition. · Total phase weight: 100% · Total provisional ETUC: 535–925 active hours · DEPENDENCIES · Website/bootstrap service. · Resend. · InstaDater. · F.O.U.R. Desktop. · Shared Schemas. · Router and Forgey Control. · Family/component packages. · Test and Documentation systems. · PROTECTED BLOCKERS · Wrong paths. · Hardware overload. · Credential leaks. · Early legacy cutover. · Mixed user data. · Unsupported remote management. · Desktop/InstaDater authority confusion. · DEFERRED · Automatic installation of unreleased families/components. · Broad all-data synchronization. · EXPLICITLY REJECTED · Hidden remote shell. · F.O.U.R. Desktop bypassing InstaDater execution. · InstaDater silently choosing user-facing products without Desktop/user authority. · SPECIAL OWNER RULES · F.O.U.R. Desktop owns user-facing install and update authority. · InstaDater owns transaction execution, package verification, repair, rollback, and evidence. · Forgey Control remains the Foundry runtime-action controller; app lifecycle authority is separate. · DADATRACKER RULES · Roadmap discovery, hash, version, source, and CONNECTED state are automatic. · Current Status and numerical Blue Current remain manually evidence-maintained. · A numerical tracker remains visible for this item. · Roadmap existence does not prove installed, running, runtime-connected, · controllable, released, or healthy state. · Family-facing UI shows `CONNECTED! · AUTOMATIC` and `CURRENT STATUS · MANUAL`. · Internal PASS WITH WARNINGS and implementation-authorization labels remain · technical artifacts, not family-facing badges. · ROADMAP APPROVAL GATE · Approved planning source. Implementation remains a separate explicit Owner · decision.

Bare Minimum

One-device core install with inventory, rollback, offline operation, and no legacy damage.
F.O.U.R. Desktop catalog and lifecycle authority.
InstaDater execution evidence.
Comfortably Functional / Purple:
Reliable Doonchy/Roy operation.
Staged updates.
Remote visibility/control where approved.
Recovery and low support burden.
First Green work target / pause point:
Approve device-role/install matrices and complete a no-change preflight/dry-run.
Pause for Owner and portfolio review before continuing.

Comfortable target

Reliable Doonchy/Roy operation.
Staged updates.
Remote visibility/control where approved.
Recovery and low support burden.
First Green work target / pause point:
Approve device-role/install matrices and complete a no-change preflight/dry-run.
Pause for Owner and portfolio review before continuing.

Green pause point

- Approve device-role/install matrices and complete a no-change preflight/dry-run. - Pause for Owner and portfolio review before continuing.

Dependencies

Website/bootstrap service.
Resend.
InstaDater.
F.O.U.R. Desktop.
Shared Schemas.
Router and Forgey Control.
Family/component packages.
Test and Documentation systems.

Blockers

Wrong paths.
Hardware overload.
Credential leaks.
Early legacy cutover.
Mixed user data.
Unsupported remote management.
Desktop/InstaDater authority confusion.
DEFERRED
Automatic installation of unreleased families/components.
Broad all-data synchronization.
EXPLICITLY REJECTED
Hidden remote shell.
F.O.U.R. Desktop bypassing InstaDater execution.
InstaDater silently choosing user-facing products without Desktop/user authority.
SPECIAL OWNER RULES
F.O.U.R. Desktop owns user-facing install and update authority.
InstaDater owns transaction execution, package verification, repair, rollback, and evidence.
Forgey Control remains the Foundry runtime-action controller; app lifecycle authority is separate.
DADATRACKER RULES
Roadmap discovery, hash, version, source, and CONNECTED state are automatic.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/Batch_06/0022_FOUR_Device_Installation_and_Multi_PC_Deployment_Roadmap_v1.0.0.txt
SHA-256 48367C6FBFE6BA2C6FACE39B631F7B4D749CCE17BAE4D50B5C48317726F19AFD

100% completion definitionThe complete device program, website bootstrap, Resend verification, Manual/AI-guided onboarding, F.O.U.R. Desktop authority, InstaDater transactions, role-based packages, enrollment, updates, recovery, offline behavior, and Owner acceptance are complete.

The Spark → F.O.U.R. · v1.0.0

F.O.U.R. — FORGEY AIO Roadmap

Build the complete local-and-cloud AI platform for models, chat, projects, memory, files, vision, tools, evaluations, and safe cross-app help.

100%phase total

For the family

F.O.U.R. — FORGEY AIO ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC755–1,335 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Approve canonical architecture and run one evaluated local-model workflow without moving model blobs. - Pause for Owner and portfolio review before continuing.

Phase	Weight	ETUC	Evidence / stop gate
01 · Existing AIO roadmap, training, source, and migration-boundary reconciliation	10%	55–95 active hours	No AIO status is lost. · Paths and hashes are recorded. · No physical migration occurs. · HOLD if training truth or model blobs cannot be preserved.
02 · Providers, models, routing, hardware profiles, and resource policy	14%	90–155 active hours	No silent cloud route. · Target-hardware evaluations pass. · Shared memory is never reported as dedicated VRAM. · HOLD on hardware overclaims or hidden cloud upload.
03 · Unified chat, projects, coding, files, and cross-app personal context	16%	100–175 active hours	Project isolation passes. · Context provenance is visible. · No secret/system-prompt leakage. · Return if cross-user or cross-project context leaks.
04 · Broad file and tool capability with hardcoded safety	16%	110–190 active hours	Representative file operations pass. · Forced-failure rollback passes. · No data loss or fabricated state. · HOLD if model output becomes authority or safety rules can be bypassed.
05 · SQLite3 memory, retrieval, consent, privacy, and family-wide learning	12%	80–140 active hours	Memory provenance/deletion pass. · Family-user isolation passes. · Backup/restore passes. · Return if memory is hidden, uncorrectable, or undeletable.
06 · Vision, multimodal, documents, audio, tools, and app integrations	10%	80–145 active hours	Unsupported capabilities are never promised. · Modality privacy and permission tests pass. · HOLD on capability hallucination or unsafe app access.
07 · Training, adapters, datasets, evaluation, and model lifecycle	10%	110–200 active hours	Task-specific coding, vision, tool, privacy, and latency evidence passes. · Metrics are reproducible. · HOLD on fake metrics, contamination, or unsupported release.
08 · Cloud availability, accounts, synchronization, cost, and offline fallback	6%	60–110 active hours	Cloud-offline tests pass. · No silent upload. · Costs and export are visible. · Return if cloud becomes mandatory or opaque.
09 · Polish, installation, recovery, documentation, and release	6%	70–125 active hours	Tests/build/security/recovery pass. · Target-hardware benchmark and local/cloud acceptance pass. · No release before evaluations, recovery, and truthful capability labels pass. · Total phase weight: 100% · Total provisional ETUC: 755–1,335 active hours · DEPENDENCIES · Ollama/local models. · Optional cloud providers. · Forgey Control/tool contracts. · Shared Schemas. · InstaDater and F.O.U.R. Desktop. · Training/evaluation systems. · PROTECTED BLOCKERS · Hardware overclaims. · Silent cloud upload. · Unsafe file changes. · Model-blob damage. · Fake evaluation progress. · Unresolved 18% versus 20% weight. · DEFERRED · Physical migration of D:\05_Forgey_AI and model blobs until separately authorized. · EXPLICITLY REJECTED · Hidden data sale. · Fake metrics. · Unrecoverable file tools. · SPECIAL OWNER RULES · Broad file addressability is Owner-approved, but no-fake-data and no-data-loss are immutable hard rules. · SQLite3 memory must remain inspectable, editable, exportable, and deletable. · Cloud is optional at runtime but required in the 100% product capability. · DADATRACKER RULES · Roadmap discovery, hash, version, source, and CONNECTED state are automatic. · Current Status and numerical Blue Current remain manually evidence-maintained. · A numerical tracker remains visible for this item. · Roadmap existence does not prove installed, running, runtime-connected, · controllable, released, or healthy state. · Family-facing UI shows `CONNECTED! · AUTOMATIC` and `CURRENT STATUS · MANUAL`. · Internal PASS WITH WARNINGS and implementation-authorization labels remain · technical artifacts, not family-facing badges. · ROADMAP APPROVAL GATE · Approved planning source. Implementation remains a separate explicit Owner · decision.

Bare Minimum

Reliable local chat/projects.
Model selection and files.
Inspectable SQLite3 memory.
Supported coding/vision.
Privacy and recovery.
Comfortably Functional / Purple:
Polished multi-model assistant.
Evaluations and multimodal tools.
Cross-app personal context.
Hardware optimization.
Optional cloud availability.
First Green work target / pause point:

Comfortable target

Polished multi-model assistant.
Evaluations and multimodal tools.
Cross-app personal context.
Hardware optimization.
Optional cloud availability.
First Green work target / pause point:
Approve canonical architecture and run one evaluated local-model workflow without moving model blobs.
Pause for Owner and portfolio review before continuing.

Green pause point

- Approve canonical architecture and run one evaluated local-model workflow without moving model blobs. - Pause for Owner and portfolio review before continuing.

Dependencies

Ollama/local models.
Optional cloud providers.
Forgey Control/tool contracts.
Shared Schemas.
InstaDater and F.O.U.R. Desktop.
Training/evaluation systems.

Blockers

Hardware overclaims.
Silent cloud upload.
Unsafe file changes.
Model-blob damage.
Fake evaluation progress.
Unresolved 18% versus 20% weight.
DEFERRED
Physical migration of D:\05_Forgey_AI and model blobs until separately authorized.
EXPLICITLY REJECTED
Hidden data sale.
Fake metrics.
Unrecoverable file tools.
SPECIAL OWNER RULES
Broad file addressability is Owner-approved, but no-fake-data and no-data-loss are immutable hard rules.
SQLite3 memory must remain inspectable, editable, exportable, and deletable.
Cloud is optional at runtime but required in the 100% product capability.
DADATRACKER RULES
Roadmap discovery, hash, version, source, and CONNECTED state are automatic.
Current Status and numerical Blue Current remain manually evidence-maintained.
A numerical tracker remains visible for this item.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/Batch_05/0018_FOUR_Forgey_AIO_Roadmap_v1.0.0.txt
SHA-256 A4B77996761A92C471FB43DCEC2725C482E79A9E0F17A8289F3B8DAE2CABCB42

100% completion definitionForgey AIO is fully local/cloud capable, secured, evaluated, documented, installable, recoverable, hardware-aware, cross-app integrated, Owner-accepted, and preserves all training/model evidence.

The Spark → F.O.U.R. · v1.0.0

F.O.U.R. — FORGEY UTILITIES Roadmap

Build the governed family of reusable F.O.U.R. utilities that do not belong to one product and can be safely cataloged, installed, updated, documented, and retired.

100%phase total

For the family

F.O.U.R. — FORGEY UTILITIES ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC365–640 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Complete the authoritative inventory and classify every legacy utility. - Pause for Owner and portfolio review before continuing.

Phase	Weight	ETUC	Evidence / stop gate
01 · Authoritative inventory and classification	18%	55–95 active hours	Every discovered utility is classified. · No duplicate ownership. · HOLD if an active utility remains unowned or path truth is unresolved.
02 · Utility standards, safety, dry-run, schemas, and UX	14%	45–80 active hours	Negative tests pass. · Dry-run performs no writes. · Standards are approved. · HOLD on destructive defaults or hidden dependencies.
03 · Core read-only and low-risk utility catalog	18%	70–120 active hours	Deterministic fixture results. · No source mutation. · Examples are documented. · Return if utilities disagree on truth.
04 · Packaging, installation, update, repair, and compatibility	14%	55–95 active hours	Tamper rejection passes. · Install/rollback tests pass. · Versions are truthful. · HOLD if provenance or rollback is missing.
05 · Cross-family integration and reusable UX	14%	55–95 active hours	Two-family integration tests pass. · No family-specific ownership leakage. · Return if a utility becomes a hidden production dependency.
06 · Cleanup planning, retirement, archive, and replacement	12%	45–80 active hours	No active dependency remains before retirement. · Historical context is preserved. · No deletion without separate fresh approval.
07 · Documentation, acceptance, and release	10%	40–75 active hours	Tests/build/install/rollback pass. · User review and artifact index pass. · No release with unsafe or unowned tools. · Total phase weight: 100% · Total provisional ETUC: 365–640 active hours · DEPENDENCIES · F.O.U.R. Desktop. · InstaDater. · Shared Schemas. · Foundry Developer Tools. · Test/Documentation systems. · Archive & Continuity. · PROTECTED BLOCKERS · Dumping-ground growth. · Duplicate ownership. · Destructive defaults. · Stale paths. · Undocumented dependencies. · DEFERRED · Public toolbox. · EXPLICITLY REJECTED · Keeping unsafe or unowned scripts active. · SPECIAL OWNER RULES · A utility must be reusable across families; otherwise it stays with its owning product. · DADATRACKER RULES · Roadmap discovery, hash, version, source, and CONNECTED state are automatic. · Current Status and numerical Blue Current remain manually evidence-maintained. · A numerical tracker remains visible for this item. · Roadmap existence does not prove installed, running, runtime-connected, · controllable, released, or healthy state. · Family-facing UI shows `CONNECTED! · AUTOMATIC` and `CURRENT STATUS · MANUAL`. · Internal PASS WITH WARNINGS and implementation-authorization labels remain · technical artifacts, not family-facing badges. · ROADMAP APPROVAL GATE · Approved planning source. Implementation remains a separate explicit Owner · decision.

Bare Minimum

Authoritative catalog.
High-value read-only/low-risk tools.
Safety standards.
Install and rollback.
Comfortably Functional / Purple:
Curated toolbox.
Consistent UX/docs/updates.
Diagnostics and compatibility.
Clean retirement.
First Green work target / pause point:
Complete the authoritative inventory and classify every legacy utility.
Pause for Owner and portfolio review before continuing.

Comfortable target

Curated toolbox.
Consistent UX/docs/updates.
Diagnostics and compatibility.
Clean retirement.
First Green work target / pause point:
Complete the authoritative inventory and classify every legacy utility.
Pause for Owner and portfolio review before continuing.

Green pause point

- Complete the authoritative inventory and classify every legacy utility. - Pause for Owner and portfolio review before continuing.

Dependencies

F.O.U.R. Desktop.
InstaDater.
Shared Schemas.
Foundry Developer Tools.
Test/Documentation systems.
Archive & Continuity.

Blockers

Dumping-ground growth.
Duplicate ownership.
Destructive defaults.
Stale paths.
Undocumented dependencies.
DEFERRED
Public toolbox.
EXPLICITLY REJECTED
Keeping unsafe or unowned scripts active.
SPECIAL OWNER RULES
A utility must be reusable across families; otherwise it stays with its owning product.
DADATRACKER RULES
Roadmap discovery, hash, version, source, and CONNECTED state are automatic.
Current Status and numerical Blue Current remain manually evidence-maintained.
A numerical tracker remains visible for this item.
Roadmap existence does not prove installed, running, runtime-connected,
controllable, released, or healthy state.
Family-facing UI shows `CONNECTED! · AUTOMATIC` and `CURRENT STATUS · MANUAL`.
Internal PASS WITH WARNINGS and implementation-authorization labels remain
technical artifacts, not family-facing badges.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/Batch_05/0019_FOUR_Forgey_Utilities_Roadmap_v1.0.0.txt
SHA-256 94A5D9DFDA94A9407EB0602F6251BC2212E674F39DD5B6423F4E4BD8B6E26DD6

100% completion definitionThe complete utility catalog is reconciled, secured, tested, consistently packaged, documented, installable, recoverable, versioned, maintained, and safely retired with Owner acceptance.

The Spark → F.O.U.R. · v1.0.0

F.O.U.R. — FUTURE FAMILIES Roadmap

Build the governed incubation area for truly new F.O.U.R. families that cannot fit existing families and pass strict Owner-approved intake.

100%phase total

For the family

F.O.U.R. — FUTURE FAMILIES ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC295–530 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Approve the family intake scorecard and zero-active-family baseline. - Pause for Owner and portfolio review before continuing.

Phase	Weight	ETUC	Evidence / stop gate
01 · Intake standard, 9.5/10 scorecard, and zero-active-family baseline	18%	40–70 active hours	Scorecard is reviewed. · No active family is falsely claimed. · HOLD if family criteria can be bypassed.
02 · Namespace, collision, architecture, and portfolio analysis	18%	45–80 active hours	Proposal proves it cannot be an app/component. · No duplicate authority. · Reject if an existing family can own it.
03 · Isolated incubation sandbox and capacity limits	16%	50–90 active hours	Sandbox separation tests pass. · No portfolio progress is inherited. · HOLD on live-data reach or abandoned-parallel risk.
04 · Prototype evidence and comparative evaluation	18%	65–115 active hours	9.5/10 threshold is met with evidence. · No unsupported claims. · Return or retire if evidence weakens.
05 · Owner promotion, weight rebalance, migration, and release gate	16%	55–100 active hours	Promotion is explicit and reversible. · Weights total 100%. · No automatic promotion.
06 · Retirement, archive, lessons, and continuity	14%	40–75 active hours	No active dependencies. · Context is preserved. · No abandoned prototype remains silently active. · Total phase weight: 100% · Total provisional ETUC: 295–530 active hours · DEPENDENCIES · F.O.U.R. HQ. · Shared Schemas. · Test/Fixture System. · Archive & Continuity. · DadaTracker. · PROTECTED BLOCKERS · Family proliferation. · Duplicated products. · Inherited authority. · Abandoned prototypes. · Weights exceeding 100%. · DEFERRED · All unnamed families. · EXPLICITLY REJECTED · Automatic promotion. · Weak ideas below 9.5/10. · SPECIAL OWNER RULES · A good idea is not automatically a family. · One major incubation at a time is the default. · DADATRACKER RULES · Roadmap discovery, hash, version, source, and CONNECTED state are automatic. · Current Status and numerical Blue Current remain manually evidence-maintained. · A numerical tracker remains visible for this item. · Roadmap existence does not prove installed, running, runtime-connected, · controllable, released, or healthy state. · Family-facing UI shows `CONNECTED! · AUTOMATIC` and `CURRENT STATUS · MANUAL`. · Internal PASS WITH WARNINGS and implementation-authorization labels remain · technical artifacts, not family-facing badges. · ROADMAP APPROVAL GATE · Approved planning source. Implementation remains a separate explicit Owner · decision.

Bare Minimum

One repeatable intake gate.
9.5/10 scorecard.
Isolated prototype process.
Zero-active-family truth.
Comfortably Functional / Purple:
Reliable incubation.
Portfolio comparison.
Promotion workflow.
Clean retirement.
First Green work target / pause point:
Approve the family intake scorecard and zero-active-family baseline.
Pause for Owner and portfolio review before continuing.

Comfortable target

Reliable incubation.
Portfolio comparison.
Promotion workflow.
Clean retirement.
First Green work target / pause point:
Approve the family intake scorecard and zero-active-family baseline.
Pause for Owner and portfolio review before continuing.

Green pause point

- Approve the family intake scorecard and zero-active-family baseline. - Pause for Owner and portfolio review before continuing.

Dependencies

F.O.U.R. HQ.
Shared Schemas.
Test/Fixture System.
Archive & Continuity.
DadaTracker.

Blockers

Family proliferation.
Duplicated products.
Inherited authority.
Abandoned prototypes.
Weights exceeding 100%.
DEFERRED
All unnamed families.
EXPLICITLY REJECTED
Automatic promotion.
Weak ideas below 9.5/10.
SPECIAL OWNER RULES
A good idea is not automatically a family.
One major incubation at a time is the default.
DADATRACKER RULES
Roadmap discovery, hash, version, source, and CONNECTED state are automatic.
Current Status and numerical Blue Current remain manually evidence-maintained.
A numerical tracker remains visible for this item.
Roadmap existence does not prove installed, running, runtime-connected,
controllable, released, or healthy state.
Family-facing UI shows `CONNECTED! · AUTOMATIC` and `CURRENT STATUS · MANUAL`.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/Batch_05/0020_FOUR_Future_Families_Roadmap_v1.0.0.txt
SHA-256 B9E51DEAC3FCDBBB391886883F663388CE3FD7B987007F078899F1996A2FA686

100% completion definitionThe intake, scoring, sandbox, prototype, promotion, weight-rebalance, retirement, security, documentation, and continuity system is fully implemented and Owner-accepted.

The Spark → F.O.U.R. · v1.0.0

F.O.U.R. — LPS PORTFOLIO RECONCILIATION Roadmap

Complete the private family operating system for planning, calendars, tasks, habits, goals, nine life pillars, guides, coordination, approved AI, and automation.

100%phase total

For the family

F.O.U.R. — LPS PORTFOLIO RECONCILIATION ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC480–845 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Reconcile the dedicated LPS roadmap, lock the daily MVP, and prove one family daily workflow end to end. - Pause for Owner and portfolio review before continuing.

Phase	Weight	ETUC	Evidence / stop gate
01 · Existing LPS roadmap, source, runtime, and MongoDB reconciliation	10%	35–65 active hours	Current source/build/runtime evidence is reproduced. · MongoDB ownership and restore path are documented. · No valid LPS history is lost. · HOLD if multiple roadmaps claim current truth or the active environment is unclear.
02 · Family identity, roles, child privacy, and nine-pillar model	14%	65–110 active hours	Permission and privacy negative tests pass. · Child-safety review passes. · Schema/version tests pass. · HOLD on over-broad access or unresolved pillar boundaries.
03 · Daily planning core and first end-to-end workflow	18%	85–145 active hours	A family profile completes the full workflow. · State survives restart and restore. · No commitments are invented. · Return if daily use requires manual database repair or loses state.
04 · Routines, goals, rewards, progress, and analytics	13%	60–105 active hours	Date/timezone tests pass. · Parent override and child-safety tests pass. · Analytics remain truthful. · HOLD if gamification or metrics create unsafe or false conclusions.
05 · Family coordination, notifications, scheduling, and multi-device reliability	13%	65–115 active hours	Two-device tests pass. · No reminders are duplicated or lost. · Offline recovery is truthful. · Return if one user can silently overwrite another.
06 · Guides, templates, workflows, and evidence-based AI	12%	60–110 active hours	AI never invents family commitments. · AI output remains separate from deterministic records. · Privacy route is visible. · HOLD if AI silently changes commitments or exposes family data.
07 · Integrations, automation, cost, backup, export, and recovery	10%	55–95 active hours	Restore drill passes. · Provider outage test passes. · Cost limits and exit path are documented. · Return if cost, lock-in, or recovery is unbounded.
08 · Accessibility, polish, packaging, documentation, and release	10%	55–100 active hours	Tests/build/accessibility pass. · Family usability review passes. · Install and recovery evidence pass. · No release with privacy gaps, broken recovery, or unfinished critical screens. · Total phase weight: 100% · Total provisional ETUC: 480–845 active hours · DEPENDENCIES · Dedicated LPS project and roadmap. · MongoDB. · Forgey AIO. · Shared Schemas. · InstaDater and F.O.U.R. Desktop. · Test and Documentation systems. · PROTECTED BLOCKERS · Conflicting roadmaps. · Child privacy gaps. · Fragile MongoDB sync/backup. · AI-invented commitments. · Unbounded hosting cost. · DEFERRED · Public SaaS. · Broad public marketplace. · EXPLICITLY REJECTED · Advertising-driven family data use. · Hidden AI changes to deterministic records. · SPECIAL OWNER RULES · The dedicated LPS roadmap remains product-level authority after reconciliation. · MongoDB remains current unless a separately approved migration proves otherwise. · DADATRACKER RULES · Roadmap discovery, hash, version, source, and CONNECTED state are automatic. · Current Status and numerical Blue Current remain manually evidence-maintained. · A numerical tracker remains visible for this item. · Roadmap existence does not prove installed, running, runtime-connected, · controllable, released, or healthy state. · Family-facing UI shows `CONNECTED! · AUTOMATIC` and `CURRENT STATUS · MANUAL`. · Internal PASS WITH WARNINGS and implementation-authorization labels remain · technical artifacts, not family-facing badges. · ROADMAP APPROVAL GATE · Approved planning source. Implementation remains a separate explicit Owner · decision.

Bare Minimum

Profiles and role permissions.
Calendar, tasks, habits, goals, and pillars.
Notifications and backups.
Stable daily planning.
Comfortably Functional / Purple:
Polished coordination.
Guides/templates and evidence-based AI.
Analytics and multi-device reliability.
Accessible low-support family UX.
First Green work target / pause point:
Reconcile the dedicated LPS roadmap, lock the daily MVP, and prove one family daily workflow end to end.
Pause for Owner and portfolio review before continuing.

Comfortable target

Polished coordination.
Guides/templates and evidence-based AI.
Analytics and multi-device reliability.
Accessible low-support family UX.
First Green work target / pause point:
Reconcile the dedicated LPS roadmap, lock the daily MVP, and prove one family daily workflow end to end.
Pause for Owner and portfolio review before continuing.

Green pause point

- Reconcile the dedicated LPS roadmap, lock the daily MVP, and prove one family daily workflow end to end. - Pause for Owner and portfolio review before continuing.

Dependencies

Dedicated LPS project and roadmap.
MongoDB.
Forgey AIO.
Shared Schemas.
InstaDater and F.O.U.R. Desktop.
Test and Documentation systems.

Blockers

Conflicting roadmaps.
Child privacy gaps.
Fragile MongoDB sync/backup.
AI-invented commitments.
Unbounded hosting cost.
DEFERRED
Public SaaS.
Broad public marketplace.
EXPLICITLY REJECTED
Advertising-driven family data use.
Hidden AI changes to deterministic records.
SPECIAL OWNER RULES
The dedicated LPS roadmap remains product-level authority after reconciliation.
MongoDB remains current unless a separately approved migration proves otherwise.
DADATRACKER RULES
Roadmap discovery, hash, version, source, and CONNECTED state are automatic.
Current Status and numerical Blue Current remain manually evidence-maintained.
A numerical tracker remains visible for this item.
Roadmap existence does not prove installed, running, runtime-connected,
controllable, released, or healthy state.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/Batch_05/0017_FOUR_LPS_Portfolio_Reconciliation_Roadmap_v1.0.0.txt
SHA-256 792D9F95E0C9CEC53BD4590CF41BE5F259854F35B2239AC31415F52C723C1D83

100% completion definitionLPS is fully implemented, secured, tested, accessible, cost-controlled, documented, multi-device reliable, recoverable, installable, and Owner/family accepted while preserving its dedicated roadmap and MongoDB truth.

F.O.U.R. → Forgey Foundry · v0.1.0

FORGEY CONTROL Roadmap

Build the only Foundry-wide authorized controller: automatically discover valid installed components and profiles, present truthful state, obtain approvals, issue bounded commands locally/remotely, preserve an SQLite command ledger, and review evidence without executing target internals.

100%phase total

For the family

FORGEY CONTROL ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC435–780 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestoneAutomatic persistent fixture inventory with truthful Installed/Stopped/runtime state and SQLite command records, then pause.

Phase	Weight	ETUC	Evidence / stop gate
01 · Source reconciliation and baseline	10%	35–65 active hours	Hash/comparison report and Owner baseline approval. · HOLD if source selection could damage verified build.
02 · Authority, identity, and command contracts	12%	45–80 active hours	Contract and negative-authorization tests. · HOLD on duplicate controller or unrestricted shell behavior.
03 · Persistent inventory and automatic discovery	15%	55–95 active hours	Automatic fixture inventory and reconciliation tests. · HOLD on manual pairing or fake live state.
04 · SQLite command and audit ledger	12%	45–80 active hours	Migration, crash-consistency, query, backup/restore, and no-secret tests. · HOLD if SQLite becomes the sole runtime-truth source or stores secrets.
05 · Authorization and approval engine	15%	65–115 active hours	Security and replay/expiry/role tests. · HOLD on stale authorization or approval bypass.
06 · Local control and target validation	10%	45–80 active hours	Local fixture command end-to-end tests. · HOLD if Control executes target internals directly.
07 · Router-mediated control	10%	50–90 active hours	Two-device fixture tests and dangerous queue rejection. · HOLD if delivery is presented as execution completion.
08 · Evidence, recovery, and Desktop integration	8%	45–80 active hours	UI truth, recovery, accessibility, and evidence-link tests. · HOLD if Desktop duplicates authorization logic.
09 · Hardening and release	8%	50–95 active hours	Target-hardware and Owner release acceptance. · No release on stale/fabricated state or incomplete rollback. · CROSS-COMPONENT DEPENDENCIES · Shared Schemas · Forgey Foundry Platform · Master Engine · Cross-Device Router · Top-level InstaDater · Forgey Desktop · SQLite backup/recovery policy · BLOCKERS AND PROTECTED RISKS · Canonical source reconciliation remains incomplete. · The exact Control UI versus Forgey Desktop boundary needs API/UX lock. · SQLite command schema, retention, encryption, backup, and migration policy require design. · The verified v1.1.0 installed build must not be damaged or confused with canonical release completeness. · SPECIAL RULES · SQLite stores command/audit history but does not replace live process/heartbeat truth. · No secrets, credentials, or authenticator material in command records. · ROADMAP APPROVAL GATE · This roadmap is ready for Owner review but is not yet approved for · implementation. · Owner review must decide: · 1. Whether the north star and 100% definition are correct. · 2. Whether the phase weights and ETUC are accepted. · 3. Whether the dependencies and blockers are complete. · 4. Whether the Green pause point is correct. · 5. Whether the component weight/parent placement is accepted. · 6. Whether a later implementation-planning phase may begin. · Until explicit Owner approval, no implementation prompt or source change is · authorized.

Bare Minimum

Automatically discover fixture items, display truthful Installed/Stopped and runtime state, authorize safe commands, reject invalid/dangerous commands, and record complete SQLite-backed command evidence.
Comfortably Functional / Purple:
Reliable daily multi-device control with mature roles, diagnostics, approvals, recovery, Desktop integration, command history, and easy evidence review.
First Green work target / pause point:
Automatic persistent fixture inventory with truthful Installed/Stopped/runtime state and SQLite command records, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Source reconciliation and baseline 10% 35–65h
02. Authority, identity, and command contracts 12% 45–80h

Comfortable target

Reliable daily multi-device control with mature roles, diagnostics, approvals, recovery, Desktop integration, command history, and easy evidence review.
First Green work target / pause point:
Automatic persistent fixture inventory with truthful Installed/Stopped/runtime state and SQLite command records, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Source reconciliation and baseline 10% 35–65h
02. Authority, identity, and command contracts 12% 45–80h
03. Persistent inventory and automatic discovery 15% 55–95h
04. SQLite command and audit ledger 12% 45–80h

Green pause point

Automatic persistent fixture inventory with truthful Installed/Stopped/runtime state and SQLite command records, then pause.

Dependencies

: Migration evidence and v1.1.0 preservation.
Deliverables:
Compare installed, fixture, and canonical candidates.
Freeze authoritative baseline.
Preserve verified v1.1.0.
Evidence gate:
Hash/comparison report and Owner baseline approval.
Stop / return condition:
HOLD if source selection could damage verified build.
PHASE 02 — Authority, identity, and command contracts
Weight: 12%
ETUC: 45–80 active hours
Dependencies: Shared Schemas.
Deliverables:
Sole-controller authority model.
Identity/role/scope/approval contracts.
Command catalog and risk classification.
Evidence gate:
Contract and negative-authorization tests.
Stop / return condition:

Blockers

Canonical source reconciliation remains incomplete.
The exact Control UI versus Forgey Desktop boundary needs API/UX lock.
SQLite command schema, retention, encryption, backup, and migration policy require design.
The verified v1.1.0 installed build must not be damaged or confused with canonical release completeness.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0008_Forgey_Control_Roadmap_v0.1.0.txt
SHA-256 CD65400A84FA0531139B58B81924C2F325ADCFE01D088FD87E7E6E4B4326D6D5

100% completion definitionAll approved Foundry items are automatically inventoried, truthfully visible, securely and role-appropriately controllable, fully audited in a recoverable SQLite command/evidence ledger, integrated with Router/Desktop/InstaDater, and Owner-accepted across approved devices.

The Spark → F.O.U.R. → Forgey Foundry · v1.0.0

FORGEY DESKTOP Roadmap

Build Forgey Desktop as the polished, accessible, truthful visual command center where Doonchy and approved family users can understand Forgey Foundry, review portfolio progress, inspect devices/components/profiles, handle approvals, review evidence and diagnostics, and safely request bounded actions through Forgey Control without duplicating runtime, authorization, routing, updating, or component logic.

100%phase total

For the family

This is the plan for the Foundry desktop command center. The roadmap is connected automatically; only current implementation status is maintained manually from evidence.

Roadmap stateApproved and imported

Total ETUC347–635 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Complete a fixture-only portfolio dashboard using approved progress and explicit installed/running/connected/controllable/released/healthy labels. - Pause for full portfolio review before live Control integration.

Phase	Weight	ETUC	Evidence / stop gate
01 · Product, source, and authority boundary lock	10%	22–40 active hours	Owner-reviewed product/authority matrix. · Source candidates and version truth are documented. · HOLD on duplicate control authority or unresolved canonical source.
02 · Information architecture and family-friendly navigation	15%	45–80 active hours	Usability review with family members. · Keyboard, screen-reader, and mobile-layout evidence. · Return if important state cannot be found quickly or hierarchy is flattened.
03 · Truthful progress, state, freshness, and evidence model	16%	50–90 active hours	Fixture data and calculation tests. · No plans/folders/elapsed time raise Blue. · HOLD on fabricated or ambiguous state.
04 · Forgey Control request and approval integration	16%	60–105 active hours	Fixture-only Control integration tests. · Negative authorization and stale-approval tests. · HOLD if Desktop performs authorization or target actions itself.
05 · Evidence, diagnostics, notifications, and audit UX	12%	40–75 active hours	Representative failure and recovery traces. · No secret exposure in views or exports. · Return if failures are buried or evidence cannot be reconstructed.
06 · Multi-device, remote, offline, and stale behavior	11%	45–85 active hours	Two-device fixture tests. · No remote approval or success is invented. · HOLD if delivered, executed, and verified states are conflated.
07 · Customization, accessibility, performance, and recovery	10%	40–75 active hours	Accessibility baseline, target-PC performance, and settings restore tests. · Return if customization can hide authority/truth or degrade critical alerts.
08 · Packaging, installation, documentation, and release	10%	45–85 active hours	Typecheck, tests, lint, build, install/rollback, accessibility, security, and Owner acceptance PASS. · No production release without rollback, source truth, and integration evidence. · Total phase weight: 100% · Total provisional ETUC: 347–635 active hours · DEPENDENCIES · Forgey Foundry Platform · Shared Schemas · Progress and evidence governance · Forgey Control · Cross-Device Router · Master Engine and profile-state contracts · Top-level InstaDater · DadaTracker data and hierarchy conventions · Test and Fixture System · PROTECTED BLOCKERS · Unresolved canonical source · Duplicate Control authority · Fabricated/stale state · Unsupported component percentages · Hidden risk or buried failure · Exposed secrets or external telemetry by default · Missing rollback or recovery · Overwhelming information architecture · Incompatible schemas or APIs · TRACKER PRESENTATION · Family-facing DadaTracker should show: · `Forgey Desktop Roadmap — Approved Planning Source` · North star, phases, ETUC, dependencies, blockers, first Green target, current · evidence, and next action · No internal `PASS WITH WARNINGS`, `implementation not authorized`, or draft · badges in the family-facing view

Bare Minimum

Official components and profiles are visible.
Blue/Amber/Purple/Green values have source, freshness, confidence, and
evidence.
Fixture approvals and bounded Control requests work safely.
Important failures and holds are visible.
Evidence and rollback paths are reviewable.
Comfortably Functional / Purple:
Reliable daily multi-device command-center workflows.
Polished navigation, notifications, diagnostics, accessibility,
customization, offline behavior, recovery, and low-friction evidence review.
First Green target / pause point:
Complete a fixture-only portfolio dashboard using approved progress and

Comfortable target

Reliable daily multi-device command-center workflows.
Polished navigation, notifications, diagnostics, accessibility,
customization, offline behavior, recovery, and low-friction evidence review.
First Green target / pause point:
Complete a fixture-only portfolio dashboard using approved progress and
explicit installed/running/connected/controllable/released/healthy labels.
Pause for full portfolio review before live Control integration.
Component allocation:
Questionnaire proposal: 7% of Forgey Foundry.
Do not use this in the official parent calculation until the entire Foundry
child-weight table is rebalanced to 100%.
Blue Current:

Green pause point

- Complete a fixture-only portfolio dashboard using approved progress and explicit installed/running/connected/controllable/released/healthy labels. - Pause for full portfolio review before live Control integration.

Dependencies

: Owner planning baseline and current Foundry architecture.
Deliverables:
Confirm canonical source and installed-runtime locations.
Lock Forgey Desktop versus Forgey Control, Master Engine, Router, InstaDater, DadaTracker, and component boundaries.
Define users, roles, privacy, telemetry, and release terminology.
Evidence gate:
Owner-reviewed product/authority matrix.
Source candidates and version truth are documented.
Stop / return condition:
HOLD on duplicate control authority or unresolved canonical source.
PHASE 02 — Information architecture and family-friendly navigation
Weight: 15%
ETUC: 45–80 active hours
Dependencies: Phase 01.
Deliverables:
Home screen, portfolio, component, profile, device, approvals, evidence, diagnostics, settings, and help navigation.
Family-friendly summaries plus technical drill-down.
Responsive desktop and compact layouts.
Evidence gate:
Usability review with family members.

Blockers

Unresolved canonical source
Duplicate Control authority
Fabricated/stale state
Unsupported component percentages
Hidden risk or buried failure
Exposed secrets or external telemetry by default
Missing rollback or recovery
Overwhelming information architecture
Incompatible schemas or APIs

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0011_Forgey_Desktop_Roadmap_v1.0.0.txt
SHA-256 F190146ADA8F39D0DA0841A1AD6E0B39DB73524B5A9CA5BB9529539F6CE7CD7B

100% completion definition100% means the complete approved Forgey Desktop product is implemented, secured, tested, documented, installable, updateable, repairable, recoverable, accessible, performant on approved Windows hardware, integrated through versioned contracts, and Owner-accepted for daily use.

The Spark → F.O.U.R. → Device Installations → Roy Computer · v1.0.0

FORGEY FOUNDRY — ROY COMPUTER INSTALLATION Roadmap

Complete the safe Roy-specific Foundry installation supporting approved projects and AI work while preserving the working legacy setup until replacement proof and rollback are accepted.

100%phase total

For the family

FORGEY FOUNDRY — ROY COMPUTER INSTALLATION ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC535–930 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Approve Roy's target install matrix and produce a no-change preflight. - Pause for Owner and portfolio review before continuing.

Phase	Weight	ETUC	Evidence / stop gate
01 · Roy hardware, role, paths, legacy baseline, and backup	12%	55–95 active hours	Hardware and path report passes. · Legacy 85% operational baseline is documented separately. · Rollback backup is verified. · HOLD if hardware, paths, or working legacy behavior cannot be reconstructed.
02 · Roy target install matrix and no-change preflight	12%	45–80 active hours	Owner/Roy review passes. · Preflight makes no changes. · No unsupported component is included. · Return if install scope or role permissions remain unclear.
03 · Bootstrap, Resend verification, InstaDater, and F.O.U.R. Desktop	14%	65–110 active hours	Install/repair/rollback pass. · F.O.U.R. Desktop controls lifecycle requests; InstaDater executes them. · HOLD if legacy workflows are altered or lifecycle authority is ambiguous.
04 · Roy app catalog, Forgey Foundry selection, and Forgey Desktop first	14%	75–125 active hours	Manifest/dependency evidence passes. · No unreleased component is marked ready. · Return if install order can break legacy GCB/Forgey Local.
05 · Forgey:7b installation and approved local-AI workflows	10%	55–95 active hours	Model identity/hash and resource tests pass. · No hardware overload. · Offline behavior is truthful. · HOLD if Forgey:7b is unavailable, incompatible, or overloads Roy's computer.
06 · Router enrollment, Control visibility, project/profile fixtures	12%	70–120 active hours	No hidden generic shell. · Read/write scopes are distinct. · Evidence is reconstructable. · HOLD on broad filesystem access, remote-control exposure, or Drive mistakes.
07 · Master Engine/Forgey Global read-only shadow proof	10%	65–115 active hours	Behavior comparison passes. · No live writes. · Rollback remains available. · Return if required legacy behavior is lost or new state is fabricated.
08 · Integration, daily workflow, recovery, and support acceptance	8%	50–90 active hours	Daily workflow and recovery drill pass. · Roy/Doonchy acceptance recorded. · No cutover if support burden or recovery risk is excessive.
09 · Explicit cutover, observation, and legacy retirement	8%	55–100 active hours	Fresh Owner approval. · Observation passes. · No unresolved dependencies. · No legacy retirement or cleanup without separate approval. · Total phase weight: 100% · Total provisional ETUC: 535–930 active hours · DEPENDENCIES · Device Deployment roadmap. · InstaDater. · F.O.U.R. Desktop. · Forgey Desktop. · Forgey:7b package/evaluation. · Router. · Forgey Control. · Master Engine/Profile SDK. · Legacy Forgey Local/GCB evidence. · PROTECTED BLOCKERS · Breaking GCB/Forgey Local. · Excessive permissions. · Model overload. · Drive mistakes. · Remote-control exposure. · Early cutover. · Confusing 85%, 18%, and Roy-install progress. · DEFERRED · LPS and Forgey Utilities installation until packages are ready. · Legacy retirement until explicit cutover approval. · EXPLICITLY REJECTED · Generic all-components installation. · Hidden remote shell. · Fake installed/running state. · Destructive legacy replacement. · SPECIAL OWNER RULES · F.O.U.R. Desktop owns user-facing install/update authority. · InstaDater executes and verifies install/update/repair/rollback. · Forgey:7b is installed only through the Desktop/InstaDater lifecycle after package and hardware verification. · Legacy 85%, system-readiness 18%, and new-install progress must remain separate numerical trackers. · DADATRACKER RULES · Roadmap discovery, hash, version, source, and CONNECTED state are automatic. · Current Status and numerical Blue Current remain manually evidence-maintained. · A numerical tracker remains visible for this item. · Roadmap existence does not prove installed, running, runtime-connected, · controllable, released, or healthy state. · Family-facing UI shows `CONNECTED! · AUTOMATIC` and `CURRENT STATUS · MANUAL`. · Internal PASS WITH WARNINGS and implementation-authorization labels remain · technical artifacts, not family-facing badges. · ROADMAP APPROVAL GATE · Approved planning source. Implementation remains a separate explicit Owner · decision.

Bare Minimum

Infrastructure plus one safe project/profile workflow without replacing legacy.
Verified Desktop/InstaDater lifecycle.
Scoped local AI and recovery.
Comfortably Functional / Purple:
Reliable daily Roy workflows.
Approved new runtime/profile.
Remote visibility/control.
Local AI, updates, recovery, and minimal support.
First Green work target / pause point:
Approve Roy's target install matrix and produce a no-change preflight.
Pause for Owner and portfolio review before continuing.

Comfortable target

Reliable daily Roy workflows.
Approved new runtime/profile.
Remote visibility/control.
Local AI, updates, recovery, and minimal support.
First Green work target / pause point:
Approve Roy's target install matrix and produce a no-change preflight.
Pause for Owner and portfolio review before continuing.

Green pause point

- Approve Roy's target install matrix and produce a no-change preflight. - Pause for Owner and portfolio review before continuing.

Dependencies

Device Deployment roadmap.
InstaDater.
F.O.U.R. Desktop.
Forgey Desktop.
Forgey:7b package/evaluation.
Router.
Forgey Control.
Master Engine/Profile SDK.
Legacy Forgey Local/GCB evidence.

Blockers

Breaking GCB/Forgey Local.
Excessive permissions.
Model overload.
Drive mistakes.
Remote-control exposure.
Early cutover.
Confusing 85%, 18%, and Roy-install progress.
DEFERRED
LPS and Forgey Utilities installation until packages are ready.
Legacy retirement until explicit cutover approval.
EXPLICITLY REJECTED
Generic all-components installation.
Hidden remote shell.
Fake installed/running state.
Destructive legacy replacement.
SPECIAL OWNER RULES
F.O.U.R. Desktop owns user-facing install/update authority.
InstaDater executes and verifies install/update/repair/rollback.
Forgey:7b is installed only through the Desktop/InstaDater lifecycle after package and hardware verification.
Legacy 85%, system-readiness 18%, and new-install progress must remain separate numerical trackers.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/Batch_06/0023_Roy_Computer_Forgey_Foundry_Installation_Roadmap_v1.0.0.txt
SHA-256 7369001E0C096419D3E5F3159CB6E7BFEFDD1DE0EB03B1F289DB6971123043FF

100% completion definitionRoy's approved installation, F.O.U.R. Desktop lifecycle authority, InstaDater transactions, Forgey Desktop, Forgey:7b, Router/Control visibility, approved runtime/profile, project workflows, recovery, support, cutover, and observation are fully proven and Owner/Roy accepted.

F.O.U.R. → Forgey Foundry · v0.1.0

FORGEY FOUNDRY PLATFORM Roadmap

Define how Foundry engines, apps, profiles, tools, tests, docs, packages, releases, and devices form one coherent platform while preserving every component's separate authority and responsibility.

100%phase total

For the family

FORGEY FOUNDRY PLATFORM ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC288–522 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestoneApprove component manifest v1 and automatic fixture inventory, then pause for portfolio review.

Phase	Weight	ETUC	Evidence / stop gate
01 · Platform goal and boundary lock	10%	18–32 active hours	Owner-approved component map. · HOLD on monolith or duplicate authority.
02 · Component model and registry	15%	35–65 active hours	Schema-validated registry fixtures. · HOLD if folders alone create official components.
03 · Manifest and automatic discovery	20%	55–95 active hours	Multiple component fixture discovery tests. · HOLD on manual pairing or false discovery.
04 · Compatibility and release sets	15%	45–80 active hours	Compatible/incompatible fixture release-set tests. · HOLD on ambiguous compatibility.
05 · Lifecycle and InstaDater integration	15%	50–90 active hours	Fixture transaction and inventory consistency tests. · HOLD if Platform performs updater transactions itself.
06 · Portfolio and Desktop presentation	10%	35–65 active hours	UI truth and accessibility tests. · HOLD on fabricated status or duplicate progress calculations.
07 · Hardening, documentation, and platform release	15%	50–95 active hours	Cross-component fixture suite and Owner release gate. · No release without compatible component evidence and rollback. · CROSS-COMPONENT DEPENDENCIES · Shared Schemas · Top-level InstaDater · Forgey Control · Forgey Desktop · DadaTracker · All official Foundry components · BLOCKERS AND PROTECTED RISKS · The new InstaDater top-level decision changes Foundry's internal component-weight table and requires rebalancing. · The component manifest standard and release-set schema are not frozen. · Automatic inventory and complete compatibility evidence are not accepted. · SPECIAL RULES · InstaDater is now a top-level The Spark lifecycle service, not a Foundry-weighted child. · Foundry may depend on InstaDater without owning it. · ROADMAP APPROVAL GATE · This roadmap is ready for Owner review but is not yet approved for · implementation. · Owner review must decide: · 1. Whether the north star and 100% definition are correct. · 2. Whether the phase weights and ETUC are accepted. · 3. Whether the dependencies and blockers are complete. · 4. Whether the Green pause point is correct. · 5. Whether the component weight/parent placement is accepted. · 6. Whether a later implementation-planning phase may begin. · Until explicit Owner approval, no implementation prompt or source change is · authorized.

Bare Minimum

Every core component has a valid manifest, canonical location, owner, compatibility record, basic automatic fixture discovery, and truthful progress/status.
Comfortably Functional / Purple:
Reliable multi-device daily operation with automatic inventory, coordinated lifecycle requests, diagnostics, rollback, and polished visual status.
First Green work target / pause point:
Approve component manifest v1 and automatic fixture inventory, then pause for portfolio review.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Platform goal and boundary lock 10% 18–32h
02. Component model and registry 15% 35–65h

Comfortable target

Reliable multi-device daily operation with automatic inventory, coordinated lifecycle requests, diagnostics, rollback, and polished visual status.
First Green work target / pause point:
Approve component manifest v1 and automatic fixture inventory, then pause for portfolio review.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Platform goal and boundary lock 10% 18–32h
02. Component model and registry 15% 35–65h
03. Manifest and automatic discovery 20% 55–95h
04. Compatibility and release sets 15% 45–80h

Green pause point

Approve component manifest v1 and automatic fixture inventory, then pause for portfolio review.

Dependencies

: Owner approval.
Deliverables:
Platform taxonomy and official-component criteria.
Logical hierarchy and authority map.
First-party/extension policy.
Evidence gate:
Owner-approved component map.
Stop / return condition:
HOLD on monolith or duplicate authority.
PHASE 02 — Component model and registry
Weight: 15%
ETUC: 35–65 active hours
Dependencies: Phase 01.
Deliverables:
Component identity model.
Registry records and lifecycle states.
Chart-level classification.
Evidence gate:
Schema-validated registry fixtures.
Stop / return condition:

Blockers

The new InstaDater top-level decision changes Foundry's internal component-weight table and requires rebalancing.
The component manifest standard and release-set schema are not frozen.
Automatic inventory and complete compatibility evidence are not accepted.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0004_Forgey_Foundry_Platform_Roadmap_v0.1.0.txt
SHA-256 FA35B6B958E0C17BA228124E08B650491EBCFD1F6D946AEBA28A588A85228F5A

100% completion definitionEvery approved component follows stable identity, manifest, discovery, compatibility, lifecycle, evidence, packaging, progress, and release-set rules; the platform is secure, documented, recoverable, installed on approved devices, and Owner-accepted.

The Spark → F.O.U.R. → Forgey Foundry · v1.0.0

FORGEY GLOBAL Roadmap

Build Forgey Global as the protected general-purpose watcher profile that can understand broad explicitly approved areas of the computer, help organize and maintain work, use approved local AI and memory, and execute only within visible modes, least-privilege permissions, policy, and fresh authorization while producing reconstructable evidence and preserving Forgey Local until accepted cutover.

100%phase total

For the family

This is the plan for the protected general watcher profile. The roadmap is connected automatically, while installed/running/current progress remains a manual evidence decision.

Roadmap stateApproved and imported

Total ETUC465–835 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Complete the fixture profile and read-only shadow comparison against Forgey Local. - Pause for evidence review before any live cutover.

Phase	Weight	ETUC	Evidence / stop gate
01 · Goal, legacy behavior, source, and boundary inventory	10%	30–55 active hours	Behavior inventory and source report. · Owner-reviewed profile boundary. · HOLD on unresolved source or duplicate runtime/control responsibilities.
02 · Profile contract, identity, configuration, and manifests	12%	45–80 active hours	Positive and negative fixture validation. · No secret-bearing configuration. · Return if visibility and write authority are conflated.
03 · Generated fixture profile and isolated runtime proof	10%	45–80 active hours	Fixture/liveness/isolation tests. · No live profile identity or path contamination. · HOLD if fixture state can appear as live production state.
04 · Permissions, modes, approval, and safety model	18%	75–130 active hours	Permission, path, secret, mode-escalation, replay, expiry, and denial tests. · HOLD on broad silent authority, unrestricted autonomy, or mode escalation.
05 · Observation, project awareness, planning, and maintenance workflows	14%	60–105 active hours	Representative fixture workflows and recovery evidence. · Return if changes can occur without policy/approval or evidence.
06 · Local AI, memory, privacy, and provider integration	10%	45–85 active hours	Provider unavailable, privacy, memory, redaction, and prompt-injection tests. · HOLD if AI can bypass authorization or hide memory.
07 · Control, Router, Desktop, InstaDater, and evidence integration	10%	55–95 active hours	End-to-end fixture workflow across approved interfaces. · HOLD if delivery is mistaken for execution or status is fabricated.
08 · Read-only shadow comparison against Forgey Local	10%	55–100 active hours	Owner-reviewed comparison report and zero live write actions. · Return to earlier phases on behavioral loss, false positives, or unsafe scope.
09 · Staged installation, cutover, hardening, and release	6%	55–105 active hours	Explicit Owner cutover/release acceptance and rollback drill. · No live replacement or legacy cleanup without fresh explicit approval. · Total phase weight: 100% · Total provisional ETUC: 465–835 active hours · DEPENDENCIES · Master Engine · Watcher Profile SDK / Generator · Shared Schemas · Adapter SDK · Forgey Control · Cross-Device Router · Forgey Desktop · Top-level InstaDater · Approved local AI provider interfaces · Test and Fixture System · Legacy Forgey Local evidence and rollback · PROTECTED BLOCKERS · Unresolved canonical profile path · Unreleased Master Engine/Profile SDK · Broad silent authority · Visibility treated as write permission · Duplicate watcher execution · Unsafe or hidden memory · Secret/system root exposure · Premature Forgey Local replacement · Missing rollback or behavior comparison · Fabricated running/connected/healthy state · TRACKER PRESENTATION · Family-facing DadaTracker should show: · `Forgey Global Roadmap — Approved Planning Source` · `Current state: Target profile; not verified installed or running` · The fixture/shadow Green target, dependencies, blockers, ETUC, and evidence · No internal checkpoint or implementation-authorization badges

Bare Minimum

A generated fixture profile can observe approved roots.
It can plan, request approval, make bounded fixture changes, produce evidence,
stop, recover, and remain isolated.
Visibility and write authority are distinct.
No silent escalation occurs.
Comfortably Functional / Purple:
Reliable daily assistance across approved projects/devices with mature
context, diagnostics, bounded automation, local AI, memory, recovery,
handoffs, and low-friction Control/Desktop workflows.
First Green target / pause point:
Complete the fixture profile and read-only shadow comparison against Forgey
Local.

Comfortable target

Reliable daily assistance across approved projects/devices with mature
context, diagnostics, bounded automation, local AI, memory, recovery,
handoffs, and low-friction Control/Desktop workflows.
First Green target / pause point:
Complete the fixture profile and read-only shadow comparison against Forgey
Local.
Pause for evidence review before any live cutover.
Component allocation:
Questionnaire proposal: 5% of Forgey Foundry.
Do not use this in the official parent calculation until the entire Foundry
child-weight table is rebalanced to 100%.
Blue Current:

Green pause point

- Complete the fixture profile and read-only shadow comparison against Forgey Local. - Pause for evidence review before any live cutover.

Dependencies

: Owner planning baseline and legacy Forgey Local evidence.
Deliverables:
Inventory Forgey Local behavior and current evidence.
Confirm canonical profile source/runtime/data candidates.
Lock Forgey Global versus Master Engine, Control, Router, InstaDater, Desktop, and component ownership.
Evidence gate:
Behavior inventory and source report.
Owner-reviewed profile boundary.
Stop / return condition:
HOLD on unresolved source or duplicate runtime/control responsibilities.
PHASE 02 — Profile contract, identity, configuration, and manifests
Weight: 12%
ETUC: 45–80 active hours
Dependencies: Shared Schemas and Watcher Profile SDK direction.
Deliverables:
Profile identity, owner, roots, exclusions, actions, modes, providers, memory, evidence, compatibility, and lifecycle contracts.
Deterministic configuration and manifest validation.
Evidence gate:
Positive and negative fixture validation.
No secret-bearing configuration.

Blockers

Unresolved canonical profile path
Unreleased Master Engine/Profile SDK
Broad silent authority
Visibility treated as write permission
Duplicate watcher execution
Unsafe or hidden memory
Secret/system root exposure
Premature Forgey Local replacement
Missing rollback or behavior comparison
Fabricated running/connected/healthy state

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0012_Forgey_Global_Roadmap_v1.0.0.txt
SHA-256 38A5A59F9E3759CF05B5FA35E83E7CDB0854AC4FA91A65CC2CCDA8C4951E9D55

100% completion definition100% means Forgey Global is fully defined, generated, validated, isolated, secured, tested, documented, installable, updateable, repairable, recoverable, integrated through approved contracts, proven by fixture and read-only shadow comparison, staged safely onto approved devices, and Owner-accepted after rollback evidence.

The Spark → F.O.U.R. → Forgey Foundry · v1.0.0

FOUNDRY DEVELOPER TOOLS Roadmap

Build the complete approved Foundry Developer Tools capability supporting reliable inspection, validation, diagnostics, reproducible build and packaging, migration, evidence, maintenance, recovery, and release without becoming a production runtime or hidden authority layer.

100%phase total

For the family

FOUNDRY DEVELOPER TOOLS ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC370–650 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Approve the tool safety standard and validate the core read-only toolkit. - Pause at this checkpoint for portfolio and evidence review before continuing.

Phase	Weight	ETUC	Evidence / stop gate
01 · Catalog, source reconciliation, and authority boundaries	12%	35–60 active hours	Complete tool inventory with hashes · No duplicate runtime, updater, fixture, or controller responsibility · Owner-reviewed source/boundary report · HOLD if canonical source or tool ownership remains ambiguous · Return if active workflows silently depend on unclassified one-off scripts
02 · Tool safety standard, dry-run, authorization, and rollback	16%	45–80 active hours	Negative tests prove dry-run performs no target writes · Path traversal, secret, stale-approval, replay, and denial tests · Rollback restores representative fixtures · HOLD on destructive defaults, hidden writes, unrestricted scope, or missing rollback
03 · Core read-only inspection and validation toolkit	18%	70–120 active hours	Deterministic outputs on fixtures · Cross-run hash stability · Malformed, missing, stale, and inaccessible-path tests · No source mutation · Return if tools disagree on source truth or produce non-reconstructable evidence
04 · Reproducible build, package, and compatibility tooling	14%	55–95 active hours	Two clean builds produce equivalent declared outputs · Tampered package rejection · Compatibility and deprecation fixture tests · HOLD if package identity, provenance, or compatibility cannot be verified
05 · Migration, repair, cleanup, and bounded write tools	16%	70–120 active hours	Dry-run versus execution diff · Forced-failure rollback · Partial-copy, lock, permission, and stale-source tests · No deletion without explicit authorization · HOLD if rollback is unproven or write scope can exceed the approved target
06 · Diagnostics, evidence, maintainer workflow, and workbench UX	12%	45–85 active hours	Representative incident reconstruction · Secret redaction · Operator usability review · Offline and degraded behavior tests · Return if evidence cannot explain what changed, why, and how to recover
07 · Installation, documentation, acceptance, and release	12%	50–90 active hours	Typecheck/tests/lint/build as applicable · Install and rollback drill · Security review · Owner acceptance package · No release without complete catalog, tested examples, rollback evidence, and truthful version labels · Total phase weight: 100% · Total provisional ETUC: 370–650 active hours · DEPENDENCIES · Forgey Foundry Platform and authoritative hierarchy · Shared Schemas · Forgey Control authorization/evidence contracts · Top-level InstaDater · Foundry Test and Fixture System · Foundry Documentation System · Component-owned build/package interfaces · PROTECTED BLOCKERS · Unresolved canonical source or tool ownership · One-off drift or hidden active dependencies · Destructive defaults or dry-run that writes · Stale paths, missing checkpoints, or unlogged actions · Tools becoming hidden production runtime dependencies · Missing rollback, secret protection, compatibility, or evidence · DEFERRED · Public IDE extension · Large hosted tool marketplace · Cloud-only maintainer services · EXPLICITLY REJECTED · Unlogged destructive scripts · Hidden authority · Silent deletion or cleanup · Untested write tools · PROGRESS AND TRACKER RULES · Preserve the current 55% Blue Current as provisional until an · evidence audit reconciles it against this roadmap. · This roadmap does not raise Blue Current. · Proposed 4% parent allocation remains excluded from official parent · calculations until the full Foundry child table is rebalanced to exactly · 100%. · The roadmap file and component connection are automatic in DadaTracker. · Current Status, Blue Current, installed/running/connected/controllable/ · released/healthy truth, freshness, blockers, and exact next action remain · manually evidence-maintained. · Family-facing DadaTracker should show `CONNECTED! · AUTOMATIC` without · internal checkpoint or authorization badges. · ROADMAP APPROVAL GATE · Approved planning source. Implementation remains a separate explicit Owner · decision.

Bare Minimum

Canonical catalog of active and archived tools.
Validated read-only inventory, hashing, manifest, hierarchy, package, evidence, and diagnostic tools.
Approved safety standard and mandatory dry-run behavior for writes.
Truthful evidence and deterministic failure reporting.
Comfortably Functional / Purple:
Reliable maintainer workbench and command catalog.
Safe write, repair, migration, and cleanup tools with previews and rollback.
Reproducible builds, validated packages, compatibility checks, and easy evidence.
Clear diagnostics, documentation, and support workflows.
First Green work target / pause point:
Approve the tool safety standard and validate the core read-only toolkit.
Pause at this checkpoint for portfolio and evidence review before continuing.

Comfortable target

Reliable maintainer workbench and command catalog.
Safe write, repair, migration, and cleanup tools with previews and rollback.
Reproducible builds, validated packages, compatibility checks, and easy evidence.
Clear diagnostics, documentation, and support workflows.
First Green work target / pause point:
Approve the tool safety standard and validate the core read-only toolkit.
Pause at this checkpoint for portfolio and evidence review before continuing.

Green pause point

- Approve the tool safety standard and validate the core read-only toolkit. - Pause at this checkpoint for portfolio and evidence review before continuing.

Dependencies

:
Authoritative Foundry hierarchy
Existing script/tool inventories
Owner-approved component boundaries
Deliverables:
Canonical tool catalog
Source/runtime/package/archive separation map
Ownership and dependency matrix
One-off classification and archive policy
Evidence gate:
Complete tool inventory with hashes
No duplicate runtime, updater, fixture, or controller responsibility
Owner-reviewed source/boundary report
Stop / return condition:
HOLD if canonical source or tool ownership remains ambiguous
Return if active workflows silently depend on unclassified one-off scripts
PHASE 02 — Tool safety standard, dry-run, authorization, and rollback
Weight: 16%
ETUC: 45–80 active hours
Dependencies:

Blockers

Unresolved canonical source or tool ownership
One-off drift or hidden active dependencies
Destructive defaults or dry-run that writes
Stale paths, missing checkpoints, or unlogged actions
Tools becoming hidden production runtime dependencies
Missing rollback, secret protection, compatibility, or evidence
DEFERRED
Public IDE extension
Large hosted tool marketplace
Cloud-only maintainer services
EXPLICITLY REJECTED
Unlogged destructive scripts
Hidden authority
Silent deletion or cleanup
Untested write tools
PROGRESS AND TRACKER RULES
Preserve the current 55% Blue Current as provisional until an
evidence audit reconciles it against this roadmap.
This roadmap does not raise Blue Current.
Proposed 4% parent allocation remains excluded from official parent

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/Batch_04/0014_Foundry_Developer_Tools_Roadmap_v1.0.0.txt
SHA-256 7E316832C64741E2F035166E94F7BDF65339DDF8896264A6CE384E2835862F41

100% completion definitionThe complete long-term tool catalog is reconciled, secured, tested, documented, installable, recoverable, versioned, packaged, evidence-producing, and Owner-accepted on approved Windows hardware.

The Spark → F.O.U.R. → Forgey Foundry · v1.0.0

FOUNDRY DOCUMENTATION SYSTEM Roadmap

Build the complete approved Foundry Documentation System capability that keeps architecture, product, developer, operator, security, installation, recovery, release, evidence, and handoff knowledge accurate, audience-specific, searchable, tested, versioned, and coupled to real source and release truth.

100%phase total

For the family

FOUNDRY DOCUMENTATION SYSTEM ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC325–590 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Create the canonical documentation index and validate current architecture and path references. - Pause at this checkpoint for portfolio and evidence review before continuing.

Phase	Weight	ETUC	Evidence / stop gate
01 · Documentation standard, canonical index, and source reconciliation	16%	40–70 active hours	Broken links and stale path scan · Owner-reviewed index · Every current document has owner, audience, status, source, and replacement rules · HOLD on multiple current truths, missing ownership, or unresolved canonical locations
02 · Architecture, hierarchy, authority, and integration documentation	16%	45–80 active hours	Diagrams match authoritative paths and contracts · Boundary review by component owners · No documentation grants duplicate authority · Return if diagrams, paths, or ownership conflict with source truth
03 · Developer, operator, family-user, and support documentation	18%	60–110 active hours	Audience usability review · All executable examples labeled and tested · No secret-bearing examples · HOLD if one giant document obscures role-specific responsibilities or risks
04 · Installation, update, repair, rollback, security, and recovery documentation	16%	55–95 active hours	Runbooks tested in fixtures · Restore and rollback steps reproduced · Dangerous commands require warnings and approvals · No release if required recovery or security instructions are stale or untested
05 · Release coupling, changelogs, evidence, and handoff records	12%	40–75 active hours	Release artifacts link to exact tested docs and evidence · Version labels are truthful · Superseded documents link to replacements · HOLD if release documentation cannot reconstruct tested scope, warnings, and rollback
06 · Automation, freshness, tested examples, diagrams, and search	12%	50–95 active hours	Automated checks pass on current docs · Intentional exceptions are labeled · No auto-published AI text without review and evidence · Return if automation can silently rewrite truth or mark unreviewed content current
07 · Acceptance, installation, support handoff, and release	10%	35–65 active hours	Owner and representative audience acceptance · Search/render/link/example checks · Recovery-document drill · Artifact index complete · No release with stale required instructions, broken diagrams, untested commands, or exposed secrets · Total phase weight: 100% · Total provisional ETUC: 325–590 active hours · DEPENDENCIES · F.O.U.R. HQ governance truth · Component-owned technical facts and evidence · Shared Schemas · Developer Tools · Test and Fixture System · Top-level InstaDater · Release and evidence artifacts · PROTECTED BLOCKERS · Stale required instructions · Multiple documents claiming current truth · Untested commands · Broken diagrams, links, paths, or version references · Secrets in examples or evidence · Auto-published AI content without review/evidence · Missing release, rollback, or recovery coupling · DEFERRED · Public documentation portal · External community documentation platform · Multilingual public publishing · EXPLICITLY REJECTED · Auto-published AI text without review and evidence · Deleting stale context without replacement/history · Marketing claims presented as runtime truth · PROGRESS AND TRACKER RULES · Preserve the current 80% Blue Current as provisional until an · evidence audit reconciles it against this roadmap. · This roadmap does not raise Blue Current. · Proposed 2% parent allocation remains excluded from official parent · calculations until the full Foundry child table is rebalanced to exactly · 100%. · The roadmap file and component connection are automatic in DadaTracker. · Current Status, Blue Current, installed/running/connected/controllable/ · released/healthy truth, freshness, blockers, and exact next action remain · manually evidence-maintained. · Family-facing DadaTracker should show `CONNECTED! · AUTOMATIC` without · internal checkpoint or authorization badges. · ROADMAP APPROVAL GATE · Approved planning source. Implementation remains a separate explicit Owner · decision.

Bare Minimum

Canonical documentation index and current architecture map.
Trustworthy install, run, recovery, boundary, progress-method, and release documentation.
Tested or visibly labeled executable examples.
Stale and superseded documents linked to replacements.
Comfortably Functional / Purple:
Polished audience-specific guides.
Automated freshness, path, link, diagram, and example validation.
Search, diagrams, handoffs, changelogs, support playbooks, and release coupling.
Reliable documentation maintenance and recovery workflow.
First Green work target / pause point:
Create the canonical documentation index and validate current architecture and path references.
Pause at this checkpoint for portfolio and evidence review before continuing.

Comfortable target

Polished audience-specific guides.
Automated freshness, path, link, diagram, and example validation.
Search, diagrams, handoffs, changelogs, support playbooks, and release coupling.
Reliable documentation maintenance and recovery workflow.
First Green work target / pause point:
Create the canonical documentation index and validate current architecture and path references.
Pause at this checkpoint for portfolio and evidence review before continuing.

Green pause point

- Create the canonical documentation index and validate current architecture and path references. - Pause at this checkpoint for portfolio and evidence review before continuing.

Dependencies

:
Authoritative Foundry hierarchy
Existing docs/handoffs
HQ governance truth
Deliverables:
Canonical documentation index
Audience taxonomy
Document status/version/freshness standard
Source and ownership map
Stale/superseded/history policy
Evidence gate:
Broken links and stale path scan
Owner-reviewed index
Every current document has owner, audience, status, source, and replacement rules
Stop / return condition:
HOLD on multiple current truths, missing ownership, or unresolved canonical locations
PHASE 02 — Architecture, hierarchy, authority, and integration documentation
Weight: 16%
ETUC: 45–80 active hours
Dependencies:

Blockers

Stale required instructions
Multiple documents claiming current truth
Untested commands
Broken diagrams, links, paths, or version references
Secrets in examples or evidence
Auto-published AI content without review/evidence
Missing release, rollback, or recovery coupling
DEFERRED
Public documentation portal
External community documentation platform
Multilingual public publishing
EXPLICITLY REJECTED
Auto-published AI text without review and evidence
Deleting stale context without replacement/history
Marketing claims presented as runtime truth
PROGRESS AND TRACKER RULES
Preserve the current 80% Blue Current as provisional until an
evidence audit reconciles it against this roadmap.
This roadmap does not raise Blue Current.
Proposed 2% parent allocation remains excluded from official parent

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/Batch_04/0016_Foundry_Documentation_System_Roadmap_v1.0.0.txt
SHA-256 2BB5A62227AD041848B21CDD70C451DADA6CF924CBB4E510F05AB0F358F9E41F

100% completion definitionThe complete long-term documentation system is implemented, secured, tested, indexed, searchable, rendered, audience-specific, installable, recoverable, release-coupled, freshness-checked, and Owner-accepted.

The Spark → F.O.U.R. → Forgey Foundry · v1.0.0

FOUNDRY TEST AND FIXTURE SYSTEM Roadmap

Build the complete approved Foundry Test and Fixture System capability that proves Foundry behavior safely through strict fixture/live separation, unit and contract harnesses, component fixtures, integration labs, negative tests, recovery, security, performance, and truthful release gates.

100%phase total

For the family

FOUNDRY TEST AND FIXTURE SYSTEM ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC425–745 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestone- Prove fixture/live separation and run the first cross-component fixture scenario. - Pause at this checkpoint for portfolio and evidence review before continuing.

Phase	Weight	ETUC	Evidence / stop gate
01 · Fixture/live standard, identities, and fail-closed separation	14%	45–80 active hours	Attempts to use live paths or credentials fail closed · Fixture UI is visibly labeled · No production data appears in fixtures · HOLD on ambiguous environment identity or any path from fixture to live targets
02 · Unit, contract, and common result harnesses	14%	55–95 active hours	Schema conformance tests · Flaky tests never count as PASS · Retries remain visible · Negative and malformed-input coverage · Return if results cannot distinguish PASS, FAIL, HOLD, SKIP, FLAKY, and ERROR
03 · Component fixtures, golden data, and recovery primitives	16%	65–110 active hours	Repeatable isolated execution · Restore returns to known baseline · No cross-test contamination · Fixture version/provenance recorded · HOLD if fixtures depend on family live data or cannot be deterministically reset
04 · Cross-component integration lab	18%	80–140 active hours	Control authorizes; Router transports; Master Engine fixture executes; evidence returns; Desktop shows truthful fixture state · No live watcher used · HOLD if delivery is mistaken for execution or fixture state appears live
05 · Security, negative, failure, and recovery testing	16%	75–130 active hours	Required negative suite passes · No secret leakage · Recovery preserves evidence and prior working state · Return on unsafe fallback, false PASS, hidden skipped tests, or unverified recovery
06 · Performance, capacity, concurrency, and degraded-resource testing	10%	50–90 active hours	Baseline and regression evidence on approved Windows hardware · Resource limits produce truthful degraded/HOLD states · HOLD if benchmarks are synthetic-only or target hardware evidence is absent
07 · Release-gate aggregation, reporting, installation, and acceptance	12%	55–100 active hours	No flaky or skipped critical test counted as PASS · Release candidate reproducible · Disaster/restore drill · Owner acceptance · No release when relevant tests are flaky, stale, hidden, fixture-contaminated, or incomplete · Total phase weight: 100% · Total provisional ETUC: 425–745 active hours · DEPENDENCIES · Shared Schemas · Forgey Control fixture authorization · Cross-Device Router fixture transport · Master Engine fixture runtime · Watcher Profile SDK / generated fixture profile · Forgey Desktop fixture presentation · Developer Tools · Documentation System · Top-level InstaDater · PROTECTED BLOCKERS · Fixture data displayed as live · Live paths, credentials, ports, or family data reachable from fixtures · Flaky tests counted as PASS · Retries hiding instability · Hidden skipped tests or environment drift · False aggregate success, missing recovery, or stale evidence · DEFERRED · Large cloud test farm · High-scale distributed load laboratory · Public fixture marketplace · EXPLICITLY REJECTED · Tests using live family data by default · Fake live state · Silent flaky retries · Release gates that ignore critical skips/failures · PROGRESS AND TRACKER RULES · Preserve the current 45% Blue Current as provisional until an · evidence audit reconciles it against this roadmap. · This roadmap does not raise Blue Current. · Proposed 4% parent allocation remains excluded from official parent · calculations until the full Foundry child table is rebalanced to exactly · 100%. · The roadmap file and component connection are automatic in DadaTracker. · Current Status, Blue Current, installed/running/connected/controllable/ · released/healthy truth, freshness, blockers, and exact next action remain · manually evidence-maintained. · Family-facing DadaTracker should show `CONNECTED! · AUTOMATIC` without · internal checkpoint or authorization badges. · ROADMAP APPROVAL GATE · Approved planning source. Implementation remains a separate explicit Owner · decision.

Bare Minimum

Hard fixture/live separation.
Common unit, contract, fixture, and result harnesses.
Core component fixtures with deterministic reset and recovery.
First cross-component scenario with truthful aggregate verdict.
Comfortably Functional / Purple:
Routine reliable release gates across components.
Security, negative, recovery, multi-device, performance, and disaster testing.
Flaky-test quarantine with visible ownership and deadlines.
Reproducible fixture environments and evidence bundles.
First Green work target / pause point:
Prove fixture/live separation and run the first cross-component fixture scenario.
Pause at this checkpoint for portfolio and evidence review before continuing.

Comfortable target

Routine reliable release gates across components.
Security, negative, recovery, multi-device, performance, and disaster testing.
Flaky-test quarantine with visible ownership and deadlines.
Reproducible fixture environments and evidence bundles.
First Green work target / pause point:
Prove fixture/live separation and run the first cross-component fixture scenario.
Pause at this checkpoint for portfolio and evidence review before continuing.

Green pause point

- Prove fixture/live separation and run the first cross-component fixture scenario. - Pause at this checkpoint for portfolio and evidence review before continuing.

Dependencies

:
Authoritative Foundry hierarchy
Component boundary matrix
Security and identity standards
Deliverables:
Distinct fixture/live roots, identities, ports, storage, credentials, banners, and guards
Common fixture manifest
Fixture/live detection library
No-live-path policy
Evidence gate:
Attempts to use live paths or credentials fail closed
Fixture UI is visibly labeled
No production data appears in fixtures
Stop / return condition:
HOLD on ambiguous environment identity or any path from fixture to live targets
PHASE 02 — Unit, contract, and common result harnesses
Weight: 14%
ETUC: 55–95 active hours
Dependencies:
Shared Schemas

Blockers

Fixture data displayed as live
Live paths, credentials, ports, or family data reachable from fixtures
Flaky tests counted as PASS
Retries hiding instability
Hidden skipped tests or environment drift
False aggregate success, missing recovery, or stale evidence
DEFERRED
Large cloud test farm
High-scale distributed load laboratory
Public fixture marketplace
EXPLICITLY REJECTED
Tests using live family data by default
Fake live state
Silent flaky retries
Release gates that ignore critical skips/failures
PROGRESS AND TRACKER RULES
Preserve the current 45% Blue Current as provisional until an
evidence audit reconciles it against this roadmap.
This roadmap does not raise Blue Current.
Proposed 4% parent allocation remains excluded from official parent

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/Batch_04/0015_Foundry_Test_and_Fixture_System_Roadmap_v1.0.0.txt
SHA-256 58C52D0A2F8245F7782C16D89976FA1995563B138D7812CFD7861975C32B76CE

100% completion definitionThe complete long-term test and fixture system is implemented, isolated, secured, documented, installable, recoverable, evidence-producing, integrated across approved components, and Owner-accepted with representative security, recovery, performance, multi-device, and release-gate proof.

The Spark · v0.1.0

INSTADATER Roadmap

Build the one and only transaction-safe lifecycle engine for all of The Spark—including F.O.U.R., LPS, Forgey AIO, Forgey Foundry, Utilities, applications, components, profiles, clients, and itself—controlled through the future F.O.U.R. Desktop rather than Forgey Desktop.

100%phase total

For the family

INSTADATER ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC445–800 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestoneComplete a fixture update and forced-failure rollback with exact evidence and 30-day retention simulation, then pause.

Phase	Weight	ETUC	Evidence / stop gate
01 · Top-level product, source, and authority reconciliation	10%	35–65 active hours	Owner-approved architecture/supersession record. · HOLD on duplicate updater or unclear control authority.
02 · Package and release contracts	15%	55–95 active hours	Valid/invalid/tampered package tests. · HOLD on untrusted or ambiguous package provenance.
03 · Transaction engine	20%	80–140 active hours	Interruption, disk-full, permission, locked-file, and partial-state tests. · HOLD if partial work can be presented as success.
04 · Backup, 30-day retention, rollback, and recovery	15%	60–110 active hours	Forced-failure rollback and restore tests. · Retention tests preserving only known-good/protected backups. · Never delete the only known-good rollback point or backup tied to an unresolved incident.
05 · Fixture install/update/repair proof	10%	45–80 active hours	Successful and forced-failure fixture PASS with no live damage. · HOLD on source/runtime contamination.
06 · F.O.U.R. Desktop, authorization, and Router integration	10%	50–90 active hours	Fixture local/remote lifecycle request tests. · HOLD if Forgey Desktop directly controls InstaDater or Router authorizes updates.
07 · Channels, staged rollout, and self-update	10%	55–100 active hours	Channel, downgrade, staged rollout, self-update failure/rollback tests. · HOLD if self-update can strand the updater.
08 · Hardening, The Spark deployment, and release	10%	65–120 active hours	Multi-device lifecycle proof and explicit Owner release approval. · No production control/deployment before F.O.U.R. Desktop and package security gates pass. · CROSS-COMPONENT DEPENDENCIES · The Spark/F.O.U.R. hierarchy decision · F.O.U.R. Desktop roadmap · Shared Schemas · Component manifests · Forgey Control authorization policy · Cross-Device Router transport · Device deployment · BLOCKERS AND PROTECTED RISKS · This supersedes the earlier provisional rule that F.O.U.R. was 100% of The Spark. · The logical parent changed, but the current source candidate remains physically under Forgey Foundry until separately authorized relocation. · Foundry component weights must be rebalanced because InstaDater is no longer a Foundry-weighted child. · Thirty-day deletion must not remove the only known-good rollback point, an open-incident backup, or a legally/Owner-protected backup. · The future F.O.U.R. Desktop control contract does not yet have its own approved roadmap. · Package signing, channels, canonical baseline, and remote update policy remain unresolved. · SPECIAL RULES · This is the newest parent-weight decision and supersedes F.O.U.R.=100%. · No source move is authorized by this roadmap. · Backups older than 30 days are eligible for deletion only after protected-exception checks. · ROADMAP APPROVAL GATE · This roadmap is ready for Owner review but is not yet approved for · implementation. · Owner review must decide: · 1. Whether the north star and 100% definition are correct. · 2. Whether the phase weights and ETUC are accepted. · 3. Whether the dependencies and blockers are complete. · 4. Whether the Green pause point is correct. · 5. Whether the component weight/parent placement is accepted. · 6. Whether a later implementation-planning phase may begin. · Until explicit Owner approval, no implementation prompt or source change is · authorized.

Bare Minimum

Install, update, repair, and roll back fixture versions of at least two components with complete evidence and no live damage.
Comfortably Functional / Purple:
Reliable multi-device lifecycle management with staged rollout, health gates, self-repair, diagnostics, protected cleanup, fast rollback, and F.O.U.R. Desktop control.
First Green work target / pause point:
Complete a fixture update and forced-failure rollback with exact evidence and 30-day retention simulation, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Top-level product, source, and authority reconciliation 10% 35–65h
02. Package and release contracts 15% 55–95h

Comfortable target

Reliable multi-device lifecycle management with staged rollout, health gates, self-repair, diagnostics, protected cleanup, fast rollback, and F.O.U.R. Desktop control.
First Green work target / pause point:
Complete a fixture update and forced-failure rollback with exact evidence and 30-day retention simulation, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Top-level product, source, and authority reconciliation 10% 35–65h
02. Package and release contracts 15% 55–95h
03. Transaction engine 20% 80–140h
04. Backup, 30-day retention, rollback, and recovery 15% 60–110h

Green pause point

Complete a fixture update and forced-failure rollback with exact evidence and 30-day retention simulation, then pause.

Dependencies

: Owner accepts The Spark 90/10 hierarchy.
Deliverables:
Top-level InstaDater logical identity.
Current-source versus future-source decision.
F.O.U.R. Desktop control and component-authorization matrix.
Evidence gate:
Owner-approved architecture/supersession record.
Stop / return condition:
HOLD on duplicate updater or unclear control authority.
PHASE 02 — Package and release contracts
Weight: 15%
ETUC: 55–95 active hours
Dependencies: Shared Schemas and product manifests.
Deliverables:
Package manifest, hashes/signatures, signer/source/build/compatibility, prerequisites, install plan, rollback metadata.
Evidence gate:
Valid/invalid/tampered package tests.
Stop / return condition:
HOLD on untrusted or ambiguous package provenance.
PHASE 03 — Transaction engine

Blockers

This supersedes the earlier provisional rule that F.O.U.R. was 100% of The Spark.
The logical parent changed, but the current source candidate remains physically under Forgey Foundry until separately authorized relocation.
Foundry component weights must be rebalanced because InstaDater is no longer a Foundry-weighted child.
Thirty-day deletion must not remove the only known-good rollback point, an open-incident backup, or a legally/Owner-protected backup.
The future F.O.U.R. Desktop control contract does not yet have its own approved roadmap.
Package signing, channels, canonical baseline, and remote update policy remain unresolved.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0010_InstaDater_Roadmap_v0.1.0.txt
SHA-256 4CD3632AA10FF4C31A0D7F33B18FB84006B477324BA83DC32C88DE29B6AB74EA

100% completion definitionAll approved The Spark software can be installed, updated, repaired, migrated, rolled back, verified, staged, and recovered through one secure manifest-driven engine with manual-by-default updates, protected 30-day backup retention, self-update recovery, multi-device evidence, and Owner acceptance.

F.O.U.R. → Forgey Foundry · v0.1.0

MASTER ENGINE Roadmap

Build one production-grade shared watcher runtime that safely runs isolated profiles, enforces authorization and permissions, maintains truthful lifecycle state, produces reconstructable evidence, recovers safely, and integrates with Control, Router, InstaDater, and Desktop without duplicating them.

100%phase total

For the family

MASTER ENGINE ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC623–1127 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestoneApprove goal, boundaries, source inputs, source-reconciliation plan, profile-contract direction, and acceptance evidence before runtime source modification.

Phase	Weight	ETUC	Evidence / stop gate
01 · Goal and contract lock	7%	18–32 active hours	Owner-approved architecture record. · Zero unresolved product-identity conflicts. · HOLD if Master Engine duplicates Control, Router, InstaDater, Desktop, or profile responsibilities.
02 · Authoritative source reconciliation	10%	40–80 active hours	Hash manifest and comparison report. · Owner baseline approval. · HOLD on conflicting source candidates or missing behavior evidence.
03 · Canonical foundation	9%	45–80 active hours	Clean build and foundational unit tests. · No invented folder system. · Return to Phase 02 if implementation cannot be traced to approved source.
04 · Runtime truth and lifecycle	10%	60–105 active hours	Lifecycle, stale-state, crash, and idempotency tests. · Fixture/live separation proof. · HOLD on false running state or uncertain duplicate execution.
05 · Authorization and isolation	12%	75–130 active hours	Negative authorization, replay, path, isolation, and network tests. · HOLD on cross-profile leakage or bypassable authorization.
06 · Watcher Profile SDK integration	8%	45–85 active hours	Two generated profiles validate and remain isolated. · Return to profile contract if generator and runtime semantics diverge.
07 · Router and Control integration	10%	70–125 active hours	Control→Router→Engine fixture end-to-end tests. · No direct unauthorized control path. · HOLD if delivery is mistaken for execution completion.
08 · Evidence, logging, and recovery	9%	55–95 active hours	Recovery drills, redaction tests, and evidence completeness checks. · HOLD if recovery can silently repeat dangerous work.
09 · Packaging and InstaDater integration	8%	50–90 active hours	Fixture install, repair, forced-failure rollback. · HOLD if legacy runtime can be overwritten during fixture proof.
10 · Multi-profile proof	7%	60–105 active hours	Multi-profile fixture PASS with no cross-profile state leakage. · Return to isolation/runtime phases on any shared-state contamination.
11 · Production hardening	6%	60–110 active hours	Target-hardware performance, soak, security, and recovery tests. · HOLD on unbounded restart, resource exhaustion, or missing diagnostics.
12 · Release and legacy cutover	4%	45–90 active hours	Owner-approved release gate and rollback proof. · Master Engine version truth updated only after acceptance. · Do not cut over or archive legacy without explicit current authorization. · CROSS-COMPONENT DEPENDENCIES · Shared Schemas · Watcher Profile SDK / Generator · Forgey Control · Cross-Device Router · InstaDater · Forgey Desktop · Test and Fixture System · BLOCKERS AND PROTECTED RISKS · The authoritative implementation baseline still requires Phase 02 source reconciliation. · The exact Watcher Profile SDK canonical path is unresolved. · No new-architecture watcher is accepted running or connected. · Master Engine v1.0.0 cannot be treated as released. · Implementation remains blocked by source, profile-contract, security, rollback, and cutover evidence. · SPECIAL RULES · Exactly 12 roadmap phases. · Master Engine v1.0.0 remains unreleased. · No live watcher change or legacy cutover is authorized. · ROADMAP APPROVAL GATE · This roadmap is ready for Owner review but is not yet approved for · implementation. · Owner review must decide: · 1. Whether the north star and 100% definition are correct. · 2. Whether the phase weights and ETUC are accepted. · 3. Whether the dependencies and blockers are complete. · 4. Whether the Green pause point is correct. · 5. Whether the component weight/parent placement is accepted. · 6. Whether a later implementation-planning phase may begin. · Until explicit Owner approval, no implementation prompt or source change is · authorized.

Bare Minimum

One canonical engine securely runs two generated isolated fixture profiles, validates authorization, enforces roots/actions, supervises lifecycle, produces evidence, recovers safely, and rolls back without replacing Forgey Local.
Comfortably Functional / Purple:
Reliable daily operation across several profiles/devices with mature diagnostics, compatibility, performance, upgrades, recovery, Control/Desktop integration, and low-friction evidence review.
First Green work target / pause point:
Approve goal, boundaries, source inputs, source-reconciliation plan, profile-contract direction, and acceptance evidence before runtime source modification.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Goal and contract lock 7% 18–32h
02. Authoritative source reconciliation 10% 40–80h

Comfortable target

Reliable daily operation across several profiles/devices with mature diagnostics, compatibility, performance, upgrades, recovery, Control/Desktop integration, and low-friction evidence review.
First Green work target / pause point:
Approve goal, boundaries, source inputs, source-reconciliation plan, profile-contract direction, and acceptance evidence before runtime source modification.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Goal and contract lock 7% 18–32h
02. Authoritative source reconciliation 10% 40–80h
03. Canonical foundation 9% 45–80h
04. Runtime truth and lifecycle 10% 60–105h

Green pause point

Approve goal, boundaries, source inputs, source-reconciliation plan, profile-contract direction, and acceptance evidence before runtime source modification.

Dependencies

: Owner roadmap approval.
Deliverables:
Approved runtime boundary and 100% definition.
Profile-contract inventory.
Authority and cutover matrix.
Evidence gate:
Owner-approved architecture record.
Zero unresolved product-identity conflicts.
Stop / return condition:
HOLD if Master Engine duplicates Control, Router, InstaDater, Desktop, or profile responsibilities.
PHASE 02 — Authoritative source reconciliation
Weight: 10%
ETUC: 40–80 active hours
Dependencies: Phase 01 and current migration evidence.
Deliverables:
Compare legacy, fixtures, installed behavior, and current candidate files.
Choose and freeze authoritative baseline.
Conflict and retained-behavior report.
Evidence gate:
Hash manifest and comparison report.

Blockers

The authoritative implementation baseline still requires Phase 02 source reconciliation.
The exact Watcher Profile SDK canonical path is unresolved.
No new-architecture watcher is accepted running or connected.
Master Engine v1.0.0 cannot be treated as released.
Implementation remains blocked by source, profile-contract, security, rollback, and cutover evidence.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0001_Master_Engine_Roadmap_v0.1.0.txt
SHA-256 8A0FA8F1E41795FA4F27511EC19484C60BDB5D5FFF4BC789F2E54A0A28892737

100% completion definitionThe complete approved runtime is implemented, secured, tested, documented, independently packaged, installable/updateable/repairable/rollback-capable, proven across approved profile types and devices, accepted for production, and safely cut over from legacy behavior.

The Spark → F.O.U.R. → Forgey Foundry · v1.0

PET FORGE 🐢

This roadmap defines the approved development sequence for Pet Forge.

12 gatesprototype sequence

For the family

This is the stable Pet Forge prototype gate plan. Gate 0 is complete and Gate 1 is in progress. Current Blue uses a separately maintained provisional equal-gate model; roadmap connection never changes completed-gate evidence.

Roadmap stateApproved and imported

Total ETUCNot yet weighted

Weight truthGate sequence only; numeric Current Status is maintained separately from roadmap connection

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestoneComplete and verify Proto Gate 1 before moving to Gate 2.

Phase	Weight	ETUC	Evidence / stop gate
00 · Pre-Implementation Controls	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 0: Pre-Implementation Controls
01 · Safe Desktop Overlay	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 1: Safe Desktop Overlay
02 · Ground-Pet Movement and Interaction	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 2: Ground-Pet Movement and Interaction
03 · Desktop Physics, Windows, Taskbar, and Monitors	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 3: Desktop Physics, Windows, Taskbar, and Monitors
04 · Control Panel, System Tray, and Onboarding	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 4: Control Panel, System Tray, and Onboarding
05 · Conversation AI and Reaction Decisions	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 5: Conversation AI and Reaction Decisions
06 · Visual Awareness and Continuous Watch	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 6: Visual Awareness and Continuous Watch
07 · Memory, Learning, Personality, and XP	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 7: Memory, Learning, Personality, and XP
08 · Three-Pet System and Multi-Pet Behavior	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 8: Three-Pet System and Multi-Pet Behavior
09 · Application Reactions and Productivity	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 9: Application Reactions and Productivity
10 · Performance, Data, Backups, and Recovery	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 10: Performance, Data, Backups, and Recovery
11 · Final Proto v1.0.0 Validation	0%	Gate sequence — ETUC not yet weighted	Complete and evidence-verify Gate 11: Final Proto v1.0.0 Validation

Bare Minimum

Comfortable target

Green pause point

Complete and verify Proto Gate 1 before moving to Gate 2.

Dependencies

Blockers

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0013_Pet_Forge_Proto_v1.0.0_Roadmap.txt
SHA-256 C77A73E116C7FFB7F79F283F701E806CBC5C3E68BDA5691CC68D597A1D3292F2

F.O.U.R. → Forgey Foundry · v0.1.0

SHARED SCHEMAS Roadmap

Give every Foundry component one versioned, language-neutral, validated meaning for identity, manifests, inventory, authorization, commands, runtime state, evidence, errors, packages, and compatibility.

100%phase total

For the family

SHARED SCHEMAS ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC305–565 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestoneFreeze identity, manifest, runtime-status, and authorization-envelope schemas for fixtures, then pause.

Phase	Weight	ETUC	Evidence / stop gate
01 · Contract inventory and source reconciliation	10%	25–45 active hours	Hash and semantic comparison report. · HOLD on unresolved duplicate meaning.
02 · Authority, identity, and naming rules	10%	25–45 active hours	Naming/ownership validation fixtures. · HOLD on ambiguous owner or identifier.
03 · Core schema set	22%	60–105 active hours	Positive and negative golden fixtures. · HOLD if security-sensitive fields are ambiguous.
04 · Validation and canonical serialization	15%	45–80 active hours	Cross-platform canonicalization and invalid-fixture tests. · HOLD on non-deterministic signed meaning.
05 · Compatibility, migrations, and deprecation	15%	45–85 active hours	Upgrade/downgrade/migration fixture evidence. · HOLD on in-place mutation of accepted semantics.
06 · Generated bindings	10%	35–70 active hours	Round-trip and source-reproducibility tests. · Return if generated code becomes hidden source truth.
07 · Cross-component integration proof	10%	40–75 active hours	Multi-component fixture PASS. · HOLD on producer/consumer semantic mismatch.
08 · Release governance and hardening	8%	30–60 active hours	Release gate and reproducible package hashes. · No release without migration and negative-test evidence. · CROSS-COMPONENT DEPENDENCIES · Forgey Foundry Platform · Adapter SDK · Master Engine · Forgey Control · Cross-Device Router · Top-level InstaDater · Test and Fixture System · BLOCKERS AND PROTECTED RISKS · Draft schema copies still require authoritative reconciliation. · The exact accepted contract set and compatibility window remain to be frozen. · Generated-language scope and deprecation periods require roadmap-stage decisions. · SPECIAL RULES · Component-private models remain component-owned. · Schema records do not authorize, transport, or execute by themselves. · ROADMAP APPROVAL GATE · This roadmap is ready for Owner review but is not yet approved for · implementation. · Owner review must decide: · 1. Whether the north star and 100% definition are correct. · 2. Whether the phase weights and ETUC are accepted. · 3. Whether the dependencies and blockers are complete. · 4. Whether the Green pause point is correct. · 5. Whether the component weight/parent placement is accepted. · 6. Whether a later implementation-planning phase may begin. · Until explicit Owner approval, no implementation prompt or source change is · authorized.

Bare Minimum

Core identity, manifest, inventory, status, authorization, command, receipt, evidence, error, package, and compatibility contracts work in fixture integrations.
Comfortably Functional / Purple:
Released components upgrade safely across supported schema versions with mature migrations, diagnostics, generated bindings, and predictable deprecation.
First Green work target / pause point:
Freeze identity, manifest, runtime-status, and authorization-envelope schemas for fixtures, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Contract inventory and source reconciliation 10% 25–45h
02. Authority, identity, and naming rules 10% 25–45h

Comfortable target

Released components upgrade safely across supported schema versions with mature migrations, diagnostics, generated bindings, and predictable deprecation.
First Green work target / pause point:
Freeze identity, manifest, runtime-status, and authorization-envelope schemas for fixtures, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Contract inventory and source reconciliation 10% 25–45h
02. Authority, identity, and naming rules 10% 25–45h
03. Core schema set 22% 60–105h
04. Validation and canonical serialization 15% 45–80h

Green pause point

Freeze identity, manifest, runtime-status, and authorization-envelope schemas for fixtures, then pause.

Dependencies

: Migration evidence.
Deliverables:
Inventory all draft contracts/copies.
Select canonical source set.
Private-versus-shared classification.
Evidence gate:
Hash and semantic comparison report.
Stop / return condition:
HOLD on unresolved duplicate meaning.
PHASE 02 — Authority, identity, and naming rules
Weight: 10%
ETUC: 25–45 active hours
Dependencies: Phase 01.
Deliverables:
Schema ownership.
IDs/namespaces/version fields.
Canonical terminology and extension rules.
Evidence gate:
Naming/ownership validation fixtures.
Stop / return condition:

Blockers

Draft schema copies still require authoritative reconciliation.
The exact accepted contract set and compatibility window remain to be frozen.
Generated-language scope and deprecation periods require roadmap-stage decisions.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0005_Shared_Schemas_Roadmap_v0.1.0.txt
SHA-256 AA383BB177C334EA510BF188D92CE84771F621AAAFC16B0E19F902ECAF1A2FCF

100% completion definitionAll approved cross-component contracts are authoritative, versioned, semantically documented, validated, canonicalized, migratable, code-generatable where approved, proven across consumers/producers, secured, released, and Owner-accepted.

F.O.U.R. → Forgey Foundry · v0.1.0

WATCHER PROFILE SDK / GENERATOR Roadmap

Provide one safe supported system for defining, generating, validating, testing, packaging, installing, updating, repairing, and rolling back isolated profiles that run on the shared Master Engine.

100%phase total

For the family

WATCHER PROFILE SDK / GENERATOR ROADMAP is connected automatically from its roadmap file. Current capability status remains separately evidence-maintained.

Roadmap stateApproved and imported

Total ETUC365–675 active hours

Weight truthRoadmap phase weights parsed automatically; parent contribution remains evidence-governed

Last verified2026-07-22

ConfidenceRoadmap file and hash verified; current implementation status is separate

Next milestoneGenerate and validate a Forgey Global fixture and minimal second profile without live execution, then pause.

Phase	Weight	ETUC	Evidence / stop gate
01 · Goal, source, and profile-contract lock	10%	25–45 active hours	Owner-approved source and contract map. · HOLD until canonical path is confirmed.
02 · Templates and deterministic core	12%	40–75 active hours	Golden-output reproducibility tests. · HOLD if templates copy Master Engine logic.
03 · Validator and diagnostics	15%	45–80 active hours	Positive/negative profile fixture suite. · HOLD on ambiguous permissions or invalid path acceptance.
04 · Capability, permission, and isolation model	15%	50–90 active hours	Privilege, root, dependency, and isolation negative tests. · HOLD on broad default authority.
05 · Fixtures and test harness	10%	35–65 active hours	Hard fixture/live separation proof. · HOLD if fixtures can appear as live state.
06 · Packaging and profile artifacts	10%	35–65 active hours	Reproducible package and integrity validation. · HOLD on embedded secrets or untracked dependencies.
07 · Top-level InstaDater integration	10%	40–75 active hours	Fixture install and rollback tests. · HOLD on manual Control/Router pairing.
08 · Multi-profile runtime proof	12%	55–100 active hours	Multi-profile end-to-end PASS. · Return to isolation/contracts on shared-state leakage.
09 · Wizard, hardening, and release	6%	40–80 active hours	CLI/wizard equivalent-output tests and Owner release gate. · No release if GUI and CLI validation diverge. · CROSS-COMPONENT DEPENDENCIES · Master Engine · Shared Schemas · Adapter SDK · Forgey Control · Cross-Device Router · Top-level InstaDater · Forgey Desktop · BLOCKERS AND PROTECTED RISKS · The canonical source path is still unresolved and must be confirmed before implementation. · The exact generation UX, template language, and first live profile sequence remain unapproved. · No complete multi-profile proof or generator release exists. · SPECIAL RULES · Implementation remains HOLD until the canonical source path is Owner-confirmed. · ROADMAP APPROVAL GATE · This roadmap is ready for Owner review but is not yet approved for · implementation. · Owner review must decide: · 1. Whether the north star and 100% definition are correct. · 2. Whether the phase weights and ETUC are accepted. · 3. Whether the dependencies and blockers are complete. · 4. Whether the Green pause point is correct. · 5. Whether the component weight/parent placement is accepted. · 6. Whether a later implementation-planning phase may begin. · Until explicit Owner approval, no implementation prompt or source change is · authorized.

Bare Minimum

Generate two distinct fixture profiles that install, register, remain isolated, run safely in fixtures, and roll back.
Comfortably Functional / Purple:
Routine profile creation through CLI and a shared-core Desktop wizard with strong diagnostics, migrations, documentation, multi-device packages, and reliable recovery.
First Green work target / pause point:
Generate and validate a Forgey Global fixture and minimal second profile without live execution, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Goal, source, and profile-contract lock 10% 25–45h
02. Templates and deterministic core 12% 40–75h

Comfortable target

Routine profile creation through CLI and a shared-core Desktop wizard with strong diagnostics, migrations, documentation, multi-device packages, and reliable recovery.
First Green work target / pause point:
Generate and validate a Forgey Global fixture and minimal second profile without live execution, then pause.
Blue Current rule:
Blue Current changes only when this roadmap is Owner-approved and accepted
evidence proves completion of weighted capabilities. Plans, questionnaires,
folders, elapsed time, imports, and roadmap creation do not increase Blue.
WEIGHTED PHASE SUMMARY
01. Goal, source, and profile-contract lock 10% 25–45h
02. Templates and deterministic core 12% 40–75h
03. Validator and diagnostics 15% 45–80h
04. Capability, permission, and isolation model 15% 50–90h

Green pause point

Generate and validate a Forgey Global fixture and minimal second profile without live execution, then pause.

Dependencies

: Master Engine and Shared Schemas direction.
Deliverables:
Canonical source decision.
Profile input/output contract.
Generator/runtime/lifecycle boundaries.
Evidence gate:
Owner-approved source and contract map.
Stop / return condition:
HOLD until canonical path is confirmed.
PHASE 02 — Templates and deterministic core
Weight: 12%
ETUC: 40–75 active hours
Dependencies: Phase 01.
Deliverables:
Python-first core library/CLI.
Profile directory/config templates.
Deterministic generation metadata.
Evidence gate:
Golden-output reproducibility tests.
Stop / return condition:

Blockers

The canonical source path is still unresolved and must be confirmed before implementation.
The exact generation UX, template language, and first live profile sequence remain unapproved.
No complete multi-profile proof or generator release exists.

Evidence

Automatically registered from Artifacts/Current/Approved_Roadmaps/0007_Watcher_Profile_SDK_Generator_Roadmap_v0.1.0.txt
SHA-256 3515864826C6B8110D2CC35619E22530948547D49C347FB411771898F5254088

100% completion definitionApproved users can create reliable least-privilege profiles with complete manifests, tests, fixtures, packages, documentation, compatibility, lifecycle metadata, automatic inventory registration, and Owner-accepted release evidence.