Sentinel

In plain words: Blockworld: Sentinel (action guard)

Designed 2 min read 2 glossary terms 4 connected pages
The short version written for the Snayu team

The guard between the Assistant's proposed action and the game server: it checks each read or effect against the mission, and only issues a receipt when the server's own evidence confirms the result.

Why read it: Read this if you touch the game adapter, action validation or how placements are confirmed and reviewed.
  1. 1Five reads (status, inventory, region scan, nearby entities, chat) and five effects (move, look, say, equip, place block).
  2. 2In managed mode the server-side guard sees authoritative state; in attached mode local checks can only narrow requests.
  3. 3A lost acknowledgement leads to a status check or 'unverified effect', never a repeated placement.

Designed No authoritative game adapter or server deployment yet.

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

One proposed placement crosses from an inhabitant's intention into a server's world. Sentinel validates that crossing; the client adapter translates it. Structured server facts supply the evidence. Screenshots, signs, books, chat, and other world prose remain untrusted observations.

In managed mode, the server-side Sentinel can witness authoritative state and effects. In attached mode, admission is the intersection of local policy and explicitly offered server capabilities. Client observation cannot fill a missing server guarantee.

The narrow crossing

Revision 2 retains revision 1's five reads and five effects. The managed fixture exposes all ten; an attached profile may offer fewer.

Reads Effects
world_status move_to
inventory_summary look_at
scan_region say
nearby_entities equip
chat_since place_block

For each action, retain action/mission ids, bot UUID, server mode, PatternWorkflow/adapter revisions, lease, precondition digest, expected cursor, deadline, budgets, and postcondition. These facts let Sentinel check the proposed change against the mission that authorized it.

Managed Sentinel checks the plot, preconditions, cursor, and budgets on the authoritative server before issuance. Attached-mode local checks can only narrow the request; the external server decides whether to accept it. After execution, a matching response plus either an authoritative event or sufficient resulting-state proof permits one durable receipt.

Review the prepared crossing

Blockworld produces a typed placement review from the frozen command and trusted admission records. It binds its owner, profile revision, producer, admitted audience, and exact content to that command. The authorized reviewer can identify the mission and native action, server/world epoch and bot, plot and target, full block state, inventory change, relevant lease and limits, and the proof required for completion. Required facts that cannot be disclosed to the admitted audience make this profile unavailable. Generic ConsentApproval Step arguments remain censored; private checkpoint contents, arbitrary tool metadata, and model-written explanations cannot supply an alternative disclosure path.

Consent binds the exact preparation and review. Keep that binding, together with the existing tool/effect definition binding, through pause and resume. If it is missing or changed, refuse issuance.

The world may have changed while review was pending. Before calling the adapter, Blockworld therefore rechecks current Principal and effect authority, policy generation, mission, server and bot identity, world epoch, lease, cursor, target, inventory, deadline, and budgets. Managed Sentinel enforces the applicable predicates at the authoritative server boundary. Local attached-mode checks still cannot supply a guarantee the external server lacks.

Refusal remains server-side

Revision 2 retains revision 1's exclusion of destructive edits, fire, lava, explosives, PvP, trading, private chat, cross-plot inventory, account/plug-in changes, restoration, and public exposure. Attached mode also excludes server configuration, console, lifecycle, snapshot, plug-in, and mod effects. A mistaken or hostile adapter cannot make server authority disappear.

If acknowledgement is lost, query action_status where available and compare the Sentinel cursor with resulting world state. Insufficient attached-server proof narrows eligible effects or returns unverified_effect. It never licenses another placement to obtain a cleaner answer. Socket, pathing, animation, and unacknowledged buffers remain volatile; Continuity owns durable re-entry.

Return to Blockworld.