{ "format": "vercy-world-model-candidate/v1", "contourId": "EM-TEC-02", "modelId": "WM-SFT-002", "registryId": "vr.wm-sft-002", "name": "Software System / Business Application", "version": "0.1.0-candidate.2", "entryKind": "operator-software-aggregate", "status": "research-candidate-description-pending-registry-row", "canonicalPublishable": false, "nameDecision": { "priorRegistryName": "Deployed System", "recommendedForm": "Software System and Business Application", "decisionStatus": "owner-decision-pending", "recordedAt": "2026-09-29", "authorityRequired": "registry owner" }, "purpose": "Describe the proposed operator-governed logical software-system, business-application and effective-dated usage boundary for the reserved slot without changing the registry row or claiming canonical completion.", "definitions": { "installation": "Derived current WM-SFT-009 deployment occurrence × operator-controlled WM-SFT-010 runtime environment; no stored identity.", "dependency": "Integration between independently owned products or systems without one owner and coordinated boundary.", "restricted": "Still identifiable and resolvable but unavailable for ordinary new usage while remediation or governance restriction is active." }, "mastership": [ { "layer": "vendor product and release", "master": "WM-SFT-001", "writer": "producer catalogue" }, { "layer": "software system, business application, placement, promotion and usage", "master": "WM-SFT-002", "writer": "operating organization software catalogue or CMDB" }, { "layer": "deployment occurrence", "master": "WM-SFT-009", "writer": "deployment ledger or CI/CD" }, { "layer": "runtime environment", "master": "WM-SFT-010", "writer": "operator platform inventory or CMDB" }, { "layer": "purchased entitlement", "master": "identifier-unassigned candidate", "writer": "software-asset-management or procurement authority" } ], "boundary": { "owns": [ "stable operator SoftwareSystem identity and enumerated boundary", "stable BusinessApplication identity and purpose", "effective-dated ApplicationUsage", "ModulePlacement and explicit ApplicationPromotion records" ], "delegates": [ "vendor product and release identity to WM-SFT-001", "deployment occurrence to WM-SFT-009", "runtime environment to WM-SFT-010", "purchased entitlement to the identifier-unassigned candidate" ], "excludes": [ "vendor product catalogue and release lifecycle", "licence and entitlement lifecycle", "deployment execution and runtime health", "minted Installation identity" ] }, "objects": { "SoftwareSystem": { "identity": [ "softwareSystemId" ], "required": [ "name", "ownerRef", "containedReleaseRefs", "criticality", "status", "provenance" ], "minimumCardinality": { "containedReleaseRefs": 1 }, "optional": [ "successorRef", "tombstoneRef" ], "lifecycle": [ "proposed", "approved", "active", "restricted", "retired", "superseded" ] }, "BusinessApplication": { "identity": [ "applicationKey" ], "keyAuthority": "operating organization software catalogue", "keyScope": "unique within operating organization", "required": [ "name", "businessPurpose", "ownerRef", "criticality", "status", "provenance" ], "optional": [ "systemRefs", "productRefs", "successorRef", "tombstoneRef" ], "lifecycle": [ "proposed", "approved", "active", "restricted", "retired", "superseded" ] }, "ModulePlacement": { "identity": [ "modulePlacementId" ], "required": [ "moduleRef", "containerRef", "effectiveFrom", "status", "provenance" ], "optional": [ "effectiveTo", "successorRef", "tombstoneRef" ], "lifecycle": [ "proposed", "active", "retired", "superseded" ] }, "ApplicationPromotion": { "identity": [ "applicationPromotionId" ], "required": [ "originPlacementRef", "resultingApplicationKey", "decisionRef", "effectiveFrom", "status", "provenance" ], "optional": [ "supersededByRef", "tombstoneRef" ], "lifecycle": [ "proposed", "approved", "effective", "revoked", "superseded" ] }, "ApplicationUsage": { "identity": [ "applicationUsageId" ], "required": [ "applicationRef", "organizationalContextRef", "purpose", "deliveryMode", "validFrom", "status", "provenance" ], "deliveryModeValues": [ "installed", "vendor-hosted", "hybrid", "unknown" ], "optional": [ "validTo", "entitlementAllocationRef", "deploymentOccurrenceRefs", "runtimeEnvironmentRefs", "absentReason", "successorRef", "tombstoneRef" ], "lifecycle": [ "proposed", "active", "suspended", "ended", "superseded" ] } }, "relations": [ { "target": "WM-SFT-001", "relation": "REFERENCE", "purpose": "vendor product and release master" }, { "target": "WM-SFT-009", "relation": "REFERENCE", "purpose": "research-candidate reference only; child containment reading unresolved and no canonical relation approval claimed" }, { "target": "WM-SFT-010", "relation": "REFERENCE", "purpose": "research-candidate reference only; runtime specification missing" }, { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "research-candidate organizational-context reference; scope fit unverified" } ], "invariantRules": [ { "id": "EM-TEC-02.SS-01", "text": "Every SoftwareSystem has at least one contained release, an accountable owner, a system criticality and a status in its declared lifecycle." }, { "id": "EM-TEC-02.SS-02", "text": "Every BusinessApplication has an immutable applicationKey minted by the operating organization software-catalogue authority, unique within that operating organization, plus name, purpose, owner, criticality and lifecycle status." }, { "id": "EM-TEC-02.SS-03", "text": "Every ApplicationUsage has applicationRef, organizationalContextRef, purpose, deliveryMode, validFrom and status; entitlement and deployment/runtime references are optional evidence only." }, { "id": "EM-TEC-02.SS-04", "text": "ApplicationUsage remains valid with zero entitlement refs and zero deployment/runtime refs and is never derived from licence or installation." }, { "id": "EM-TEC-02.SS-05", "text": "deliveryMode is one of installed, vendor-hosted, hybrid or unknown; installed requires a resolvable deployment/runtime pair, vendor-hosted forbids an operator-local pair, and unknown records an explicit absent reason." }, { "id": "EM-TEC-02.SS-06", "text": "Installation is a derived view only: the pair of a current WM-SFT-009 deployment occurrence and its operator-controlled WM-SFT-010 runtime environment; it has no minted identifier." }, { "id": "EM-TEC-02.SS-07", "text": "A deployment occurrence is current only when its effective interval covers the query instant and no later successful superseding occurrence for the same target is effective." }, { "id": "EM-TEC-02.SS-08", "text": "Product-to-application and application-to-derived-installation mappings are many-to-many; one installation may support multiple applications and one application may have zero, one or many installations." }, { "id": "EM-TEC-02.SS-09", "text": "A regional deployment alone creates no product, system or application identity; a distinct system or application requires its own owner, enumerated boundary, purpose and criticality." }, { "id": "EM-TEC-02.SS-10", "text": "ModulePlacement records an operator placement independently of vendor module packaging; promotion requires a dated ApplicationPromotion with originPlacementRef and resultingApplicationKey." }, { "id": "EM-TEC-02.SS-11", "text": "ApplicationPromotion creates no product or deployment identity, preserves the originating placement and cannot reuse a parent application key." }, { "id": "EM-TEC-02.SS-12", "text": "A multi-product assembly earns SoftwareSystem identity only with one accountable owner, an enumerated contained release set, system criticality and coordinated change authority; integration alone is a dependency." }, { "id": "EM-TEC-02.SS-13", "text": "A product providing a runtime class remains WM-SFT-001; an operator-controlled execution context is WM-SFT-010, and vendor-hosted execution is not operator runtime by default." }, { "id": "EM-TEC-02.SS-14", "text": "Provenance on system, application, placement, promotion and usage states the creating authority and source evidence; product name, licence, deployment or region alone is forbidden provenance for minting system/application identity." }, { "id": "EM-TEC-02.SS-15", "text": "Legal lifecycle transitions are proposed→approved→active→restricted→active, active/restricted→retired, and any non-retired state→superseded; no other transition is valid." }, { "id": "EM-TEC-02.SS-16", "text": "Retired or superseded system, application, placement, promotion and usage identifiers remain resolvable through tombstone or successor references and are never recycled." }, { "id": "EM-TEC-02.SS-17", "text": "An active BusinessApplication may reference a retired SoftwareSystem only with an effective successor system reference or explicit detached-system justification." }, { "id": "EM-TEC-02.SS-18", "text": "WM-SFT-002 never masters vendor product, licence, deployment occurrence or runtime environment; each referenced layer retains exactly one named writer." }, { "id": "EM-TEC-02.SS-19", "text": "Name, status and timestamps may share a structural vocabulary, but SKU and edition remain product-only; purpose and usage remain WM-SFT-002-only; occurrence time remains deployment-only; platform and node remain runtime-only." }, { "id": "EM-TEC-02.SS-20", "text": "This candidate description does not become authoritative for the reserved slot until the registry row is amended and the shared N4 specification is partitioned." } ], "invariants": [ "Every SoftwareSystem has at least one contained release, an accountable owner, a system criticality and a status in its declared lifecycle.", "Every BusinessApplication has an immutable applicationKey minted by the operating organization software-catalogue authority, unique within that operating organization, plus name, purpose, owner, criticality and lifecycle status.", "Every ApplicationUsage has applicationRef, organizationalContextRef, purpose, deliveryMode, validFrom and status; entitlement and deployment/runtime references are optional evidence only.", "ApplicationUsage remains valid with zero entitlement refs and zero deployment/runtime refs and is never derived from licence or installation.", "deliveryMode is one of installed, vendor-hosted, hybrid or unknown; installed requires a resolvable deployment/runtime pair, vendor-hosted forbids an operator-local pair, and unknown records an explicit absent reason.", "Installation is a derived view only: the pair of a current WM-SFT-009 deployment occurrence and its operator-controlled WM-SFT-010 runtime environment; it has no minted identifier.", "A deployment occurrence is current only when its effective interval covers the query instant and no later successful superseding occurrence for the same target is effective.", "Product-to-application and application-to-derived-installation mappings are many-to-many; one installation may support multiple applications and one application may have zero, one or many installations.", "A regional deployment alone creates no product, system or application identity; a distinct system or application requires its own owner, enumerated boundary, purpose and criticality.", "ModulePlacement records an operator placement independently of vendor module packaging; promotion requires a dated ApplicationPromotion with originPlacementRef and resultingApplicationKey.", "ApplicationPromotion creates no product or deployment identity, preserves the originating placement and cannot reuse a parent application key.", "A multi-product assembly earns SoftwareSystem identity only with one accountable owner, an enumerated contained release set, system criticality and coordinated change authority; integration alone is a dependency.", "A product providing a runtime class remains WM-SFT-001; an operator-controlled execution context is WM-SFT-010, and vendor-hosted execution is not operator runtime by default.", "Provenance on system, application, placement, promotion and usage states the creating authority and source evidence; product name, licence, deployment or region alone is forbidden provenance for minting system/application identity.", "Legal lifecycle transitions are proposed→approved→active→restricted→active, active/restricted→retired, and any non-retired state→superseded; no other transition is valid.", "Retired or superseded system, application, placement, promotion and usage identifiers remain resolvable through tombstone or successor references and are never recycled.", "An active BusinessApplication may reference a retired SoftwareSystem only with an effective successor system reference or explicit detached-system justification.", "WM-SFT-002 never masters vendor product, licence, deployment occurrence or runtime environment; each referenced layer retains exactly one named writer.", "Name, status and timestamps may share a structural vocabulary, but SKU and edition remain product-only; purpose and usage remain WM-SFT-002-only; occurrence time remains deployment-only; platform and node remain runtime-only.", "This candidate description does not become authoritative for the reserved slot until the registry row is amended and the shared N4 specification is partitioned." ], "holds": [ "Registry owner must decide the final name form and amend the prior Deployed System row before this candidate describes the slot.", "The shared legacy N4 specification must be partitioned before WM-SFT-001 or WM-SFT-002 advances.", "WM-SFT-010 has no verified specification; derived installation remains non-executable.", "Containment versus reference for WM-SFT-009/010 parentage remains an explicit owner decision; child parent claims and ledger rows must be reconciled together.", "The registry owner_or_maintainer value producing organization contradicts the operator boundary and requires correction.", "WM-SFT-009 prose naming WM-SFT-002 as parent software product or service model becomes stale and requires correction.", "factor_overlap 0.09 with low priority_confidence must be recomputed against the published WM-SFT-001 draft including deployed-instance, hosting-environment and effective-configuration findings.", "WM-ORG-001, WM-SFT-010 and all relation scope fits remain unverified in this dossier.", "Purchased Licence / Entitlement remains identifier-unassigned.", "Grok returned conditional accept; the single frozen audit returned REVISE and was remediated once without rerun.", "ArchiMate, CSDM, SPDX, OpenTelemetry and Google SRE are alignment-only comparison tracks; no conformance is claimed.", "Package conversion and live conformance remain pending." ] }