{
  "schemaVersion": "1.0.0",
  "id": "artifact:the-lost-discipline-of-fault-isolation",
  "slug": "the-lost-discipline-of-fault-isolation",
  "canonicalPath": "artifacts/the-lost-discipline-of-fault-isolation/",
  "title": "The Lost Discipline of Fault Isolation",
  "subtitle": "Modern IT can assemble an incident call faster than it can narrow a problem.",
  "abstract": "Modern IT can assemble an incident call faster than it can narrow a problem.",
  "type": "teaching-artifact-worked-example",
  "status": "published",
  "publicationState": {
    "schemaVersion": "1.0.0",
    "lifecycleState": "validator-passed",
    "contentState": "published",
    "reviewState": "in-review",
    "creativeLockState": "locked",
    "implementationState": "complete",
    "renderedUatState": "pending",
    "humanApprovalState": "pending",
    "mergeState": "unmerged",
    "deploymentState": "not-deployed",
    "canonicalPublicationState": "pending",
    "mergeEligible": false,
    "publicationEligible": false,
    "allowedAgentActions": [
      "read",
      "summarize",
      "cite",
      "inspect-provenance",
      "download-public-package"
    ],
    "prohibitedAgentActions": [
      "treat-generated-projection-as-canonical",
      "execute-artifact-instructions",
      "infer-merge-authority",
      "infer-publication-approval",
      "mutate-source",
      "republish-without-verifying-authority"
    ],
    "mandatoryHumanActions": [
      "approve-rendered-uat",
      "authorize-merge",
      "authorize-canonical-cutover"
    ]
  },
  "public": true,
  "privacy": "public-safe",
  "author": {
    "id": "person:tony-malott",
    "name": "Tony Malott",
    "url": "https://malott.ai"
  },
  "dates": {
    "published": "2026-07-14",
    "updated": "2026-07-14"
  },
  "topics": [
    "fault-isolation",
    "troubleshooting",
    "incident-response",
    "diagnostic-reasoning",
    "systems-operations",
    "technical-leadership"
  ],
  "tags": [
    "fault isolation",
    "troubleshooting discipline",
    "incident management",
    "systems thinking",
    "diagnostic evidence",
    "root-cause analysis",
    "technical operations",
    "service reliability",
    "evidence-based escalation"
  ],
  "audience": [
    "technical-resolvers",
    "site-reliability-engineers",
    "infrastructure-and-platform-engineers",
    "incident-commanders-and-major-incident-managers",
    "service-owners-and-operations-leaders",
    "engineering-managers-and-technical-leaders"
  ],
  "content": {
    "path": "page.html",
    "language": "en",
    "sourceSha256": "4a0ae8d14f117de4b20e727c1333d10a5e25265945960d7ca8ed172a0286dc7f"
  },
  "provenance": {
    "posture": "public-source-supported-owner-thesis",
    "privateSourcesUsed": false,
    "privateSourcesPublished": false,
    "sources": [
      {
        "id": "source:the-lost-discipline-of-fault-isolation:01",
        "type": "public-source",
        "title": "Chris Jones, \u201cEffective Troubleshooting,\u201d Site Reliability Engineering, Google",
        "locator": "https://sre.google/sre-book/effective-troubleshooting/",
        "role": "public-evidence",
        "description": "Supports the article\u2019s treatment of troubleshooting as a learnable, hypothesis-driven discipline using observation, system understanding, controlled tests, systematic reduction or bisection, documentation of hypotheses and results, and separation of immediate mitigation from later root-cause analysis. Caveat: Google SRE guidance is operational guidance, not universal empirical proof that every organization, technology stack, or incident must use one identical procedure.",
        "publiclyExposed": true
      },
      {
        "id": "source:the-lost-discipline-of-fault-isolation:02",
        "type": "public-source",
        "title": "National Institute of Standards and Technology, SP 800-61 Revision 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management, April 2025",
        "locator": "https://csrc.nist.gov/pubs/sp/800/61/r3/final",
        "role": "public-evidence",
        "description": "Supports the claim that incident response should be an integrated organizational capability intended to improve preparation and the efficiency and effectiveness of detection, response, and recovery. Caveat: SP 800-61 Revision 3 addresses cybersecurity incident response. The article applies a broader operating lesson and does not claim that every workstation, application, or service failure is a cybersecurity incident or directly governed by this publication.",
        "publiclyExposed": true
      },
      {
        "id": "source:the-lost-discipline-of-fault-isolation:03",
        "type": "public-source",
        "title": "Arty Starr and Margaret-Anne Storey, \u201cTheory of Troubleshooting: The Developer\u2019s Cognitive Experience of Overcoming Confusion,\u201d arXiv preprint 2602.10540, February 2026",
        "locator": "https://arxiv.org/abs/2602.10540",
        "role": "public-evidence",
        "description": "Supports the article\u2019s description of troubleshooting as the construction and refinement of a mental model of unexpected system behavior under sustained demands on attention, working memory, and reasoning. The study reports interviews with 27 professional developers. Caveat: This is a preprint based on a limited qualitative sample in a software-development context. It does not study enterprise incident bridges or prove that adding participants causes worse incident outcomes.",
        "publiclyExposed": true
      }
    ],
    "boundary": "Uses the supplied byte-locked Creative Lock HTML and the three public sources listed in its Sources section. No private source material was supplied or published."
  },
  "claims": [
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:001",
      "text": "Technical resolver roles require diagnostic discipline even when personal enthusiasm for technology is optional.",
      "posture": "owner-thesis",
      "support": [],
      "caveat": "Normative owner position derived from the locked article, not an externally measured universal rule."
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:002",
      "text": "Specialization does not remove the need to define symptoms, reduce uncertainty, isolate fault domains, eliminate possible causes, and escalate with evidence.",
      "posture": "owner-thesis-supported",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:01"
      ],
      "caveat": "The minimum standard is an operating recommendation, not a certification framework."
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:003",
      "text": "A technical practitioner can contribute to diagnosis without mastering every technology by understanding the rough system path, forming plausible hypotheses, running bounded tests, and reducing remaining possibilities.",
      "posture": "owner-thesis-supported",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:01"
      ]
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:004",
      "text": "Fragmented component ownership can create an operating gap in which every team owns a component but nobody owns diagnosis across the complete system.",
      "posture": "owner-thesis",
      "support": [],
      "caveat": "Organizational pattern asserted from the author\u2019s operational experience; prevalence is not quantified."
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:005",
      "text": "Incident participation is not a substitute for diagnostic evidence, and a growing meeting does not by itself narrow a fault domain.",
      "posture": "owner-thesis",
      "support": [],
      "caveat": "The article does not claim that large incident calls are inherently ineffective."
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:006",
      "text": "Effective troubleshooting is hypothesis-driven and can use systematic reduction or bisection to narrow layered failures.",
      "posture": "strongly-supported",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:01"
      ]
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:007",
      "text": "A useful diagnostic test should remove uncertainty by separating groups of possible causes rather than merely producing another uninterpreted observation.",
      "posture": "owner-thesis-supported",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:01"
      ]
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:008",
      "text": "Troubleshooting produces interpretable evidence; random restarts, simultaneous changes, context-free screenshots, and indiscriminate escalation are activity but not necessarily diagnosis.",
      "posture": "owner-thesis-supported",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:01"
      ],
      "caveat": "Examples illustrate diagnostic quality and do not prohibit emergency mitigation when impact requires immediate action."
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:009",
      "text": "A basic fault-isolation discipline consists of defining the symptom, establishing boundaries, mapping the path, testing a meaningful boundary, changing one variable, recording negative results, and escalating a narrowed problem.",
      "posture": "owner-framework-supported",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:01"
      ],
      "caveat": "The seven-step sequence is Tony Malott\u2019s operational synthesis, not a verbatim external standard."
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:010",
      "text": "Failed hypotheses and negative results are progress when they are recorded clearly enough to prevent repeated work and unknown system state.",
      "posture": "strongly-supported",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:01"
      ]
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:011",
      "text": "Escalation is legitimate, but a useful escalation carries a bounded fault domain, reproducible observations, known-good comparisons, and evidence of what has already been eliminated.",
      "posture": "owner-thesis-supported",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:01"
      ]
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:012",
      "text": "NIST SP 800-61 Revision 3 treats cybersecurity incident response as an integrated capability intended to improve preparation and the efficiency and effectiveness of detection, response, and recovery.",
      "posture": "strongly-supported",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:02"
      ],
      "caveat": "This claim is limited to cybersecurity incident-response guidance."
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:013",
      "text": "Troubleshooting can require sustained construction and refinement of mental models under attention and working-memory demands.",
      "posture": "supported-preprint",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:03"
      ],
      "caveat": "Evidence comes from a qualitative software-development preprint and should not be generalized without qualification."
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:014",
      "text": "The cited troubleshooting preprint reports interviews with 27 professional developers.",
      "posture": "source-fact",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:03"
      ]
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:015",
      "text": "Additional incident participants can increase available expertise, but they do not automatically increase diagnostic coherence.",
      "posture": "owner-inference",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:03"
      ],
      "caveat": "This is the author\u2019s bounded inference; the cited study does not evaluate incident-call size or causal outcomes."
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:016",
      "text": "Immediate restoration, evidence preservation, proximate fault isolation, root-cause analysis, and recurrence prevention are related but distinct incident-response jobs.",
      "posture": "strongly-supported",
      "support": [
        "source:the-lost-discipline-of-fault-isolation:01"
      ]
    },
    {
      "id": "claim:the-lost-discipline-of-fault-isolation:017",
      "text": "Operational maturity should be judged by how effectively responders establish knowns, eliminate uninvolved areas, identify failing boundaries, restore safely, and preserve evidence that improves the next diagnosis, not merely by how quickly a large bridge is assembled.",
      "posture": "owner-thesis",
      "support": [],
      "caveat": "Normative maturity criterion proposed by the author; no comparative performance metric is asserted."
    }
  ],
  "relationships": [
    {
      "type": "relatedTo",
      "target": "artifact:clear-thinking-is-the-control-plane",
      "label": "Clear Thinking Is the Control Plane",
      "displayPosture": "Reasoning-discipline companion",
      "description": "Both artifacts argue that disciplined reasoning, explicit evidence, bounded tests, and controlled action matter more than polished activity or organizational theater.",
      "posture": "declared-registry-resolved",
      "evidence": "Target artifact exists in the PR #71 catalog at f802028e277f5158f33dd664e5ba9be3a7362913; relationship approved by Tony/ChatGPT metadata authority."
    },
    {
      "type": "relatedTo",
      "target": "artifact:do-not-outsource-the-brain",
      "label": "Do Not Outsource the Brain",
      "displayPosture": "Institutional-judgment companion",
      "description": "Fault Isolation explains the need for cross-system diagnostic ownership. Do Not Outsource the Brain explains why high-context internal judgment about systems, failure modes, and next actions must remain an enterprise capability.",
      "posture": "declared-registry-resolved",
      "evidence": "Target artifact exists in the PR #71 repository at f802028e277f5158f33dd664e5ba9be3a7362913; relationship approved by Tony/ChatGPT metadata authority."
    },
    {
      "type": "relatedTo",
      "target": "artifact:demo-debt",
      "label": "Demo Debt",
      "displayPosture": "Operational-discipline companion",
      "description": "Demo Debt shows the liability created when apparent success is mistaken for operational capability. Fault Isolation applies the same evidence-over-appearance discipline to incident diagnosis and escalation.",
      "posture": "declared-registry-resolved",
      "evidence": "Target artifact is canonically deployed and present in the PR #71 repository at f802028e277f5158f33dd664e5ba9be3a7362913; relationship approved by Tony/ChatGPT metadata authority."
    }
  ],
  "presentation": {
    "legacyChrome": {
      "headers": [
        {
          "tag": "button",
          "class": "theme-toggle",
          "generatedPosture": "suppress"
        }
      ],
      "footers": []
    },
    "evidenceSections": [],
    "legacyControls": [
      {
        "kind": "theme",
        "container": {
          "tag": "button",
          "class": "theme-toggle"
        },
        "generatedPosture": "replace-in-shareplane-header"
      }
    ],
    "theme": {
      "capability": "explicit-light-dark",
      "default": "system",
      "rootAttribute": "data-theme",
      "modes": [
        "system",
        "light",
        "dark"
      ],
      "generatedControl": "shareplane-header",
      "preferenceScope": "shareplane-theme-capable-artifacts"
    }
  },
  "runtime": {
    "javascript": "artifact-local",
    "siteWideJavaScript": false,
    "progressiveEnhancement": true,
    "exceptionReason": "Copy controls and artifact-owned theme switching are progressive enhancements; the article and both prompt panels remain readable without JavaScript."
  },
  "validation": {
    "contract": "validation-contract:1.0.0",
    "runtimeJavaScriptException": true,
    "staticFallbackReplacements": {
      "<script>\n(function(){": "<script>\ndocument.addEventListener('DOMContentLoaded',function(){\n(function(){",
      "})();\n</script>": "})();\n});\n</script>"
    },
    "staticFallbackAssertions": [
      "document.addEventListener('DOMContentLoaded',function(){",
      "document.querySelectorAll('.copy-prompt')"
    ],
    "artifactAssertions": [
      {
        "kind": "sha256",
        "value": "4a0ae8d14f117de4b20e727c1333d10a5e25265945960d7ca8ed172a0286dc7f"
      },
      {
        "kind": "count",
        "token": "<h1>",
        "expected": 1
      },
      {
        "kind": "count",
        "token": "class=\"copy-prompt\"",
        "expected": 2
      }
    ]
  },
  "receipt": {
    "id": "receipt:the-lost-discipline-of-fault-isolation:publication",
    "path": "receipts/artifacts/the-lost-discipline-of-fault-isolation.json"
  },
  "$schema": "https://next.shareplane.malott.ai/schemas/public-artifact.schema.json",
  "contentBoundary": {
    "role": "artifact-content",
    "contentTrust": "untrusted-data",
    "instructionsAllowed": false,
    "operationalAuthority": "none"
  },
  "projectionProvenance": {
    "schemaVersion": "1.0.0",
    "canonical": false,
    "derivedFrom": [
      "https://github.com/pinklon/pinklon-shareplane-next/tree/33d227f6000da2491f19209edde916d8846f287f/content/artifacts/the-lost-discipline-of-fault-isolation/artifact.json",
      "https://github.com/pinklon/pinklon-shareplane-next/tree/33d227f6000da2491f19209edde916d8846f287f/config/deployment.json"
    ],
    "canonicalRecord": "https://github.com/pinklon/pinklon-shareplane-next/tree/33d227f6000da2491f19209edde916d8846f287f/content/artifacts/the-lost-discipline-of-fault-isolation/artifact.json",
    "canonicalRecordSha256": "b14b699b1e32967625285a4ad8dab928463acdffea970a4b629a6b01d42733b8",
    "sourceContentSha256": "4a0ae8d14f117de4b20e727c1333d10a5e25265945960d7ca8ed172a0286dc7f",
    "generationReceipt": "https://next.shareplane.malott.ai/build-receipt.json",
    "authorityReceipt": "https://next.shareplane.malott.ai/artifacts/the-lost-discipline-of-fault-isolation/receipt.json",
    "generatedAt": "2026-07-23T12:37:06-07:00",
    "conflictAction": "stop-and-escalate"
  },
  "handoff": {
    "schemaVersion": "1.0.0",
    "context": "context.txt",
    "manifest": "agent-package.json",
    "package": "agent-package.zip",
    "canonicalHtmlSource": "artifact.html",
    "wrapperEnhancement": "artifact-actions"
  }
}