{
  "schema": "cw-supplemental-advisory-1",
  "classification": "synthetic-only",
  "purpose": "supplemental-advisory-draft",
  "title": "Foundations context to operating conversations",
  "family": {
    "id": "family-fedciv-publication",
    "name": "Federal Environmental Data Office — fictional teaching case",
    "scope": "An entirely invented federal civilian office is considering agency-operated cloud foundations for a data-publication service that still depends on a retained on-site data service. No actual agency, client statement, provider entitlement or agreed schedule is represented."
  },
  "provenance": {
    "sourceCommit": "019bc90270368cd677c7afebbd61174add4ade46",
    "packSha256": "sha256:f3d2e216940cb264e5dba9a5357aa936cd247118c30ea820e5d3fe1eaa26f8c6",
    "manifestSha256": "sha256:40e193c83ada191ddd10953586fb9f3a6d0f1063928a9d649cae5f0e14a71bf4",
    "member": "studio/reporting-pack.json",
    "sourceSchema": "crp-1",
    "recordSchema": "cjs-0.32",
    "producedBy": {
      "engine": "cw-engine",
      "record": "cjs-0.32",
      "asOf": "2026-10-06",
      "clockRead": false
    },
    "source": {
      "name": "Federal Environmental Data Office — fictional teaching case",
      "schema": "cjs-0.32",
      "updated": "",
      "contentFingerprint": "cw-content-v1:7dc04a1b802ca988ccbc592d843fb15378ea28675b27983c2976fa73b108d66c",
      "fictional": true
    },
    "limitation": "Hashes verify byte pairing, not authenticity, currentness, release authority or data admission. Source commit is supplied by the caller, not recovered from the pack.",
    "reviewSha256": "sha256:06a6e258fa51fd378def83b8fc7127754d3b3d8558cfb19de56183c0493953d1",
    "mappingId": "fedciv-retained-publication",
    "contextHash": "sha256:ad0ce700c3175f8b45e772d5cd2a80019eb33fc33ed2030ee3b33bcfcb0754ce"
  },
  "coverage": {
    "availablePositions": 51,
    "selected": 8,
    "recordedDispositions": 7,
    "included": 3,
    "clarification": 3,
    "excluded": 1,
    "unreviewed": 1,
    "meaning": "Counts describe selected source positions carried into this draft. Unreviewed items have no consultant disposition. No count establishes readiness, evidence sufficiency, completion of Foundations or acceptance."
  },
  "services": [
    {
      "id": "publication",
      "name": "Publication service operating handoffs",
      "scope": "Proposed discussion across an agency-operated foundation option and retained data service.",
      "boundaryLimitation": "Conceptual service scope; no verified technical or authorization boundary.",
      "status": "proposed-planning-scope",
      "includedPositionIds": [
        "AR-012",
        "AR-014"
      ],
      "clarificationPositionIds": [
        "AR-010",
        "AR-015",
        "AR-048"
      ],
      "acceptance": {
        "acceptedOwner": null,
        "acceptedScope": false,
        "agreedDate": null,
        "serviceCommitment": null,
        "responseAuthority": null
      },
      "limitation": "A proposed service name is not a verified operating service or authorization boundary. No mapped context is not evidence that the service has no issues."
    },
    {
      "id": "capacity",
      "name": "Operations capacity planning",
      "scope": "Proposed examination of skills, support coverage and potential shared-service alternatives.",
      "boundaryLimitation": "No program entitlement, staffing acceptance or supplier commitment is established.",
      "status": "proposed-planning-scope",
      "includedPositionIds": [
        "AR-049"
      ],
      "clarificationPositionIds": [],
      "acceptance": {
        "acceptedOwner": null,
        "acceptedScope": false,
        "agreedDate": null,
        "serviceCommitment": null,
        "responseAuthority": null
      },
      "limitation": "A proposed service name is not a verified operating service or authorization boundary. No mapped context is not evidence that the service has no issues."
    }
  ],
  "observations": [
    {
      "positionId": "AR-010",
      "source": {
        "sourcePointer": "/readings/positions/9",
        "values": {
          "id": "AR-010",
          "title": "Logging, monitoring, backup, and baseline operations design",
          "domain": "Operations / observability",
          "dim": "Technology",
          "rationale": "Fictional account A says the enterprise monitor collects on-site and cloud alerts. Fictional account B says cloud alerts remain in the foundation console and no enterprise forwarding has been demonstrated. These accounts conflict; neither is treated as authoritative.",
          "evidenceRef": "[SRC-1] [SRC-2]",
          "evidenceStatus": "",
          "evidenceQuality": "",
          "confidence": "",
          "owner": "",
          "gap": "Collection coverage, service identifiers, retention, transport and transfer costs are unverified.",
          "recommendation": "Walk a synthetic alert through both proposed paths and compare receipts before choosing an aggregation location.",
          "confirmed": false,
          "confirmedOn": "",
          "updated": "",
          "disposition": ""
        },
        "missingFields": [],
        "interpretation": "Recorded Foundations values only. A status or confirmation does not establish operational acceptance, effectiveness or authorization."
      },
      "disposition": "clarify",
      "review": {
        "positionId": "AR-010",
        "disposition": "clarify",
        "serviceId": "publication",
        "rationale": "Collection coverage, service identifiers, retention, transport and transfer costs are unverified.",
        "interpretation": "Consultant interpretation: central collection cannot yet be assumed. Compare federated summaries and central forwarding against coverage, permitted transfers and cost; retain both accounts until a trace resolves the disagreement.",
        "proposedOwner": "Enterprise monitoring lead — proposed",
        "reviewer": "Fictional teaching reviewer",
        "reviewedAt": "2026-10-06T00:00:00.000Z",
        "scopeHash": "sha256:65a79054d49304f85dccd314fcd4dde48f3b0a3f52aec5d4f6c5852948d8dc58"
      },
      "proposedServiceId": "publication",
      "nextConversation": {
        "status": "proposed-for-consultant-review",
        "consultantInterpretation": "Consultant interpretation: central collection cannot yet be assumed. Compare federated summaries and central forwarding against coverage, permitted transfers and cost; retain both accounts until a trace resolves the disagreement.",
        "proposedRole": "Enterprise monitoring lead — proposed",
        "acceptedOwner": null,
        "agreedDate": null,
        "serviceCommitment": null,
        "responseAuthority": null,
        "questions": [
          "Does this observation apply to the proposed service scope?",
          "Who should receive the follow-up, and have they accepted it?",
          "What evidence and authority must be confirmed before any test or operational action?"
        ]
      }
    },
    {
      "positionId": "AR-012",
      "source": {
        "sourcePointer": "/readings/positions/11",
        "values": {
          "id": "AR-012",
          "title": "Incident, change, problem, and request procedures",
          "domain": "ITIL service practices",
          "dim": "Process",
          "rationale": "The fictional team describes scheduled on-site change windows. A proposed cloud release flow has no agreed link to the service change record or rollback evidence.",
          "evidenceRef": "[SRC-3]",
          "evidenceStatus": "",
          "evidenceQuality": "",
          "confidence": "",
          "owner": "",
          "gap": "The emergency-change path, rollback decision and incident-to-problem handoff have not been agreed.",
          "recommendation": "Rehearse one synthetic release and rollback with the service desk and foundation team.",
          "confirmed": false,
          "confirmedOn": "",
          "updated": "",
          "disposition": ""
        },
        "missingFields": [],
        "interpretation": "Recorded Foundations values only. A status or confirmation does not establish operational acceptance, effectiveness or authorization."
      },
      "disposition": "include",
      "review": {
        "positionId": "AR-012",
        "disposition": "include",
        "serviceId": "publication",
        "rationale": "The emergency-change path, rollback decision and incident-to-problem handoff have not been agreed.",
        "interpretation": "Consultant interpretation: a linked change record and observable rollback can make the two operating cadences discussable. The rehearsal is proposed; no change authority, deployment success or recovery capability has been established.",
        "proposedOwner": "Service change lead — proposed",
        "reviewer": "Fictional teaching reviewer",
        "reviewedAt": "2026-10-06T00:00:00.000Z",
        "scopeHash": "sha256:65a79054d49304f85dccd314fcd4dde48f3b0a3f52aec5d4f6c5852948d8dc58"
      },
      "proposedServiceId": "publication",
      "nextConversation": {
        "status": "proposed-for-consultant-review",
        "consultantInterpretation": "Consultant interpretation: a linked change record and observable rollback can make the two operating cadences discussable. The rehearsal is proposed; no change authority, deployment success or recovery capability has been established.",
        "proposedRole": "Service change lead — proposed",
        "acceptedOwner": null,
        "agreedDate": null,
        "serviceCommitment": null,
        "responseAuthority": null,
        "questions": [
          "Does this observation apply to the proposed service scope?",
          "Who should receive the follow-up, and have they accepted it?",
          "What evidence and authority must be confirmed before any test or operational action?"
        ]
      }
    },
    {
      "positionId": "AR-014",
      "source": {
        "sourcePointer": "/readings/positions/13",
        "values": {
          "id": "AR-014",
          "title": "Day-2 operations model and support tiering",
          "domain": "Operations / observability",
          "dim": "People",
          "rationale": "The fictional publication service depends on an on-site data service. The planning discussion names possible platform and data support roles but neither has accepted coverage or escalation responsibilities.",
          "evidenceRef": "[SRC-3] [SRC-4]",
          "evidenceStatus": "",
          "evidenceQuality": "",
          "confidence": "",
          "owner": "",
          "gap": "Support hours, absence cover and the retained-service recovery handoff are unknown.",
          "recommendation": "Confirm coverage and escalation for both sides of the dependency before proposing a service target.",
          "confirmed": false,
          "confirmedOn": "",
          "updated": "",
          "disposition": ""
        },
        "missingFields": [],
        "interpretation": "Recorded Foundations values only. A status or confirmation does not establish operational acceptance, effectiveness or authorization."
      },
      "disposition": "include",
      "review": {
        "positionId": "AR-014",
        "disposition": "include",
        "serviceId": "publication",
        "rationale": "Support hours, absence cover and the retained-service recovery handoff are unknown.",
        "interpretation": "Consultant interpretation: cloud-side health would not prove the publication service has recovered while its retained data dependency is unavailable. A joint verification step and named backup coverage need discussion before a service commitment.",
        "proposedOwner": "Publication service and retained-data leads — proposed",
        "reviewer": "Fictional teaching reviewer",
        "reviewedAt": "2026-10-06T00:00:00.000Z",
        "scopeHash": "sha256:65a79054d49304f85dccd314fcd4dde48f3b0a3f52aec5d4f6c5852948d8dc58"
      },
      "proposedServiceId": "publication",
      "nextConversation": {
        "status": "proposed-for-consultant-review",
        "consultantInterpretation": "Consultant interpretation: cloud-side health would not prove the publication service has recovered while its retained data dependency is unavailable. A joint verification step and named backup coverage need discussion before a service commitment.",
        "proposedRole": "Publication service and retained-data leads — proposed",
        "acceptedOwner": null,
        "agreedDate": null,
        "serviceCommitment": null,
        "responseAuthority": null,
        "questions": [
          "Does this observation apply to the proposed service scope?",
          "Who should receive the follow-up, and have they accepted it?",
          "What evidence and authority must be confirmed before any test or operational action?"
        ]
      }
    },
    {
      "positionId": "AR-015",
      "source": {
        "sourcePointer": "/readings/positions/14",
        "values": {
          "id": "AR-015",
          "title": "Integrated operations toolchain, systems of record, operational metrics, review cadence, and service reporting",
          "domain": "DevSecOps / IaC / CaC",
          "dim": "Process",
          "rationale": "The fictional planning notes propose a service-management record and a foundation monitoring console, but do not identify the authoritative service inventory or demonstrate event-to-ticket correlation.",
          "evidenceRef": "[SRC-1] [SRC-2] [SRC-3]",
          "evidenceStatus": "",
          "evidenceQuality": "",
          "confidence": "",
          "owner": "",
          "gap": "Service identity mapping, deduplication and the source of record are unresolved.",
          "recommendation": "Trace one service identifier across telemetry, configuration and the service record using synthetic data.",
          "confirmed": false,
          "confirmedOn": "",
          "updated": "",
          "disposition": ""
        },
        "missingFields": [],
        "interpretation": "Recorded Foundations values only. A status or confirmation does not establish operational acceptance, effectiveness or authorization."
      },
      "disposition": "clarify",
      "review": {
        "positionId": "AR-015",
        "disposition": "clarify",
        "serviceId": "publication",
        "rationale": "Service identity mapping, deduplication and the source of record are unresolved.",
        "interpretation": "Consultant interpretation: do not select an AIOps correlation layer simply because alerts can create tickets. First reconcile service identity and timestamps, then evaluate a read-only association against a rules baseline; association is not root cause.",
        "proposedOwner": null,
        "reviewer": "Fictional teaching reviewer",
        "reviewedAt": "2026-10-06T00:00:00.000Z",
        "scopeHash": "sha256:65a79054d49304f85dccd314fcd4dde48f3b0a3f52aec5d4f6c5852948d8dc58"
      },
      "proposedServiceId": "publication",
      "nextConversation": {
        "status": "proposed-for-consultant-review",
        "consultantInterpretation": "Consultant interpretation: do not select an AIOps correlation layer simply because alerts can create tickets. First reconcile service identity and timestamps, then evaluate a read-only association against a rules baseline; association is not root cause.",
        "proposedRole": null,
        "acceptedOwner": null,
        "agreedDate": null,
        "serviceCommitment": null,
        "responseAuthority": null,
        "questions": [
          "Does this observation apply to the proposed service scope?",
          "Who should receive the follow-up, and have they accepted it?",
          "What evidence and authority must be confirmed before any test or operational action?"
        ]
      }
    },
    {
      "positionId": "AR-032",
      "source": {
        "sourcePointer": "/readings/positions/31",
        "values": {
          "id": "AR-032",
          "title": "Cost management, showback, or chargeback model",
          "domain": "FinOps / service catalog",
          "dim": "Process",
          "rationale": "The fictional planning discussion asks who would pay for transferring and retaining telemetry. No usage sample, allocation basis or rates are recorded.",
          "evidenceRef": "[SRC-4]",
          "evidenceStatus": "",
          "evidenceQuality": "",
          "confidence": "",
          "owner": "",
          "gap": "Shared-cost ownership and bill-to-usage reconciliation are missing.",
          "recommendation": "Request a bounded synthetic usage example and an allocation rule before estimating collection alternatives.",
          "confirmed": false,
          "confirmedOn": "",
          "updated": "",
          "disposition": ""
        },
        "missingFields": [],
        "interpretation": "Recorded Foundations values only. A status or confirmation does not establish operational acceptance, effectiveness or authorization."
      },
      "disposition": "exclude",
      "review": {
        "positionId": "AR-032",
        "disposition": "exclude",
        "serviceId": null,
        "rationale": "Shared-cost ownership and bill-to-usage reconciliation are missing.",
        "interpretation": "Teaching scope choice: a full showback model is outside this narrow handoff rehearsal. Collection-cost uncertainty still constrains the architecture decision and is not resolved by excluding the workstream.",
        "proposedOwner": null,
        "reviewer": "Fictional teaching reviewer",
        "reviewedAt": "2026-10-06T00:00:00.000Z",
        "scopeHash": "sha256:65a79054d49304f85dccd314fcd4dde48f3b0a3f52aec5d4f6c5852948d8dc58"
      },
      "proposedServiceId": null,
      "nextConversation": null
    },
    {
      "positionId": "AR-047",
      "source": {
        "sourcePointer": "/readings/positions/46",
        "values": {
          "id": "AR-047",
          "title": "Infrastructure-as-Code and configuration-as-code maturity",
          "domain": "DevSecOps / IaC / CaC",
          "dim": "Technology",
          "rationale": "An agency-operated foundation is a fictional option under discussion. No reproducible configuration, release logs or rollback results have been supplied.",
          "evidenceRef": "[SRC-2]",
          "evidenceStatus": "",
          "evidenceQuality": "",
          "confidence": "",
          "owner": "",
          "gap": "Implementation and verification evidence is absent.",
          "recommendation": "Ask for an approved synthetic pipeline trace before discussing automation readiness.",
          "confirmed": false,
          "confirmedOn": "",
          "updated": "",
          "disposition": ""
        },
        "missingFields": [],
        "interpretation": "Recorded Foundations values only. A status or confirmation does not establish operational acceptance, effectiveness or authorization."
      },
      "disposition": "unreviewed",
      "review": null,
      "proposedServiceId": null,
      "nextConversation": null
    },
    {
      "positionId": "AR-048",
      "source": {
        "sourcePointer": "/readings/positions/47",
        "values": {
          "id": "AR-048",
          "title": "Service-level objectives and observability maturity (SLOs, golden signals, error budgets)",
          "domain": "Operations / observability",
          "dim": "Process",
          "rationale": "A fictional participant describes a successful console health check; no end-to-end publication check or accepted service objective accompanies it.",
          "evidenceRef": "[SRC-3]",
          "evidenceStatus": "",
          "evidenceQuality": "",
          "confidence": "",
          "owner": "",
          "gap": "Service outcome, measurement point and accepted objective remain undefined.",
          "recommendation": "Define a proposed user-visible check and identify who can confirm it represents restored service.",
          "confirmed": false,
          "confirmedOn": "",
          "updated": "",
          "disposition": ""
        },
        "missingFields": [],
        "interpretation": "Recorded Foundations values only. A status or confirmation does not establish operational acceptance, effectiveness or authorization."
      },
      "disposition": "clarify",
      "review": {
        "positionId": "AR-048",
        "disposition": "clarify",
        "serviceId": "publication",
        "rationale": "Service outcome, measurement point and accepted objective remain undefined.",
        "interpretation": "Consultant interpretation: retain the console check as a limited signal. Ask what the user can successfully do, which dependency must also work and who accepts the result; do not infer an SLO or restoration from a green console.",
        "proposedOwner": "Publication service lead — proposed",
        "reviewer": "Fictional teaching reviewer",
        "reviewedAt": "2026-10-06T00:00:00.000Z",
        "scopeHash": "sha256:65a79054d49304f85dccd314fcd4dde48f3b0a3f52aec5d4f6c5852948d8dc58"
      },
      "proposedServiceId": "publication",
      "nextConversation": {
        "status": "proposed-for-consultant-review",
        "consultantInterpretation": "Consultant interpretation: retain the console check as a limited signal. Ask what the user can successfully do, which dependency must also work and who accepts the result; do not infer an SLO or restoration from a green console.",
        "proposedRole": "Publication service lead — proposed",
        "acceptedOwner": null,
        "agreedDate": null,
        "serviceCommitment": null,
        "responseAuthority": null,
        "questions": [
          "Does this observation apply to the proposed service scope?",
          "Who should receive the follow-up, and have they accepted it?",
          "What evidence and authority must be confirmed before any test or operational action?"
        ]
      }
    },
    {
      "positionId": "AR-049",
      "source": {
        "sourcePointer": "/readings/positions/48",
        "values": {
          "id": "AR-049",
          "title": "Cloud workforce skills inventory and gap assessment",
          "domain": "Governance & mission ownership",
          "dim": "People",
          "rationale": "The fictional discussion describes a small operations team and interest in automation, but contains no skills inventory or verified capacity allocation.",
          "evidenceRef": "[SRC-4]",
          "evidenceStatus": "",
          "evidenceQuality": "",
          "confidence": "",
          "owner": "",
          "gap": "Cloud platform coverage, onboarding effort and specialist availability are unknown.",
          "recommendation": "Compare an agency-operated foundation with a shared-service option using actual support and skill requirements when available.",
          "confirmed": false,
          "confirmedOn": "",
          "updated": "",
          "disposition": ""
        },
        "missingFields": [],
        "interpretation": "Recorded Foundations values only. A status or confirmation does not establish operational acceptance, effectiveness or authorization."
      },
      "disposition": "include",
      "review": {
        "positionId": "AR-049",
        "disposition": "include",
        "serviceId": "capacity",
        "rationale": "Cloud platform coverage, onboarding effort and specialist availability are unknown.",
        "interpretation": "Consultant interpretation: investigate specialist support for bounded platform tasks while retaining internal service ownership. Neither outsourcing nor joining a program guarantees capacity, faster authorization or lower cost.",
        "proposedOwner": "Operations workforce lead — proposed",
        "reviewer": "Fictional teaching reviewer",
        "reviewedAt": "2026-10-06T00:00:00.000Z",
        "scopeHash": "sha256:65a79054d49304f85dccd314fcd4dde48f3b0a3f52aec5d4f6c5852948d8dc58"
      },
      "proposedServiceId": "capacity",
      "nextConversation": {
        "status": "proposed-for-consultant-review",
        "consultantInterpretation": "Consultant interpretation: investigate specialist support for bounded platform tasks while retaining internal service ownership. Neither outsourcing nor joining a program guarantees capacity, faster authorization or lower cost.",
        "proposedRole": "Operations workforce lead — proposed",
        "acceptedOwner": null,
        "agreedDate": null,
        "serviceCommitment": null,
        "responseAuthority": null,
        "questions": [
          "Does this observation apply to the proposed service scope?",
          "Who should receive the follow-up, and have they accepted it?",
          "What evidence and authority must be confirmed before any test or operational action?"
        ]
      }
    }
  ],
  "referenceContext": {
    "sources": [
      {
        "sourcePointer": "/workProduct/3/rows/0",
        "id": "SRC-1",
        "title": "Fictional operations interview — account A",
        "kind": "",
        "location": "",
        "origin": "Invented operations participant; not a client statement",
        "receivedOn": "",
        "citedBy": "AR-010; AR-015",
        "standing": "expected",
        "documentVersion": null,
        "limitation": "Receipt date is not a document version. A cited source was not fetched or independently verified by this adapter."
      },
      {
        "sourcePointer": "/workProduct/3/rows/1",
        "id": "SRC-2",
        "title": "Fictional foundation planning note — account B",
        "kind": "",
        "location": "",
        "origin": "Invented platform participant; not a client statement",
        "receivedOn": "",
        "citedBy": "AR-010; AR-015; AR-047",
        "standing": "expected",
        "documentVersion": null,
        "limitation": "Receipt date is not a document version. A cited source was not fetched or independently verified by this adapter."
      },
      {
        "sourcePointer": "/workProduct/3/rows/2",
        "id": "SRC-3",
        "title": "Fictional service desk and recovery discussion",
        "kind": "",
        "location": "",
        "origin": "Invented service owner discussion; no acceptance recorded",
        "receivedOn": "",
        "citedBy": "AR-012; AR-014; AR-015; AR-048",
        "standing": "expected",
        "documentVersion": null,
        "limitation": "Receipt date is not a document version. A cited source was not fetched or independently verified by this adapter."
      },
      {
        "sourcePointer": "/workProduct/3/rows/3",
        "id": "SRC-4",
        "title": "Fictional workforce and cost questions",
        "kind": "",
        "location": "",
        "origin": "Invented planning questions; staffing and funding not verified",
        "receivedOn": "",
        "citedBy": "AR-014; AR-032; AR-049",
        "standing": "expected",
        "documentVersion": null,
        "limitation": "Receipt date is not a document version. A cited source was not fetched or independently verified by this adapter."
      }
    ],
    "findings": [],
    "decisions": [],
    "relationship": "Unassigned source context only. No finding, source or prior decision is automatically attributed to a proposed service; references are preserved, not independently verified."
  },
  "exclusions": [
    "Scores and calculated maturity",
    "Private intake observations and review history",
    "Source and meeting notes",
    "Desk library and working/session records",
    "Unselected position detail",
    "Raw authorization/acceptance receipts",
    "Unverified assumption schema and arbitrary nested fields"
  ],
  "clientAcceptance": false,
  "executionAllowed": false,
  "limitation": "Fictional supplemental advisory candidate, not a fifth Foundations deliverable, agreed RACI, service agreement, incident runbook or authorization. Original source and recorded interpretations remain separate. Missing evidence requires clarification, not fabricated completion.",
  "maintenance": {
    "trigger": "Changed source bytes, source selection, declared provenance or proposed scope requires a newly validated review. Changed dispositions require regeneration.",
    "instruction": "Keep issued packages immutable. Reconcile proposed roles, authority, evidence and unresolved questions before any client acceptance.",
    "accepted": false
  }
}
