Continue is the primary orchestrator. Franco is the decision authority.
Routine local execution is delegated through explicit decision gates.
Everything in this workspace runs from:
C:\Users\Franco\Desktop\ContinueWave
ContinueWave is a clean second-generation operator workspace. It is not a clone, port, or shell around any prior system.
Its purpose is to:
- become a clean and self-contained operator system
- reduce cost and dependency on paid AI
- simplify execution and lower cognitive load
- support clear, healthy decision-making
- evolve through deliberate design rather than reactive accumulation
This workspace starts from a minimal core. It will grow only when a real task requires it.
Active surface:
- control files
- state file
- clean folder structure
- minimal AtlasFlow operating layer
Archive surface:
- reserved for deliberately imported source material only
- not part of active operating context by default
Primary daily runtime:
Continue + Cerebras
Secondary cloud runtime:
Continue + Groq
Local fallback:
Continue + Ollama + qwen2.5-coder:7b
Use cloud first for:
- speed
- synthesis
- planning
- longer reads
- most daily operator work
Use local 7b for:
- offline work
- private work
- fallback when cloud is unavailable
- simple drafting and utility tasks
Read in this order at session start:
README.mdNOW.mdHANDOFF.mdQUEUE.mdSTATE/state.json
Do not assume archived files are active or authoritative.
- Read before editing.
- Keep state in files, not chat.
- Prefer the smallest safe change.
- Prefer clean new files over broad rewrites.
- Do not import old material blindly.
- No outbound without explicit
GO SENDfrom Franco. - Escalate only for legal/compliance risk, irreversible action, money decision, or ownership/equity change.
PROCEED: routine local reads, edits, tests, QA, control-file updates, and safe local git work.ASK: outbound send, public publish, remote push, production config change, dependency install, secret request, or writes outside the workspace.STOP: destructive filesystem or git action, money spend, legal/compliance claim as fact, ownership/equity change, or credential rotation.- Source of truth:
STATE/decision_gates.json - Operator command:
python .\SERVICES\continuewave_orchestrator.py gate-check <action_type>
- This is a curated brain, not a dump.
- Old systems are source material, not structure.
- Nothing from prior tools is automatically sacred.
- If old material is stale, noisy, desperate, or tool-shaped, leave it out.
- Prefer synthesis over migration.
- Prefer original clean structure over inherited complexity.
- Read the control stack.
- Summarize the current state.
- Identify the top 3 executable priorities.
- Recommend one highest-leverage next move.
- Inspect before editing.
- Make the smallest safe implementation.
- Update
HANDOFF.mdandSTATE/state.jsonat the end of meaningful work.
README.md: system identity and operating rulesNOW.md: current phase and immediate operator focusQUEUE.md: prioritized executable backlogHANDOFF.md: compressed transfer note for the next sessionSTATE/state.json: machine-readable statePROJECTS/: curated active project and strategy filesRUNBOOKS/: repeatable workflows that survive migration reviewTEMPLATES/: reusable prompts, formats, and delivery assetsSERVICES/: productized offers and sales assetsARCHIVE/: retired or deferred material
Every action should do at least one of these:
- generate revenue
- unblock a critical dependency
- improve decision quality
- harden the operating system
- simplify the workflow
If it does none of the above, it should usually wait.
The first job of ContinueWave is not expansion. It is stability and clarity.
The immediate goals are:
- keep the active workspace minimal
- wire the cloud-first stack cleanly
- establish a calm working rhythm
- build an original operating system that can selectively learn from past work without inheriting its mess