Published

Program / Portfolio

vr.wm-act-029 · wm-act-029-program-portfolio

Represent a governed program or portfolio that coordinates or selects components to advance strategy and realize outcomes or value while preserving the identity and lifecycle of every component master.

World Models Activities and processes ACT.PGM

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Identity, profile, mandate and governance Defines the aggregate root and the authority under which it is governed.

Profile definition and identity

Pins the kind, identity, version and source lineage of the aggregate.

Program or portfolio definition, profile and neighbor boundary

Required profile discriminator, inclusion and exclusion tests, lifecycle vocabulary and distinctions from project, operation, product, campaign and strategy masters.

What identities, types, roles, scope, versions and explicit values define program or portfolio definition, profile and neighbor boundary? classification
Which authority, source, method, evidence, event time and knowledge time support program or portfolio definition, profile and neighbor boundary? provenance
How is program or portfolio definition, profile and neighbor boundary validated, accessed, changed, contested, corrected and retained? validation

Aggregate identifier, name, alias, version, source and lineage

Authoritative identifier, governed names and aliases, profile and schema versions, source system, predecessor, successor and duplicate assertions.

What identities, types, roles, scope, versions and explicit values define aggregate identifier, name, alias, version, source and lineage? identity
Which authority, source, method, evidence, event time and knowledge time support aggregate identifier, name, alias, version, source and lineage? provenance
How is aggregate identifier, name, alias, version, source and lineage validated, accessed, changed, contested, corrected and retained? validation

Mandate, ownership and governance

Records why the aggregate exists and who may direct, assure or change it.

Mandate, sponsor, owner, governing body, authority and jurisdiction

Mandate source, accountable owner, sponsor or portfolio owner, governing body, delegated authority, jurisdiction and effective interval.

What identities, types, roles, scope, versions and explicit values define mandate, sponsor, owner, governing body, authority and jurisdiction? authority
Which authority, source, method, evidence, event time and knowledge time support mandate, sponsor, owner, governing body, authority and jurisdiction? provenance
How is mandate, sponsor, owner, governing body, authority and jurisdiction validated, accessed, changed, contested, corrected and retained? validation

Governance model, decision rights, assurance, gates and accountability

Governance structure, role assignments, reserved decisions, thresholds, assurance plan, gates, escalation and accountability evidence.

What identities, types, roles, scope, versions and explicit values define governance model, decision rights, assurance, gates and accountability? authority
Which authority, source, method, evidence, event time and knowledge time support governance model, decision rights, assurance, gates and accountability? provenance
How is governance model, decision rights, assurance, gates and accountability validated, accessed, changed, contested, corrected and retained? validation

Strategy, scope, components and dependencies Connects the governed aggregate to strategy and to the components it coordinates or selects.

Strategy, objectives and scope

Defines strategic purpose, success conditions and the controlled boundary.

Strategy, policy, need, objective, alignment, thesis and priority

External strategy and policy references, evidenced need, objective hierarchy, alignment assertion, investment thesis, priority and trade-off.

What identities, types, roles, scope, versions and explicit values define strategy, policy, need, objective, alignment, thesis and priority? requirement
Which authority, source, method, evidence, event time and knowledge time support strategy, policy, need, objective, alignment, thesis and priority? provenance
How is strategy, policy, need, objective, alignment, thesis and priority validated, accessed, changed, contested, corrected and retained? validation

Scope, inclusion, exclusion, assumption, constraint, context and success

Declared scope, boundary criteria, assumptions, constraints, operating context, acceptance tests and success conditions.

What identities, types, roles, scope, versions and explicit values define scope, inclusion, exclusion, assumption, constraint, context and success? definition
Which authority, source, method, evidence, event time and knowledge time support scope, inclusion, exclusion, assumption, constraint, context and success? provenance
How is scope, inclusion, exclusion, assumption, constraint, context and success validated, accessed, changed, contested, corrected and retained? validation

Component membership and dependency

Represents membership without absorbing project, programme, product or operational masters.

Component identity, type, membership, basis, status and accountability

External component ID and type, membership assertion, admission basis, effective interval, status, component owner and source authority.

What identities, types, roles, scope, versions and explicit values define component identity, type, membership, basis, status and accountability? composition
Which authority, source, method, evidence, event time and knowledge time support component identity, type, membership, basis, status and accountability? provenance
How is component identity, type, membership, basis, status and accountability validated, accessed, changed, contested, corrected and retained? validation

Dependency, interface, shared change, sequencing, conflict and external relation

Typed component dependencies, interfaces, shared capabilities, change coupling, sequencing, conflicts, assumptions and external relationships.

What identities, types, roles, scope, versions and explicit values define dependency, interface, shared change, sequencing, conflict and external relation? relationship
Which authority, source, method, evidence, event time and knowledge time support dependency, interface, shared change, sequencing, conflict and external relation? provenance
How is dependency, interface, shared change, sequencing, conflict and external relation validated, accessed, changed, contested, corrected and retained? validation

Outcomes, benefits, roadmaps and transition Models intended change and how it is expected to become operational and produce measurable value.

Results chain and benefit realization

Defines the change logic and benefit ownership with measurable evidence.

Input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link

Typed results-chain nodes and links with intended or unintended direction, affected stakeholder, assumptions, dependencies, evidence and uncertainty.

What identities, types, roles, scope, versions and explicit values define input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link? relationship
Which authority, source, method, evidence, event time and knowledge time support input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link? provenance
How is input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link validated, accessed, changed, contested, corrected and retained? validation

Benefit owner, baseline, target, indicator, realization plan and attribution limit

Benefit or disbenefit owner, baseline, target, indicator, realization activity, forecast and actual period, method, contribution claim and causal limit.

What identities, types, roles, scope, versions and explicit values define benefit owner, baseline, target, indicator, realization plan and attribution limit? measurement
Which authority, source, method, evidence, event time and knowledge time support benefit owner, baseline, target, indicator, realization plan and attribution limit? provenance
How is benefit owner, baseline, target, indicator, realization plan and attribution limit validated, accessed, changed, contested, corrected and retained? validation

Roadmap, tranches and operating transition

Coordinates staged delivery and transfer into operational use.

Roadmap, tranche, wave, milestone, horizon, dependency and review point

Versioned roadmap, programme tranche or portfolio horizon, milestone, dependency, planned and actual interval, review point and forecast confidence.

What identities, types, roles, scope, versions and explicit values define roadmap, tranche, wave, milestone, horizon, dependency and review point? relationship
Which authority, source, method, evidence, event time and knowledge time support roadmap, tranche, wave, milestone, horizon, dependency and review point? provenance
How is roadmap, tranche, wave, milestone, horizon, dependency and review point validated, accessed, changed, contested, corrected and retained? validation

Transition, operating model, change adoption, readiness, handover and sustainment

Target operating model reference, readiness, affected groups, adoption, transition ownership, handover, operational acceptance and post-close sustainment.

What identities, types, roles, scope, versions and explicit values define transition, operating model, change adoption, readiness, handover and sustainment? lifecycle
Which authority, source, method, evidence, event time and knowledge time support transition, operating model, change adoption, readiness, handover and sustainment? provenance
How is transition, operating model, change adoption, readiness, handover and sustainment validated, accessed, changed, contested, corrected and retained? validation

Investment, resources, prioritization and control Governs allocation decisions and the constraints that affect delivery and value.

Investment, funding and capacity

References money and capacity without replacing their source systems.

Funding, budget, investment, cost, forecast, actual, commitment and value reference

Currency-qualified approved envelope and external funding, budget, contract, commitment, cost, forecast, actual and value references with valuation basis.

What identities, types, roles, scope, versions and explicit values define funding, budget, investment, cost, forecast, actual, commitment and value reference? measurement
Which authority, source, method, evidence, event time and knowledge time support funding, budget, investment, cost, forecast, actual, commitment and value reference? provenance
How is funding, budget, investment, cost, forecast, actual, commitment and value reference validated, accessed, changed, contested, corrected and retained? validation

Resource, capability, capacity, demand, allocation, utilization, gap and conflict

External resource or capability ID, time-bounded demand, capacity, assignment, utilization, shortage, contention and resolution decision.

What identities, types, roles, scope, versions and explicit values define resource, capability, capacity, demand, allocation, utilization, gap and conflict? composition
Which authority, source, method, evidence, event time and knowledge time support resource, capability, capacity, demand, allocation, utilization, gap and conflict? provenance
How is resource, capability, capacity, demand, allocation, utilization, gap and conflict validated, accessed, changed, contested, corrected and retained? validation

Selection, sequencing, risk and change control

Applies profile-specific prioritization and common control evidence.

Programme sequencing or portfolio selection, prioritization, balancing and reallocation

For programmes, dependency-led sequencing and coordination; for portfolios, criteria-based selection, ranking, balance, scenario and allocation decisions with rationale.

What identities, types, roles, scope, versions and explicit values define programme sequencing or portfolio selection, prioritization, balancing and reallocation? decision
Which authority, source, method, evidence, event time and knowledge time support programme sequencing or portfolio selection, prioritization, balancing and reallocation? provenance
How is programme sequencing or portfolio selection, prioritization, balancing and reallocation validated, accessed, changed, contested, corrected and retained? validation

Risk, issue, opportunity, dependency, change control, exception and assurance

External risk and issue references, aggregate exposure, owner, response, residual state, change request, impact, exception, assurance evidence and escalation.

What identities, types, roles, scope, versions and explicit values define risk, issue, opportunity, dependency, change control, exception and assurance? relationship
Which authority, source, method, evidence, event time and knowledge time support risk, issue, opportunity, dependency, change control, exception and assurance? provenance
How is risk, issue, opportunity, dependency, change control, exception and assurance validated, accessed, changed, contested, corrected and retained? validation

Lifecycle, decisions, performance and learning Preserves authorized state changes and source-qualified evidence of performance and value.

Lifecycle, membership and decision history

Records transitions and component changes without rewriting history.

Propose, authorize, start, pause, rebalance, terminate, close and supersede event

Typed transition, prior and next state, scope, actor, authority, rationale, event time, knowledge time, evidence and reversibility.

What identities, types, roles, scope, versions and explicit values define propose, authorize, start, pause, rebalance, terminate, close and supersede event? lifecycle
Which authority, source, method, evidence, event time and knowledge time support propose, authorize, start, pause, rebalance, terminate, close and supersede event? provenance
How is propose, authorize, start, pause, rebalance, terminate, close and supersede event validated, accessed, changed, contested, corrected and retained? validation

Component admission, removal, priority change, successor and history

Immutable membership or priority event, component, criteria version, alternatives, decision, effective interval, predecessor, successor and downstream effect.

What identities, types, roles, scope, versions and explicit values define component admission, removal, priority change, successor and history? lifecycle
Which authority, source, method, evidence, event time and knowledge time support component admission, removal, priority change, successor and history? provenance
How is component admission, removal, priority change, successor and history validated, accessed, changed, contested, corrected and retained? validation

Measurement, evaluation and learning

Separates metric definitions, observations, conclusions and learning.

Metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation

Metric ID and version, definition, formula, unit, dimensions, numerator and denominator, baseline, target, forecast, observation link, aggregation and deduplication.

What identities, types, roles, scope, versions and explicit values define metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation? classification
Which authority, source, method, evidence, event time and knowledge time support metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation? provenance
How is metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation validated, accessed, changed, contested, corrected and retained? validation

Performance observation, evaluation, health, variance, benefit review and lesson

Source dataset, period, observed value, quality, uncertainty, health rule, variance, evaluation method, benefit review, conclusion, decision, lesson and applicability.

What identities, types, roles, scope, versions and explicit values define performance observation, evaluation, health, variance, benefit review and lesson? evidence
Which authority, source, method, evidence, event time and knowledge time support performance observation, evaluation, health, variance, benefit review and lesson? provenance
How is performance observation, evaluation, health, variance, benefit review and lesson validated, accessed, changed, contested, corrected and retained? validation

Provenance, interoperability, access, retention and agent operation Makes every important claim attributable, exchangeable and governable throughout its information lifecycle.

Decision provenance, evaluation and crosswalk

Supports audit, evaluation and standards alignment without pretending semantic equivalence.

Decision, gate, exception, rationale, alternative, evidence, provenance and confidence

Decision identity, question, alternatives, criteria, rationale, authority, evidence, supporting and contradicting observations, confidence and PROV links.

What identities, types, roles, scope, versions and explicit values define decision, gate, exception, rationale, alternative, evidence, provenance and confidence? decision
Which authority, source, method, evidence, event time and knowledge time support decision, gate, exception, rationale, alternative, evidence, provenance and confidence? provenance
How is decision, gate, exception, rationale, alternative, evidence, provenance and confidence validated, accessed, changed, contested, corrected and retained? validation

ISO programme, portfolio and governance, results, Data Cube and PROV crosswalk

Pinned source and target versions, term and field mappings, profile guards, omissions, semantic conflicts and round-trip classification.

What identities, types, roles, scope, versions and explicit values define iso programme, portfolio and governance, results, data cube and prov crosswalk? authority
Which authority, source, method, evidence, event time and knowledge time support iso programme, portfolio and governance, results, data cube and prov crosswalk? provenance
How is iso programme, portfolio and governance, results, data cube and prov crosswalk validated, accessed, changed, contested, corrected and retained? validation

Access, retention and autonomous operation

Controls views, changes and disposition for people and agents.

Role view, access, purpose, disclosure, segregation, exception and audit

Purpose-bound role views, bundle or field scope, decision segregation, disclosure rule, exception authority, expiry and tamper-evident access log.

What identities, types, roles, scope, versions and explicit values define role view, access, purpose, disclosure, segregation, exception and audit? access
Which authority, source, method, evidence, event time and knowledge time support role view, access, purpose, disclosure, segregation, exception and audit? provenance
How is role view, access, purpose, disclosure, segregation, exception and audit validated, accessed, changed, contested, corrected and retained? validation

Retention, legal hold, disposition, tombstone, agent authority and safe automation

Retention class, trigger, hold, deletion eligibility, minimum tombstone, delegated agent scope, precondition, dry run, idempotency, expected revision and post-check. Exact schedules and tombstones are Vercy house policy unless Dimension law or policy overrides them.

What identities, types, roles, scope, versions and explicit values define retention, legal hold, disposition, tombstone, agent authority and safe automation? retention
Which authority, source, method, evidence, event time and knowledge time support retention, legal hold, disposition, tombstone, agent authority and safe automation? provenance
How is retention, legal hold, disposition, tombstone, agent authority and safe automation validated, accessed, changed, contested, corrected and retained? validation

Classifiers Filled

Family: World Models
Category: Activities and processes
Entry kind: aggregate
Navigation path: NAV.ACT.PGM
Domain: ACT.PGM
Industry: Cross-industry
Tags: programportfolioact.pgm

What it is Filled

Owns the program-or-portfolio root and lineage, required profile discriminator, mandate and governance, strategy alignment, aggregate scope, component membership and dependencies, outcome and benefit logic, roadmaps or horizons, aggregate assignments and allocation decisions, prioritization or sequencing, lifecycle, metrics and aggregate evaluation, projections, access and retention. Party, strategy, objective, project, program-as-component, product, operation, benefit, resource, budget, contract, risk, issue, decision, observation, dataset, policy and generic audit masters remain external.

In scope

Program or portfolio identity, profile, mandate, governance, strategy alignment, scope, component membership, dependencies and decision rights
Objectives, outputs, capabilities, outcomes, benefits, disbenefits, impacts, roadmaps, tranches or horizons, transition, resources, funding references, prioritization, balancing and controls
Authorization, component changes, start, pause, rebalance, termination, closure, metrics, observations, evaluation, learning, interoperability, access, retention and agent operations

Out of scope

Party, strategy, objective, project, product, operation, benefit, resource, budget, contract, risk, issue, decision, observation, dataset, policy or audit-log master lifecycle
Treating Program and Portfolio as synonyms, admitting an instance without a profile, or inferring outcome, benefit or causal impact from completion, spending or output alone
Implementing scheduling, portfolio optimization, financial accounting, procurement, workforce management, risk engines, analytics platforms or universal legal compliance and claiming full ISO conformance from public abstracts

Why it exists Filled

Distinguishing features Filled

Requires one profile: a programme coordinates related components for benefits, a portfolio selects and balances investments.
Holds aggregate scope and membership, while each project or operation keeps its own record.
Separates output, outcome, benefit and causal attribution; spending does not prove benefit.
Covers prioritisation and reallocation decisions that single projects do not have.

What robots and AI may and may not do Filled

Must not

Admit, remove or reprioritise components without governance approval.
Report a benefit as realized from completion or spend alone.
Change component data in the projects it aggregates.
Hide disbenefits or negative outcomes from reviews.
Create an aggregate root with an ambiguous profile.

Only with a human decision

Investment, prioritisation and reallocation decisions.
Starting, closing or changing the mandate of a programme or portfolio.

May

Aggregate status, cost and risk from component records for reporting.
Map dependencies and alignment to strategy objectives.
Model prioritisation scenarios for decision makers.
Flag components missing benefit evidence.

Moral aspects Filled

Portfolio choices allocate public or company resources and affect people who depend on the funded work.
Disbenefits often fall on groups who are not stakeholders in the decision.
Honest benefit reporting matters for accountability of public spending.

Who is affected

Beneficiaries and those bearing disbenefits
Staff of component projects
Sponsors, funders and taxpayers

Owners Filled

Steward

Dimension identity, owner, strategy, programme and portfolio governance authority, finance, risk, privacy and records stewards

Roles

Programme sponsor or portfolio owner: Own mandate, strategic alignment, authorization and accountable closure or continuation.
Programme or portfolio manager: Maintain boundary, components, coordination or selection logic, roadmap and current state.
Governing body or investment committee: Exercise reserved decisions, prioritization, allocation, gates and exceptions.
Component owner: Own the external component master, commitments, evidence and escalations.
Benefit and change owner: Own aggregate-scoped outcome definitions, adoption, baselines, targets and realization evidence without taking ownership of the external benefit master.
Finance, resource, risk and assurance stewards: Control source-qualified constraints, allocations, exposure and independent assurance.
Data, privacy and records steward: Control data quality, protected views, retention, holds, disposition and auditability.

Links to other meta-models Filled

references

Project, Program-as-component, Product, Operation and Campaign models - Resolve component masters while preserving their identity, lifecycle, authority and evidence.
Party, Role, Mandate, Strategy, Objective and Policy models - Resolve accountable actors, decision authority, governing context and strategic alignment.
Outcome, Benefit, Resource, Budget, Contract, Risk, Issue, Decision, Metric, Observation, Dataset and Audit models - Bind external masters to aggregate-scoped plans, allocations, controls, observations and evaluation without copying their lifecycle.

aligned

ISO 21500, ISO 21503, ISO 21504 and ISO 21505 - Project the declared programme or portfolio profile, context and governance with explicit public-source and conformance limits.
OECD results terminology, W3C PROV-O and RDF Data Cube - Project results chains, provenance and multidimensional performance observations with declared semantic loss.

neighbor

Program versus Portfolio - A program coordinates related components to deliver outcomes and realize benefits; a portfolio selects, prioritizes and balances investments aligned to strategy, and components need not be related. The root is shared only under a required profile and profile-specific rules.
Project / Component / Operation / Product - The aggregate owns membership and coordination or selection assertions, while each external component keeps its own purpose, owner, lifecycle, plan, resources and evidence.
Strategy / Objective / Policy - The aggregate records versioned alignment and contribution claims; authoritative strategy, objective and policy masters remain external.
Outcome / Benefit / Disbenefit / Impact - The aggregate owns its results logic and realization plan, while observed results and benefit masters remain source-qualified and completion does not establish causation.
Finance / Resource / Risk / Decision / Observation - The aggregate owns scoped assignments, rankings, allocations, control and evaluation views; source systems retain authoritative transactions, capacities, risks, decisions and observations.

parent

WM-ACT-005

contains

WM-ACT-005

What else AI and robots need to interact with it Filled

Sources Filled

ISO 21500:2021 Project, programme and portfolio management - Context and concepts - International Organization for Standardization
ISO 21503:2022 Project, programme and portfolio management - Guidance on programme management - International Organization for Standardization
ISO 21504:2022 Project, programme and portfolio management - Guidance on portfolio management - International Organization for Standardization
ISO 21505:2017 Project, programme and portfolio management - Guidance on governance - International Organization for Standardization
ISO 21502:2020 Project, programme and portfolio management - Guidance on project management - International Organization for Standardization
Government Functional Standard GovS 002: Project Delivery - UK Government Project Delivery and Cabinet Office
Guide for Effective Benefits Management in Major Projects - UK Infrastructure and Projects Authority
Glossary of Key Terms in Evaluation and Results-Based Management for Sustainable Development, Second Edition - Organisation for Economic Co-operation and Development
Effective Results Frameworks for Sustainable Development - Organisation for Economic Co-operation and Development
PROV-O: The PROV Ontology - World Wide Web Consortium
The RDF Data Cube Vocabulary - World Wide Web Consortium
Date and Time on the Internet: Timestamps - Internet Engineering Task Force
The Standard for Portfolio Management, Fourth Edition - Project Management Institute
Disposing of records - The National Archives, United Kingdom
NIST Privacy Framework - National Institute of Standards and Technology

Open questions

Obtain licensed clause-level text of ISO 21500, 21502, 21503, 21504 and 21505 and re-derive the programme-versus-portfolio discriminator, governance and component definitions against normative clauses rather than catalogue abstracts.
Cross-validate the profile discriminator and the selection-versus-sequencing split against at least one non-ISO practice standard family so the boundary does not rest on a single standards body.
Acquire a records-management authority and a privacy or access-control authority to ground the retention class, legal hold, tombstone, purpose-bound view and minimum-necessary disclosure rules that are currently unsourced.
Close the stakeholder engagement, communication and reporting coverage gap, which appears only incidentally as affected groups and affected stakeholder inside the transition and results-chain findings.
Replace the forty-eight boilerplate provenance and validation questions with finding-specific probes, since their identical wording gives no discriminating research signal across twenty-four findings.
Assess RFC 9557 additional-information suffixes against the RFC 3339 timestamp rule and the separation of planned, decision, event, effective, observation, ingestion and knowledge times.
Collect implementation evidence on whether one profiled root or two separate Programme and Portfolio models is safer, and record the trigger that would force the split.
Reconcile the campaign, product and operation neighbor boundaries with the sibling subject models that own those masters, and attach source refs to each asserted distinction.
Attempt one bounded supplemental Grok review pass under the record-and-continue policy so the reviewable-draft hold can eventually be lifted by a genuinely independent provider.
No successful independent Claude or Grok result was available; program-management, portfolio-management, finance, benefits-attribution, regional and sector review is required before canonical promotion.
No approved relation rows were supplied; the registry Project parent link and proposed strategy, component, benefit, finance, risk, decision, observation, policy and audit links remain holds.
The combined package requires profile-specific validation and may be split into separate Program and Portfolio models if implementation evidence shows unsafe ambiguity.
Full ISO text was not freely available; the package uses official abstracts and public-authority guidance and therefore needs licensed clause-level conformity review before any claim of ISO conformance.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-act-029-program-portfolio/spec.yaml, ver-cy/world-models/card-supplements/wm-act-029-program-portfolio.json