This document defines executable tasks for the REPL CLI system.
Status: MVP
- Each TASK corresponds to a single CLI command.
- Each TASK must be independently executable.
- Each TASK must be independently verifiable.
- Tasks are executed in isolation.
- No TASK depends on partial completion of another TASK.
- If a TASK fails, execution stops immediately.
- No retry is allowed.
- Error must be printed explicitly.
- Failed TASK is marked as BLOCKED.
- System does not attempt automatic recovery.
Initialize REPL project runtime environment.
.repl/directory exists after execution.repl/runtime/directory exists- Default runtime state is initialized
- Execution environment is ready for subsequent commands
Validate REPL system integrity.
- All required REPL directories exist
- Runtime state is consistent
- No missing or corrupted runtime files
- CLI reports system health status explicitly
Reset runtime environment to clean state.
.repl/runtime/state is cleared- Execution logs are removed or reset
- System returns to initial state after reset
- No residual execution state remains
Start execution session.
- Execution session is activated
- Context loading is prepared
- Runtime state reflects "active session"
- System is ready for AI execution input
Stop execution session.
- Execution session is terminated
- Runtime state reflects "inactive session"
- No active task remains in execution mode
Apply external AI execution result to runtime state.
- Accepts structured JSON input via stdin
- Input is validated against runtime schema
- Runtime state is updated deterministically
- Task status is updated to "done" or "blocked" (lowercase)
- On failure, execution stops immediately with error output
Display current runtime state.
- Current active task is displayed
- Runtime session status is shown (active/inactive)
- Task progress is visible
- Runtime state is readable and consistent
TASK SELECTED
↓
EXECUTE CLI COMMAND
↓
VALIDATE OUTPUT
↓
UPDATE RUNTIME STATE
↓
COMPLETE OR BLOCKED
The following must always remain true:
- Each CLI command maps to exactly one TASK
- TASK execution is deterministic
- TASK completion depends only on acceptance criteria
- Runtime state is the only source of truth
- No hidden or implicit state transitions exist