Mission
In plain words: Blockworld: Mission
How one Minecraft mission is admitted (exact bot, world, plot, blueprint, deadline and budgets) and how a single block placement is prepared, frozen and reviewed before it can run.
- 1Missing or stale authority (bot, world epoch, lease) refuses the mission before the model proposes anything.
- 2Blueprints must be a verified block grid or pass a pinned schematic parser; a preview never proves placement.
- 3A placement command is validated and frozen before approval, so review and execution refer to the same action.
Partial Placement admission is tested in an inactive workflow; no live server.
Words on this page, decoded click one for its card
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 PatternWorkflow 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 begins with an already admitted one-placement blueprint mission. Before accepting a proposed step, Blockworld resolves the trusted mission, blueprint, lease, and authority records; caller arguments cannot create that admission.
It then validates the exact target, full block state, one-item inventory change, and expected cursor against those records and Sentinel's action contract. Freeze the validated command before ConsentApproval Step admission or checkpoint encoding so later review and execution refer to the same placement. The operation includes no movement, equipment change, digging, or replanning.
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.
Carry the same native action identity through preparation, judgment, issuance, and reconciliation. Fresh corroborating evidence may support the unchanged command. A security-relevant change to the command itself instead requires new preparation and ConsentApproval Step.
The admitted effect policy decides how judgment happens. It may permit an exact bounded CodexSettings Folder preauthorization to settle the call; otherwise it requires live judgment or refusal. Either path still performs 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 LichThe Assistant 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.