{
  "edition": "1.0",
  "period": "2026-09",
  "objects": [
    {
      "id": "O1",
      "name": "Accepted resolution",
      "kind": "Outcome",
      "meaning": "The learner receives a timely resolution they accept, with one named owner until it is confirmed.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "P1",
      "name": "Learner agreement",
      "kind": "Principle",
      "meaning": "The learner must agree to the chosen alternative.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "R1",
      "name": "Continuous ownership",
      "kind": "Requirement",
      "meaning": "Preserve learner agreement and continuous case ownership through each handover.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "C1",
      "name": "Resolve a cancelled booking",
      "kind": "Capability",
      "meaning": "The ability to reach a confirmed resolution after a course cancellation.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "VS1",
      "name": "Cancellation resolution",
      "kind": "Value stream",
      "meaning": "Understand options, agree a resolution and receive confirmation.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "PR1",
      "name": "Resolution process",
      "kind": "Process",
      "meaning": "Open the case, assign an owner, contact the learner, agree an alternative and confirm.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "RO1",
      "name": "Case owner",
      "kind": "Role",
      "meaning": "The named person responsible for the case until confirmed resolution or effective accepted transfer.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "I1",
      "name": "Cancellation case record",
      "kind": "Information",
      "meaning": "The case, booking reference, current owner, options, agreement, state, next action and confirmation reference.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "A1",
      "name": "Responsibility and information",
      "kind": "Relationship",
      "meaning": "The case owner maintains the case record through the resolution process.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "D1",
      "name": "Process-only trial",
      "kind": "Decision",
      "meaning": "Propose a shared register and accepted handovers for provider-run courses.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "V1",
      "name": "Two-handover check",
      "kind": "Check",
      "meaning": "Follow a cancellation through two handovers and check owner, agreement and next action; unrun.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "L1",
      "name": "Partner confirmation gap",
      "kind": "Finding",
      "meaning": "A hypothetical partner alternative has no agreed confirmation owner; it triggers a scope decision.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Purpose",
        "Process",
        "Information"
      ]
    },
    {
      "id": "ID-DEF1",
      "name": "Learner agreement definition",
      "kind": "Definition",
      "meaning": "Acceptance of a specific alternative with actor, time and supporting interaction.",
      "source": "/information-data/worked-example",
      "aspects": [
        "Information"
      ]
    },
    {
      "id": "ID-D1",
      "name": "Shared case register",
      "kind": "Decision",
      "meaning": "Use a case register with linked assignment, agreement and correction history.",
      "source": "/information-data/worked-example",
      "aspects": [
        "Information"
      ]
    },
    {
      "id": "ID-V1",
      "name": "Case meaning checks",
      "kind": "Check",
      "meaning": "Check duplicate cases, agreement/confirmation consistency, ownership and corrections; unrun.",
      "source": "/information-data/worked-example",
      "aspects": [
        "Information"
      ]
    },
    {
      "id": "OP-D1",
      "name": "Accepted-transfer procedure",
      "kind": "Decision",
      "meaning": "Offer current context; receiver checks access, capacity and authority; record acceptance and effective transfer.",
      "source": "/organisation-process/worked-example",
      "aspects": [
        "Process",
        "Structure"
      ]
    },
    {
      "id": "OP-V1",
      "name": "Handover checks",
      "kind": "Check",
      "meaning": "Check waiting, absent owners, access, changed records and conflicting offers; unrun.",
      "source": "/organisation-process/worked-example",
      "aspects": [
        "Process",
        "Structure"
      ]
    },
    {
      "id": "SI-D1",
      "name": "Case-service option",
      "kind": "Decision",
      "meaning": "Possible later software increment replacing the shared register after migration and acceptance.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "SI-C01",
      "name": "Transfer acceptance contract",
      "kind": "Contract",
      "meaning": "Authority, version, atomic acceptance, retained result, repeat and failure rules for an offered transfer.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "SI-V1",
      "name": "Interface checks",
      "kind": "Check",
      "meaning": "Exercise lost responses, conflicts, repeats, restart, notifications and unknown booking outcomes; unrun.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "SW-D1",
      "name": "Case-service components",
      "kind": "Decision",
      "meaning": "Separate input, transfer handling, pure rules, conditional storage and notification work.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "SW-R1",
      "name": "Transfer rule",
      "kind": "Rule",
      "meaning": "Validate current facts and return a transfer plan or rejection without external effects.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "SW-C1",
      "name": "Summary workflow contract",
      "kind": "Contract",
      "meaning": "Prepare permitted context, generate and check a proposed summary, then obtain human review.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "SW-V1",
      "name": "Component checks",
      "kind": "Check",
      "meaning": "Check rules, atomic writes, concurrency, recovery and summary restrictions; unrun.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "C42",
      "name": "Example cancellation case",
      "kind": "Example instance",
      "meaning": "An illustrative instance of the cancellation case, not a class of case.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "H7",
      "name": "Example transfer offer",
      "kind": "Example instance",
      "meaning": "An offer naming the intended receiver of case C42 at expected version 12.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "X7",
      "name": "Acceptance operation",
      "kind": "Example instance",
      "meaning": "A unique acceptance request identity scoped to the caller and operation type; retained for lookup or an identical retry.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "SEC-R1",
      "name": "Excess disclosure",
      "kind": "Risk",
      "meaning": "Disclosure of unrelated or unnecessary learner information.",
      "source": "/security/worked-example",
      "aspects": [
        "Security"
      ]
    },
    {
      "id": "SEC-R2",
      "name": "Unauthorised acceptance",
      "kind": "Risk",
      "meaning": "An actor without current authority accepts ownership.",
      "source": "/security/worked-example",
      "aspects": [
        "Security"
      ]
    },
    {
      "id": "SEC-R3",
      "name": "Unsafe summary use",
      "kind": "Risk",
      "meaning": "Summary content discloses information or induces an unauthorised action.",
      "source": "/security/worked-example",
      "aspects": [
        "Security"
      ]
    },
    {
      "id": "SEC-R4",
      "name": "Altered records or traces",
      "kind": "Risk",
      "meaning": "An intruder changes records or removes information needed for investigation.",
      "source": "/security/worked-example",
      "aspects": [
        "Security"
      ]
    },
    {
      "id": "SEC-A1",
      "name": "Service authorisation",
      "kind": "Control",
      "meaning": "Check trusted identity and current policy where a read or action takes effect, including receipt lookup.",
      "source": "/security/worked-example",
      "aspects": [
        "Security"
      ]
    },
    {
      "id": "SEC-O1",
      "name": "Security operation record",
      "kind": "Record",
      "meaning": "Link actor, action, case, policy decision and result for protected investigation and recovery.",
      "source": "/security/worked-example",
      "aspects": [
        "Security"
      ]
    },
    {
      "id": "TD-D1",
      "name": "Runtime arrangement",
      "kind": "Decision",
      "meaning": "Evaluate one application release and a durable transactional store; products and instance counts remain open.",
      "source": "/technology-deployment/worked-example",
      "aspects": [
        "Technology"
      ]
    },
    {
      "id": "TD-R1",
      "name": "Recovery procedure",
      "kind": "Record",
      "meaning": "Distinguish restart from restoring older data; reconcile lost accepted work before resumption.",
      "source": "/technology-deployment/worked-example",
      "aspects": [
        "Technology"
      ]
    },
    {
      "id": "TD-C1",
      "name": "Release and compatibility",
      "kind": "Record",
      "meaning": "Control package, configuration, schema, clients and recovery behaviour through a release.",
      "source": "/technology-deployment/worked-example",
      "aspects": [
        "Technology"
      ]
    },
    {
      "id": "TD-V1",
      "name": "Environment checks",
      "kind": "Check",
      "meaning": "Test commit, restart, restoration, access dependency and representative load in the chosen configuration; unrun.",
      "source": "/technology-deployment/worked-example",
      "aspects": [
        "Technology"
      ]
    },
    {
      "id": "MG-D1",
      "name": "Shared direction",
      "kind": "Decision",
      "meaning": "Link learner resolution to the cancellation trial and a possible partner service.",
      "source": "/management/worked-example",
      "aspects": [
        "Management"
      ]
    },
    {
      "id": "MG-R1",
      "name": "Service roadmap",
      "kind": "Record",
      "meaning": "Sequence changes and prerequisites, including partner acceptance responsibilities.",
      "source": "/management/worked-example",
      "aspects": [
        "Management"
      ]
    },
    {
      "id": "MG-E1",
      "name": "Temporary exception",
      "kind": "Record",
      "meaning": "Identify the owner, scope, checks and review trigger for a temporary arrangement.",
      "source": "/management/worked-example",
      "aspects": [
        "Management"
      ]
    },
    {
      "id": "FN-D1",
      "name": "Option cost comparison",
      "kind": "Decision",
      "meaning": "Compare invented twelve-month costs on a stated common basis; preference remains open.",
      "source": "/finance/worked-example",
      "aspects": [
        "Finance"
      ]
    },
    {
      "id": "FN-C1",
      "name": "Funding commitment",
      "kind": "Record",
      "meaning": "Link expenditure and its authorisation to a funding owner and architecture decision.",
      "source": "/finance/worked-example",
      "aspects": [
        "Finance"
      ]
    },
    {
      "id": "MT-M1",
      "name": "Resolution measures",
      "kind": "Measure",
      "meaning": "Measure resolution time, ownership gaps, correction effort and architecture decision time separately.",
      "source": "/metrics/worked-example",
      "aspects": [
        "Metrics"
      ]
    },
    {
      "id": "MT-Q1",
      "name": "Recovery quality",
      "kind": "Measure",
      "meaning": "After restore, establish the accepted work lost and reconciled as well as technical recovery time.",
      "source": "/metrics/worked-example",
      "aspects": [
        "Metrics"
      ]
    },
    {
      "id": "CU-D1",
      "name": "Customer roles",
      "kind": "Decision",
      "meaning": "Distinguish learner choice, payer authority and representative permissions.",
      "source": "/customers/worked-example",
      "aspects": [
        "Customer"
      ]
    },
    {
      "id": "CU-F1",
      "name": "Channel research",
      "kind": "Check",
      "meaning": "Check whether assisted and online routes preserve the same learner choice; unrun.",
      "source": "/customers/worked-example",
      "aspects": [
        "Customer"
      ]
    },
    {
      "id": "SU-D1",
      "name": "Partner responsibilities",
      "kind": "Decision",
      "meaning": "Agree authority, confirmation, information, failure and exit before adding a partner service.",
      "source": "/suppliers/worked-example",
      "aspects": [
        "Supplier"
      ]
    },
    {
      "id": "SU-X1",
      "name": "Partner exit exercise",
      "kind": "Check",
      "meaning": "Transfer an open case and remove former access without losing necessary history; unrun.",
      "source": "/suppliers/worked-example",
      "aspects": [
        "Supplier"
      ]
    },
    {
      "id": "CH-D1",
      "name": "Cross-channel journey",
      "kind": "Decision",
      "meaning": "Retain the same case and meaning through messages and assisted calls.",
      "source": "/channels/worked-example",
      "aspects": [
        "Channel"
      ]
    },
    {
      "id": "CH-S1",
      "name": "Pending and accepted actions",
      "kind": "Requirement",
      "meaning": "A locally saved or offline proposal becomes accepted only after authoritative service acceptance.",
      "source": "/channels/worked-example",
      "aspects": [
        "Channel"
      ]
    },
    {
      "id": "SO-R1",
      "name": "Readiness record",
      "kind": "Record",
      "meaning": "Gather migration, staffing, observation and recovery checks before use.",
      "source": "/service-operations/worked-example",
      "aspects": [
        "Management"
      ]
    },
    {
      "id": "SO-A1",
      "name": "Service acceptance",
      "kind": "Record",
      "meaning": "Service-owner decision based on checks, risks, funding and fallback arrangements.",
      "source": "/service-operations/worked-example",
      "aspects": [
        "Management"
      ]
    },
    {
      "id": "SO-I1",
      "name": "Incident and restoration",
      "kind": "Record",
      "meaning": "Pause affected work, reconcile accepted actions, and obtain service-owner agreement before resuming.",
      "source": "/service-operations/worked-example",
      "aspects": [
        "Management"
      ]
    },
    {
      "id": "PROC-01",
      "name": "Process-only proposal",
      "kind": "Design state",
      "meaning": "The provider-run course trial using a shared register and an accepted-transfer procedure.",
      "source": "/blueprint",
      "aspects": [
        "Purpose"
      ]
    },
    {
      "id": "SOFT-01",
      "name": "Later software option",
      "kind": "Design state",
      "meaning": "The unimplemented case-service arrangement preserving the process and information rules.",
      "source": "/blueprint",
      "aspects": [
        "Purpose"
      ]
    },
    {
      "id": "PART-01",
      "name": "Partner extension",
      "kind": "Design state",
      "meaning": "A later scope option requiring agreement on supplier responsibilities and confirmation.",
      "source": "/blueprint",
      "aspects": [
        "Purpose"
      ]
    },
    {
      "id": "ROLE-LEARNER",
      "name": "Learner",
      "kind": "Role",
      "meaning": "Chooses whether an alternative meets their need.",
      "source": "/customers/worked-example",
      "aspects": [
        "Customer"
      ]
    },
    {
      "id": "ROLE-TEAMS",
      "name": "Booking and course teams",
      "kind": "Role",
      "meaning": "Record cancellation, identify alternatives and provide booking confirmation.",
      "source": "/business-architecture/worked-example",
      "aspects": [
        "Structure",
        "Process"
      ]
    },
    {
      "id": "ROLE-COORD",
      "name": "Duty coordinator",
      "kind": "Role",
      "meaning": "Arranges suitable cover and escalates unresolved gaps.",
      "source": "/organisation-process/worked-example",
      "aspects": [
        "Structure"
      ]
    },
    {
      "id": "ROLE-SERVICE",
      "name": "Service owner",
      "kind": "Role",
      "meaning": "Approves service meaning, readiness, exceptions and changes in scope.",
      "source": "/organisation-process/worked-example",
      "aspects": [
        "Management"
      ]
    },
    {
      "id": "ROLE-STEWARD",
      "name": "Data steward",
      "kind": "Role",
      "meaning": "Maintains shared definitions and coordinates recurring quality issues.",
      "source": "/organisation-process/worked-example",
      "aspects": [
        "Information"
      ]
    },
    {
      "id": "ROLE-FUNDING",
      "name": "Funding owner",
      "kind": "Role",
      "meaning": "Authorises expenditure and commitments.",
      "source": "/management/worked-example",
      "aspects": [
        "Finance"
      ]
    },
    {
      "id": "ROLE-PARTNER",
      "name": "Course partner",
      "kind": "Role",
      "meaning": "Would accept agreed booking and confirmation responsibilities.",
      "source": "/suppliers/worked-example",
      "aspects": [
        "Supplier"
      ]
    },
    {
      "id": "ROLE-RECEIVER",
      "name": "Receiving case owner",
      "kind": "Role",
      "meaning": "Checks current information, authority, access and capacity before accepting a transfer.",
      "source": "/organisation-process/worked-example",
      "aspects": [
        "Structure"
      ]
    },
    {
      "id": "SYS-CLIENT",
      "name": "Staff client",
      "kind": "Component",
      "meaning": "Presents case state and sends proposals; offline saving does not transfer ownership.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Channel"
      ]
    },
    {
      "id": "SYS-CASE",
      "name": "Case service",
      "kind": "Component",
      "meaning": "Owns authoritative case information and accepts permitted case changes.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "SYS-BOOKING",
      "name": "Booking service",
      "kind": "Component",
      "meaning": "Owns bookings and booking confirmation independently of case transfers.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems"
      ]
    },
    {
      "id": "SYS-IDENTITY",
      "name": "Identity service",
      "kind": "Component",
      "meaning": "Provides trusted identity information; service policy determines authority.",
      "source": "/technology-deployment/worked-example",
      "aspects": [
        "Systems",
        "Security"
      ]
    },
    {
      "id": "SYS-NOTIFY",
      "name": "Notification delivery",
      "kind": "Component",
      "meaning": "Delivers committed notifications and exposes failures; delivery may repeat.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems"
      ]
    },
    {
      "id": "SYS-REPORT",
      "name": "Reporting consumer",
      "kind": "Component",
      "meaning": "Maintains a derived view, detects version gaps and reconciles with the authoritative case.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Metrics"
      ]
    },
    {
      "id": "SYS-SUMMARY",
      "name": "Optional summary workflow",
      "kind": "Component",
      "meaning": "Returns a source-linked proposal for human review; cannot accept agreement or ownership.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Security"
      ]
    },
    {
      "id": "CMP-INPUT",
      "name": "Input adapter",
      "kind": "Component",
      "meaning": "Decodes requests and obtains authenticated context.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems"
      ]
    },
    {
      "id": "CMP-HANDLER",
      "name": "Transfer handler",
      "kind": "Component",
      "meaning": "Coordinates authority, retained-result lookup, rule evaluation and conditional save.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems"
      ]
    },
    {
      "id": "CMP-RULE",
      "name": "Transfer rule module",
      "kind": "Component",
      "meaning": "Returns a plan or rejection based on current facts; causes no external effects.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems"
      ]
    },
    {
      "id": "CMP-STORE",
      "name": "Transaction store",
      "kind": "Component",
      "meaning": "Commits all acceptance records together only against the expected version.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems",
        "Information"
      ]
    },
    {
      "id": "CMP-RELAY",
      "name": "Notification relay",
      "kind": "Component",
      "meaning": "Sends committed pending work and records delivery progress.",
      "source": "/systems/worked-example",
      "aspects": [
        "Systems"
      ]
    },
    {
      "id": "DATA-BOOKING",
      "name": "Cancelled booking",
      "kind": "Information object",
      "meaning": "The learner and cancelled course occurrence that a case concerns.",
      "source": "/information-data/worked-example",
      "aspects": [
        "Information"
      ]
    },
    {
      "id": "DATA-ASSIGN",
      "name": "Owner assignment",
      "kind": "Information object",
      "meaning": "One case assignment with its effective period; only one is current.",
      "source": "/information-data/worked-example",
      "aspects": [
        "Information"
      ]
    },
    {
      "id": "DATA-AGREEMENT",
      "name": "Learner agreement record",
      "kind": "Information object",
      "meaning": "One accepted alternative, actor, time and source reference; at most one current agreement.",
      "source": "/information-data/worked-example",
      "aspects": [
        "Information"
      ]
    },
    {
      "id": "DATA-CONFIRM",
      "name": "Booking confirmation",
      "kind": "Information object",
      "meaning": "Confirmation of the current agreement and resulting booking.",
      "source": "/information-data/worked-example",
      "aspects": [
        "Information"
      ]
    },
    {
      "id": "DATA-RECEIPT",
      "name": "Acceptance receipt",
      "kind": "Information object",
      "meaning": "The retained outcome of one operation; historical and distinct from the current owner.",
      "source": "/systems/worked-example",
      "aspects": [
        "Information"
      ]
    },
    {
      "id": "DATA-PENDING",
      "name": "Pending notification",
      "kind": "Information object",
      "meaning": "Work to deliver recorded atomically with the accepted transfer.",
      "source": "/systems/worked-example",
      "aspects": [
        "Information"
      ]
    },
    {
      "id": "TECH-APP",
      "name": "Application release",
      "kind": "Runtime responsibility",
      "meaning": "The evaluated packaging of the case-service components and notification worker.",
      "source": "/technology-deployment/worked-example",
      "aspects": [
        "Technology"
      ]
    },
    {
      "id": "TECH-STORE",
      "name": "Durable transactional store",
      "kind": "Runtime responsibility",
      "meaning": "Preserves accepted state, receipt and pending work across restart.",
      "source": "/technology-deployment/worked-example",
      "aspects": [
        "Technology"
      ]
    },
    {
      "id": "TECH-COPY",
      "name": "Recovery copy",
      "kind": "Runtime responsibility",
      "meaning": "A mutually consistent recovery set whose retention and acceptable loss need agreement.",
      "source": "/technology-deployment/worked-example",
      "aspects": [
        "Technology"
      ]
    },
    {
      "id": "BP-V01",
      "name": "Service overview",
      "kind": "Blueprint view",
      "meaning": "The learner agrees a replacement with the case owner. Booking and course teams supply cancellation, alternatives and confirmation. The owner maintains I1 (Cancellation case record), the shared case record. The duty coordinator arranges cover; the service owner decides unresolved exceptions. Ownership continues until confirmed resolution or an explicitly accepted transfer.",
      "source": "/blueprint/service-overview",
      "aspects": [
        "Purpose",
        "Customer",
        "Channel",
        "Process",
        "Structure",
        "Information",
        "Management"
      ]
    },
    {
      "id": "BP-V02",
      "name": "Accepted handover",
      "kind": "Blueprint view",
      "meaning": "A receiving member of staff requests acceptance through the staff client. The case service checks authority and current state, then commits assignment, offer, receipt and pending notification together. The response is lost. A repeat uses the same operation and inputs. Current permission is checked before the retained result is returned, without another assignment. Notifications follow the commit independently. Booking confirmation is separate.",
      "source": "/blueprint/accepted-handover",
      "aspects": [
        "Process",
        "Structure",
        "Information",
        "Security",
        "Systems"
      ]
    },
    {
      "id": "BP-V03",
      "name": "Work and responsibility",
      "kind": "Blueprint view",
      "meaning": "The case owner opens a case and identifies alternatives. The learner can accept or reject an alternative. A matching confirmation resolves the case. An unavailable alternative or authority gap is escalated while ownership and next action are retained. Handover changes the assignment only on explicit acceptance.",
      "source": "/blueprint/work-responsibility",
      "aspects": [
        "Process",
        "Structure",
        "Customer",
        "Channel",
        "Supplier"
      ]
    },
    {
      "id": "BP-V04",
      "name": "Information relationships",
      "kind": "Blueprint view",
      "meaning": "A cancelled booking may have historical cancellation cases, with at most one active case. Each active case has one current owner assignment. Agreement and confirmation histories retain corrections. A resolved case requires confirmation matching its current agreement.",
      "source": "/blueprint/information",
      "aspects": [
        "Information",
        "Process"
      ]
    },
    {
      "id": "BP-V05",
      "name": "Case lifecycle",
      "kind": "Blueprint view",
      "meaning": "Opening assigns an owner. Learner agreement permits awaiting confirmation. Matching confirmation permits resolution. Exceptions retain responsibility while escalated; the appropriate active state resumes after a decision. Corrections can invalidate an agreement or confirmation. Ownership transfer preserves the case state.",
      "source": "/blueprint/information",
      "aspects": [
        "Information",
        "Process",
        "Systems"
      ]
    },
    {
      "id": "BP-V06",
      "name": "Systems and rules",
      "kind": "Blueprint view",
      "meaning": "The staff client sends a request through the input adapter. The transfer handler checks authority and existing operation results. New operations use the pure transfer rule and a conditional transaction store. The notification relay sends committed pending work. Booking remains separately authoritative. Optional summary work has no authority to change ownership.",
      "source": "/blueprint/systems",
      "aspects": [
        "Systems",
        "Information",
        "Channel",
        "Security"
      ]
    },
    {
      "id": "BP-V07",
      "name": "Access and authority",
      "kind": "Blueprint view",
      "meaning": "The caller uses a staff client. The case service checks trusted identity, current policy and requested resource before performing the permitted operation. Protected case and receipt records remain behind this decision. A restricted summary workflow reads permitted context and returns a proposal for human review. Security records support authorised investigation.",
      "source": "/blueprint/security",
      "aspects": [
        "Security",
        "Systems",
        "Information"
      ]
    },
    {
      "id": "BP-V08",
      "name": "Runtime and recovery",
      "kind": "Blueprint view",
      "meaning": "The staff client calls the application. Its case handler uses a durable transactional store; the notification worker resumes committed work. Identity and booking have separate dependencies. Recovery copies can restore older records, so accepted business work may need reconciliation before writes resume. Runtime products, instance counts and service objectives remain open.",
      "source": "/blueprint/technology-operation",
      "aspects": [
        "Technology",
        "Systems",
        "Security",
        "Management"
      ]
    },
    {
      "id": "BP-R01",
      "name": "Blueprint record set",
      "kind": "Asset set",
      "meaning": "Cover, view records, linked objects, decisions and reusable outline.",
      "source": "/blueprint/records",
      "aspects": [
        "Management"
      ]
    }
  ],
  "author": "Adrian Sutherland",
  "copyright": "© 2005–2026 Adrian Sutherland"
}