Appearance
Database & State Persistence
Summary
This document describes the state management and data storage mechanisms utilized across the system, including WORK_LOG.md, tasks.json, .env environment states, and local SQLite caches.
1. Persistence Mechanisms Overview
The system uses light-weight, file-backed state stores to ensure maximum portability, auditability, and zero external database setup requirements.
| Store | Format | Location | Primary Purpose |
|---|---|---|---|
| Work Log | Markdown | [WORK_LOG.md](file:///home/kizamladjanijebac/Documents/antigravity/elegant-franklin/WORK_LOG.md#L1-L52) | Immutable audit log of all system actions |
| Tasks Store | JSON | [tasks.json](file:///home/kizamladjanijebac/Documents/antigravity/elegant-franklin/tasks.json#L1-L34) | Active micro-task state for OBS HUD telemetry |
| Credentials & Config | Environment (.env) | .env | OAuth tokens, API keys, Notebook IDs |
| Local Cache | SQLite / JSON | .pytest_cache, logs/ | Local execution logs and test caches |
2. Micro-Tasks JSON Schema (tasks.json)
The tasks.json file maintains real-time subtask states observed by the Ralph Wiggum OBS HUD bridge:
json
[
{
"task_id": "task_1786121071_1",
"title": "Atomize & Clean Room Init",
"description": "Initialize zero cognitive load state",
"status": "completed",
"cognitive_cost": 1,
"result": "Executed subtask Atomize & Clean Room Init successfully."
}
]3. Work Log Specification (WORK_LOG.md)
WORK_LOG.md acts as an append-only transaction ledger. Each entry must strictly adhere to standard emoji markers:
markdown
🟡 Starting [ACTION_NAME]
✅ Completed [ACTION_NAME]judge_guard.py inspects file timestamps to ensure that no action proceeds without an active, non-stale 🟡 Starting entry created within the last 300 seconds.