nen-godspeed-loop

Godspeed Loop · 神速

Move quickly by deciding safe reactions before the event arrives. Keep conscious control at checkpoints and stop the instant the world no longer matches the compiled rules.

Qualify the loop

Use Godspeed only when every candidate action is:

• already authorized by the task;
• local or otherwise explicitly in scope;
• reversible or observational;
• deterministic enough to verify;
• bounded by a finite event set and stop condition.

Do not use it for ambiguous mutations, credentials, purchases, publication, external messages, destructive operations, production incidents with unknown state, or decisions requiring fresh consent.

Program Whirlwind

Compile rules before execution:

Priority	Stimulus	Guard	Response	Verification	Halt if

Make stimuli exact and observable. Define rule ordering and prevent two rules from firing on the same event unless their composition is proven safe.

Always include:

• unknown stimulus → halt and inspect;
• authority or scope change → halt;
• verification failure → halt;
• ambiguous state-changing result → do not retry automatically;
• budget or iteration cap reached → halt.

Run a canary

1. Execute one representative event.
2. Verify both the intended result and absence of the most likely adjacent damage.
3. Recompile the rule table if the canary reveals a new state.
4. Begin the loop only after the canary passes.

Move at speed

• Observe one event, apply one matching rule, and verify its postcondition.
• Keep a minimal execution count and exception log.
• Batch only homogeneous actions with a recoverable boundary.
• Pause at predefined conscious checkpoints to sample the wider system.
• Treat an out-of-band or unmodeled source, tool-version, instruction, or environment change as novelty. A source change produced by the matched rule may continue only when that exact change class and its verification were compiled into the table.

Discharge