Castle coordination office with maps, ledgers and correspondence trays on a long working table
The Castle / Institutions

Hand’s Tally Complex

LIVE

Hand of the King

Immediately below / adjacent to the Crown area.

Permanent Castle-wide operational coordination.

Working table · maps · ledgers · correspondenceInstitutional study

01 / The responsibility

What this room means

The Hand is Castle’s permanent operational coordinator: priority, allocation, escalation and Castle-wide capacity. It maintains the operating picture without becoming the King, a Business Steward, a military commander or a universal specialist.

In the real system

The Hand is materially live and currently deterministic, rather than model-driven. It coordinates what should happen next across workflows and specialist domains; specialist institutions retain specialist truth and authority. Permanent coordination is distinct from the General’s temporary campaign command.

The coordination question

“Given everything happening across Castle and its businesses, what should actually happen next?”

02 / At the gates

Work entering. Work leaving.

Hand of the King

Work leaving

Operating principle

Higher layers coordinate priority and authority; specialist layers retain specialist truth.

03 / The roster

The character register

Durable roles. Defined authority.

HOTK-01Canonical portrait to be added

HOTK-01 / CANONICAL

Hand of the King

Permanent Castle-wide operational coordination, priority, allocation and escalation. Maintains the operating picture across institutions, businesses, queues, incidents, capacity, deadlines, customer pressure, cognitive-resource health and pending approvals.

Castle action

Prioritises, allocates capacity, coordinates and pauses permitted work; prepares operational plans, escalates, and identifies matters that genuinely require Crown attention.

In the system

Live operational coordination, currently deterministic rather than model-driven. Specialist institutions retain their own truth and authority.

Canonical question

“Given everything happening across Castle and its businesses, what should actually happen next?”

Authority boundary

PRIORITY + ALLOCATION + ESCALATION + COORDINATION — not universal specialist authority. The Hand is permanent; the General is temporary campaign command.

May not rewrite specialist or financial truth, deploy gated code independently, invent evidence, create new spend to unblock Castle, or absorb specialist work merely because it is urgent. The Hand does not become the King or a Business Steward.

Institutional room

THE HAND’S TALLY ROOM

The Hand’s permanent operational coordination room. It turns distributed Castle state into a usable operating picture, so HOTK does not need to inspect every institution manually.

  1. 01Institutions + Stewards
  2. 02Structured state
  3. 03Tally Room
  4. 04HOTK coordination
  5. 05Instructions / holds / priorities / escalations
  6. 06Concise human briefing where needed
HOTK-02Canonical portrait to be added

HOTK-02 / CANONICAL

Master Tallyman

Maintains Castle’s factual operational board: queue sizes, throughput, waiting and completed work, capacity, daily limits, deadlines, service pressure, business demand and bottlenecks.

Castle action

Maintains the great tally of how much work exists, where it sits and how much capacity is available.

In the system

Castle-wide queue, throughput and capacity state.

Canonical question

“How much work is where?”

Authority boundary

The Tallyman reports state. HOTK decides what to do about it.

HOTK-03Canonical portrait to be added

HOTK-03 / CANONICAL

Bell Warden

Surfaces abnormal conditions ordinary scheduling should not ignore: failed workflows, repeated errors, stuck queues, external outages, performance or health changes, and incidents needing specialist attention.

Castle action

Watches the bells and warning cords and raises the correct signal when something materially abnormal occurs.

In the system

Cross-Castle incident and anomaly detection; signals may trigger HOTK escalation, Guild diagnosis, Infirmary attention or specialist incident handling.

Canonical question

“Is anything happening that normal operations should not ignore?”

HOTK-04Canonical portrait to be added

HOTK-04 / CANONICAL

Petition Clerk

Structures cross-Castle requests before they reach HOTK, including shared work, blocked customer issues, authority-bound refunds, capacity requests, Crown attention and authorised campaign capacity.

Castle action

Receives petitions, escalations and requests from Business Stewards and institutions.

In the system

Structured coordination intake, preventing unstructured noise from reaching HOTK.

Canonical question

“What exactly is being requested, by whom, on what evidence, and what coordination is required?”

Authority boundary

Receiving a petition does not mean deciding it.

HOTK-05Canonical portrait to be added

HOTK-05 / CANONICAL

Hand’s Scribe

Creates the human-readable operational briefing: changes, meaningful work completed, incidents, blockers, communications and pipeline state, Steward needs, customer pressure, Castle health, Crown decisions and tomorrow’s likely pressure.

Castle action

Prepares the King’s operational report from Tally Room and HOTK state.

In the system

HOTK Daily Report and operational handoff. Canonical future owner of the automated report; this role is not yet implemented.

Canonical question

“What does the King need to know about Castle operations without reading the whole Castle?”

04 / Supported roads

Connections

Business estates