Data Flows

Visual workflows showing how data moves through CLEO operations

Data Flows

This page visualizes how data moves through CLEO during key operations.

Task Creation Flow

1. User Input

   User runs cleo add "Task title" --priority high

2. Input Validation

   CLI validates required fields and format

3. ID Generation

   System generates unique task ID (T###)

4. Atomic Write

   Task written using atomic pattern

5. Audit Log

   Operation logged to todo-log.json

Atomic Write Pattern

Every write operation in CLEO follows this pattern:

This pattern ensures no partial writes - the operation either fully succeeds or the original file is preserved.

Validation Layers

Schema

JSON Schema validation ensures correct data types, required fields, and enum values.

Semantic

Cross-file checks for ID uniqueness, valid references, and cycle detection.

Temporal

Timestamp validation prevents future dates and ensures logical ordering.

Content

Content validation ensures meaningful data (title != description).

Session State Machine

Sessions transition through defined states:

Task Lifecycle

Backup System

Related Concepts

Architecture

System design and components

Anti-Hallucination

Validation mechanisms in detail