{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-xct-039","code":"wm-xct-039-managed-it-service-graph","url":"https://ver.cy/models/wm-xct-039-managed-it-service-graph/","name":"Managed IT Service Graph","alternateNames":["Managed client IT infrastructure mastership and service graph"],"kind":"world-model","status":"published","version":"0.1.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Cross-cutting context","entryKind":"aggregate","plane":"","domain":["XCT.ITG"],"industry":["Cross-industry"],"navPath":"NAV.XCT.ITG","tags":["managed","it","service","graph","xct.itg","managed client it infrastructure mastership and service graph"],"facets":{}},"whatItIs":"A bounded service-provider/client graph profile. It records tenant boundary, service/asset references, dependencies, desired versus observed state, per-fact mastership, routed change outcomes, and authorized projections. It does not become a competing CMDB or authorization engine.","purpose":"Compose client-isolated infrastructure and service references with explicit authoritative data routing.","scope":{"in":["Client and provider relationship references","Typed service-to-asset dependencies","Per-fact owning Dimension and master-system mapping","Source-qualified observations and change outcomes","Purpose-bound projections and handover evidence"],"out":["Full asset, party, ownership, task or contract lifecycles","Implemented IAM, CMDB, discovery, Jira connector or distributed transaction engine","Automatic legal ownership transfer or proof of client acceptance","Universal infrastructure schema or full Redfish conformance"],"boundaries":[{"neighbor":"Ownership / Stewardship","distinction":"Reference control assertions; administration does not imply title or client acceptance."},{"neighbor":"Dependency / Impact","distinction":"Reference typed dependency semantics; domain profile supplies tenant/master boundaries, not universal impact calculus."},{"neighbor":"Redfish and CMDB","distinction":"Reference infrastructure identities and observations; adapters and their schema versions are separately validated."},{"neighbor":"Task and service case","distinction":"Link work IDs; do not copy task state as an independently editable authority."}]},"distinguishingFeatures":["A provider-client view of services and assets, not a CMDB or asset master.","Records which system masters each fact and routes changes there.","Keeps desired and observed state apart.","Enforces client isolation in a multi-tenant provider context."],"structure":{"bundles":[{"id":"boundary-bundle","name":"Tenant and service boundary","description":"Bounded graph concerns: tenant and service boundary","layers":[{"id":"tenant-layer","name":"Client and provider identities","description":"Authored composition-profile design for client and provider identities. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"tenant-finding","name":"Client and provider identities","description":"Authored composition-profile design for client and provider identities. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"Which client Dimension and provider organization does this graph describe?","id":"tenant-q1","kind":"identity"},{"text":"Who is the current graph steward and what evidence authorizes administration?","id":"tenant-q2","kind":"ownership"},{"text":"Which shared resources are referenced without transferring their ownership to this client?","id":"tenant-q3","kind":"constraint"}]}]},{"id":"service-layer","name":"Service responsibility","description":"Authored composition-profile design for service responsibility. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"service-finding","name":"Service responsibility","description":"Authored composition-profile design for service responsibility. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"What bounded service outcome is represented by this graph?","id":"service-q1","kind":"definition"},{"text":"Which provider roles perform work and which party remains accountable?","id":"service-q2","kind":"relationship"},{"text":"Which services or subcontractor obligations are explicitly outside this graph?","id":"service-q3","kind":"exception"}]}]},{"id":"identity-map-layer","name":"Asset identity and recognition","description":"Authored composition-profile design for asset identity and recognition. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"identity-map-finding","name":"Asset identity and recognition","description":"Authored composition-profile design for asset identity and recognition. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"Which authoritative identifier distinguishes this asset from similarly named resources?","id":"identity-map-q1","kind":"identity"},{"text":"Is the referenced item physical equipment, a virtual resource or a service endpoint?","id":"identity-map-q2","kind":"classification"},{"text":"How was the identity match observed and how are ambiguous matches quarantined?","id":"identity-map-q3","kind":"evidence"}]}]}]},{"id":"graph-bundle","name":"Dependencies and observations","description":"Bounded graph concerns: dependencies and observations","layers":[{"id":"dependency-layer","name":"Service-to-asset dependencies","description":"Authored composition-profile design for service-to-asset dependencies. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"dependency-finding","name":"Service-to-asset dependencies","description":"Authored composition-profile design for service-to-asset dependencies. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"Which service depends on which asset and in what direction?","id":"dependency-q1","kind":"relationship"},{"text":"Under which condition and time interval is this dependency valid?","id":"dependency-q2","kind":"constraint"},{"text":"Is the dependency declared, observed or inferred and what uncertainty remains?","id":"dependency-q3","kind":"quality"}]}]},{"id":"state-layer","name":"Declared and observed state","description":"Authored composition-profile design for declared and observed state. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"state-finding","name":"Declared and observed state","description":"Authored composition-profile design for declared and observed state. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"What desired state is declared by the configuration authority?","id":"state-q1","kind":"state"},{"text":"What actual state was observed and by which method?","id":"state-q2","kind":"measurement"},{"text":"How is a discrepancy retained without overwriting desired or observed state?","id":"state-q3","kind":"validation"}]}]},{"id":"impact-layer","name":"Bounded impact assessment","description":"Authored composition-profile design for bounded impact assessment. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"impact-finding","name":"Bounded impact assessment","description":"Authored composition-profile design for bounded impact assessment. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"Which directed dependency paths are traversed for this impact question?","id":"impact-q1","kind":"process"},{"text":"Which missing or stale edges limit the confidence of the impact result?","id":"impact-q2","kind":"quality"},{"text":"Who reviews an inferred impact before it authorizes an operational action?","id":"impact-q3","kind":"decision"}]}]}]},{"id":"mastership-bundle","name":"Authoritative data and changes","description":"Bounded graph concerns: authoritative data and changes","layers":[{"id":"master-layer","name":"Per-fact mastership","description":"Authored composition-profile design for per-fact mastership. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"master-finding","name":"Per-fact mastership","description":"Authored composition-profile design for per-fact mastership. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"Which one owning Dimension and master system govern this fact path at this time?","id":"master-q1","kind":"ownership"},{"text":"What approved evidence defines that master assignment and its precedence?","id":"master-q2","kind":"authority"},{"text":"What happens when mastership is unknown or equally authoritative sources disagree?","id":"master-q3","kind":"exception"}]}]},{"id":"write-layer","name":"Routed change lifecycle","description":"Authored composition-profile design for routed change lifecycle. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"write-finding","name":"Routed change lifecycle","description":"Authored composition-profile design for routed change lifecycle. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"To which master endpoint is the proposed change routed under the current grant?","id":"write-q1","kind":"process"},{"text":"Which version precondition and retry key protect the change from stale writes or duplication?","id":"write-q2","kind":"constraint"},{"text":"What authoritative acknowledgement or readback proves that the change took effect?","id":"write-q3","kind":"event"}]}]},{"id":"work-layer","name":"External work tracking","description":"Authored composition-profile design for external work tracking. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"work-finding","name":"External work tracking","description":"Authored composition-profile design for external work tracking. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"Which master task identifier links the work record to the affected service?","id":"work-q1","kind":"identity"},{"text":"Which task fields are projections and which remain authoritative in the work system?","id":"work-q2","kind":"state"},{"text":"How is an unavailable or failed task update kept distinct from a completed change?","id":"work-q3","kind":"exception"}]}]}]},{"id":"exchange-bundle","name":"Projection and provider lifecycle","description":"Bounded graph concerns: projection and provider lifecycle","layers":[{"id":"projection-layer","name":"Authorized cross-Dimension view","description":"Authored composition-profile design for authorized cross-dimension view. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"projection-finding","name":"Authorized cross-Dimension view","description":"Authored composition-profile design for authorized cross-dimension view. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"Which recipient, purpose, objects and fields are permitted in this projection?","id":"projection-q1","kind":"access"},{"text":"How fresh is the projected view and when must it expire or be rechecked?","id":"projection-q2","kind":"temporal"},{"text":"How are revocation, deletion and derived sensitive relationships handled by this view?","id":"projection-q3","kind":"privacy"}]}]},{"id":"handover-layer","name":"Provider change and handover","description":"Authored composition-profile design for provider change and handover. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"handover-finding","name":"Provider change and handover","description":"Authored composition-profile design for provider change and handover. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"Which authority acceptance and cutover evidence allow a new provider to take over?","id":"handover-q1","kind":"lifecycle"},{"text":"Which object identifiers and historical master references must survive handover?","id":"handover-q2","kind":"identity"},{"text":"Which previous grants and connector credentials must be revoked and verified?","id":"handover-q3","kind":"security"}]}]},{"id":"assurance-layer","name":"Graph completeness and audit","description":"Authored composition-profile design for graph completeness and audit. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","findings":[{"id":"assurance-finding","name":"Graph completeness and audit","description":"Authored composition-profile design for graph completeness and audit. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.","questions":[{"text":"Which graph invariants have been checked and which checks remain unimplemented?","id":"assurance-q1","kind":"validation"},{"text":"Which source revisions and approvals explain each material graph change?","id":"assurance-q2","kind":"provenance"},{"text":"Which exported fields are preserved, transformed or lost by a destination adapter?","id":"assurance-q3","kind":"interoperability"}]}]}]}]},"agentConduct":{"may":["Register a graph for a client within declared policy.","Route proposed changes to the owning master system.","Build projections allowed for a given role and purpose.","Reconcile observed state with desired state and report drift."],"mustNot":["Access or mix data across clients.","Store credentials in graph records.","Retry a non-idempotent change after a timeout without reconciling.","Change facts whose owner or identity is unresolved.","Treat the graph as proof of client acceptance or ownership."],"requiresHuman":["Approving changes to production systems.","Provider handover to another provider.","Resolving ownership conflicts."]},"ethics":{"considerations":["Clients entrust providers with access to critical systems; isolation failures can expose many organizations.","Outages caused by wrong changes affect people who depend on client services.","Provider lock-in through incomplete handover harms clients."],"affectedParties":["Client organizations and their users","Provider staff","End customers of client services"]},"owners":{"steward":"Stable Dimension namespace","roles":[{"name":"owner","responsibilities":["Approve scope and delegations"]},{"name":"steward","responsibilities":["Maintain source mappings and resolve conflicts"]},{"name":"operator","responsibilities":["Execute only separately authorized changes"]},{"name":"verifier","responsibilities":["Check evidence, invariants and unresolved gaps"]},{"name":"projection-consumer","responsibilities":["Read only approved purpose-bound views"]}],"masterSystems":[]},"relations":[{"target":"vr.wm-xct-001","type":"composes","note":"Control and stewardship assertions for referenced Dimension and resources"},{"target":"vr.wm-xct-003","type":"composes","note":"Projection and disclosure constraints"},{"target":"vr.wm-xct-037","type":"composes","note":"Typed dependency and bounded impact semantics"},{"target":"Ownership / Stewardship","type":"neighbor","note":"Reference control assertions; administration does not imply title or client acceptance."},{"target":"Dependency / Impact","type":"neighbor","note":"Reference typed dependency semantics; domain profile supplies tenant/master boundaries, not universal impact calculus."},{"target":"Redfish and CMDB","type":"neighbor","note":"Reference infrastructure identities and observations; adapters and their schema versions are separately validated."},{"target":"Task and service case","type":"neighbor","note":"Link work IDs; do not copy task state as an independently editable authority."},{"target":"vr.wm-xct-001","type":"requires"},{"target":"vr.wm-xct-003","type":"requires"},{"target":"vr.wm-xct-037","type":"requires"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier","Stable Dimension-scoped identifier","Attributed external alias with identity evidence"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A service graph has a client tenant, provider, service and asset nodes, dependencies and per-fact master references.","Confused with a CMDB, a monitoring topology and an asset inventory."]},"capabilities":{"applicability":"required","items":["Register graph: Register graph within the declared Dimension policy.","Route proposed change: Route proposed change within the declared Dimension policy.","Build permitted projection: Build permitted projection within the declared Dimension policy.","Record provider handover: Record provider handover within the declared Dimension policy."]},"hazards":{"applicability":"required","items":["Cross-tenant data leak.","Duplicate or conflicting changes after timeouts.","Outages from wrong dependency data.","Lost knowledge at provider handover."]},"interfaces":{"applicability":"required","items":["DMTF Redfish.","DMTF Common Information Model.","ISO/IEC 20000-1 service management.","ISO/IEC 19770 IT asset management."]},"context":{"applicability":"required","items":["Ownership, retention and contractual authority require the adopting organization legal/policy profile; no jurisdictional rule is inferred."]}},"sources":[{"title":"Vercy agent entry contract","url":"https://ver.cy/AGENTS.md","note":"Vercy"},{"title":"Vercy model agent protocol","url":"https://ver.cy/model-agent-protocol.md","note":"Vercy"},{"title":"PROV-O","url":"https://www.w3.org/TR/prov-o/","note":"W3C"},{"title":"ODRL Information Model","url":"https://www.w3.org/TR/odrl-model/","note":"W3C"},{"title":"Redfish standards overview","url":"https://www.dmtf.org/standards/redfish","note":"DMTF"},{"title":"HTTP Semantics","url":"https://www.rfc-editor.org/rfc/rfc9110.html","note":"IETF"}],"openQuestions":["Executable nested schemas and tenant-isolation negative fixtures","Versioned CMDB/Redfish/Jira adapters and operational readback tests","Nested data-group schemas and executable graph/IAM enforcement are not supplied.","Redfish source is the standards overview; concrete DSP schema mapping is not claimed.","No production Jira, discovery, CMDB or revocable-cache adapter is implemented.","External independent research results are admitted only if available and validated; assurance remains reviewable-draft.","Claude timed out after one 60-second attempt; Grok returned provider-error after one bounded attempt. A separate Codex no-tools audit reviewed the supplied design summary, not source truth or executable behavior."],"resources":{"spec":"/models/wm-xct-039-managed-it-service-graph/spec.yaml","agents":"/models/wm-xct-039-managed-it-service-graph/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/publish/dt-model-requests-20260920/research/runs/wm-xct-039"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-xct-039-managed-it-service-graph/spec.yaml","ver-cy/world-models/card-supplements/wm-xct-039-managed-it-service-graph.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-20T19:02:23Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}