How it works

Three things have to survive between runs: which live object each block owns, the values the platform cannot hold, and whether an effect already ran. Each lives somewhere the platform already has, and the state file becomes a projection of them.

Each page below is the short answer, with a per-platform table, and links to the full model for the reasoning.

• Identity Which live object a configuration block owns, held on the object itself.
• Values Where the few values the platform cannot hold are kept.
• Effects How something that leaves nothing behind to read back is made visible to a plan.
• The cache What the state file is once the record lives elsewhere, and what losing it costs.