A pathology category for unwanted propagation across agents, workspaces, or state boundaries.
92 · Immunity & Medicine
Infectious failure
in GenOS.
A pathology category for unwanted propagation across agents, workspaces, or state boundaries.
DEFINITION AND SCIENCE
What it means
in GenOS.
Infection spreads through contact and transmission paths. The software analogy tracks unwanted propagation of a bad artifact or state across workspaces, without implying a pathogen.
Infection spreads along contact paths. The analogy motivates tracing artifact propagation and isolating affected software boundaries.
A pathology category for unwanted propagation across agents, workspaces, or state boundaries.
On graph G=(V,E), exposure set R_{t+1}=R_t∪neighbors(R_t) subject to actual transfer events; containment removes or blocks implicated edges.
ANIMATED DIAGRAM · INTERACTIVE MODEL
01 / 03Explore the mechanism: Infectious failure
A qualitative teaching model of this concept. It does not run GenOS or validate its implementation.
01Trace a faulty artifactINPUT
02Map its propagationMECHANISM
03Isolate affected scopeCONDITIONAL OUTCOME
Current transition · Step 1Trace a faulty artifact
The modeled transition may proceed. Change the assumption and move through the stages to inspect the decision path.
PROCESS AND USE
How it works
at a glance.
Trace a faulty artifact
A pathology category for unwanted propagation across agents, workspaces, or state boundaries.
Map its propagation
On graph G=(V,E), exposure set R_{t+1}=R_t∪neighbors(R_t) subject to actual transfer events; containment removes or blocks implicated edges.
Isolate affected scope
Isolate affected scope. Infection spreads through contact and transmission paths. The software analogy tracks unwanted propagation of a bad artifact or state across workspaces, without implying a pathogen.
RUNTIME IMPLEMENTATION
What is connected,
and how far.
The linked, versioned GenOS source defines this concept's supported operations and limits. The status axes describe the implementation and evidence recorded for this entry; they do not establish general mission success, scientific equivalence or behavior beyond that scope.
The runtime models selected infection and quarantine cases; this is a software threat/pathology model, not biological infection simulation.
Failure modes have not yet been separately cataloged for this entry; follow the source and evidence links before relying on the mechanism.
PRIMARY RESEARCH · MECHANISM LEVEL
The mechanism
behind the analogy.
Design of fault-tolerant computers
Algirdas Avižienis · AFIPS Fall Joint Computer Conference, 733–743
Original fault-tolerance design work. It motivates software failure analysis but does not validate a GenOS pathology label.
Open publication ↗Primary research describes the cited mechanism; specific technologies may instead cite their original technical documentation. These sources provide context and do not validate the GenOS implementation.
EVIDENCE AND LIMITS
Scope and validation boundaries
The linked, versioned GenOS source defines this concept's supported operations and limits. The status axes describe the implementation and evidence recorded for this entry; they do not establish general mission success, scientific equivalence or behavior beyond that scope.