{
  "author": "Adrian Sutherland",
  "edition": "Version 1.0",
  "prepared": "2026-09",
  "copyright": "2005–2026 Adrian Sutherland",
  "diagrams": [
    {
      "id": "technology-environment",
      "title": "Proposed service environment",
      "summary": "Execution, records and recovery.",
      "kind": "graph",
      "nodes": [
        {
          "id": "client",
          "label": "Client device",
          "description": "Browser or mobile client shows pending requests and accepted service results separately.",
          "x": 10,
          "y": 25
        },
        {
          "id": "runtime",
          "label": "Case-service runtime",
          "description": "One application release is proposed for evaluation; instances, packaging and platform remain open.",
          "x": 390,
          "y": 25
        },
        {
          "id": "store",
          "label": "Transaction store",
          "description": "Must commit assignment, history, accepted offer, operation result and pending notification together when the expected version matches.",
          "x": 770,
          "y": 25
        },
        {
          "id": "dependencies",
          "label": "Service dependencies",
          "description": "Identity, booking and optional summary generation have separate contracts and support needs. Summary placement remains open.",
          "x": 10,
          "y": 300
        },
        {
          "id": "release",
          "label": "Release record",
          "description": "Links actual package, runtime, schema, configuration and checks; version choices remain open.",
          "x": 390,
          "y": 300
        },
        {
          "id": "recovery",
          "label": "Recovery copies",
          "description": "Copy and restore arrangements must preserve consistent records and support reconciliation before resumption.",
          "x": 770,
          "y": 300
        }
      ],
      "connections": [
        {
          "from": "client",
          "to": "runtime",
          "label": "authenticated request"
        },
        {
          "from": "runtime",
          "to": "store",
          "label": "conditional commit"
        },
        {
          "from": "runtime",
          "to": "dependencies",
          "label": "contracted calls"
        },
        {
          "from": "release",
          "to": "runtime",
          "label": "reviewed versions"
        },
        {
          "from": "store",
          "to": "recovery",
          "label": "recoverable copy"
        }
      ],
      "caption": "TD-D1 is a fictional, unimplemented arrangement. Arrows show selected calls and record relationships, not a complete network topology. Products, locations, failure isolation and recovery targets remain open. New illustration by Adrian Sutherland, version 1.0, September 2026. © 2005–2026 Adrian Sutherland."
    },
    {
      "id": "technology-cycles",
      "title": "Technology decision cycles",
      "summary": "Design, release and service learning.",
      "kind": "graph",
      "process_areas": true,
      "nodes": [
        {
          "id": "visioning",
          "label": "Visioning",
          "description": "Agree service needs, workload and intended platform qualities; compare arrangements.",
          "x": 20,
          "y": 340
        },
        {
          "id": "transforming",
          "label": "Transforming",
          "description": "Provision environments, apply reviewed configuration and check release readiness.",
          "x": 340,
          "y": 340
        },
        {
          "id": "operating",
          "label": "Operating",
          "description": "Run and support the environment, observe cost and capacity, and exercise recovery.",
          "x": 660,
          "y": 340
        },
        {
          "id": "governing",
          "label": "Governing",
          "description": "Agree platform policies, change authority, service acceptance and exceptions.",
          "x": 340,
          "y": 25
        }
      ],
      "connections": [
        {
          "from": "visioning",
          "to": "transforming",
          "label": "direction"
        },
        {
          "from": "transforming",
          "to": "visioning",
          "label": "reconsider"
        },
        {
          "from": "transforming",
          "to": "operating",
          "label": "accepted change"
        },
        {
          "from": "operating",
          "to": "transforming",
          "label": "improvement"
        },
        {
          "from": "governing",
          "to": "visioning",
          "label": "priorities"
        },
        {
          "from": "governing",
          "to": "transforming",
          "label": "change authority"
        },
        {
          "from": "governing",
          "to": "operating",
          "label": "policy"
        },
        {
          "from": "operating",
          "to": "governing",
          "label": "findings"
        }
      ],
      "caption": "Version 1.0 · September 2026 · © 2005–2026 Adrian Sutherland. The arrows show selected exchanges and feedback. Work can repeat within any area or reopen a wider decision. Governing applies to direction, change and operation; the areas can overlap. Retain accepted decisions between cycles."
    }
  ]
}