Approvals
Approvals pause a proposed action when the current policy requires the developer to accept or reject it.
Approve a bounded change
Inspect a single-file cooldown edit in Project Starfall, approve the requested action, then review the resulting checkpoint and session change.
When a request appears
The active specialist shows what it wants to do and waits for a decision. Approval details identify the proposed file, command, or engine action; review that scope rather than relying on the button label alone.
Review procedure
- Confirm the active project, session, and specialist.
- Inspect the proposed action and its target.
- Deny or refine a request whose purpose or scope is unclear.
- Allow the action only when it matches the intended task.
- Inspect the resulting changes, diff, and relevant evidence.
Auto-approve controls
EngineForge separates automatic approval into Read Files, Write Files, Run Commands, Game Engine, and Execute Code categories. Read access starts enabled; the consequential categories start disabled. Changing these controls affects whether a permitted action pauses—it does not give a specialist tools outside its role or make Plan writable.
Command boundaries
Command approval can also be narrowed with allowed and denied command rules. A denied rule still blocks the command, and an unknown or unmatched action can still require a decision.
Limitations
Approval confirms permission to attempt the action, not that its output is correct. Continue through review and verification.