# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-20T19:02:23Z", "synthesisSha256": "dcda6e0b3750b6d70b888d298f966e732d86bca9813c6a27255ffb4d6314f0f2", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-XCT-039", "registryId": "vr.wm-xct-039", "name": "Managed IT Service Graph", "version": "0.1.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Cross-cutting context", "industry": [ "Cross-industry" ], "domain": [ "XCT.ITG" ], "tags": [ "managed", "it", "service", "graph", "xct.itg", "managed client it infrastructure mastership and service graph" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-xct-039-managed-it-service-graph/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/publish/dt-model-requests-20260920/research/runs/wm-xct-039", "model": { "registry_id": "vr.wm-xct-039", "model_id": "WM-XCT-039", "name": "Managed IT Service Graph", "entry_kind": "aggregate", "purpose": "Compose client-isolated infrastructure and service references with explicit authoritative data routing.", "scope_statement": "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.", "in_scope": [ "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_of_scope": [ "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" ], "boundary_notes": [ { "neighbor": "Ownership / Stewardship", "distinction": "Reference control assertions; administration does not imply title or client acceptance.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "Dependency / Impact", "distinction": "Reference typed dependency semantics; domain profile supplies tenant/master boundaries, not universal impact calculus.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "neighbor": "Redfish and CMDB", "distinction": "Reference infrastructure identities and observations; adapters and their schema versions are separately validated.", "source_refs": [ "SRC-005" ] }, { "neighbor": "Task and service case", "distinction": "Link work IDs; do not copy task state as an independently editable authority.", "source_refs": [ "SRC-001", "SRC-006" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Vercy agent entry contract", "organization": "Vercy", "url": "https://ver.cy/AGENTS.md", "version_or_date": "Inspected 2026-09-20", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-20T19:02:23Z", "relevance": "Dimension ownership, one write master and approved cross-Dimension projections." }, { "id": "SRC-002", "title": "Vercy model agent protocol", "organization": "Vercy", "url": "https://ver.cy/model-agent-protocol.md", "version_or_date": "Inspected 2026-09-20", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-20T19:02:23Z", "relevance": "Versioned model lifecycle and five-facet description gate." }, { "id": "SRC-003", "title": "PROV-O", "organization": "W3C", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-20T19:02:23Z", "relevance": "Entity, activity and agent attribution and derivation distinctions; not an authority resolver." }, { "id": "SRC-004", "title": "ODRL Information Model", "organization": "W3C", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "2.2 Recommendation 2018-02-15", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-20T19:02:23Z", "relevance": "Permission, prohibition, duty, party, asset and constraint distinctions; not a deployed enforcement engine." }, { "id": "SRC-005", "title": "Redfish standards overview", "organization": "DMTF", "url": "https://www.dmtf.org/standards/redfish", "version_or_date": "Overview inspected 2026-09-20", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-20T19:02:23Z", "relevance": "Heterogeneous infrastructure management and resource representations; concrete schema mappings remain deployment-specific." }, { "id": "SRC-006", "title": "HTTP Semantics", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc9110.html", "version_or_date": "RFC 9110 June 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-20T19:02:23Z", "relevance": "Conditional requests, entity tags and response semantics; not distributed transaction guarantees." } ], "structure": { "bundles": [ { "id": "boundary-bundle", "name": "Tenant and service boundary", "description": "Bounded graph concerns: tenant and service boundary", "rationale": "Keep this group separate so graph composition does not replace the referenced system of record.", "source_refs": [ "SRC-001", "SRC-002" ], "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.", "source_refs": [ "SRC-001", "SRC-004" ], "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.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "tenant-q1", "text": "Which client Dimension and provider organization does this graph describe?", "kind": "identity", "answer_data": [ "tenant-identity-data" ] }, { "id": "tenant-q2", "text": "Who is the current graph steward and what evidence authorizes administration?", "kind": "ownership", "answer_data": [ "tenant-stewardship-data" ] }, { "id": "tenant-q3", "text": "Which shared resources are referenced without transferring their ownership to this client?", "kind": "constraint", "answer_data": [ "tenant-shared-resources-data" ] } ], "data_elements": [ { "id": "tenant-identity-data", "name": "identity", "description": "Proposed members: clientDimensionId, providerPartyRef, graphId, namespace. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "tenant-stewardship-data", "name": "stewardship", "description": "Proposed members: stewardRef, authorityEvidenceRef, effectiveFrom, effectiveTo. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "tenant-shared-resources-data", "name": "shared-resources", "description": "Proposed members: resourceRefs, owningDimensionRefs, permittedReferenceScope. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "tenant-artifact", "name": "Client and provider identities record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-003" ], "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.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "service-q1", "text": "What bounded service outcome is represented by this graph?", "kind": "definition", "answer_data": [ "service-service-data" ] }, { "id": "service-q2", "text": "Which provider roles perform work and which party remains accountable?", "kind": "relationship", "answer_data": [ "service-responsibility-data" ] }, { "id": "service-q3", "text": "Which services or subcontractor obligations are explicitly outside this graph?", "kind": "exception", "answer_data": [ "service-exclusions-data" ] } ], "data_elements": [ { "id": "service-service-data", "name": "service", "description": "Proposed members: serviceRef, outcomeDescription, boundary, lifecycleState. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "service-responsibility-data", "name": "responsibility", "description": "Proposed members: responsibleRoleRefs, accountablePartyRef, agreementRef. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "service-exclusions-data", "name": "exclusions", "description": "Proposed members: excludedServiceRefs, reason, evidenceRef. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "service-artifact", "name": "Service responsibility record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-002", "SRC-005" ], "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.", "source_refs": [ "SRC-002", "SRC-005" ], "questions": [ { "id": "identity-map-q1", "text": "Which authoritative identifier distinguishes this asset from similarly named resources?", "kind": "identity", "answer_data": [ "identity-map-anchor-data" ] }, { "id": "identity-map-q2", "text": "Is the referenced item physical equipment, a virtual resource or a service endpoint?", "kind": "classification", "answer_data": [ "identity-map-classification-data" ] }, { "id": "identity-map-q3", "text": "How was the identity match observed and how are ambiguous matches quarantined?", "kind": "evidence", "answer_data": [ "identity-map-recognition-data" ] } ], "data_elements": [ { "id": "identity-map-anchor-data", "name": "anchor", "description": "Proposed members: assetRef, masterSystemId, masterRecordId, aliasEvidence. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "identity-map-classification-data", "name": "classification", "description": "Proposed members: assetClassRef, resourceKind, classificationEvidence. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "identity-map-recognition-data", "name": "recognition", "description": "Proposed members: observationRef, observedAt, matchEvidence, ambiguityState. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "identity-map-artifact", "name": "Asset identity and recognition record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "graph-bundle", "name": "Dependencies and observations", "description": "Bounded graph concerns: dependencies and observations", "rationale": "Keep this group separate so graph composition does not replace the referenced system of record.", "source_refs": [ "SRC-001", "SRC-002" ], "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "questions": [ { "id": "dependency-q1", "text": "Which service depends on which asset and in what direction?", "kind": "relationship", "answer_data": [ "dependency-edge-data" ] }, { "id": "dependency-q2", "text": "Under which condition and time interval is this dependency valid?", "kind": "constraint", "answer_data": [ "dependency-validity-data" ] }, { "id": "dependency-q3", "text": "Is the dependency declared, observed or inferred and what uncertainty remains?", "kind": "quality", "answer_data": [ "dependency-assurance-data" ] } ], "data_elements": [ { "id": "dependency-edge-data", "name": "edge", "description": "Proposed members: sourceRef, targetRef, relationType, owningDimensionId. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "dependency-validity-data", "name": "validity", "description": "Proposed members: condition, validFrom, validTo, evidenceRef. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "dependency-assurance-data", "name": "assurance", "description": "Proposed members: assertionKind, confidence, sourceRef, unresolvedAssumptions. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "dependency-artifact", "name": "Service-to-asset dependencies record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "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.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "state-q1", "text": "What desired state is declared by the configuration authority?", "kind": "state", "answer_data": [ "state-desired-data" ] }, { "id": "state-q2", "text": "What actual state was observed and by which method?", "kind": "measurement", "answer_data": [ "state-observed-data" ] }, { "id": "state-q3", "text": "How is a discrepancy retained without overwriting desired or observed state?", "kind": "validation", "answer_data": [ "state-difference-data" ] } ], "data_elements": [ { "id": "state-desired-data", "name": "desired", "description": "Proposed members: configurationRef, revision, validFrom, declaringAuthority. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "state-observed-data", "name": "observed", "description": "Proposed members: observationRef, value, unit, method, observedAt, tolerance. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "state-difference-data", "name": "difference", "description": "Proposed members: desiredRef, observedRef, discrepancyId, assessmentState. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "state-artifact", "name": "Declared and observed state record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-002", "SRC-003" ], "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.", "source_refs": [ "SRC-002", "SRC-003" ], "questions": [ { "id": "impact-q1", "text": "Which directed dependency paths are traversed for this impact question?", "kind": "process", "answer_data": [ "impact-traversal-data" ] }, { "id": "impact-q2", "text": "Which missing or stale edges limit the confidence of the impact result?", "kind": "quality", "answer_data": [ "impact-limits-data" ] }, { "id": "impact-q3", "text": "Who reviews an inferred impact before it authorizes an operational action?", "kind": "decision", "answer_data": [ "impact-review-data" ] } ], "data_elements": [ { "id": "impact-traversal-data", "name": "traversal", "description": "Proposed members: startRefs, relationFilter, depthLimit, cyclePolicy. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "impact-limits-data", "name": "limits", "description": "Proposed members: missingEdgeRefs, staleSourceRefs, confidence, completenessBoundary. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "impact-review-data", "name": "review", "description": "Proposed members: reviewerRef, evidenceRef, decisionRef, actionAuthorizationRef. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "impact-artifact", "name": "Bounded impact assessment record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "mastership-bundle", "name": "Authoritative data and changes", "description": "Bounded graph concerns: authoritative data and changes", "rationale": "Keep this group separate so graph composition does not replace the referenced system of record.", "source_refs": [ "SRC-001", "SRC-002" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "master-q1", "text": "Which one owning Dimension and master system govern this fact path at this time?", "kind": "ownership", "answer_data": [ "master-mapping-data" ] }, { "id": "master-q2", "text": "What approved evidence defines that master assignment and its precedence?", "kind": "authority", "answer_data": [ "master-authority-data" ] }, { "id": "master-q3", "text": "What happens when mastership is unknown or equally authoritative sources disagree?", "kind": "exception", "answer_data": [ "master-conflict-data" ] } ], "data_elements": [ { "id": "master-mapping-data", "name": "mapping", "description": "Proposed members: subjectRef, factPath, owningDimensionId, masterSystemId, validFrom, validTo. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "master-authority-data", "name": "authority", "description": "Proposed members: policyRef, approvingRoleRef, approvalEvidenceRef, precedenceScope. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "master-conflict-data", "name": "conflict", "description": "Proposed members: pendingState, conflictingAssertionRefs, resolutionOwnerRef, resolutionEvidence. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "master-artifact", "name": "Per-fact mastership record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-006" ], "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.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "write-q1", "text": "To which master endpoint is the proposed change routed under the current grant?", "kind": "process", "answer_data": [ "write-route-data" ] }, { "id": "write-q2", "text": "Which version precondition and retry key protect the change from stale writes or duplication?", "kind": "constraint", "answer_data": [ "write-preconditions-data" ] }, { "id": "write-q3", "text": "What authoritative acknowledgement or readback proves that the change took effect?", "kind": "event", "answer_data": [ "write-outcome-data" ] } ], "data_elements": [ { "id": "write-route-data", "name": "route", "description": "Proposed members: changeId, targetSystemRef, operation, scope, authorizationRef. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "write-preconditions-data", "name": "preconditions", "description": "Proposed members: expectedRevision, conditionalRequestBinding, operationKey, retryPolicy. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "write-outcome-data", "name": "outcome", "description": "Proposed members: requestRef, responseRef, masterRevision, state, failureReason, readbackEvidence. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "write-artifact", "name": "Routed change lifecycle record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "work-q1", "text": "Which master task identifier links the work record to the affected service?", "kind": "identity", "answer_data": [ "work-task-data" ] }, { "id": "work-q2", "text": "Which task fields are projections and which remain authoritative in the work system?", "kind": "state", "answer_data": [ "work-task-mastership-data" ] }, { "id": "work-q3", "text": "How is an unavailable or failed task update kept distinct from a completed change?", "kind": "exception", "answer_data": [ "work-task-failure-data" ] } ], "data_elements": [ { "id": "work-task-data", "name": "task", "description": "Proposed members: taskSystemRef, taskId, serviceRef, changeId. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "work-task-mastership-data", "name": "task-mastership", "description": "Proposed members: fieldMappings, masterSystemRef, lastReadRevision, freshness. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "work-task-failure-data", "name": "task-failure", "description": "Proposed members: operationState, retryAfter, pendingProposalRef, failureEvidence. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "work-artifact", "name": "External work tracking record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "exchange-bundle", "name": "Projection and provider lifecycle", "description": "Bounded graph concerns: projection and provider lifecycle", "rationale": "Keep this group separate so graph composition does not replace the referenced system of record.", "source_refs": [ "SRC-001", "SRC-002" ], "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "questions": [ { "id": "projection-q1", "text": "Which recipient, purpose, objects and fields are permitted in this projection?", "kind": "access", "answer_data": [ "projection-grant-data" ] }, { "id": "projection-q2", "text": "How fresh is the projected view and when must it expire or be rechecked?", "kind": "temporal", "answer_data": [ "projection-freshness-data" ] }, { "id": "projection-q3", "text": "How are revocation, deletion and derived sensitive relationships handled by this view?", "kind": "privacy", "answer_data": [ "projection-withdrawal-data" ] } ], "data_elements": [ { "id": "projection-grant-data", "name": "grant", "description": "Proposed members: sourceDimensionId, targetDimensionId, recipientRef, purpose, objectFilter, fieldAllowlist, policyRef. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "projection-freshness-data", "name": "freshness", "description": "Proposed members: sourceRevision, observedAt, refreshedAt, maxAge, expiresAt. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "projection-withdrawal-data", "name": "withdrawal", "description": "Proposed members: revocationState, tombstoneRef, cacheInvalidationBinding, retentionException, derivedEdgeFilter. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "projection-artifact", "name": "Authorized cross-Dimension view record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "handover-q1", "text": "Which authority acceptance and cutover evidence allow a new provider to take over?", "kind": "lifecycle", "answer_data": [ "handover-cutover-data" ] }, { "id": "handover-q2", "text": "Which object identifiers and historical master references must survive handover?", "kind": "identity", "answer_data": [ "handover-continuity-data" ] }, { "id": "handover-q3", "text": "Which previous grants and connector credentials must be revoked and verified?", "kind": "security", "answer_data": [ "handover-revocation-data" ] } ], "data_elements": [ { "id": "handover-cutover-data", "name": "cutover", "description": "Proposed members: outgoingProviderRef, incomingProviderRef, clientAcceptanceRef, cutoverAt, verificationState. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "handover-continuity-data", "name": "continuity", "description": "Proposed members: preservedIds, mappingRefs, historicalMasterRefs, exportManifestRef. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "handover-revocation-data", "name": "revocation", "description": "Proposed members: grantRefs, credentialReferencesOnly, revocationEvidence, residualAccessReview. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "handover-artifact", "name": "Provider change and handover record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "assurance-q1", "text": "Which graph invariants have been checked and which checks remain unimplemented?", "kind": "validation", "answer_data": [ "assurance-checks-data" ] }, { "id": "assurance-q2", "text": "Which source revisions and approvals explain each material graph change?", "kind": "provenance", "answer_data": [ "assurance-audit-data" ] }, { "id": "assurance-q3", "text": "Which exported fields are preserved, transformed or lost by a destination adapter?", "kind": "interoperability", "answer_data": [ "assurance-mapping-data" ] } ], "data_elements": [ { "id": "assurance-checks-data", "name": "checks", "description": "Proposed members: validationRunRef, ruleIds, failures, unimplementedChecks. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "assurance-audit-data", "name": "audit", "description": "Proposed members: eventRefs, actorRefs, sourceRevisions, approvalRefs, recordingTime. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "assurance-mapping-data", "name": "mapping", "description": "Proposed members: adapterVersion, fieldMap, lossReport, reconciliationEvidence. This draft declares a semantic record group; nested executable schemas are not yet supplied. Unknown and not-applicable require explicit reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "assurance-artifact", "name": "Graph completeness and audit record", "description": "Attributed minimal record or protected master-system reference; preserves unknowns and excludes secrets.", "media_or_form": [ "structured record", "source reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier; otherwise namespace-scoped immutable identifier with explicit mapping.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-graph", "name": "Register graph", "description": "Register graph within the declared Dimension policy.", "inputs": [ "approved tenant boundary and authority" ], "outputs": [ "stable graph identity and referenced endpoints" ], "preconditions": [ "Owner authority and client scope are established" ], "effects": [ "Create an attributed graph revision; do not create client acceptance" ], "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "route-change", "name": "Route proposed change", "description": "Route proposed change within the declared Dimension policy.", "inputs": [ "fact path, proposed value and expected master revision" ], "outputs": [ "acknowledged, pending or failed operation evidence" ], "preconditions": [ "Exactly one master and current operation grant resolve" ], "effects": [ "Submit through the authorized adapter; only authoritative confirmation updates the observed projection" ], "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "project-graph", "name": "Build permitted projection", "description": "Build permitted projection within the declared Dimension policy.", "inputs": [ "graph revision, recipient, purpose and field policy" ], "outputs": [ "filtered view with origin and freshness" ], "preconditions": [ "Source and target policies and role/task scope permit every disclosed field and inferred edge" ], "effects": [ "Materialize a revocable derived view; do not grant independent write authority" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "handover-graph", "name": "Record provider handover", "description": "Record provider handover within the declared Dimension policy.", "inputs": [ "accepted transfer plan and access inventory" ], "outputs": [ "continuity manifest and revocation evidence" ], "preconditions": [ "Incoming authority acceptance and retention obligations are verified" ], "effects": [ "Record cutover with stable IDs; external credential changes require separate authorized execution" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "composition": [ { "target": "vr.wm-xct-001", "relation": "COMPOSE", "purpose": "Control and stewardship assertions for referenced Dimension and resources", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "vr.wm-xct-003", "relation": "COMPOSE", "purpose": "Projection and disclosure constraints", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "vr.wm-xct-037", "relation": "COMPOSE", "purpose": "Typed dependency and bounded impact semantics", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Stable Dimension namespace", "Named owner and approving roles", "Explicit master-system and projection policies" ], "namespace_guidance": "Keep provider and each client Dimension identifiers distinct. Physical hosting does not determine logical ownership.", "registry_links": [ "object registry", "model registry", "mastership mappings", "projection registry" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve authoritative identifiers and exact source versions." ], "patch_rules": [ "Do not mutate released specifications; publish a new version with a semantic diff." ], "compatibility_rules": [ "A changed master, field meaning or disclosure scope requires explicit migration review." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Stable Dimension-scoped identifier", "Attributed external alias with identity evidence" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit UTC offset; preserve effective and recording time separately.", "serial_naming_rule": "Stable record ID plus immutable revision; date is metadata rather than identity.", "integrity_rule": "Verify specification SHA-256 and expected object head; preserve provenance." }, "policies": [ "Default-deny cross-client access; do not put credentials in records.", "Every write routes to exactly one current owning Dimension and master system; unknown ownership is pending.", "An API timeout is indeterminate, not proof of failure; reconcile before retrying non-idempotent operations.", "Ambiguous subject identity, unknown master or unresolved authoritative conflict MUST block mutations of affected facts until identity and authority resolve for the effective time; preserve conflicting evidence.", "Resolve owning Dimension and master for every modified fact. Reject or decompose cross-master operations into separately authorized operations with explicit partial-completion and reconciliation behavior.", "Required revision preconditions MUST be atomically enforced by the authoritative target or a demonstrated equivalent. Read-then-unconditional-write is insufficient. Operation keys deduplicate only under a receiving-system contract. Hold execution when required guarantees are unavailable; reconcile indeterminate outcomes before safe retry.", "Stewardship, accountability, client acceptance and reviewer approval are evidence, not implicit mutation or access grants. Handover changes mastership and grants only through explicit authorized transitions; overlap grants require scope and expiry.", "Missing, stale, filtered or inaccessible dependencies yield incomplete impact, never an unsupported no-impact conclusion.", "Retention exceptions preserve records under an approved purpose; they do not preserve operational access or permit redistribution." ], "crud": { "read": [ "Resolve role, source/target policies, purpose and freshness before reading." ], "create": [ "Create only with declared ownership, master mapping and evidence." ], "update": [ "Validate expected revision, authority and adapter outcome; preserve previous assertions." ], "delete": [ "Use approved retention and tombstones; revoke views separately; do not infer deletion from a missing read." ] }, "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" ] } ], "access": { "default_rule": "Deny unless role, source, target, projection and task policies all permit access.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Break-glass access requires explicit recorded authority and retrospective review; it does not silently widen standing grants." ], "audit_requirements": [ "Record actor, purpose, scope, source revisions and approval evidence for material changes." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Dimension authority, policies and master mappings", "Model AGENTS and pinned specification", "Authorized source references and relevant records" ] } }, "coverage": { "claim": "Source-grounded bounded composition profile for review; not a working CMDB, connector, access-control engine or canonical complete IT ontology.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable tenant and master identifiers; ambiguous matches remain pending." }, { "dimension": "direct properties", "status": "covered", "notes": "Graph boundary and master mappings required; physical attributes delegated to referenced assets." }, { "dimension": "recognition", "status": "covered", "notes": "Identity evidence and ambiguous matching are recorded." }, { "dimension": "capabilities", "status": "covered", "notes": "Routed changes and projections declare preconditions and outcomes; no authority implied by capability." }, { "dimension": "lifecycle", "status": "covered", "notes": "Onboarding, changes and provider handover are source-qualified." }, { "dimension": "relationships", "status": "covered", "notes": "Directed dependencies with conditions and validity." }, { "dimension": "temporal", "status": "covered", "notes": "Effective, observed and recorded time kept distinct." }, { "dimension": "provenance", "status": "covered", "notes": "Source revisions and operation evidence retained." }, { "dimension": "ownership", "status": "covered", "notes": "Provider custody differs from client ownership and field-level mastership." }, { "dimension": "access", "status": "covered", "notes": "Tenant, purpose, recipient and field restrictions include derived edges." }, { "dimension": "interoperability", "status": "covered", "notes": "Adapter field maps and information loss are explicit." }, { "dimension": "validation", "status": "gap", "notes": "Research schema and references checked; executable nested/runtime schemas are deferred." } ], "known_omissions": [ "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." ], "conflicts": [], "regional_assumptions": [ "Ownership, retention and contractual authority require the adopting organization legal/policy profile; no jurisdictional rule is inferred." ], "adversarial_checks": [ "Identical asset names in different tenants cannot be merged without authoritative identity evidence.", "An acknowledged task update does not prove an infrastructure change occurred.", "A timed-out write remains indeterminate until master readback or idempotent reconciliation.", "A cached or inferred edge must not bypass revoked projection rights.", "A provider handover preserves identifiers but does not silently retain previous credentials." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "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." }, "decisions": [ { "concept": "Cross-client composition", "disposition": "accepted", "rationale": "Own only graph relationships and master mappings; preserve referenced model boundaries." }, { "concept": "Operational enforcement", "disposition": "deferred", "rationale": "Publication does not implement adapters, IAM or nested runtime schemas." } ], "publicationHolds": [ "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." ], "deferredResearch": [ "Executable nested schemas and tenant-isolation negative fixtures", "Versioned CMDB/Redfish/Jira adapters and operational readback tests" ] }, "statistics": { "sources": 6, "bundles": 4, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 4 } }