nx_cell.nx

nx_cell.nx -- THE base computational unit. Per [[feedback-naming-discipline-no-industry-competitor-overlap]]: "nx_cell" is the foundational biology primitive replacing "container" in the cardinal naming taxonomy. Every other primitive references it semantically but until now it was conceptual; this file makes the cell concrete. A cell is the substrate's atomic unit of compute + isolation + life-cycle. Each cell has: - identity (cell_id, methyl mark for self-verification) - intent (attention_class — foreground/background/idle classification) - boundary (brane — capability tokens for what crosses) - storage (vacuole — sealed content-addressed bytes) - backup (chromatin — pre-failover snapshot) - lineage (parent_pathway_id — the cell-graph membership) - lifecycle (state machine: NASCENT → RUNNING → YIELDING/SUSPENDED → ABORTIVE → TERMINATED, with chromatin survivable across the terminal transition) Per Captain Moroni doctrine: cells are the unit of accountability. Every observable substrate event happens in or between cells; every audit trail is keyed by cell_id; every defensive action targets a specific cell. Composes: nx_methyl -- self-marker validates this cell is substrate-self nx_brane -- capability membrane controlling IO nx_vacuole -- the cell's sealed storage nx_chromatin -- backup state for failover nx_pathway -- multi-cell graphs of which this cell is a member nx_budget -- the cell's declared resource ceiling nx_attention_class -- the cell's declared priority class nx_immune -- colony tracks each cell's state nx_abortive -- terminal-state machine composes here V1 ships the struct + state-machine transitions + accessors. Behavior verbs (run/yield/suspend/etc) are caller-driven; cell itself doesn't schedule -- nx_pathway and the surrounding substrate do that.