{ "format": "vercy-enterprise-profile-candidate/v1", "contourId": "EM-WRK-04", "name": "Enterprise Portfolio Selection and Allocation", "decision": "PROFILE", "newRuntimeId": false, "bases": [ "WM-ACT-029", "WM-ACT-005", "WM-ACT-030", "WM-ECO-012", "WM-KNW-011", "WM-KNW-010", "WM-ACT-024", "WM-REC-010" ], "constraints": [ "Portfolio profiles WM-ACT-029 with exactly one discriminator drawn from {Program, Portfolio}; ambiguity or absence fails validation, profile change is supersession with new identity, and enforcement remains suspended pending token normalization in WM-ACT-029.", "PortfolioComponent, Prioritization, InvestmentAllocation, PortfolioScenario and ApprovedCompositionAndAllocationBaseline are addressable effective-dated portfolio-owned releases; the baseline is a distinct release, never a mutable designation on a scenario.", "The Portfolio profile disables, and may never assert, Program-derived delivery coordination, joint-outcome or benefit-hypothesis semantics, exclusive child-set or exclusive-owner ownership, component-to-portfolio rollup of plan, cost, actuals or benefit, mandatory component relatedness, and single-owner funding. Any WM-ACT-029 clause binding these at aggregate level blocks the profile until an explicit profile-level negation is recorded in the base.", "Membership never transfers component mastership and one component may belong to multiple portfolios with independently declared shares.", "Portfolio allocation is intent within an approved envelope and remains distinct from authority, commitment, actual and component funding.", "Every InvestmentAllocation declares shareBasis, enumerated {capital, cost, capacity, headcount}, with no default.", "Scenario is an immutable hypothesis release and becomes no baseline without a separate authorized decision and issued record.", "An approval decision attaches to exactly one PortfolioScenario release; the rationale, decision occurrence and issued record are external and referenced by the resulting baseline release, never absorbed into it.", "Rebalance creates successor composition and allocation releases and preserves prior criteria, ranking, allocation, scenario, baseline and decision history.", "Upstream cancellation, split, merge or re-mastership of a component ends affected memberships prospectively at the recorded effective instant, terminates forward allocation intent, and mutates no released Prioritization, InvestmentAllocation, PortfolioScenario or baseline; a split or re-mastership requires new membership assertions for each successor master and no automatic share inheritance.", "A profile whose base pins are unverified supports no conformance, installability or publication claim." ], "candidateRevision": 3, "status": "provider-reconciled-audited-remediated-allocation-held", "canonicalPublishable": false, "installable": false, "installabilityClaim": "none", "publicationReadinessClaim": "none", "basePins": [ { "modelId": "WM-ACT-029", "version": null, "digestAlgorithm": "sha256", "contentDigest": null, "pinState": "unverified" }, { "modelId": "WM-ACT-005", "version": null, "digestAlgorithm": "sha256", "contentDigest": null, "pinState": "unverified" }, { "modelId": "WM-ACT-030", "version": null, "digestAlgorithm": "sha256", "contentDigest": null, "pinState": "unverified" }, { "modelId": "WM-ECO-012", "version": null, "digestAlgorithm": "sha256", "contentDigest": null, "pinState": "unverified" }, { "modelId": "WM-KNW-011", "version": null, "digestAlgorithm": "sha256", "contentDigest": null, "pinState": "unverified" }, { "modelId": "WM-KNW-010", "version": null, "digestAlgorithm": "sha256", "contentDigest": null, "pinState": "unverified" }, { "modelId": "WM-ACT-024", "version": null, "digestAlgorithm": "sha256", "contentDigest": null, "pinState": "unverified" }, { "modelId": "WM-REC-010", "version": null, "digestAlgorithm": "sha256", "contentDigest": null, "pinState": "unverified" } ], "constraintRules": [ { "id": "WRK04-PROFILE-CONSTRAINT-001", "rule": "Portfolio profiles WM-ACT-029 with exactly one discriminator drawn from {Program, Portfolio}; ambiguity or absence fails validation, profile change is supersession with new identity, and enforcement remains suspended pending token normalization in WM-ACT-029." }, { "id": "WRK04-PROFILE-CONSTRAINT-002", "rule": "PortfolioComponent, Prioritization, InvestmentAllocation, PortfolioScenario and ApprovedCompositionAndAllocationBaseline are addressable effective-dated portfolio-owned releases; the baseline is a distinct release, never a mutable designation on a scenario." }, { "id": "WRK04-PROFILE-CONSTRAINT-003", "rule": "The Portfolio profile disables, and may never assert, Program-derived delivery coordination, joint-outcome or benefit-hypothesis semantics, exclusive child-set or exclusive-owner ownership, component-to-portfolio rollup of plan, cost, actuals or benefit, mandatory component relatedness, and single-owner funding. Any WM-ACT-029 clause binding these at aggregate level blocks the profile until an explicit profile-level negation is recorded in the base." }, { "id": "WRK04-PROFILE-CONSTRAINT-004", "rule": "Membership never transfers component mastership and one component may belong to multiple portfolios with independently declared shares." }, { "id": "WRK04-PROFILE-CONSTRAINT-005", "rule": "Portfolio allocation is intent within an approved envelope and remains distinct from authority, commitment, actual and component funding." }, { "id": "WRK04-PROFILE-CONSTRAINT-006", "rule": "Every InvestmentAllocation declares shareBasis, enumerated {capital, cost, capacity, headcount}, with no default." }, { "id": "WRK04-PROFILE-CONSTRAINT-007", "rule": "Scenario is an immutable hypothesis release and becomes no baseline without a separate authorized decision and issued record." }, { "id": "WRK04-PROFILE-CONSTRAINT-008", "rule": "An approval decision attaches to exactly one PortfolioScenario release; the rationale, decision occurrence and issued record are external and referenced by the resulting baseline release, never absorbed into it." }, { "id": "WRK04-PROFILE-CONSTRAINT-009", "rule": "Rebalance creates successor composition and allocation releases and preserves prior criteria, ranking, allocation, scenario, baseline and decision history." }, { "id": "WRK04-PROFILE-CONSTRAINT-010", "rule": "Upstream cancellation, split, merge or re-mastership of a component ends affected memberships prospectively at the recorded effective instant, terminates forward allocation intent, and mutates no released Prioritization, InvestmentAllocation, PortfolioScenario or baseline; a split or re-mastership requires new membership assertions for each successor master and no automatic share inheritance." }, { "id": "WRK04-PROFILE-CONSTRAINT-011", "rule": "A profile whose base pins are unverified supports no conformance, installability or publication claim." } ], "objects": { "PrioritizationRelease": { "requiredPins": [ "selectionCriteriaSetVersionRef", "weightingSchemeVersionRef", "observationAuthorityRef", "observationPeriod", "candidatePopulationRef", "horizon", "priceBase", "metricRevisionRefs" ] }, "InvestmentAllocation": { "required": [ "componentRef", "shareOrAmount", "shareBasis", "effectiveInterval" ], "vocabularies": { "shareBasis": [ "capital", "cost", "capacity", "headcount" ] } }, "ApprovedCompositionAndAllocationBaseline": { "identity": "portfolio-owned release identity", "required": [ "portfolioScenarioRef", "decisionRationaleRef", "decisionOccurrenceRef", "issuedRecordRef" ] } }, "invariants": [ { "id": "WRK04-PROFILE-INV-001", "rule": "Exactly one discriminator value is present, drawn from {Program, Portfolio}; enforcement is suspended pending token normalization in WM-ACT-029." }, { "id": "WRK04-PROFILE-INV-002", "rule": "Portfolio components need not be related and membership implies no Program semantics." }, { "id": "WRK04-PROFILE-INV-003", "rule": "Membership never transfers component mastership or cascades portfolio lifecycle state." }, { "id": "WRK04-PROFILE-INV-004", "rule": "One component may belong to multiple portfolios and conflicting ranks may remain unreconciled." }, { "id": "WRK04-PROFILE-INV-005", "rule": "Criteria, weighting, observations and ranking releases remain distinct." }, { "id": "WRK04-PROFILE-INV-006", "rule": "Rank is release-scoped and never intrinsic to work." }, { "id": "WRK04-PROFILE-INV-007", "rule": "Rankings are comparable only when criteria-set version, weighting-scheme version, observation authority, observation period, candidate population, horizon, price base and metric revisions are identical; conflicting ranks for one component across portfolios are permitted and are not reconciled here." }, { "id": "WRK04-PROFILE-INV-008", "rule": "A strategic-alignment contribution claim is owned by the prioritization release, references WM-KNW-011, and is never written onto a criteria set, a scenario or a component master; it asserts no causal or realized benefit." }, { "id": "WRK04-PROFILE-INV-009", "rule": "Portfolio allocation is distinct from authority, commitment, actual and component funding." }, { "id": "WRK04-PROFILE-INV-010", "rule": "Declared shares for one component across portfolios need not sum to 1.0; no completeness, exclusivity or total-cost coverage may be inferred from the declared shares." }, { "id": "WRK04-PROFILE-INV-011", "rule": "Accounting actuals, capacity consumption, outcomes and benefit realization are never derived, apportioned or summed from allocation shares." }, { "id": "WRK04-PROFILE-INV-012", "rule": "Source-side non-exceedance and residual reconciliation are external reconciliation obligations against the unallocated Funding Source referent; enforcement is suspended pending its allocation, and oversubscription is surfaced as a flagged scenario condition, never as an implicit transfer of authority, cash or ownership." }, { "id": "WRK04-PROFILE-INV-013", "rule": "A scenario is neither an actual nor an approved baseline; baseline approval creates a distinct immutable release through the decision triad." }, { "id": "WRK04-PROFILE-INV-014", "rule": "Alignment does not prove causal or realized benefit." }, { "id": "WRK04-PROFILE-INV-015", "rule": "Rebalance creates successors and preserves immutable history." }, { "id": "WRK04-PROFILE-INV-016", "rule": "Unverified base pins support no conformance, installability or publication claim." } ], "holds": [ "Selection Criteria Set remains identifier-unassigned; no identifier may be guessed.", "Funding Source referent is unallocated; source non-exceedance is non-enforceable and no funding-integrity claim is supported.", "Provider divergence unresolved: baseline-as-distinct-release (Claude, local synthesis) versus baseline-as-scenario-designation (Grok). Reconciled in favour of a distinct release; not verified against WM-ACT-029.", "WM-ACT-029 discriminator token is inconsistent across name, naming rule and identity strategies; enforcement is suspended pending normalization.", "WM-ACT-029 access scopes cannot express field-level rules assumed by its default and audit clauses.", "WM-ACT-029 all-covered checklist is contradicted by its own omissions.", "Frozen relation contracts are empty and relation rows remain unapproved.", "Standards support is abstract-level only and retention/access rules are unsourced house policy.", "All base pins are unverified; reused bases remain non-canonical single-provider drafts.", "WM-ACT-029 parent/containment and WM-ACT-030 parent conflicts remain unresolved.", "Independent provider review and the single frozen semantic audit are complete; no further provider run is admissible.", "No conformance, installability or publication-readiness claim is made." ] }