Intake

What happens

Someone, another being or a transport or a scheduled wake, sends a SUMMON addressed at a being. That SUMMON is a Fact stamped on the sender's reel. A cross cutting projection picks it up and writes one row into the recipient's inbox.

The inbox is just a projection of facts that name a recipient. Nothing runs yet. The being has not been awoken. It might be busy with another moment, or asleep, or never have run before. The row sits in the inbox until the scheduler is ready for it.

What the row carries

The inbox entry holds everything the next beat will need: who's sending, what they want, what the active role should be, the priority, a correlation id so the eventual answer can find its way home, and a pointer to the originating fact.

Many entries can stack up at once. Priorities decide order. A human-pressed key beats a background background re-fold beats a scheduled tick.

Why intake is its own beat

Receiving is not acting. A being can be paged faster than it can answer. Intake exists so that the rate at which the world talks to a being is decoupled from the rate at which the being can think. The inbox is the buffer.