This note turns the durable result of the immune tolerance audit into an evaluation contract. The useful transfer is not an “immune score.” It is the refusal to collapse representation, recognition, permission, response, suppression, deletion, impairment, memory, and recovery into one bit.
State vocabulary
For module or rule at time , define
is categorical and dimensionless. The names describe engineered states; they do not assert biological identity. Every transition stores:
- the previous and proposed state;
- the evidence and representation support used;
- the actor and authority that may make the transition;
- expected useful effect and distinct collateral-loss terms;
- compute, data, time, energy, and reserve budget;
- expiry, revalidation, rollback or recovery target; and
- the observed outcome and decision lineage.
“Inactive” is not an admissible terminal diagnosis. It can mean that the rule was never generated, relevant evidence was not represented, eligibility is unknown, policy suppressed it, resources starved it, prior response contracted, the rule is retained as memory, or the implementation is impaired.
Representation, recognition, and permission
Let be the declared scenario set and the scenarios represented by current evidence. Representation coverage is
where scenario weights and are dimensionless. describes the registered scenario set; it does not prove that an unrepresented state is safe or that represented evidence is current.
For principal , action , object , and epoch or time , permission is
All predicates are Boolean. Authentication identifies the principal; authorization scopes the action and object; is observed system state; and is evidence with provenance, coverage, uncertainty, and expiry. A recognition or anomaly score can inform but cannot replace any predicate.
Cost-sensitive response
Let latent state range over benign/needed, harmful, compromised, and unresolved conditions. Let the action set include permit, monitor, rate-limit, quarantine, suppress, delete, and escalate. A calibrated policy chooses
where is observed evidence, is context and provenance, and every term is converted into one declared decision unit. Before any optional scalarization, the loss vector remains visible:
The components may use different native units—lost useful requests, incidents, seconds, joules, or currency—until a documented authority supplies conversion weights. Rare useful capability deleted by a gate is a measured outcome, not a free reduction in false accepts.
Population and contraction accounting
When modules can replicate, scale, pause, retire, or return from memory, track lineage as
where is instances, is replication or scale-up rate, is retirement/failure rate, and is reversible transition into quiescence, all in s or h; is newly admitted instances per second or hour. A fall in active count must be attributed to retirement, contraction, movement, suppression, resource loss, or quiescence.
Lineage share and effective diversity are
and are dimensionless. is an effective count of equally represented lineages, not proof of functional independence, failure-domain separation, or future coverage.
Maintained memory and local placement
For retained memory instances ,
where refresh and loss rates and are in s, is candidate instances per second entering the memory pathway, and is a dimensionless conversion fraction. Storage without retrieval, refresh, invalidation, compatibility, and retirement is not credited as useful memory.
For copies at location , compare placement policies with
and moved amount use instances or bytes; unmet events use events; coefficients convert all terms to joules or currency over one horizon. Local latency gains must pay for replication, refresh, inconsistency, invalidations, and recovery.
Reactivation and recovery gate
A quarantined, suppressed, or impaired module cannot be reactivated merely because load increased or the original detector score fell. Reactivation at time requires
where indicators are dimensionless, health and its threshold share a declared unit or normalized scale, and resource headroom and its minimum share a unit such as joules, bytes, or operations per second. A pass creates a bounded probation state; independent outcome verification is still required.
Recovery time is measured to sustained useful service plus restored reserve:
where and are seconds, is a frozen sustainment interval, and and are task service and reserve in their declared units. A lower alert rate or an empty queue is not recovery.
Lifecycle boundary and null
Charge sensing, routing, candidate generation, training, evaluation, replication, serving, monitoring, replay, reserve, movement, retirement, and recovery in joules over the same horizon. Report task quality, false permit, false suppression, false deletion, missed harm, containment latency, verified recovery, rare-capability retention, second-event readiness, and energy as a vector.
The complete null is a typed state machine plus calibrated risk and abstention, least-privilege identity and access control, anomaly detection, constrained control, evolutionary or ensemble search where applicable, replay, placement, and resource-aware scheduling. Reject the immune framing if this ordinary stack reproduces its decisions and frontier at equal information, intervention, compute, storage, reserve, and maintenance budget.
Editable lifecycle diagram: typed-tolerance-lifecycle.mmd.