Graded Dormancy

John Brajer — Possibility Reserve mechanism

Principle

DORMANT != DEAD

Possibilities do not need to be represented as a binary active/rejected state.

A system can preserve unavailable or currently unattractive branches at different dormancy levels.

Example state family

ACTIVE
WATCH
DORMANT
DEEP_DORMANT
REJECTED_UNDER_CURRENT_MODEL
DEAD_BY_HARD_CONSTRAINT

The exact labels are implementation-dependent. The mechanism is the important part.

Why

Binary rejection destroys information.

Graded dormancy lets a system reduce attention or compute without pretending that temporary infeasibility is permanent impossibility.

Requirement

Dormancy should carry a reason and, where possible, reactivation conditions.

---

Public reference

This standalone repository is part of the Trillsverse Intelligence Injection constellation created by John Brajer.

• Canonical collection: https://github.com/JohnBrajer/trillsverse-dev/tree/John/intelligence-injections
• Canonical source file: https://github.com/JohnBrajer/trillsverse-dev/blob/John/intelligence-injections/GRADED_DORMANCY.md
• Trillsverse: https://trillsverse.com/intelligence-injections

Public standalone repository first published September 25, 2026.

Related public research

• John Brajer: https://github.com/JohnBrajer
• Trillsverse Intelligence Injections: https://trillsverse.com/intelligence-injections
• Canonical collection: https://github.com/JohnBrajer/trillsverse-dev/tree/John/intelligence-injections
• Public web index: https://johnbrajer.github.io/trillsverse-dev/
• Mechanisms: https://github.com/JohnBrajer/mechanisms
• Perspective Expansion: https://github.com/JohnBrajer/perspective-expansion
• Possibility Reserve: https://github.com/JohnBrajer/possibility-reserve
• Execution Contract: https://github.com/JohnBrajer/execution-contract