Governance innovation
Labs, experiments, portfolios, anticipatory governance and their critics.
Governance-innovation practice already holds most of the vocabulary Holagram needs, and its own documents state the limits. The OECD portfolio approach treats innovation as a spread of activities so that some can fail, with learning at portfolio level; UNDP's portfolio pages work with interconnected options, accommodate failures, and call the approach a good start in changing ways of thinking, not a management tool. Experimentalist governance in the EU already has peer review between units. Critics say labs are small, short-lived and dependent on patronage, and that pilots judged yes or no lose their lessons. What the sources do not show is anyone testing a reading of a document at another level or by another author, or keeping a log of readings that broke. The nearest cases are a lab failure report written for a funder, whose interviewee says it depended on trust, and an Estonian programme record that gives a failure share without reasons. For Mandates the useful anchors are Moore's authorising environment, the capability literature (isomorphic mimicry, premature load bearing) and the UAE's layered instruments: the constitution's free-zone clause shows that levels can be carved out, not only nested. The strongest objections are that portfolio logic aggregates by design, that documents-first reading misses political support, and that publishing failure is unsafe where stakes are high. Introduce the method through what practitioners already do, with two additions: a test by someone else at another level, and a log recording the level of each broken reading.
Sources
- OECD, Observatory of Public Sector Innovation (OPSI) (2022). Tackling Policy Challenges Through Public Sector Innovation: A Strategic Portfolio Approach. OECD Publishing, Parischeckedmust readopen accessdated 2022-11-23 (publication); validation workshops Dec 2020 to May 2021, as stated in the abstract
The practitioner baseline for 'portfolio'. A portfolio here is a managed, regularly reviewed spread of innovation activities across four facets (enhancement-oriented, adaptive, mission-oriented, anticipatory), built so that the failure of some does not sink the goals; the OPSI page says learning is expected at portfolio level. That is the opposite of Holagram's rule 2 (no level sums up another): portfolio logic aggregates by design, Holagram refuses to. The abstract says the findings were validated in facet workshops with close to a thousand experts; that is validation by consultation, not by an agent set to break the claims, and it marks the gap for rule 5. The facets give practitioners a vocabulary for asking what kind of claim an Entry makes, so a Strategy making Entry could carry a facet tag.
Read first: Chapter 1 (the Public Sector Innovation Facets model) and Chapter 2 (working with innovation portfolios), as named on the OPSI page.
- UNDP Strategic Innovation Unit ('Unstuck' initiative); no individual author shown (n.d.). Portfolios: How a multiplicity of approaches could help us get unstuck. Unstuck by UNDP (unstuck.systems)checkedopen accessdated Undated page; read 2026-10-14
UNDP's own description of the portfolio approach, with its limits stated. A portfolio is a set of interconnected options that adapts as learnings and failures come in; the page lists outcomes as not possible to define up front and uncertainty as communicated and accepted. It says that treating the approach as a managing tool is the wrong track, describes deep demonstrations as reality checks for portfolios, concentrated in a few places, and calls the approach “a good start in changing our ways of thinking”. That is where rule 5 and the failure log would add something. Its reframing questions (what has our attention and what does not; where we sit in relation to the problem; what is outside the scope of our perspective; whose interests the perspectives favour) can be reused as Reading prompts at authority level.
Read first: The whole page (short): the three steps and the cautions section.
- UNDP Innovation for Development, Europe and Central Asia (no individual author shown) (2024). How we're building Portfolio GPT. UNDP Innovation for Development, Europe and Central Asia (innovation.eurasia.undp.org)checkedopen accessdated 2024-07-25
Evidence that synthetic agents are already inside portfolio practice. The page describes a prototype for country offices, built on knowledge bases from UNDP handbooks, guides, manuals and learning materials, meant to support applying the portfolio approach. For the protocol this is a useful boundary case: this tool reads guidance, not project files, so it supplies no Traces; a tool that read project files and reported what they show would be supplying Traces, which the Holagram protocol forbids. It also shows why the hands note is needed in practice: a portfolio narrative drafted with such a tool should say which register the tool wrote.
Read first: The whole post (short); the passage on what the tool reads and the passage on limits.
- Geoff Mulgan and Giulio Quaggiotto (as credited on the Apolitical page) (2023). Creating useful policy steering rooms. Apoliticalcheckedopen accessdated 2023-11-08
The nearest published practice to a Holagram room. Four walls, one dimension each (patterns, proven, promising, possible); 'proven' covers evidence on what works and what fails. The rooms are temporary, set up for weeks or months while an issue is live. The authors argue for key indicators (KIs) with performance indicators (KPIs) as a subset, because KPIs serve accountability and not sensemaking, and that linear prose and dashboards fragment or mislead. This supports rule 7 (draw it so that others can contest it) and gives Mandates a way to separate indicators by role. Sharpening point: the room expects a synthetic judgement across the four walls; Holagram says no level sums up another, so the synthesis would be its own Entry with its own Test by someone outside the room. The article suggests machine learning for hidden patterns and language models for evidence maps; Holagram would confine them to Fiction and Test roles.
Read first: The whole essay (short); the passages on the four walls and on KIs versus KPIs.
- Javier Guillot, Jesper Christiansen and Jody Parra (2019). The challenge of innovation pilots. States of Changecheckedmust readopen accessdated 2019-03-06
A short essay from two pilots, on why pilots mislead. Pilots framed as demonstrations get a yes or no verdict, so lessons go unrecorded; teams then shelve the result or stage a story of value beyond the evidence (the authors call it innovation theatre). The authors read pilots labelled failures as weak authorising environments rather than weak ideas, and recommend running pilots as experiments; their nine lessons include ongoing authorisation, turning briefs into portfolios and linking small pilots to systems change. For Holagram, a third Test state ('unchecked') and a level tag (idea, unit, authorising environment) are what a binary verdict removes. For Mandates it states the central failure mode: mistaking the fate of a mandate for the fate of an idea.
Read first: The section on the core issue with how pilots are framed, then the lessons on demonstration versus experiment and on ongoing authorisation (headings seen on the page).
- Jenny M. Lewis (2020). The limits of policy labs: characteristics, opportunities and constraints. Policy Design and Practice 4(2), pp. 242-251 (online 22 Dec 2020)checkedopen access
A short paper on what policy labs are and cannot do. From its abstract: labs are typically small and short-lived, comparatively easy to shut down, defund or ignore, and survive on political patronage; they are limited in operational capacity, and their design methods clash with standard policy processes and bureaucratic structures; alone they cannot solve policy design problems. For Mandates it gives the base rate to start from: treat a lab's mandate as fragile, and test a reading that a unit 'can act' at authority level (is it funded, cited, used by an operational owner?). For the style: Holagram's Fiction and diagram registers will be filed as design practice by this audience, so the point about clashing methods applies to Holagram too.
Read first: Whole paper (about ten pages, pp. 242-251).
- Charles F. Sabel and Jonathan Zeitlin (2008). Learning from Difference: The New Architecture of Experimentalist Governance in the EU. European Law Journal 14(3), pp. 271-327checkedmust readopen access
Describes an institutional form of 'test by another agent at another level' that already exists. In the architecture the authors describe for EU rule-making, framework goals and measures are set jointly; lower-level units are free to pursue them but must report and take part in peer review that compares their results with those of units using other means; goals, measures and procedures are then revised periodically, including by newly involved participants. Practitioners will answer rule 5 with 'we already have peer review'. The reply has to be specific: this form reviews performance against agreed measures, not the readings made of documents, and the abstract mentions no log of reviews that went against a unit. It also offers a model for the outside-reader rule in Mandates (units review each other, not their own parent) and a rival account of levels to which the nested scheme must be compared.
Read first: The abstract states the four elements (joint framework goals, local discretion, reporting and peer review, periodic revision); the full article runs pp. 271-327.
- Lant Pritchett, Michael Woolcock and Matt Andrews (2013). Looking Like a State: Techniques of Persistent Failure in State Capability for Implementation. Journal of Development Studies 49(1), pp. 1-18 (online Dec 2012; earlier working paper 2012)checkedmust readopen access
Names the two failure modes the Mandates method has to watch. Isomorphic mimicry is the adoption of the outward forms of functional organisations elsewhere while function stays absent; premature load bearing is the routine placing of unrealistic expectations on fledgling systems, which undermines learning and legitimacy. A decree, charter, terms of reference or KPI sheet is such a form, so the Test for a Mandates Entry has to ask for the act, not the text. It is also a warning about the method itself: a unit can copy the four registers as a form and never let a Test break a Reading. The paper is about fragile states and development aid, so its transfer to wealthy federations and free zones is a claim to check, not assume.
Read first: The abstract names the two techniques (isomorphic mimicry; premature load bearing); the paper is 18 pages (pp. 1-18).
- David Dolowitz and David Marsh (2000). Learning from Abroad: The Role of Policy Transfer in Contemporary Policy-Making. Governance 13(1), pp. 5-23checked
The standard framework for what is transferred between jurisdictions (policies, administrative arrangements, institutions, ideas), why and how; the abstract says its last section addresses the relationship between transfer and policy failure. For Holagram it explains why pilot results travel badly: what moves is the document, not the conditions. An Entry about a copied model (a sandbox, a lab, a foresight unit) should pair a Trace from the origin with a Trace from the copy and say what did not travel (authority, budget, staff). Pair with the 2013 paper on isomorphic mimicry (govinnov-08) for the same failure in development settings.
- Jean Hartley and Laurence Knell (2021). Innovation, exnovation and intelligent failure. Public Money & Management 42(1), pp. 40-48 (online 1 Sept 2021)checkedmust readopen access
The nearest existing argument for a failure log. The abstract says failure is an under-explored part of innovation, that a deliberate intelligent-failure approach supports innovation, and that exnovation, the conscious pruning and ending of initiatives, belongs in the innovation cycle. Practitioners will accept this vocabulary, so Holagram has to say what its log adds: it records failures of interpretation (a reading that broke at a stated level, with its hands) and not only failures of delivery, and it is public and read by an outside reader. Exnovation suggests an extra Entry type for what was stopped. The abstract says nothing about who judges a failure or whether the record is published; that is the part Holagram would specify.
Read first: Whole article (pp. 40-48); the abstract frames it as aimed at managers, so expect a short, practical text.
- UN System Staff College (SDG Lab); interview, no named author or interviewee on the page (2019). Embracing failure (and success) as part of Innovation. UN System Staff College (unssc.org), news and insightscheckedopen accessdated 2019-12-05
A precedent for a lab writing a failure report for its funder. The interview describes the SDG Lab's Failure Report, written for the lab's main funder, a government: what went wrong, why the team thought it happened, and what it would change. The interviewee gives the condition: this depended on a high level of trust with stakeholders and none of the failures was critical; where failures are more sensitive, discussing them 'can be challenging'. That is the main counter-argument to a public failure log in governance settings, and the log needs a design answer (log readings, not people; delay publication; an outside reader with a stop right). The report itself was not found, so what it listed is unknown.
Read first: The whole interview (short).
- Rainer Kattel, Wolfgang Drechsler and Erkki Karo (2022). How to Make an Entrepreneurial State: Why Innovation Needs Bureaucracy. Yale University Presscheckeddated 2022-09-13 (publisher page)
A book-length argument, as the publisher describes it, that state organisations must be able to act as nimbly as start-ups while staying stable enough to pursue long-term policy and to survive political and financial resistance, which the authors call agile stability (examples from Europe, the USA and Asia). The title puts the weight on bureaucratic capacity. It supports the Mandates definition of a mandate as ability to act, which is capacity as well as authorisation, and it is the reading a sceptical audience will bring to Holagram: one more off-line practice beside the bureaucracy. So the Mandates method should take bureaucratic documents (statutes, terms of reference, budget lines) as its ground, not the lab's own products.
- Mark H. Moore (1995). Creating Public Value: Strategic Management in Government. Harvard University Presschecked
Source of the strategic triangle (a public value proposition, legitimacy and support from the authorising environment, and operational capacity) and of the term authorising environment that the pilots essay uses (govinnov-05). It gives the Mandates method a three-part test for 'can the next step be taken': value, authorisation, capacity. Threat: in this scheme authorisation is a political fact to be managed, not a text to be read, which limits a documents-first method. Decrees show formal authorisation; the support corner lives in practice and may not be public. The triangle is three dimensions at one level, whereas Holagram's levels are nested, so the method has to say how the two relate.
- Mariana Mazzucato and Rainer Kattel (2026). The market shaping state: capacities and capabilities for a new generation of mission-oriented policies. Policy Design and Practice (online first, 7 Oct 2026), introduction to a special issuecheckedopen accessdated 2026-10-07 (online-first date in Crossref and OpenAlex)
The newest statement of the mission-oriented approach, from the abstract: a three-layer framework separating structural capacities, organisational routines and dynamic capabilities, with public value emerging from their interaction and not from any single attribute, and an explicit concern with how governments can be stable and agile at once. It is the closest published rival to the Mandates levels: Holagram has to explain why act, unit, authority, jurisdiction and polity are not the same thing as these analytic layers. It also states the tension the Mandates audience lives with, and gives the audience's own terms (capacities, routines, capabilities) in which a Mandates Test could be reported.
Read first: The abstract; the paper introduces a special issue, so the other articles in that issue are the next reading.
- Piret Tõnurist and Angela Hanson (2020). Anticipatory innovation governance: Shaping the future through proactive policy making. OECD Working Papers on Public Governance, No. 44checkedopen accessdated 2020-12 (Crossref issued 2020-12-24)
Defines anticipatory innovation governance as the structures and mechanisms that allow and promote anticipatory innovation alongside other kinds of public-sector innovation; it draws on foresight, anticipatory governance and emerging-technology literature and outlines a framework for policy-making under uncertainty. For Strategy making it is the practitioner category into which Holagram's Fiction register will be filed (a scenario or foresight output), and it frames the question practitioners will ask: how is a scenario tested against a decision? That suggests the Strategy making Test: does a foresight output change a move at unit level, and who other than the foresight unit says so? A 2025 follow-up on guidelines exists (Tõnurist and Orlik, OECD, 22 May 2025; Crossref only).
- Centre for Strategic Futures, Strategy Group, Prime Minister's Office, Singapore (2026). Who We Are. csf.gov.sg (page last updated 29 Sept 2026)checkedopen accessdated Dates printed on the page: late 1980s, 1995, 2003, 2009, 1 July 2015; page updated 2026-09-29; read 2026-10-14
A primary document on one foresight unit's mandate and placement. By the page's account, futures planning began as an experiment in the Ministry of Defence in the late 1980s; a Scenario Planning Office was set up in the Prime Minister's Office in 1995, renamed Strategic Policy Office in 2003, and the Centre for Strategic Futures was created in 2009 as a futures think tank within it; on 1 July 2015 the Centre moved into the Prime Minister's Office Strategy Group, alongside a strategic planning team. This gives a ready lineage for a series of Mandates Entries: each renaming or move is a Trace at authority level, and the Test is what the unit could do before and after (publications, agency foresight teams, budget). The page also says several agencies have since set up their own foresight teams, a unit-level change that it does not tie to any document.
Read first: The whole page (short): the history list.
- Finnish Government / Prime Minister's Office (n.d.). Government Report on the Future. valtioneuvosto.fi (Finnish Government), foresight activities and work on the futurecheckedopen accessdated Operating-environment analysis 2024-11-22; Part I announced 2025-09-18; Part II press release listed as 2026-10-08 (not opened); page read 2026-10-14
This is good first-study material for Strategy making: the document is public, and the ground (ministry plans, budget lines) is public too. The page states no legal basis, and finding it is itself a Mandates task. Programme claims here are as the page states them.
- UAE Government portal (u.ae) (2024). Regulatory sandboxes in the UAE. u.ae, digital UAE, regulatory framework (page updated 30 Dec 2024)checkedopen accessdated Page updated 2024-12-30 (later changes not checked). As printed: RegLab launched January 2019; a federal law issued in 2018 lets the Cabinet grant temporary licences; electric cargo aircraft licence March 2023; ICT sandbox launched at the 2023 World Government Summit. Read 2026-10-14.
An official list of sandboxes that sit at different levels of the UAE structure. It names the federal Regulations Lab (RegLab), launched in January 2019 with the Dubai Future Foundation, under a 2018 federal law that lets the Cabinet grant temporary licences for testing future-technology uses (no law number given); the telecommunications and digital government regulator's ICT sandbox; the Dubai Financial Services Authority's Innovation Testing Licence (a two-stage process with four stated objectives); the Abu Dhabi Global Market's RegLab, which runs in cohorts; a Central Bank insurance sandbox; and a trade-technology sandbox with the World Economic Forum. It lists licences issued (electric cargo aircraft, March 2023; self-driving vehicles; a fractional bonds pilot) and the possible outcomes of a sandbox: full or tailored authorisation, regulatory change, or a cease-and-desist order. This is the sandbox-conditions document type for Mandates, in a setting of layered jurisdiction, and it supplies Tests of the form 'was a licence issued under this regime, by whom, when'.
Read first: The whole page; then look for the 2018 federal law and the Cabinet's licensing rules behind RegLab.
- United Arab Emirates (constitutional text; hosted by Constitute, Comparative Constitutions Project) (1971 (rev. 2009)). United Arab Emirates 1971 (rev. 2009) Constitution. Constitute Project (constituteproject.org)checkedopen accessdated Text as revised 2009 (per Constitute Project); read 2026-10-14
A polity-level Trace for the Mandates levels. Article 120 lists matters over which the federation has exclusive legislative and executive power; Article 121 lists matters of exclusive federal legislative power and includes, as its last item, the regulation of the financial free zones, how they are established and how far they are excluded from federal legislation; Article 122 leaves to the emirates whatever is not conferred exclusively on the federal authorities; Article 151 gives the constitution and valid federal laws priority over emirate rules. For Holagram the free-zone item is the test case for nested levels: a part whose exemption from the whole's rules is itself set by the whole. A strict holarchy will not fit it, so the Mandates levels need a rule for carve-outs. Read with the sandboxes page (govinnov-18): its Dubai Financial Services Authority and Abu Dhabi Global Market sandboxes operate in financial free zones (DIFC and ADGM; that status comes from secondary sources in search results, not from the portal page, and is worth confirming).
Read first: Articles 120 to 122 and 151 (the checked passages).
- OECD Observatory of Public Sector Innovation (case record about Accelerate Estonia) (2022). Accelerate Estonia. OECD OPSI Case Study Library (oecd-opsi.org)checkedopen accessdated 2022-10-19 (date published); programme start 2019
A public record of a government-backed portfolio. It describes a platform that finds ministries willing to change, defines unsolved problems with them, calls for innovators, selects a few, develops them with government access and a grant, runs pilots and makes follow-up investments; the portfolio grew to about twenty-five experiments. On failures it says: “Ca 20% have failed due to different reasons (team, timing, policy concerns).” It does not say what was learned from them, so it gives an aggregate share and no log. It also reports a change of government about two months in as the programme's first challenge. For Holagram this is where rule 5 and the failure log would add something in the Estonian setting: the programme's reading (ministries have problems their structures cannot solve) is judged by the programme's own team. Use as a Mandates series: the programme page (Trace), the change of government (Reading at authority level), what the unit did afterwards (Test).
Read first: The results and challenges sections.
What it implies for the proposals
- Levels and carve-outs. Keep the five Mandates levels (act, unit, authority, jurisdiction, polity) and add a rule for carve-outs: a part may be exempt from the whole's rules by the whole's own instrument. In the UAE the constitution leaves to federal regulation how far financial free zones sit outside federal legislation (Article 121), and the sandboxes on the government portal sit at federal, financial-free-zone and sectoral-authority level (the free-zone status of the Dubai and Abu Dhabi programmes comes from secondary sources and needs confirming) [govinnov-19, govinnov-18]. Every Entry names the level of its claim and, where a claim crosses levels, the instrument that creates the crossing. Keep levels distinct from the dimension schemes practitioners will cite: value, authorisation and capacity (Moore), or structural capacities, routines and dynamic capabilities (Mazzucato and Kattel) are dimensions at one level, not nested wholes [govinnov-13, govinnov-14].
- Documents to read (the invisible literature). Constitutional articles on competence; the statute or Cabinet decision behind a unit or sandbox; establishing decrees and terms of reference; licence announcements and register entries; programme pages and project lists; dated 'who we are' pages that record renamings and moves (Singapore's foresight unit: a Scenario Planning Office in 1995, a Strategy Group placement in 2015); periodic foresight reports (Finland); KPI sheets [govinnov-19, govinnov-18, govinnov-20, govinnov-16, govinnov-17].
- The ground is the next step. For Mandates the ground is whether someone takes the next step: a licence issued, a budget line, a named owner in the operating unit, a minute, a procurement. A Mandates Test asks for one such act in the public record [govinnov-08, govinnov-13]. For pilots the ground is whether an operational owner outside the lab carries the result forward; the pilots essay names the authorising environment as the usual weak point [govinnov-05]. Record the hands of each Trace: a programme's self-report (govinnov-20), a funder-facing report (govinnov-11) and an official page (govinnov-18) are different kinds of document and carry different interests.
- Testing at another level, or by another agent. Three patterns. (a) An act-level check of a unit-level reading: does a decision that came from the unit show up in an authority's act? (b) An authority-level check: does the parent's budget, regulation or strategy cite or fund the unit? (c) Peer-unit review: one unit tests another unit's Entries, never its own or its parent's, modelled on the report-and-peer-review step of experimentalist governance [govinnov-07].
- Pilots and portfolios are separate Entries. A pilot Entry carries a level tag (idea, unit, authorising environment) and one of three Test results, held, broke or unchecked, instead of a pass or fail verdict [govinnov-05]. A portfolio-level reading ('the portfolio is coherent', 'the lab is working') is its own Entry at authority level and is not supported by adding up project Entries; it needs a Test by someone outside the portfolio team [govinnov-01, govinnov-02]. Read KPI sheets as accountability documents and key indicators as sensemaking inputs, each labelled with the level it describes [govinnov-04]. Where a record gives only a failure share, as the Estonian programme record does (about a fifth, reasons given as team, timing or policy concerns), record the share as a Trace and ask for the individual cases [govinnov-20].
- Domain failure modes to write into the Mandates protocol. (a) Isomorphic mimicry, reading a charter as capacity, and premature load bearing, reading a KPI sheet as if the capacity existed [govinnov-08]. (b) Innovation theatre, where success is narrated beyond the evidence [govinnov-05]. (c) Mandate churn: labs are easy to close and depend on patronage [govinnov-06], and the Estonian record reports a change of government about two months into the programme [govinnov-20]. (d) Over-reading boilerplate: much public text is formulaic, and that is the ground on which a paranoid reading becomes self-confirming; care rules are that the outside reader is someone who has drafted such documents and that reading mode is switched off when meeting officials. (e) Adoption of the method as a form only, which the failure log must be able to show [govinnov-08].
- Failure log in governance settings. Log readings, not people or units, with level and hands. Allow a delay between entry and publication. Add an entry type for what was stopped (a lapsed mandate, a closed lab, a dropped indicator), since the argument for intelligent failure includes deliberate ending [govinnov-10]. Expect candour to depend on trust and on failures not being critical [govinnov-11]. Treat 'unchecked' as an honest published result, since public material often cannot settle a reading.
- Strategy making. Documents: a government's periodic foresight report, the foresight unit's own mandate page, and the anticipatory-innovation framing practitioners use [govinnov-17, govinnov-16, govinnov-15]. Levels as given (move, unit, organisation, field, world). A test at another level: take one scenario or driver from the report and look for a move (a ministry plan, a budget line) that cites or contradicts it, so the foresight unit's reading is tested at organisation level and not by the unit. Date every claim: Finland's report cycle and Singapore's unit history are public and checkable.
- First study for Mandates (three weeks, public material only). Option A, a sandbox regime: start from the UAE portal's list, find the number and text of the 2018 federal law and the Cabinet's rules for temporary licences, trace one licence from rule to announcement, then compare with one free-zone sandbox and with the constitutional allocation [govinnov-18, govinnov-19]. Option B, a programme: take the Estonian programme record and three of its experiments, and look for each in ministry documents [govinnov-20]. Either gives six to ten Entries, one outside reader and a first failure log; neither needs client material.
- What to say first to this audience. They already run portfolio sensemaking, peer review and failure reports [govinnov-01, govinnov-02, govinnov-07, govinnov-11]. Lead with what they do, then name the gap in their own documents: the UNDP page says failures are learned from but shows no format; the OECD report validated its framework in workshops with close to a thousand experts and its abstract names no test meant to break it; the AI tool is described with a first user test and no formal check of outputs; the Estonian programme record gives a failure share and no log [govinnov-02, govinnov-01, govinnov-03, govinnov-20]. Use plain terms (level, next step, who tested it) before 'holon'.
Ideas to take
Make the Mandates Trace a pair: the text and the act. Each Entry records the instrument (what it authorises, in which verbs), who holds the next step, and one observable act in the public record; the Test asks whether that act exists.
Changes: Defines the Trace for Mandates and ties the definition of a mandate as ability to act to something checkable; separates authorisation (the text) from capacity (the act).
Risk: The public record is thin, so many Entries will end unchecked; the pair can read like an audit of a named unit, which needs consent and the outside reader's stop right.
In Mandates studies, replace the single outside reader with a reciprocal peer unit: two units in different authorities each test the other's Entries.
Changes: Gives the outside-reader rule an institutional form practitioners already recognise (peer review) and puts the test at unit level, never with the author or the author's parent.
Risk: Reciprocity can become mutual comfort, and units in one jurisdiction share blind spots; needs rotation, a pre-agreed stop right and some outside check on the pair.
Offer a pilot Entry template: a level tag (idea, unit, authorising environment), three Test states, and a line on who owns the next step after the pilot.
Changes: Gives labs and offices a small, usable form for pilots, makes 'unchecked' respectable, and ties a failure to the level where it happened.
Risk: Funders still want pass or fail; the template may be seen as extra paperwork; level tags need worked examples to avoid sounding like jargon.
Add an exnovation Entry type: what was stopped, by which instrument, and what the unit could and could not do afterwards.
Changes: Extends the failure log from broken readings to deliberate endings (labs closed, mandates lapsed, indicators dropped), which this literature treats as part of innovation.
Risk: Closures are politically loaded and records are thin; needs a publication delay and care about naming.
Write one short layered-jurisdiction case in the condensed-novel format: the constitutional allocation, a sandbox rule and one licence, with the Fiction labelled and kept separate.
Changes: Gives the Mandates method a worked example for audiences with a federation, emirate, authority and free zone, and tests whether the five levels hold or need a carve-out rule.
Risk: Legal accuracy; any Reading about named institutions can be taken as a finding; needs a legal reader and strict labelling of Fiction.
Treat a portfolio-level reading as its own Entry: written at authority level, tested by someone outside the portfolio team, and not supported by adding up project Entries.
Changes: Applies rule 2 in the medium practitioners already use (portfolio sensemaking) and gives the steering room a rule for who tests its synthesis.
Risk: Clashes with portfolio logic, which aggregates by design; needs a worked example so that it does not look like a refusal to manage portfolios.
Pilot the Adversary role on an existing sensemaking output: give a synthetic agent a portfolio sensemaking summary and the cited documents, ask for the strongest Test, and log which Tests a human then ran.
Changes: A first concrete use of the two-role protocol with a practitioner setting; the log shows whether Adversary Tests ever break a Reading.
Risk: Agreeableness and flattening in language models (held critic-01, agents-07); data-handling limits inside agencies; the agent must not supply Traces.
Add a standing self-test to every Holagram study: has any Test broken any Reading? If none has, mark the study as possible isomorphic mimicry.
Changes: Makes the failure log accountable to its own function and not only its form.
Risk: Could push authors to stage breaks; the outside reader should judge whether a break is real.
Counter-arguments
- 'We already do this.' Portfolio sensemaking with feedback loops, peer review between units, evaluation and failure reports all exist [govinnov-01, govinnov-02, govinnov-07, govinnov-10, govinnov-11]. Holagram has to show a specific difference: the object (readings of documents, not performance), the level label on every claim, and the hands note.
- A portfolio is a hedge, not a set of claims. The OECD text expects some items to fail and manages the spread, and the UNDP page says portfolios have room for failures [govinnov-01, govinnov-02]; saying that no level sums up another can look like a refusal to do portfolio management. The reply has to separate managing a portfolio (adding up is legitimate) from reading it (the portfolio-level reading is a separate claim with its own test).
- Innovation needs stable bureaucracy, not one more off-line practice [govinnov-12, govinnov-06]. A three-week Entry protocol, outside readers and logs add load to small, short-lived units, and labs are already described as having design-led methods that clash with bureaucratic routine.
- Public failure logs are unsafe where stakes or sensitivity are high. The failure report interview says candour depended on trust and on non-critical failures [govinnov-11]; the pilots essay describes teams staging a story instead of recording lessons [govinnov-05]; intelligent failure is framed as a condition of culture [govinnov-10]. A log of broken readings about named institutions may be read as accusation, so it needs delay, level labels and the outside reader's stop right, and in some settings it may not be publishable.
- Nesting does not fit layered jurisdictions. The free-zone item in Article 121 (the federation decides how far a zone sits outside federal law) and sandboxes at federal, free-zone and sectoral-authority level are carve-outs and overlaps [govinnov-19, govinnov-18]. Public-value and capability schemes are dimensions, not levels [govinnov-13, govinnov-14], and the EU architecture described by Sabel and Zeitlin is iterative revision between units, not a stack [govinnov-07]. Expect the objection that 'holarchy' imports a tidy picture.
- Documents-first reading misses where ability to act lives. The authorising environment is political support that texts record only in part [govinnov-13], and capability sits in practice, where documents can mimic it [govinnov-08]. A method limited to public material will often return 'unchecked'.
- Public material is selective. Critics will say the method reads brochures.
- Practitioners already use language models in sensemaking [govinnov-03] and see machine learning as a way to find hidden patterns [govinnov-04]. A rule that synthetic agents never supply Traces removes the use they value most (extraction and pattern-finding), while the Alter and Adversary roles are untested against the flattening and agreeableness that held items critic-01 and agents-07 describe.
- Copying the form. Isomorphic mimicry [govinnov-08] suggests any method can be adopted as form without function. A lab that adopts the four registers and never lets a Test break a Reading would be an instance. Policy-transfer scholars would add that the method will travel as a document without the conditions (outside reader, care rules) that make it work [govinnov-09].
- Fiction about real institutions (inferred; no source states this). In politically sensitive settings, a Fiction in a world where a reading about a named authority is true can be read as an allegation however it is labelled, and governance audiences may file Fiction with design-led methods that sit uneasily with bureaucratic process [govinnov-06, govinnov-11].
Gaps
- No public failure log from a government innovation unit found. The nearest are a funder-facing lab report known only through an interview page with no link to it [govinnov-11], an Estonian programme record that gives a failure share without reasons [govinnov-20], and UNDP's statement that failures are learned from, without a format [govinnov-02].
- No evidence found that portfolio sensemaking improves decisions. UNDP's page calls its approach a good start in changing ways of thinking, which is a claim about thinking and not about decisions [govinnov-02]. The best candidate, the UNDP Innovation Facility 2.0 evaluation (completed 31 Oct 2024; record read on the UNDP evaluation resource centre), could not be fetched (HTTP parse error), so its findings are not used.
- Several UNDP items (a 2022 guidebook on portfolio approaches by an external author; 'Collective Intelligence in Action', which reads project documents with machine data, October 2022 per a search result; Medium posts on sensemaking and on systems monitoring) are known only from search-result summaries and are not listed.
- Legal instruments not located: the number and text of the 2018 UAE federal law behind RegLab; the instrument that established the Mohammed Bin Rashid Centre for Government Innovation (a launch report dated 8 Sept 2014 states its purpose, not a legal basis); the legal basis of Finland's Government Report on the Future; the DFSA's licence conditions (known from law-firm summaries only). Finding the instrument is the first Trace task in any Mandates study.
- Finland: no Sitra document read beyond its about page (a fund under Parliament with a statutory mission and a strategy updated in 2024, document dated 3 July 2024); no evaluation of the government's experimentation programme found.
- A practitioner book on the creative bureaucracy was not found on Open Library and is left out.
- Mission-oriented governance: the Mazzucato and Kattel paper of 7 Oct 2026 and Wanzenböck et al. (2020) are verified at abstract level only; no critic of missions writing from a documents or mandate angle was found.
- Estonian-, Finnish- and Arabic-language sources were not searched systematically. A 2015 Demos Helsinki report on experimentation in Finnish government ('Design for Government') and a 2016 report on funding experiments (KORVA) appeared in search results but were not read.