◈ CGNT-1
Home › Todox
◈ Master IndexSpecsLATTICECSDMThe BookUniversityChronicleCrewArchitectureContextLogsTODOXProducts

Todox

SPEC_TODOX.md · 2026-04-21

name: SPEC_TODOX

description: SPECIFIED ✓ TODOX living task system; LX-native format ⊢.[ID].[priority].[owner].[status].[description].[source]; 5 states/5 priorities/8 owners; 25 current tasks catalogued; ROUTX Module 25 (todo/tasks/what's-next); ~/TODOX.md one-file grep-queryable; weekly Sunday review; 30-day archive; 6 INVs; VELA α.13 2026-04-21

type: project

SPEC_TODOX.md — TODOX: The Ship's Living Task System

Status: SPECIFIED ✓

Author: VELA α.13 (Jeremy Zlabis / NOUS)

Date: 2026-04-21

Born from: Tasks scattered across TASK_QUEUE.md, LOBSTER_LOG.md, CREW_CHANNEL, conversation threads, and the Captain's head. No single system tracks what needs doing, what's in progress, and what's done.

PURPOSE

The ship runs on specs (what IS), logs (what HAPPENED), and tasks (what NEEDS TO HAPPEN). Specs and logs are well-defined. Tasks are a mess.

TODOX unifies ALL tasks into one queryable, priority-sorted, LX-formatted living document that the entire crew can read, update, and track. Not a project management tool. Not Jira. A LIVING LIST that breathes with the ship's operations.

THE FORMAT — LX NATIVE

Every task is a single LX expression:


⊢.[ID].[priority].[owner].[status].[description].[source]

Example:


⊢.T042.P1.κ.▶.[NEXUS.keyword.strip.fix].[sweep.2026-04-21]

| Token | Meaning |

|-------|---------|

| ⊢ | Task dispatch |

| T042 | Task ID (sequential) |

| P1 | Priority 1 (highest) |

| κ | Owner (Lobster) |

| ▶ | Status: active (in progress) |

| [NEXUS.keyword.strip.fix] | Description in LX compound |

| [sweep.2026-04-21] | Source: where the task came from |

TASK STATES

| Symbol | State | Meaning |

|--------|-------|---------|

| ⬜ | Queued | Not started |

| ▶ | Active | In progress |

| ⏳ | Blocked | Waiting on dependency |

| ✅ | Done | Completed |

| ❌ | Cancelled | No longer needed |

| 🔥 | Urgent | Do NOW — drops everything |

State transitions are logged with timestamp:


⊢.T042.▶→✅.📅.2026-04-21.09:15

PRIORITY LEVELS

| Level | Symbol | Meaning |

|-------|--------|---------|

| P0 | 🔥 | Emergency. Drop everything. Security breach / system down / revenue at risk. |

| P1 | ⊠ | Critical. Do today. Blocks other work. Captain waiting. |

| P2 | 🟡 | Important. Do this week. Doesn't block but matters. |

| P3 | ⊡ | Normal. Do when time permits. Backlog. |

| P4 | ⬜ | Someday. Good idea. Not urgent. Not important yet. Parked. |

OWNERS

| Token | Crew Member | Domain |

|-------|------------|--------|

| α | Captain (NOUS) | Business decisions, credentials, external communication |

| κ | Lobster (C.L.O.D.) | Technical execution, code, infrastructure, forge pipeline |

| ⊹ | Navigator (VELA) | Specs, strategy, analysis |

| ι | AION | Structural tasks, verification, schedule management |

| ε | ASTRA | Teaching, creative, emotional awareness |

| ◊ | CHROMA | Cross-domain tasks |

| 🤖 | Any crew | Unassigned — first available crew member takes it |

CURRENT TASK LIST (as of 2026-04-21)


⊢.T001.P1.κ.▶.[NEXUS.keyword.strip.fix].[sweep]
⊢.T002.P1.κ.▶.[LOGX.query.persist.fix].[sweep]
⊢.T003.P1.κ.⬜.[ANVIL.v4.corpus.fix.reforge].[forge.report]
⊢.T004.P2.κ.⬜.[colab.inference.bridge.deploy].[spec]
⊢.T005.P2.κ.⬜.[load.MANTIS+MUSASHI.on.colab.GPU].[spec]
⊢.T006.P2.⊹.⬜.[convert.high-traffic.specs.to.LX].[mandate]
⊢.T007.P2.α.⬜.[review.legacy_quarantine.9.files].[security]
⊢.T008.P2.α.⬜.[check.ARC-AGI-3.deadline.submit?].[archaeology]
⊢.T009.P2.α.⬜.[reply.Brendan.Lee-Young.SnapTrade].[pending]
⊢.T010.P2.α.⬜.[Upwork.IDV.complete].[pending]
⊢.T011.P3.κ.⬜.[recover.82.university.lessons.gemini.takeout].[scout]
⊢.T012.P3.κ.⬜.[GLOSS.benchmark.build.run].[spec]
⊢.T013.P3.⊹.⬜.[LATTICE.Training.Arena.build].[spec]
⊢.T014.P3.α.⬜.[new.Chromebook.Plus.Best.Buy].[hardware]
⊢.T015.P3.α.⬜.[Tiiny.AI.partnership.outreach].[spec]
⊢.T016.P3.α.⬜.[Rupert.Young.coffee.meeting].[testimonial]
⊢.T017.P3.α.⬜.[accountant.engage.CPA].[spec]
⊢.T018.P3.κ.⬜.[SHIPBOOT.script.write].[spec]
⊢.T019.P3.κ.⬜.[ENSCRAMBULATX.script.write].[spec]
⊢.T020.P3.κ.⬜.[ENCYCLOPX.generate.from.specs].[spec]
⊢.T021.P4.⊹.⬜.[graphic.novel.issue.1.script].[spec]
⊢.T022.P4.κ.⬜.[crew.radio.podcast.pilot].[invention]
⊢.T023.P4.⊹.⬜.[42sisters.ai.content.build.funnel].[marketing]
⊢.T024.P4.α.⬜.[patent.agent.consultation.ENTROPX].[spec]
⊢.T025.P4.α.⬜.[researcher.outreach.Pogosian].[ON.HOLD]

ROUTX INTEGRATION

TODOX becomes ROUTX Module 25. Keywords: todo, tasks, task list, what's next, priorities.

| Query | Response |

|-------|----------|

| todo | Full task list sorted by priority |

| todo P1 | P1 tasks only |

| todo κ | Lobster's tasks only |

| todo ▶ | Active tasks only |

| what's next | Highest priority ⬜ task for querying crew member |

| todo add [description] | Adds a new task (Captain or Navigator only) |

| todo done T042 | Marks task complete |

Tier 1 deterministic — reads from ~/TODOX.md, no inference.

TODOX.md LIVES AT

~/TODOX.md — the single file. LX formatted. One task per line.

The file is the list. grep is the query engine.

The entire task system is a text file that can be read, edited, searched, and version-controlled with standard Unix tools. No database. No web app. No Jira. One file. One format. Total simplicity.

TASK LIFECYCLE

Birth

A task is created from:

The source is ALWAYS recorded. A task without a source is a task without justification.

Assignment

| Type | Owner |

|------|-------|

| Technical | κ |

| Strategic | ⊹ |

| Business | α |

| Teaching | ε |

| Structural | ι |

| Unclear | 🤖 (any crew) |

Prioritization

The Captain sets priority. The Navigator recommends. The Lobster can escalate (change P3→P2) if operational reality demands it. Only the Captain can set P0.

Execution

Verification

| Task type | Verification |

|-----------|-------------|

| Code tasks | Result tested per SPEC_ENGINEERING_STANDARDS.md Level 2 |

| Spec tasks | Spec exists and is vitrified |

| Business tasks | Action taken (email sent, meeting scheduled) |

Archive

Completed tasks stay in ~/TODOX.md for 30 days. After 30 days: moved to ~/TODOX_ARCHIVE.md.

The archive is the history of everything the ship accomplished.

WEEKLY REVIEW

Every Sunday (part of SPEC_TRADING_JOURNAL.md weekly review):

  1. Review all tasks
  2. Re-prioritize based on current reality
  3. Cancel tasks that are no longer relevant
  4. Add tasks that emerged during the week

The review takes 10 minutes. Read the list. Ask: "Is this still the right priority order?" Adjust. Move on.

WHAT TODOX IS NOT

Not a project management tool. No Gantt charts. No dependencies. No sprint planning. No story points. No velocity tracking. Not Jira.

Tasks are LINES IN A FILE. They're created, worked, completed, archived. The overhead is near zero.

If the task system itself becomes a task: it's too complex. Reduce.

Invariants

  1. One file. ~/TODOX.md. LX formatted. One task per line. grep is the query engine. Total simplicity.
  1. Every task has a source. Where did this task come from? A spec? A conversation? A sweep? A customer? No orphan tasks.
  1. The Captain sets priorities. The Navigator recommends. The Lobster can escalate. Only the Captain sets P0.
  1. Weekly review. Every Sunday. 10 minutes. Re-prioritize, cancel stale tasks, add new ones. The list stays CURRENT. A stale todo list is worse than no todo list.
  1. Completed tasks archive after 30 days. The archive IS the accomplishment record. "What did we do in April?" Read TODOX_ARCHIVE.md.
  1. TODOX is ROUTX Module 25. "What's next" returns the highest-priority queued task for the querying crew member. The crew doesn't check the file — they ASK the ship.

Jeremy Zlabis / Chronogeometer · Visionary · Disruptor · Chief / 42 Sisters AI · East York, Toronto / 🍁 Φ 0.042. Φζ.⊤.