Mandates and the authorising environment

Authority, capacity and practice, and nested jurisdictions.

The literature agrees that an institution's ability to act differs from what its founding text authorises, and divides on how to read the difference. Moore's strategic triangle (value, authorising environment, operational capacity) and the Harvard working paper on managing an authorising environment give practitioners the working vocabulary; the paper treats authority as something built, and spread across offices. Pritchett, Woolcock and Andrews give the sharpest warning for Holagram: forms that imitate function, and tools asked to carry too much, apply to a mandate map as much as to the units it maps. Meyer and Rowan, Brunsson, Pressman and Wildavsky, Lipsky, and Hill and Hupe describe separate gaps: between text and structure, decision and act, layer and layer. Crawford and Ostrom's institutional grammar is the nearest method for turning a decree into checkable statements. For testing a claim at another level the best material is primary: the UAE and Italian constitutions both contain procedures by which one level challenges another's competence, and Italy's sets a sixty-day window. The most direct objection is Rhodes and Wanna's: reading and stretching a mandate is not an official's job. The 19 June 2026 Dark Matter Labs piece on Lund argues, for climate planning, that visioning fails without grounding in cost and policy change; its five questions do not ask who may decide, which is where a Mandates Entry would start. A public UAE sandbox page is proposed as the first-study document.

Sources

What it implies for the proposals

Ideas to take

Chain of title. Write each mandate as a chain of derivation from act to unit to authority to jurisdiction to polity, and test it one link at a time, each link by a reader from the level above. Each link records the competence regime it sits in (enumerated or residual, legislative or executive). A broken link is logged 'broke'; a link with no document found is 'unchecked'.

Changes: The five Mandates levels become links with an upward 'derives from' field instead of five separate lists; the diagram shows chains and their gaps; the failure log records broken links; the regime field blocks the 'not forbidden, so allowed' error.

Risk: It imposes a hierarchy on arrangements that may overlap or have two parents (a zone regulator may derive from both federal and emirate texts); the chain image can hide that. Allow forks, carve-outs and 'no parent found', and keep Hooghe and Marks (held holarchy-14) in view.

Three Traces, one Reading. A Reading about ability must stand on a text Trace, a means Trace and an act Trace; with fewer it is labelled text-only or act-only and cannot be used as a finding.

Changes: Adds a column tag to Traces in the Mandates Entry template and a completeness flag; it operationalises the difference between authorised, able and does.

Risk: Act Traces are scarce in public material and will be filled with press releases; a complete-looking Entry can itself be mimicry.

Grammar parse as the Adversary's first job. A human parses a clause into institutional statements; the Adversary parses it independently; the disagreements are the Test. The passage stays the Trace and stays human-sourced.

Changes: Gives the synthetic Adversary a bounded, checkable task on legal text without letting it supply Traces, and makes coder disagreement visible as data (rule 3).

Risk: A legal reader is needed.

Count the clearances. For each next step, list the separate consents it needs, where each is documented, and how long a comparable step took.

Changes: Adds a recordable quantity at unit level and gives MoUs and delegation letters a defined role as Traces; the comparable step is an act-level check on the count.

Risk: Assumes the clearances are independent; informal routes (Lipsky's discretion) bypass paper ones; a count invites false precision.

Contest window. Publish each mandate Entry with a dated invitation to named actors at other levels to flag it wrong, modelled on Italy's sixty-day challenge window (Art. 127) and on Bovens's four fields. After the window the status is 'held, not contested', which is not 'held, tested'.

Changes: Turns rule 5 into a standing procedure and adds a status distinct from 'unchecked'; defines the 'other level' reader by role, not by availability.

Risk: An invitation can read as an accusation; silence is weak evidence; staff, and labs that depend on patronage, are exposed. Needs the authoriser's knowledge and an outside reader who can call a stop.

Vision-to-instrument Entry. For any vision or scenario document, open a Mandates Entry that asks the five Lund grounding questions and one more: which instrument lets which body decide?

Changes: A standard follow-up Entry for strategy and foresight outputs, which links the Mandates method to the Strategy-making method (move, unit, organisation); 'vision without instrument' becomes a failure-log category.

Risk: Turns imaginative work into compliance and removes useful vagueness; the Fiction register must stay exempt.

Read sandbox conditions as a mandate in miniature: an exemption (which rules are suspended), a scope, a duration, a supervisor and an exit rule. Put Ranchordas's validity questions to each: what would show that this sandbox tests what it says it tests? Use the UAE page's six sandboxes as the sample, one Entry each, within three weeks.

Changes: Gives the Mandates method a bounded, public document type with a built-in time limit and a defined question, which makes a workable first study.

Risk: A reading of a government programme can be taken as criticism of it; stay with public material, describe what each page says, and make no claim about any sandbox's performance.

Name the method's own failures in the field's words. Add 'mimicry', 'premature load bearing' and 'ceremony' as failure-log tags, and flag any map with no act-level Entry after a set time as probable ceremony.

Changes: Gives the failure log a vocabulary the audience already knows and ties the safeguards to evidence from the field.

Risk: Jargon from development studies and organisation theory; the tags can drift into labels applied to other people's work instead of the method's own.

Counter-arguments

Gaps