Beat 4

Momentum

The being acts. Its role runs against the face it was given. New Facts accumulate in ΔF, not yet committed.

What happens

The being's role is whatever logic decides what to do next. For an LLM being, the role assembles a prompt from the fold, calls the model, parses the response into tool calls, and runs each one. For a scripted being, the role is a function that reads the fold and calls the verbs directly. For a human being, the role is a no op. The human acts out of band, through their own transport, and the system trusts the transport act that arrives.

Whatever the cognition, the outcome is the same shape: a stream of new Facts pushed onto ΔF. A move stamps a coord change. A summon stamps an inbox entry on someone else's reel. A creation stamps a new aggregate's first Fact. The role decides; the kernel emits.

Facts staged, not committed

During momentum, every Fact emitted joins ΔF, the moment's delta fact set. Nothing has hit Mongo yet. The being can act on many aggregates inside one moment, and the staging buffer holds them all together until the seal.

This is why a moment is atomic. If the role throws partway through, ΔF is discarded. If the seal runs, every Fact in ΔF commits together in one transaction. No half state, ever.

What momentum produces

A cognition result. Success means the role finished and ΔF is ready to seal. Failure means the role threw or returned a problem; the moment is released, ΔF is dropped, the Act row is never written. From the outside the moment never happened, even though the inbox entry that triggered it did.