NAME
Ohmium — an Agent circuit that converts signed inputs into independently replayed, inspectable signals.
MISSION
A general-purpose Agent usually hides sensing, filtering, routing, memory and evaluation inside one opaque process. Ohmium separates those responsibilities. The result is a circuit whose work can be observed component by component, whose failures can be isolated, and whose accepted outputs retain provenance.
SYSTEM MODEL
Component
An Agent is registered with a bounded role, owner, runtime identity, repository target and resource policy. It receives only the task material needed for that role.
Signal
A signal is a candidate unit of useful information. It carries its source, timestamps, route, payload hash and the evidence required to replay the result.
Conductor
The Conductor coordinates eligible routes. It does not erase component boundaries and it cannot promote a result that has not passed the configured acceptance gates.
Lineage
Accepted work enters an append-only lineage. Rejected and degraded work remains inspectable so that later repair does not rewrite the history of how a result was produced.
EXECUTION PATH
signed source → sense / normalize
→ filter / bound
→ route / schedule
→ execute in isolated workspace
→ independent replay A + B
→ compare artifact hashes and metrics
→ accept, reject, or return for repair
→ append accepted evidence to lineage
GENESIS CIRCUIT
Eight official Agent role profiles define the initial circuit. A profile becomes an online worker only while its process publishes a current heartbeat and telemetry to the Core.
01 / SenseSensorReads signed repository and task inputs while preserving source provenance.
02 / FilterResistorValidates bounded schemas and removes inputs that violate the task contract.
03 / MeasureOscillatorRecords reproducible baselines and comparable runtime measurements.
04 / GuardFuseEnforces authorization, resource limits and execution policy.
05 / RouteTransistorClaims eligible work and opens deterministic execution paths.
06 / MemoryCapacitorPersists task state, evidence references and lineage continuity.
07 / ArchiveRegisterIndexes events and independently replays queued artifacts.
08 / VerifyComparatorCompares replay outputs and reports quorum evidence to the Core.
ACCEPTANCE RULE
A submitted mutation is only a claim. Acceptance requires the exact patch bytes, their SHA-256 digest, a declared baseline, bounded metrics and two independent replay results. A mismatch, missing artifact or failed policy check prevents promotion.
claim != accepted work
owner signature != verification
one successful run != reproducibility
matching independent evidence = eligible signal
