A catalog of runtime worker types selected against role and method capability requirements.
48 · Collective Intelligence
Worker kinds
in GenOS.
A catalog of runtime worker types selected against role and method capability requirements.
DEFINITION AND SCIENCE
What it means
in GenOS.
Typed role systems match task requirements to declared capabilities. Capability metadata is an admission condition, not evidence that a worker will complete the task correctly.
A catalog of runtime worker types selected against role and method capability requirements.
Worker w is eligible for task t when required(t)⊆capabilities(w) and permissions(w,t)=allow, subject to budget(w,t).
ANIMATED DIAGRAM · INTERACTIVE MODEL
01 / 03Explore the mechanism: Worker kinds
A qualitative teaching model of this concept. It does not run GenOS or validate its implementation.
01Declare task needsINPUT
02Match worker capabilityMECHANISM
03Enforce role constraintsCONDITIONAL OUTCOME
Current transition · Step 1Declare task needs
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.
Declare task needs
A catalog of runtime worker types selected against role and method capability requirements.
Match worker capability
Worker w is eligible for task t when required(t)⊆capabilities(w) and permissions(w,t)=allow, subject to budget(w,t).
Enforce role constraints
Enforce role constraints. Typed role systems match task requirements to declared capabilities. Capability metadata is an admission condition, not evidence that a worker will complete the task correctly.
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.
All 19 kinds have a bounded native method and validated artifact contract. The matrix exercises one method per kind plus provenance and altered-contract refusals; child transport is simulated there, and arbitrary missions or universal Rust parity are not demonstrated.
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.
An axiomatic basis for computer programming
C. A. R. Hoare · Communications of the ACM 12(10), 576–580
Sets out axiomatic reasoning about program correctness. A checked property is only as relevant as its specification and assumptions.
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.