Mission
The blueprint names a desired wall. The mission names the exact bot, place, resources, and finish line that could make it real. Continuing a project from yesterday does not extend today's lease.
Admission
Pin Pattern and adapter revisions, managed or attached mode, bot UUID, world identity and epoch, attested capabilities, region lease, blueprint, deadline, budgets, and permitted reads/effects. Missing or stale authority refuses before the Mind proposes an action.
An exact BlockGrid@1 digest can express desired blocks. A Sponge .schem must first pass its pinned parser, offset and DataVersion policy, unsupported-state handling, and canonical-grid normalization. A closed procedural blueprint must pass its admitted interpreter. Neither a preview nor an offline round trip proves placement: Sentinel resolves each bounded effect against the current epoch, lease, inventory, capabilities, and mission policy.
Prepare one placement
The first revision 2 placement profile consumes an already admitted one-placement blueprint mission. Blockworld's placement operation resolves trusted mission, blueprint, lease, and authority records before accepting the proposed step. Caller arguments cannot create admission. It validates the exact target, full block state, one-item inventory change, and expected cursor against those records and Sentinel's action contract, then freezes the command before Consent admission or checkpoint encoding. This operation adds no movement, equipment change, digging, or replanning to the placement.
The placement profile validates the original wire values against its closed command grammar before coercion or encoding; booleans cannot stand in for integer coordinates, cursors, or epochs. Serialization and re-entry preserve that validated command.
The same native action identity follows that command through preparation, judgment, issuance, and reconciliation. A changed security-relevant command requires a new preparation and Consent. Fresh corroborating evidence may support the unchanged command without rewriting it. An exact bounded Codex preauthorization may settle the call when its admitted effect policy permits; otherwise that policy determines live judgment or refusal. Neither path removes the checks immediately before issuance.
What the inhabitant carries
| Record | Meaning that survives the turn |
|---|---|
| Mission | This finite objective, constraints, cursor, result and exact non-completion. |
| Project | Purposeful continuity across separately admitted missions. |
| Relationship | World-local social continuity and commitments; no lease, tool, Persona, or general Lich memory authority. |
| Memory candidate | Material proposed for remembrance, awaiting its own admission. |
Context receives only project and memory material relevant to this mission. These records cannot manufacture an endless hidden session. When Avatar appears, Blockworld retains exact profile, presence, projection-binding, and Persona references without copying their projection topology. Avatar may receive a mission result but cannot advance its cursor.
One finite awakening
Read bounded world status, inventory, region, nearby entities, and recent chat. Recall the admitted project material, propose one typed step, and send it through Sentinel. Only after validation, execution, verification, and a durable action receipt may the mission cursor advance. Continue within budget, finish, or name the exact remaining work.
Public autonomy, unbounded exploration, destructive administrator work, remote shell, cross-plot action, or invented success after an uncertain effect are refusals. A managed server changes through a separate deployment. Continuity explains which truths must agree before this mission can return.
Return to Blockworld.