Mind · Inference
ScopeFreeze
Lock requirements to prevent scope creep
Definition
Mechanism
Phase Transition Control. Defines a discrete point (T_freeze) after which the `AcceptSpec` and `Goal` of a Task become Immutable. Any new requirements discovered after T_freeze must be rejected or moved to a 'Backlog' object for future execution. It locks the Task requirements, forcing the agent to Satisfice within the remaining TimeboxThink rather than Decompose further.
Preconditions
- Initial requirements defined
- Task is active
Postconditions
- New requirements routed to Backlog
- Task marked as Frozen (Read-Only Requirements)
Invariants
- Immutability: After freeze, Task.AcceptSpec cannot be modified.
- Rejection: New SubTasks created after freeze must serve EXISTING goals only (no new features).
Risks
Failure modes
Feature Creep
Agent discovers 'nice to have' sub-tasks and attempts to execute them during the closing phase.
Perfectionism Spiral
Continuous refinement of the AcceptSpec prevents task completion.
Relationships
Builds on
References
Infrastructure
Non-compensatory acceptance contract; consumer Verify yields Solution or FrameError
Autonomous Goal-Directed Entity
Dividing complexity into manageable units
Optimizing for speed via threshold acceptance
Infrastructure
The atomic unit of intent
Temporal bounding of exploration
Infrastructure
State change
Nothing in this library builds on this pattern yet.
Reference
Parameters
exception_policyEnum, {Reject, Queue, CostAnalysis}- Default: Queue
freeze_triggerEnum, {Time, Progress, Manual}- Default: Manual