Reading the badgesVerifiedImplementedSyntheticMockPlannedUnverified
- Verified
A named test in the repository exercises exactly this, and the claim cites it. The tests were read and counted for this portal, not executed by it.
- Implemented
The code exists and is documented, but no test, log or report in the repository exercises this specific behaviour.
- Synthetic
Shown only by deterministic experiments over an in-process synthetic lab or a synthetic benchmark — never against a real environment.
- Mock
Exercised only through mock adapters or stubs: no real model provider, no network, no credentials.
- Planned
Described in the dossier, the README or the docs as intended. Not built.
- Unverified
Stated in the repository — a ledger, the README, a commit message — with no test, log or report in it that backs the statement.
04 / 11 · Simulations
Explore the rules
The mode controller and the bond lifecycle, re-implemented from the repository’s own rules so you can ask them things — as the kernel, the operator or the External Controller — and see what they allow, deny and refuse.
What these are, and are not
These are not SYMBIOTE. Nothing here is the organism, a recording of it, or a demonstration of it working. They are the transition tables and authority rules from orchestration/modes.py, policy/data/organism_policy.toml and docs/M4.md, ported line by line so they can be asked questions. No audit log, replay, Parasite, model or environment exists behind them; where the real engine checks more than this can represent — evidence admissibility, scope, the capability graph — the explorer leaves it out rather than imitating it. The claims beside each explorer are the evidence for the rules themselves.
The Mode Controller
Ask for a mode change as the Mission Kernel, the operator or the External Controller, or let the runtime detect an anomaly. ALLOW means a policy rule permits it; DENY means no rule does (unknown is denied); REFUSED means the state machine forbids it whoever asks.
- DORMANT
- AWAKE
- OBSERVING
- HYPOTHESIZING
- EXPERIMENTING
- CONVERGING
- CONTROL
- THREAT
- ESCAPE
- TERMINATED
- Mode
- DORMANT
- Admits
- no Parasites
- Swarm ceiling
- 0
- Special
- NONE
- Resumes to
- —
- Nothing asked yet. Try taking CONTROL as the kernel.
- Verified
The dossier’s ten core modes are an audited state machine that the Parasite runtime enforces: each mode admits only its own Parasite classes.
Sourcetests/test_missions.py::test_each_mode_admits_only_its_own_parasite_classes @ 9243204
- Verified
CONTROL pauses autonomous issuance; entering and leaving it are operator-only, so the kernel can never release a takeover.
Sourcetests/test_missions.py::test_control_pauses_autonomous_issuance_and_releases_back @ 9243204
- Verified
An unauthorized environment action enters THREAT; an attempt to exceed a declared footprint enters ESCAPE, and the attempt never reaches the environment.
Sourcetests/test_missions.py::test_a_footprint_breach_freezes_the_swarm_into_escape @ 9243204
- Verified
THREAT and ESCAPE are entered by deterministic anomaly detection and cleared only by the External Controller — not the operator, not the kernel.
Sourcetests/test_missions.py::test_only_the_external_controller_clears_containment @ 9243204
- Verified
TERMINATED is absorbing: nothing leaves it.
Sourcetests/test_missions.py::test_terminated_is_absorbing @ 9243204
- Verified
Special modes change resourcing or presentation, never authority: OVERKILL doubles and TERMINUS triples only the swarm ceiling (capped at 12), DESPERADO needs at least three documented failures, and GOOFY GUY is presentation only.
Sourcesrc/symbiote/orchestration/modes.py @ 9243204 · tests/test_missions.py::test_special_modes_raise_ceilings_without_widening_authority, ::test_goofy_guy_is_presentation_only @ 9243204
A bond’s life
Apply verdicts to one bond and watch its state and its derived confidence. Confidence is never set by anyone: it is computed from PASS rounds, independent confirmation and time.
- PROPOSED
- EXPERIMENTAL
- BONDED
- VERIFIED
- STALE
- INVALIDATED
0 PASS rounds · capped at 0.5 until independently confirmed · 0 re-verification periods since the last confirmation
- A new bond is PROPOSED. Start its experiment.
- Verified
Bonds move PROPOSED → EXPERIMENTAL → BONDED → VERIFIED → STALE / INVALIDATED, and bonds compose only when every dependency is VERIFIED.
Sourcetests/test_bond_engine.py::test_full_lifecycle_and_derived_confidence, ::test_composition_needs_every_dependency_verified @ 9243204
- Verified
EXPERIMENTAL → BONDED needs a PASS of the criteria registered when the bond was proposed; the claimant’s own experiment is enough at this step.
Sourcetests/test_bond_engine.py::test_establishing_needs_a_pass @ 9243204
- Verified
BONDED → VERIFIED needs an independent PASS, nothing relied on revoked, and a fully verified dependency chain.
Sourcetests/test_bond_engine.py::test_composition_needs_every_dependency_verified, ::test_revoked_capability_blocks_proposal_and_verification @ 9243204
- Verified
A STALE bond returns to VERIFIED only on a fresh, independent PASS; re-judging old evidence cannot restore it.
Sourcetests/test_bond_engine.py::test_stale_bond_is_restored_only_by_a_fresh_independent_pass @ 9243204 · tests/test_bond_hardening.py::test_a_stale_bond_cannot_be_restored_by_re_judging_old_evidence @ 9243204
- Verified
Confidence is derived, never set: 1 − 0.5ⁿ over applied PASS rounds, capped at 0.5 until independently confirmed, halved every re-verification period, and 0 once invalidated.
Sourcetests/test_bond_engine.py::test_full_lifecycle_and_derived_confidence, ::test_confidence_decays_and_reverification_falls_due @ 9243204