{
  "schema": "org-writing@v1",
  "slug": "consistency-is-not-fidelity",
  "kg": {
    "id": "org:writing:consistency-is-not-fidelity",
    "type": "brick",
    "graph": "/kg.json"
  },
  "title": "Consistency is not fidelity",
  "subtitle": "In an adaptive practice the deviation is the judgment, so perfect reproduction is its own kind of failure",
  "abstract": "Why absolute consistency is the wrong promise for an adaptive method, and what has to be stated before fidelity can be claimed at all. The canonical treatment of adaptive fidelity.",
  "kind": "brick",
  "topics": [
    "Tacit knowledge"
  ],
  "courseMemberships": [
    {
      "course": "org:courses:tacit",
      "topic": "Tacit knowledge",
      "wall": "org:walls:practice",
      "position": 4,
      "total": 6
    }
  ],
  "publishedAt": "2026-08-03T00:00:00.000Z",
  "updatedAt": "2026-08-11T00:00:00.000Z",
  "version": 2,
  "guidelinesVersion": 15,
  "brief": {
    "problem": {
      "text": "Machine delivery of a codified method is being sold on the promise of zero fidelity drift, and in a practice whose value lies in responding to the person present, the deviations are where the judgment was.",
      "claims": [
        "zero fidelity drift as the selling point"
      ]
    },
    "mechanism": {
      "text": "Fidelity in an adaptive method is agreement with what the method would have decided here, while consistency is agreement with what it decided last time, and only the second one can be maximized by a system that is not deciding.",
      "claims": [
        "Integrity defined functionally, rather than compositionally, is the key",
        "moderated by quality of delivery and participant responsiveness"
      ]
    },
    "move": {
      "text": "State the function a method is meant to perform before promising fidelity to it, then judge every deviation by whether it served the function, because a system graded on form will reproduce the form perfectly and lose the method.",
      "claims": []
    }
  },
  "sources": [
    {
      "repo": "mnstry-strategy",
      "path": "docs/20-business/30-competitive-analysis/defensibility-research.md"
    }
  ],
  "canonicalPath": "/writing/consistency-is-not-fidelity/",
  "body": "Our own competitive research proposes a pitch we are going to argue against, and we are recording it rather than quietly dropping it. Franchise your methodology without franchisees, it says, with zero-marginal-cost replication and zero fidelity drift, on the reasoning that human operators introduce cognitive bias, emotional fatigue, personal interpretation, and deviation, while a machine applies the method with absolute consistency across unlimited simultaneous deployments. The argument is coherent and it is aimed at a real wound, since fidelity variance is the franchise model's most expensive problem. We think the conclusion is inverted, and the discipline this corpus keeps is to leave the losing argument on the page with its reasoning attached, because that is the only way anyone later can check which of us was right.\n\nStart with the half of it that holds. Some human variance is decay rather than judgment. An implementer who is tired, who glosses over dissent because the meeting is running long, who has quietly swapped the method's harder move for one they find easier, is not exercising discrimination. They are drifting, and a licensor who wants that gone is right to want it gone. Any honest account of this has to keep the two apart.\n\nHere is where they separate. Fidelity in an adaptive method is agreement with what the method would have decided here, while consistency is agreement with what it decided last time, and only the second of those can be maximized by a system that is not deciding anything. The four dimensions where judgment lives are all conditional on the person present. Timing responds to the state of the room, interpretation responds to what this particular behavior means for this particular history, the branch you take depends on which of a dozen resistances you are looking at. A delivery that is identical every time has not achieved high fidelity on those dimensions. It has scored a perfect zero on all four and been graded on a different exam.\n\nThe evaluation literature worked this out for complex interventions two decades ago. Hawe, Shiell and Riley argued in the BMJ in 2004 that requiring an intervention to look the same everywhere may be part of why some community interventions produce weak effects, and proposed that what is standardized should be the steps in the change process and the key functions the components are meant to serve rather than the components themselves. Integrity defined functionally, rather than compositionally, is the key, in their phrase. Carroll and colleagues built the same understanding into measurement three years later, assessing fidelity as adherence to content and dose moderated by quality of delivery and participant responsiveness, which is a way of saying that the field already knows a protocol can be followed exactly and delivered badly.\n\nThe educators reached it from the other direction and further. The Reggio Emilia approach is described by its own alliance as not a method and not a pre-established curriculum, and no certifications in it are approved, precisely because the practice is supposed to be constructed around the children who are actually in the room. A version of it that could be shipped identically to a thousand classrooms would not be a scaled version of the approach. It would be a different thing wearing the name, which is the same failure label drift produces, arriving this time through the front door with a fidelity guarantee attached.\n\nNone of which means machine delivery cannot be faithful. It means fidelity is unclaimable until somebody states what the method is for, at the level of function rather than form, because that statement is the only thing a deviation can be judged against. Do that and the interesting question becomes answerable. Did this departure from the script serve the function the script exists to serve? A system that never departs cannot pass that test, and it cannot fail it either, which is the more damning result. Ask any method's owner to write down its functions and you will learn a great deal in the first ten minutes, most of it about how much of their method they have never had to say out loud, and every one of those sentences is a piece of the remainder coming into the light.",
  "apparatus": {
    "note": "The human-facing essay is deliberately practical; this apparatus carries the full references, evidence-graded claims, article-local concepts, and research context behind it. Canonical concept definitions come from the concept registry.",
    "references": [
      {
        "id": "org:references:consistency-is-not-fidelity:r01",
        "author": "MNSTRY strategy record",
        "work": "Defensibility research, internal competitive analysis",
        "year": 2026,
        "relevance": "The argument this brick inverts, recorded rather than dropped. It proposes franchising a methodology without franchisees, on zero-marginal-cost replication with zero fidelity drift, reasoning that human operators introduce bias, fatigue, personal interpretation and deviation while a machine applies the method with absolute consistency."
      },
      {
        "id": "org:references:consistency-is-not-fidelity:r02",
        "author": "Penelope Hawe, Alan Shiell, Therese Riley",
        "work": "Complex interventions, how out of control can a randomised controlled trial be? (BMJ 328:1561)",
        "year": 2004,
        "relevance": "The published statement of the inversion. Requiring an intervention to look the same everywhere may be part of why some community interventions show weak effects; what should be standardized are the steps in the change process and the key functions the components serve. Integrity defined functionally rather than compositionally."
      },
      {
        "id": "org:references:consistency-is-not-fidelity:r03",
        "author": "Christopher Carroll, Malcolm Patterson, Stephen Wood, Andrew Booth, Jo Rick, Shashi Balain",
        "work": "A conceptual framework for implementation fidelity (Implementation Science 2:40)",
        "year": 2007,
        "relevance": "Fidelity as adherence moderated by quality of delivery and participant responsiveness, which is the measurement community conceding that a protocol can be followed exactly and delivered badly."
      },
      {
        "id": "org:references:consistency-is-not-fidelity:r04",
        "author": "North American Reggio Emilia Alliance",
        "work": "General FAQs",
        "relevance": "The pedagogical case for the same conclusion. The approach is not a method or a pre-established curriculum and no certifications in it are approved, because the practice is constructed around the children actually present."
      }
    ],
    "claims": [
      {
        "id": "org:claims:consistency-is-not-fidelity:c01",
        "claim": "Our own competitive research proposes zero fidelity drift as the selling point of machine-delivered methodology, arguing that a machine applies a method with absolute consistency where human operators introduce bias, fatigue, personal interpretation and deviation.",
        "basis": "The internal defensibility document, read during authoring and quoted in substance. The existence of the argument is not in question; the brick disputes its conclusion and records the reasoning under the corpus's preserved-dissent discipline, which is why it is graded contested rather than directional.",
        "confidence": "contested",
        "sources": []
      },
      {
        "id": "org:claims:consistency-is-not-fidelity:c02",
        "claim": "Hawe, Shiell and Riley argued in 2004 that standardizing the form of a complex intervention across sites may explain weak effects, and that what should be standardized is the change process and the key functions the components serve. Integrity defined functionally, rather than compositionally, is the key.",
        "basis": "The BMJ paper itself, fetched and quoted during authoring.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:consistency-is-not-fidelity:c03",
        "claim": "Carroll and colleagues assess implementation fidelity as adherence to content and dose moderated by quality of delivery and participant responsiveness.",
        "basis": "Carroll et al., Implementation Science 2007, framework as published.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:consistency-is-not-fidelity:c04",
        "claim": "The North American Reggio Emilia Alliance states that the approach is not a method or a pre-established curriculum and that no certifications in it are approved.",
        "basis": "Fetched directly from the alliance's own FAQ during authoring.",
        "confidence": "verified",
        "sources": []
      }
    ],
    "concepts": [
      {
        "id": "org:concepts:adaptive-fidelity",
        "name": "Adaptive fidelity",
        "definition": "Fidelity to what a method would have decided in the situation actually present, as opposed to consistency, which is agreement with what the method did last time. The two come apart in any practice whose value depends on responding to the person in the room, because there the deviation is where the judgment lives, and a delivery that never deviates has maximized adherence to form while scoring nothing on the dimensions the method existed to serve. Adaptive fidelity is unclaimable until a method's functions are stated rather than only its components, since a stated function is the only thing a departure from the script can be judged against. Hawe, Shiell and Riley put it as integrity defined functionally rather than compositionally; the practical test is whether this departure served the function the script exists to serve, a test that a system incapable of departing can neither pass nor fail.",
        "provenance": "canonical"
      },
      {
        "id": "org:concepts:label-drift",
        "name": "Label drift",
        "definition": "The condition in which a method's vocabulary diffuses far ahead of its practice. Adopting the word costs a sentence and adopting the judgment costs an apprenticeship, so the label and the skill spread at speeds differing by orders of magnitude, and past some ratio the word stops predicting anything about what happens in the room. The informed and inspired suffixes are its usual carriers. Drift does not require bad faith; it requires only that the part which failed to transfer is the part nobody could have written down. The honest form of the same suffix declares its own uncertainty, as the Reggio Emilia alliance does in stating that Reggio-inspired is self-determined by the schools using it. The diagnostic is one question asked of any label, including our own safety vocabulary: what would have to be true for this word to be false here?",
        "provenance": "canonical"
      },
      {
        "id": "org:concepts:tacit-remainder",
        "name": "Tacit remainder",
        "definition": "What is left of a practice after the best possible writing-down. Codification carries everything a method can state about itself, the sequence, the vocabulary, the diagnostic categories, and leaves behind the situational judgment that decides when the stated thing applies, because that judgment was never in sentence form even in its originator's head. The remainder is not diffuse: it sits in four dimensions, decision trees (what to do when the person does not do the expected thing), micro-timing (when to probe and when to wait), interpretive frameworks (what a behavior means inside the method's worldview), and feedback loops (how a practitioner learns they are drifting). Polanyi's observation that we can know more than we can tell is its oldest statement. Its practical consequence is that codification does not transmit expertise at some percentage of fidelity; it clears the ground around the remainder so that whoever is forming the next practitioner can see exactly what still has to be learned by proximity.",
        "provenance": "canonical"
      }
    ],
    "researchContext": "The agent-facing body for \"Consistency is not fidelity\": the inverted source,\nthe published support for the inversion, and the record of what was claimed.\n\n## The recorded dissent\n\nThe source argument is ours. An internal competitive document proposes zero\nfidelity drift as the pitch for machine-delivered methodology, and this brick\nconcludes the opposite. Under the corpus's preserved-dissent discipline the\nlosing argument is kept on the page with its reasoning intact rather than\nquietly dropped, which is why the claim is graded contested and stated in the\nbrick's first paragraph rather than paraphrased into a straw position. If the\nevidence later favors the source, the record is intact enough to reverse the\nverdict without archaeology.\n\n## What the source gets right\n\nHuman delivery variance is not all judgment. Fatigue, bias, glossing over\ndissent, and quiet substitution of an easier move are decay, and a licensor\nwanting them eliminated is right. The brick concedes this explicitly, because\nan inversion that pretended the original had no case would be worth less than\nthe case it replaced.\n\n## Grading\n\nThree claims are verified from primary sources fetched during authoring. The\nfourth, the internal pitch, is contested by construction: the document says\nwhat it says, and we disagree with it.\n\n## De-identification\n\nThe internal source is competitive analysis containing named competitors,\nfunding figures, and positioning material. None of that ships. What is used is\nthe one argument the brick disputes, stated in our own words."
  },
  "contract": "https://mnstry.org/contracts/org/org-writing.v1.schema.json",
  "releaseHash": "a8dc088e1229b756943fcee00ef6390b7b20975c1f6087091ffaddc7713b10a0",
  "versions": [
    {
      "version": 2,
      "cutAt": "2026-08-11",
      "note": "Tacit remainder demotion release: reparented to The honest instrument and Tacit Knowledge course projection updated.",
      "visibility": "published",
      "path": "/writing/consistency-is-not-fidelity/",
      "contentHash": "sha256:eae355c4e80fef7e",
      "releaseHash": "a8dc088e1229b756943fcee00ef6390b7b20975c1f6087091ffaddc7713b10a0"
    },
    {
      "version": 1,
      "cutAt": "2026-08-03",
      "note": "Initial publication, tacit wave",
      "visibility": "published",
      "path": "/writing/consistency-is-not-fidelity/v/1/",
      "contentHash": "sha256:eae355c4e80fef7e"
    }
  ]
}