World Models · Published

Managed IT Service Graph

Compose client-isolated infrastructure and service references with explicit authoritative data routing.

AI YAMLAGENTS.mdResearch evidence
Published. Research assurance: reviewable-draft. The Codex-only synthesis is published under an explicit repository-owner provider waiver. It passed structural validation and a separate no-tools adversarial audit, but remains a reviewable draft until independent second-provider review and the holds below are closed.
Catalogue IDWM-XCT-039
Version0.1.0-research.1
Previous version-
Typeaggregate
ValidationPassed
Synthesis digestsha256:dcda6e0b3750b6d7…
6Sources
4Bundles
12Layers
12Findings
36Questions
12Artifacts
Format-independent logical structure

Bundles to Layers to Findings to Questions + Artifacts

boundary-bundleTenant and service boundary3 layers

Bounded graph concerns: tenant and service boundary

tenant-layerClient and provider identities1 findings

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.

tenant-finding

Client and provider identities

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
  1. Which client Dimension and provider organization does this graph describe?identity
    Expected answer
    • tenant-identity-data
  2. Who is the current graph steward and what evidence authorizes administration?ownership
    Expected answer
    • tenant-stewardship-data
  3. Which shared resources are referenced without transferring their ownership to this client?constraint
    Expected answer
    • tenant-shared-resources-data
Artifacts
  • Client and provider identities recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
service-layerService responsibility1 findings

Authored composition-profile design for service responsibility. Cited sources motivate distinctions; these field groups are not asserted to be mandated verbatim by those sources.

service-finding

Service responsibility

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
  1. What bounded service outcome is represented by this graph?definition
    Expected answer
    • service-service-data
  2. Which provider roles perform work and which party remains accountable?relationship
    Expected answer
    • service-responsibility-data
  3. Which services or subcontractor obligations are explicitly outside this graph?exception
    Expected answer
    • service-exclusions-data
Artifacts
  • Service responsibility recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
identity-map-layerAsset identity and recognition1 findings

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.

identity-map-finding

Asset identity and recognition

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
  1. Which authoritative identifier distinguishes this asset from similarly named resources?identity
    Expected answer
    • identity-map-anchor-data
  2. Is the referenced item physical equipment, a virtual resource or a service endpoint?classification
    Expected answer
    • identity-map-classification-data
  3. How was the identity match observed and how are ambiguous matches quarantined?evidence
    Expected answer
    • identity-map-recognition-data
Artifacts
  • Asset identity and recognition recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
graph-bundleDependencies and observations3 layers

Bounded graph concerns: dependencies and observations

dependency-layerService-to-asset dependencies1 findings

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.

dependency-finding

Service-to-asset dependencies

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
  1. Which service depends on which asset and in what direction?relationship
    Expected answer
    • dependency-edge-data
  2. Under which condition and time interval is this dependency valid?constraint
    Expected answer
    • dependency-validity-data
  3. Is the dependency declared, observed or inferred and what uncertainty remains?quality
    Expected answer
    • dependency-assurance-data
Artifacts
  • Service-to-asset dependencies recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
state-layerDeclared and observed state1 findings

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.

state-finding

Declared and observed state

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
  1. What desired state is declared by the configuration authority?state
    Expected answer
    • state-desired-data
  2. What actual state was observed and by which method?measurement
    Expected answer
    • state-observed-data
  3. How is a discrepancy retained without overwriting desired or observed state?validation
    Expected answer
    • state-difference-data
Artifacts
  • Declared and observed state recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
impact-layerBounded impact assessment1 findings

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.

impact-finding

Bounded impact assessment

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
  1. Which directed dependency paths are traversed for this impact question?process
    Expected answer
    • impact-traversal-data
  2. Which missing or stale edges limit the confidence of the impact result?quality
    Expected answer
    • impact-limits-data
  3. Who reviews an inferred impact before it authorizes an operational action?decision
    Expected answer
    • impact-review-data
Artifacts
  • Bounded impact assessment recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
mastership-bundleAuthoritative data and changes3 layers

Bounded graph concerns: authoritative data and changes

master-layerPer-fact mastership1 findings

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.

master-finding

Per-fact mastership

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
  1. Which one owning Dimension and master system govern this fact path at this time?ownership
    Expected answer
    • master-mapping-data
  2. What approved evidence defines that master assignment and its precedence?authority
    Expected answer
    • master-authority-data
  3. What happens when mastership is unknown or equally authoritative sources disagree?exception
    Expected answer
    • master-conflict-data
Artifacts
  • Per-fact mastership recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
write-layerRouted change lifecycle1 findings

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.

write-finding

Routed change lifecycle

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
  1. To which master endpoint is the proposed change routed under the current grant?process
    Expected answer
    • write-route-data
  2. Which version precondition and retry key protect the change from stale writes or duplication?constraint
    Expected answer
    • write-preconditions-data
  3. What authoritative acknowledgement or readback proves that the change took effect?event
    Expected answer
    • write-outcome-data
Artifacts
  • Routed change lifecycle recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
work-layerExternal work tracking1 findings

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.

work-finding

External work tracking

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
  1. Which master task identifier links the work record to the affected service?identity
    Expected answer
    • work-task-data
  2. Which task fields are projections and which remain authoritative in the work system?state
    Expected answer
    • work-task-mastership-data
  3. How is an unavailable or failed task update kept distinct from a completed change?exception
    Expected answer
    • work-task-failure-data
Artifacts
  • External work tracking recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
exchange-bundleProjection and provider lifecycle3 layers

Bounded graph concerns: projection and provider lifecycle

projection-layerAuthorized cross-Dimension view1 findings

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.

projection-finding

Authorized cross-Dimension view

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
  1. Which recipient, purpose, objects and fields are permitted in this projection?access
    Expected answer
    • projection-grant-data
  2. How fresh is the projected view and when must it expire or be rechecked?temporal
    Expected answer
    • projection-freshness-data
  3. How are revocation, deletion and derived sensitive relationships handled by this view?privacy
    Expected answer
    • projection-withdrawal-data
Artifacts
  • Authorized cross-Dimension view recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
handover-layerProvider change and handover1 findings

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.

handover-finding

Provider change and handover

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
  1. Which authority acceptance and cutover evidence allow a new provider to take over?lifecycle
    Expected answer
    • handover-cutover-data
  2. Which object identifiers and historical master references must survive handover?identity
    Expected answer
    • handover-continuity-data
  3. Which previous grants and connector credentials must be revoked and verified?security
    Expected answer
    • handover-revocation-data
Artifacts
  • Provider change and handover recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.
assurance-layerGraph completeness and audit1 findings

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.

assurance-finding

Graph completeness and audit

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
  1. Which graph invariants have been checked and which checks remain unimplemented?validation
    Expected answer
    • assurance-checks-data
  2. Which source revisions and approvals explain each material graph change?provenance
    Expected answer
    • assurance-audit-data
  3. Which exported fields are preserved, transformed or lost by a destination adapter?interoperability
    Expected answer
    • assurance-mapping-data
Artifacts
  • Graph completeness and audit recordAttributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.

Publication holds

  • 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.
  • Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft.

Deferred research

  • Executable nested schemas and tenant-isolation negative fixtures
  • Versioned CMDB/Redfish/Jira adapters and operational readback tests