NOX: Task Signal Lifecycle

How does a task move through the NOX system? This page documents the lifecycle of a task signal — from initial emission in a project log to structured capture in the central logbook.

1. Emit Point

Tasks are first expressed in-line, within a working model or log. At this point, they are raw — unconfirmed, unprioritized, but observed. We use `{ }` to distinguish them from traditional checklists. The domain clarifies scope, and a trailing semicolon signals intent to emit elsewhere.

---
file: a-model-log-13.md
---

- { } Add routing to HNET [HNET]();

2. Binding Phase (signals-13.md)

Once observed, a task is bound into the day’s signal file. This allows it to be scored, seen, or rerouted. We now use `[ ]` to confirm it's a real checkbox, and include its origin file.

- { [ ] Add routing to HNET [HNET](a-model-log-13.md); }

Tip: This should happen early. Once it’s in the signal shell, it can be tracked without rereading the full model log.

3. Centralization Phase (log.md)

Multi-day or system-wide tasks migrate into log.md — the NOX master log. This step happens during morning review, when yesterday’s signals are tallied and outstanding work is centralized.

---
file: log.md
---

## Emit Shell

- { [ ] Add routing to HNET [HNET](models/homework/2025/07-july/13-homework/a-model-log-13.md); }
- { [ ] Update glossary with “Signal Shell” definition [NOX](models/applications/alexcatalano/nox/glossary.html); @due:2025-07-18 }

Syntax Rules

{ } = emitted item (not yet actionable)
[ ] = confirmed task
[DOMAIN](source) = scope and source file
Semicolon ; = deliberate emission (optional stylistic marker)

“Emit signals like seeds. Track them like roots. Let the system hold what your brain shouldn’t.”

← Back to What is NOX
← Return to Portfolio Home