# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T05:47:45Z", "synthesisSha256": "563b0f71214287d6b4e6d4ed7e4e786749b07272494cfd61d8282d288e14dd84", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-029", "registryId": "vr.wm-act-029", "name": "Program / Portfolio", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.PGM" ], "tags": [ "program", "portfolio", "act.pgm" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-029-program-portfolio/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-029", "model": { "registry_id": "vr.wm-act-029", "model_id": "WM-ACT-029", "name": "Program / Portfolio", "entry_kind": "aggregate", "purpose": "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.", "scope_statement": "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" ], "boundary_notes": [ { "neighbor": "Program versus Portfolio", "distinction": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-013" ] }, { "neighbor": "Project / Component / Operation / Product", "distinction": "The aggregate owns membership and coordination or selection assertions, while each external component keeps its own purpose, owner, lifecycle, plan, resources and evidence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005" ] }, { "neighbor": "Strategy / Objective / Policy", "distinction": "The aggregate records versioned alignment and contribution claims; authoritative strategy, objective and policy masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-009" ] }, { "neighbor": "Outcome / Benefit / Disbenefit / Impact", "distinction": "The aggregate owns its results logic and realization plan, while observed results and benefit masters remain source-qualified and completion does not establish causation.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011" ] }, { "neighbor": "Finance / Resource / Risk / Decision / Observation", "distinction": "The aggregate owns scoped assignments, rankings, allocations, control and evaluation views; source systems retain authoritative transactions, capacities, risks, decisions and observations.", "source_refs": [ "SRC-004", "SRC-006", "SRC-010", "SRC-011" ] } ] }, "sources": [ { "id": "SRC-001", "title": "ISO 21500:2021 Project, programme and portfolio management - Context and concepts", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/75704.html", "version_or_date": "ISO 21500:2021, Edition 2; official catalogue abstract only", "source_type": "standard", "primary_source": false, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Defines at abstract level the organizational context and underlying concepts shared by project, programme and portfolio management; it does not support a clause-level conformance claim." }, { "id": "SRC-002", "title": "ISO 21503:2022 Project, programme and portfolio management - Guidance on programme management", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/82868.html", "version_or_date": "ISO 21503:2022, Edition 2; official catalogue abstract only", "source_type": "standard", "primary_source": false, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Provides at abstract level terms, concepts, prerequisites, practices, roles and responsibilities for programme management; it does not support a clause-level conformance claim." }, { "id": "SRC-003", "title": "ISO 21504:2022 Project, programme and portfolio management - Guidance on portfolio management", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/82867.html", "version_or_date": "ISO 21504:2022, Edition 2; official catalogue abstract only", "source_type": "standard", "primary_source": false, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Provides at abstract level principles for project and programme portfolio management and requires adaptation to organizational context; it does not support a clause-level conformance claim." }, { "id": "SRC-004", "title": "ISO 21505:2017 Project, programme and portfolio management - Guidance on governance", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/63578.html", "version_or_date": "ISO 21505:2017, Edition 1; official catalogue abstract only", "source_type": "standard", "primary_source": false, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Describes at abstract level governance and assurance for projects, programmes and portfolios; it does not support a clause-level conformance claim." }, { "id": "SRC-005", "title": "ISO 21502:2020 Project, programme and portfolio management - Guidance on project management", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/74947.html", "version_or_date": "ISO 21502:2020, Edition 1; official catalogue abstract only", "source_type": "standard", "primary_source": false, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Provides at abstract level the project boundary needed to keep project masters distinct; it does not support a clause-level conformance claim." }, { "id": "SRC-006", "title": "Government Functional Standard GovS 002: Project Delivery", "organization": "UK Government Project Delivery and Cabinet Office", "url": "https://www.gov.uk/government/publications/project-delivery-functional-standard", "version_or_date": "Version 2.1, updated 17 September 2025", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Sets expectations for direction, governance, portfolio management, programme management, planning, controls and solution transition." }, { "id": "SRC-007", "title": "Guide for Effective Benefits Management in Major Projects", "organization": "UK Infrastructure and Projects Authority", "url": "https://assets.publishing.service.gov.uk/media/5a8210e1e5274a2e87dc0f71/Guide_for_Effective_Benefits_Management_in_Major_Projects.pdf", "version_or_date": "October 2017", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Distinguishes outputs, outcomes, benefits and disbenefits and describes identification, planning, tracking, realization and optimization across and after delivery." }, { "id": "SRC-008", "title": "Glossary of Key Terms in Evaluation and Results-Based Management for Sustainable Development, Second Edition", "organization": "Organisation for Economic Co-operation and Development", "url": "https://www.oecd.org/en/publications/glossary-of-key-terms-in-evaluation-and-results-based-management-for-sustainable-development-second-edition_632da462-en-fr-es.html", "version_or_date": "OECD Publishing, 2023", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Defines results chains, outputs, outcomes, impacts, indicators, evaluation terms and the limits of attribution." }, { "id": "SRC-009", "title": "Effective Results Frameworks for Sustainable Development", "organization": "Organisation for Economic Co-operation and Development", "url": "https://www.oecd.org/en/publications/effective-results-frameworks-for-sustainable-development_aaa4bb52-en.html", "version_or_date": "OECD Publishing, 2024", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Connects strategic intent, causal links, assumptions, risks, indicators, baselines, targets, data sources and means of verification." }, { "id": "SRC-010", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Defines entity, activity, agent, responsibility, derivation, revision, attribution and generation provenance." }, { "id": "SRC-011", "title": "The RDF Data Cube Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-data-cube/", "version_or_date": "W3C Recommendation, 16 January 2014", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Defines observations, measures, dimensions, attributes, slices and data-structure definitions for performance and benefit observations." }, { "id": "SRC-012", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002, updated by RFC 9557", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Defines seconds and explicit-offset timestamps for lifecycle events, decisions, measurements and knowledge time." }, { "id": "SRC-013", "title": "The Standard for Portfolio Management, Fourth Edition", "organization": "Project Management Institute", "url": "https://www.pmi.org/standards/for-portfolio-management", "version_or_date": "Fourth Edition, November 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Provides an independent standards-family check that portfolio management groups projects, programmes and other activities to meet strategic objectives." }, { "id": "SRC-014", "title": "Disposing of records", "organization": "The National Archives, United Kingdom", "url": "https://www.nationalarchives.gov.uk/information-management/manage-information/policy-process/disposal/", "version_or_date": "Official records-management guidance, accessed 2026-09-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Grounds retention policies, retention triggers and responsible disposition based on business, legal and historical requirements." }, { "id": "SRC-015", "title": "NIST Privacy Framework", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/privacy-framework", "version_or_date": "Privacy Framework 1.0; version 1.1 initial public draft available", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Grounds privacy-risk governance, purpose-aware profiles and managed data lifecycle operations including access, disclosure, retention and disposal." } ], "structure": { "bundles": [ { "id": "identity-profile-mandate-and-governance", "name": "Identity, profile, mandate and governance", "description": "Defines the aggregate root and the authority under which it is governed.", "rationale": "Every instance declares exactly one programme or portfolio profile; the shared root never erases their different purposes and invariants.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ], "layers": [ { "id": "profile-definition-and-identity", "name": "Profile definition and identity", "description": "Pins the kind, identity, version and source lineage of the aggregate.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "program-or-portfolio-definition-profile-and-neighbor-boundary", "name": "Program or portfolio definition, profile and neighbor boundary", "description": "Required profile discriminator, inclusion and exclusion tests, lifecycle vocabulary and distinctions from project, operation, product, campaign and strategy masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-013" ], "questions": [ { "id": "program-or-portfolio-definition-profile-and-neighbor-boundary-q01", "text": "What identities, types, roles, scope, versions and explicit values define program or portfolio definition, profile and neighbor boundary?", "kind": "classification", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "program-or-portfolio-definition-profile-and-neighbor-boundary-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support program or portfolio definition, profile and neighbor boundary?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "program-or-portfolio-definition-profile-and-neighbor-boundary-q03", "text": "How is program or portfolio definition, profile and neighbor boundary validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "program-or-portfolio-definition-profile-and-neighbor-boundary-data", "name": "Program or portfolio definition, profile and neighbor boundary data", "description": "Structured programme or portfolio data for program or portfolio definition, profile and neighbor boundary.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-013" ] } ], "artifacts": [ { "id": "program-or-portfolio-definition-profile-and-neighbor-boundary-record", "name": "Program or portfolio definition, profile and neighbor boundary record", "description": "Versioned evidence-bearing program or portfolio record for program or portfolio definition, profile and neighbor boundary with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus program-or-portfolio-definition-profile-and-neighbor-boundary assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "aggregate-identifier-name-alias-version-source-and-lineage", "name": "Aggregate identifier, name, alias, version, source and lineage", "description": "Authoritative identifier, governed names and aliases, profile and schema versions, source system, predecessor, successor and duplicate assertions.", "source_refs": [ "SRC-001", "SRC-010" ], "questions": [ { "id": "aggregate-identifier-name-alias-version-source-and-lineage-q01", "text": "What identities, types, roles, scope, versions and explicit values define aggregate identifier, name, alias, version, source and lineage?", "kind": "identity", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "aggregate-identifier-name-alias-version-source-and-lineage-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support aggregate identifier, name, alias, version, source and lineage?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "aggregate-identifier-name-alias-version-source-and-lineage-q03", "text": "How is aggregate identifier, name, alias, version, source and lineage validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "aggregate-identifier-name-alias-version-source-and-lineage-data", "name": "Aggregate identifier, name, alias, version, source and lineage data", "description": "Structured programme or portfolio data for aggregate identifier, name, alias, version, source and lineage.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-010" ] } ], "artifacts": [ { "id": "aggregate-identifier-name-alias-version-source-and-lineage-record", "name": "Aggregate identifier, name, alias, version, source and lineage record", "description": "Versioned evidence-bearing program or portfolio record for aggregate identifier, name, alias, version, source and lineage with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus aggregate-identifier-name-alias-version-source-and-lineage assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-001", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "mandate-ownership-and-governance", "name": "Mandate, ownership and governance", "description": "Records why the aggregate exists and who may direct, assure or change it.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "mandate-sponsor-owner-governing-body-authority-and-jurisdiction", "name": "Mandate, sponsor, owner, governing body, authority and jurisdiction", "description": "Mandate source, accountable owner, sponsor or portfolio owner, governing body, delegated authority, jurisdiction and effective interval.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "mandate-sponsor-owner-governing-body-authority-and-jurisdiction-q01", "text": "What identities, types, roles, scope, versions and explicit values define mandate, sponsor, owner, governing body, authority and jurisdiction?", "kind": "authority", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "mandate-sponsor-owner-governing-body-authority-and-jurisdiction-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support mandate, sponsor, owner, governing body, authority and jurisdiction?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "mandate-sponsor-owner-governing-body-authority-and-jurisdiction-q03", "text": "How is mandate, sponsor, owner, governing body, authority and jurisdiction validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "mandate-sponsor-owner-governing-body-authority-and-jurisdiction-data", "name": "Mandate, sponsor, owner, governing body, authority and jurisdiction data", "description": "Structured programme or portfolio data for mandate, sponsor, owner, governing body, authority and jurisdiction.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "mandate-sponsor-owner-governing-body-authority-and-jurisdiction-record", "name": "Mandate, sponsor, owner, governing body, authority and jurisdiction record", "description": "Versioned evidence-bearing program or portfolio record for mandate, sponsor, owner, governing body, authority and jurisdiction with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus mandate-sponsor-owner-governing-body-authority-and-jurisdiction assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "governance-model-decision-rights-assurance-gates-and-accountability", "name": "Governance model, decision rights, assurance, gates and accountability", "description": "Governance structure, role assignments, reserved decisions, thresholds, assurance plan, gates, escalation and accountability evidence.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "governance-model-decision-rights-assurance-gates-and-accountability-q01", "text": "What identities, types, roles, scope, versions and explicit values define governance model, decision rights, assurance, gates and accountability?", "kind": "authority", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "governance-model-decision-rights-assurance-gates-and-accountability-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support governance model, decision rights, assurance, gates and accountability?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "governance-model-decision-rights-assurance-gates-and-accountability-q03", "text": "How is governance model, decision rights, assurance, gates and accountability validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "governance-model-decision-rights-assurance-gates-and-accountability-data", "name": "Governance model, decision rights, assurance, gates and accountability data", "description": "Structured programme or portfolio data for governance model, decision rights, assurance, gates and accountability.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "governance-model-decision-rights-assurance-gates-and-accountability-record", "name": "Governance model, decision rights, assurance, gates and accountability record", "description": "Versioned evidence-bearing program or portfolio record for governance model, decision rights, assurance, gates and accountability with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus governance-model-decision-rights-assurance-gates-and-accountability assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "strategy-scope-components-and-dependencies", "name": "Strategy, scope, components and dependencies", "description": "Connects the governed aggregate to strategy and to the components it coordinates or selects.", "rationale": "Programme components are related through coordinated change and outcomes; portfolio components may be independent and are selected and balanced for strategic value.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "layers": [ { "id": "strategy-objectives-and-scope", "name": "Strategy, objectives and scope", "description": "Defines strategic purpose, success conditions and the controlled boundary.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-009" ], "findings": [ { "id": "strategy-policy-need-objective-alignment-thesis-and-priority", "name": "Strategy, policy, need, objective, alignment, thesis and priority", "description": "External strategy and policy references, evidenced need, objective hierarchy, alignment assertion, investment thesis, priority and trade-off.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-009" ], "questions": [ { "id": "strategy-policy-need-objective-alignment-thesis-and-priority-q01", "text": "What identities, types, roles, scope, versions and explicit values define strategy, policy, need, objective, alignment, thesis and priority?", "kind": "requirement", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "strategy-policy-need-objective-alignment-thesis-and-priority-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support strategy, policy, need, objective, alignment, thesis and priority?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "strategy-policy-need-objective-alignment-thesis-and-priority-q03", "text": "How is strategy, policy, need, objective, alignment, thesis and priority validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "strategy-policy-need-objective-alignment-thesis-and-priority-data", "name": "Strategy, policy, need, objective, alignment, thesis and priority data", "description": "Structured programme or portfolio data for strategy, policy, need, objective, alignment, thesis and priority.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "strategy-policy-need-objective-alignment-thesis-and-priority-record", "name": "Strategy, policy, need, objective, alignment, thesis and priority record", "description": "Versioned evidence-bearing program or portfolio record for strategy, policy, need, objective, alignment, thesis and priority with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus strategy-policy-need-objective-alignment-thesis-and-priority assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "scope-inclusion-exclusion-assumption-constraint-context-and-success", "name": "Scope, inclusion, exclusion, assumption, constraint, context and success", "description": "Declared scope, boundary criteria, assumptions, constraints, operating context, acceptance tests and success conditions.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "scope-inclusion-exclusion-assumption-constraint-context-and-success-q01", "text": "What identities, types, roles, scope, versions and explicit values define scope, inclusion, exclusion, assumption, constraint, context and success?", "kind": "definition", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "scope-inclusion-exclusion-assumption-constraint-context-and-success-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support scope, inclusion, exclusion, assumption, constraint, context and success?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "scope-inclusion-exclusion-assumption-constraint-context-and-success-q03", "text": "How is scope, inclusion, exclusion, assumption, constraint, context and success validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "scope-inclusion-exclusion-assumption-constraint-context-and-success-data", "name": "Scope, inclusion, exclusion, assumption, constraint, context and success data", "description": "Structured programme or portfolio data for scope, inclusion, exclusion, assumption, constraint, context and success.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "scope-inclusion-exclusion-assumption-constraint-context-and-success-record", "name": "Scope, inclusion, exclusion, assumption, constraint, context and success record", "description": "Versioned evidence-bearing program or portfolio record for scope, inclusion, exclusion, assumption, constraint, context and success with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus scope-inclusion-exclusion-assumption-constraint-context-and-success assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "component-membership-and-dependency", "name": "Component membership and dependency", "description": "Represents membership without absorbing project, programme, product or operational masters.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ], "findings": [ { "id": "component-identity-type-membership-basis-status-and-accountability", "name": "Component identity, type, membership, basis, status and accountability", "description": "External component ID and type, membership assertion, admission basis, effective interval, status, component owner and source authority.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-010" ], "questions": [ { "id": "component-identity-type-membership-basis-status-and-accountability-q01", "text": "What identities, types, roles, scope, versions and explicit values define component identity, type, membership, basis, status and accountability?", "kind": "composition", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "component-identity-type-membership-basis-status-and-accountability-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support component identity, type, membership, basis, status and accountability?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "component-identity-type-membership-basis-status-and-accountability-q03", "text": "How is component identity, type, membership, basis, status and accountability validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "component-identity-type-membership-basis-status-and-accountability-data", "name": "Component identity, type, membership, basis, status and accountability data", "description": "Structured programme or portfolio data for component identity, type, membership, basis, status and accountability.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-010" ] } ], "artifacts": [ { "id": "component-identity-type-membership-basis-status-and-accountability-record", "name": "Component identity, type, membership, basis, status and accountability record", "description": "Versioned evidence-bearing program or portfolio record for component identity, type, membership, basis, status and accountability with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus component-identity-type-membership-basis-status-and-accountability assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "dependency-interface-shared-change-sequencing-conflict-and-external-relation", "name": "Dependency, interface, shared change, sequencing, conflict and external relation", "description": "Typed component dependencies, interfaces, shared capabilities, change coupling, sequencing, conflicts, assumptions and external relationships.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "dependency-interface-shared-change-sequencing-conflict-and-external-relation-q01", "text": "What identities, types, roles, scope, versions and explicit values define dependency, interface, shared change, sequencing, conflict and external relation?", "kind": "relationship", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "dependency-interface-shared-change-sequencing-conflict-and-external-relation-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support dependency, interface, shared change, sequencing, conflict and external relation?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "dependency-interface-shared-change-sequencing-conflict-and-external-relation-q03", "text": "How is dependency, interface, shared change, sequencing, conflict and external relation validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "dependency-interface-shared-change-sequencing-conflict-and-external-relation-data", "name": "Dependency, interface, shared change, sequencing, conflict and external relation data", "description": "Structured programme or portfolio data for dependency, interface, shared change, sequencing, conflict and external relation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "dependency-interface-shared-change-sequencing-conflict-and-external-relation-record", "name": "Dependency, interface, shared change, sequencing, conflict and external relation record", "description": "Versioned evidence-bearing program or portfolio record for dependency, interface, shared change, sequencing, conflict and external relation with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus dependency-interface-shared-change-sequencing-conflict-and-external-relation assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "outcomes-benefits-roadmaps-and-transition", "name": "Outcomes, benefits, roadmaps and transition", "description": "Models intended change and how it is expected to become operational and produce measurable value.", "rationale": "Outputs, capabilities, outcomes, benefits, disbenefits and impacts are separate source-qualified assertions; delivery never proves realization or attribution.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ], "layers": [ { "id": "results-chain-and-benefit-realization", "name": "Results chain and benefit realization", "description": "Defines the change logic and benefit ownership with measurable evidence.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ], "findings": [ { "id": "input-activity-output-capability-outcome-benefit-disbenefit-impact-and-causal-link", "name": "Input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link", "description": "Typed results-chain nodes and links with intended or unintended direction, affected stakeholder, assumptions, dependencies, evidence and uncertainty.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "input-activity-output-capability-outcome-benefit-disbenefit-impact-and-causal-link-q01", "text": "What identities, types, roles, scope, versions and explicit values define input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link?", "kind": "relationship", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "input-activity-output-capability-outcome-benefit-disbenefit-impact-and-causal-link-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "input-activity-output-capability-outcome-benefit-disbenefit-impact-and-causal-link-q03", "text": "How is input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "input-activity-output-capability-outcome-benefit-disbenefit-impact-and-causal-link-data", "name": "Input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link data", "description": "Structured programme or portfolio data for input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "input-activity-output-capability-outcome-benefit-disbenefit-impact-and-causal-link-record", "name": "Input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link record", "description": "Versioned evidence-bearing program or portfolio record for input, activity, output, capability, outcome, benefit, disbenefit, impact and causal link with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus input-activity-output-capability-outcome-benefit-disbenefit-impact-and-causal-link assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "benefit-owner-baseline-target-indicator-realization-plan-and-attribution-limit", "name": "Benefit owner, baseline, target, indicator, realization plan and attribution limit", "description": "Benefit or disbenefit owner, baseline, target, indicator, realization activity, forecast and actual period, method, contribution claim and causal limit.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011" ], "questions": [ { "id": "benefit-owner-baseline-target-indicator-realization-plan-and-attribution-limit-q01", "text": "What identities, types, roles, scope, versions and explicit values define benefit owner, baseline, target, indicator, realization plan and attribution limit?", "kind": "measurement", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "benefit-owner-baseline-target-indicator-realization-plan-and-attribution-limit-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support benefit owner, baseline, target, indicator, realization plan and attribution limit?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "benefit-owner-baseline-target-indicator-realization-plan-and-attribution-limit-q03", "text": "How is benefit owner, baseline, target, indicator, realization plan and attribution limit validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "benefit-owner-baseline-target-indicator-realization-plan-and-attribution-limit-data", "name": "Benefit owner, baseline, target, indicator, realization plan and attribution limit data", "description": "Structured programme or portfolio data for benefit owner, baseline, target, indicator, realization plan and attribution limit.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011" ] } ], "artifacts": [ { "id": "benefit-owner-baseline-target-indicator-realization-plan-and-attribution-limit-record", "name": "Benefit owner, baseline, target, indicator, realization plan and attribution limit record", "description": "Versioned evidence-bearing program or portfolio record for benefit owner, baseline, target, indicator, realization plan and attribution limit with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus benefit-owner-baseline-target-indicator-realization-plan-and-attribution-limit assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "roadmap-tranches-and-operating-transition", "name": "Roadmap, tranches and operating transition", "description": "Coordinates staged delivery and transfer into operational use.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ], "findings": [ { "id": "roadmap-tranche-wave-milestone-horizon-dependency-and-review-point", "name": "Roadmap, tranche, wave, milestone, horizon, dependency and review point", "description": "Versioned roadmap, programme tranche or portfolio horizon, milestone, dependency, planned and actual interval, review point and forecast confidence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-012" ], "questions": [ { "id": "roadmap-tranche-wave-milestone-horizon-dependency-and-review-point-q01", "text": "What identities, types, roles, scope, versions and explicit values define roadmap, tranche, wave, milestone, horizon, dependency and review point?", "kind": "relationship", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "roadmap-tranche-wave-milestone-horizon-dependency-and-review-point-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support roadmap, tranche, wave, milestone, horizon, dependency and review point?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "roadmap-tranche-wave-milestone-horizon-dependency-and-review-point-q03", "text": "How is roadmap, tranche, wave, milestone, horizon, dependency and review point validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "roadmap-tranche-wave-milestone-horizon-dependency-and-review-point-data", "name": "Roadmap, tranche, wave, milestone, horizon, dependency and review point data", "description": "Structured programme or portfolio data for roadmap, tranche, wave, milestone, horizon, dependency and review point.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-012" ] } ], "artifacts": [ { "id": "roadmap-tranche-wave-milestone-horizon-dependency-and-review-point-record", "name": "Roadmap, tranche, wave, milestone, horizon, dependency and review point record", "description": "Versioned evidence-bearing program or portfolio record for roadmap, tranche, wave, milestone, horizon, dependency and review point with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus roadmap-tranche-wave-milestone-horizon-dependency-and-review-point assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "transition-operating-model-change-adoption-readiness-handover-and-sustainment", "name": "Transition, operating model, change adoption, readiness, handover and sustainment", "description": "Target operating model reference, readiness, affected groups, adoption, transition ownership, handover, operational acceptance and post-close sustainment.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ], "questions": [ { "id": "transition-operating-model-change-adoption-readiness-handover-and-sustainment-q01", "text": "What identities, types, roles, scope, versions and explicit values define transition, operating model, change adoption, readiness, handover and sustainment?", "kind": "lifecycle", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "transition-operating-model-change-adoption-readiness-handover-and-sustainment-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support transition, operating model, change adoption, readiness, handover and sustainment?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "transition-operating-model-change-adoption-readiness-handover-and-sustainment-q03", "text": "How is transition, operating model, change adoption, readiness, handover and sustainment validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "transition-operating-model-change-adoption-readiness-handover-and-sustainment-data", "name": "Transition, operating model, change adoption, readiness, handover and sustainment data", "description": "Structured programme or portfolio data for transition, operating model, change adoption, readiness, handover and sustainment.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "transition-operating-model-change-adoption-readiness-handover-and-sustainment-record", "name": "Transition, operating model, change adoption, readiness, handover and sustainment record", "description": "Versioned evidence-bearing program or portfolio record for transition, operating model, change adoption, readiness, handover and sustainment with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus transition-operating-model-change-adoption-readiness-handover-and-sustainment assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "investment-resources-prioritization-and-control", "name": "Investment, resources, prioritization and control", "description": "Governs allocation decisions and the constraints that affect delivery and value.", "rationale": "External finance, contract, workforce, resource, risk and issue masters remain authoritative; this aggregate owns scoped assignments, rankings, decisions and control views.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ], "layers": [ { "id": "investment-funding-and-capacity", "name": "Investment, funding and capacity", "description": "References money and capacity without replacing their source systems.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "findings": [ { "id": "funding-budget-investment-cost-forecast-actual-commitment-and-value-reference", "name": "Funding, budget, investment, cost, forecast, actual, commitment and value reference", "description": "Currency-qualified approved envelope and external funding, budget, contract, commitment, cost, forecast, actual and value references with valuation basis.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "funding-budget-investment-cost-forecast-actual-commitment-and-value-reference-q01", "text": "What identities, types, roles, scope, versions and explicit values define funding, budget, investment, cost, forecast, actual, commitment and value reference?", "kind": "measurement", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "funding-budget-investment-cost-forecast-actual-commitment-and-value-reference-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support funding, budget, investment, cost, forecast, actual, commitment and value reference?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "funding-budget-investment-cost-forecast-actual-commitment-and-value-reference-q03", "text": "How is funding, budget, investment, cost, forecast, actual, commitment and value reference validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "funding-budget-investment-cost-forecast-actual-commitment-and-value-reference-data", "name": "Funding, budget, investment, cost, forecast, actual, commitment and value reference data", "description": "Structured programme or portfolio data for funding, budget, investment, cost, forecast, actual, commitment and value reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "funding-budget-investment-cost-forecast-actual-commitment-and-value-reference-record", "name": "Funding, budget, investment, cost, forecast, actual, commitment and value reference record", "description": "Versioned evidence-bearing program or portfolio record for funding, budget, investment, cost, forecast, actual, commitment and value reference with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus funding-budget-investment-cost-forecast-actual-commitment-and-value-reference assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "resource-capability-capacity-demand-allocation-utilization-gap-and-conflict", "name": "Resource, capability, capacity, demand, allocation, utilization, gap and conflict", "description": "External resource or capability ID, time-bounded demand, capacity, assignment, utilization, shortage, contention and resolution decision.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "resource-capability-capacity-demand-allocation-utilization-gap-and-conflict-q01", "text": "What identities, types, roles, scope, versions and explicit values define resource, capability, capacity, demand, allocation, utilization, gap and conflict?", "kind": "composition", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "resource-capability-capacity-demand-allocation-utilization-gap-and-conflict-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support resource, capability, capacity, demand, allocation, utilization, gap and conflict?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "resource-capability-capacity-demand-allocation-utilization-gap-and-conflict-q03", "text": "How is resource, capability, capacity, demand, allocation, utilization, gap and conflict validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "resource-capability-capacity-demand-allocation-utilization-gap-and-conflict-data", "name": "Resource, capability, capacity, demand, allocation, utilization, gap and conflict data", "description": "Structured programme or portfolio data for resource, capability, capacity, demand, allocation, utilization, gap and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "resource-capability-capacity-demand-allocation-utilization-gap-and-conflict-record", "name": "Resource, capability, capacity, demand, allocation, utilization, gap and conflict record", "description": "Versioned evidence-bearing program or portfolio record for resource, capability, capacity, demand, allocation, utilization, gap and conflict with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus resource-capability-capacity-demand-allocation-utilization-gap-and-conflict assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "selection-sequencing-risk-and-change-control", "name": "Selection, sequencing, risk and change control", "description": "Applies profile-specific prioritization and common control evidence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "programme-sequencing-or-portfolio-selection-prioritization-balancing-and-reallocation", "name": "Programme sequencing or portfolio selection, prioritization, balancing and reallocation", "description": "For programmes, dependency-led sequencing and coordination; for portfolios, criteria-based selection, ranking, balance, scenario and allocation decisions with rationale.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "programme-sequencing-or-portfolio-selection-prioritization-balancing-and-reallocation-q01", "text": "What identities, types, roles, scope, versions and explicit values define programme sequencing or portfolio selection, prioritization, balancing and reallocation?", "kind": "decision", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "programme-sequencing-or-portfolio-selection-prioritization-balancing-and-reallocation-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support programme sequencing or portfolio selection, prioritization, balancing and reallocation?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "programme-sequencing-or-portfolio-selection-prioritization-balancing-and-reallocation-q03", "text": "How is programme sequencing or portfolio selection, prioritization, balancing and reallocation validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "programme-sequencing-or-portfolio-selection-prioritization-balancing-and-reallocation-data", "name": "Programme sequencing or portfolio selection, prioritization, balancing and reallocation data", "description": "Structured programme or portfolio data for programme sequencing or portfolio selection, prioritization, balancing and reallocation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "programme-sequencing-or-portfolio-selection-prioritization-balancing-and-reallocation-record", "name": "Programme sequencing or portfolio selection, prioritization, balancing and reallocation record", "description": "Versioned evidence-bearing program or portfolio record for programme sequencing or portfolio selection, prioritization, balancing and reallocation with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus programme-sequencing-or-portfolio-selection-prioritization-balancing-and-reallocation assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "risk-issue-opportunity-dependency-change-control-exception-and-assurance", "name": "Risk, issue, opportunity, dependency, change control, exception and assurance", "description": "External risk and issue references, aggregate exposure, owner, response, residual state, change request, impact, exception, assurance evidence and escalation.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "risk-issue-opportunity-dependency-change-control-exception-and-assurance-q01", "text": "What identities, types, roles, scope, versions and explicit values define risk, issue, opportunity, dependency, change control, exception and assurance?", "kind": "relationship", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "risk-issue-opportunity-dependency-change-control-exception-and-assurance-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support risk, issue, opportunity, dependency, change control, exception and assurance?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "risk-issue-opportunity-dependency-change-control-exception-and-assurance-q03", "text": "How is risk, issue, opportunity, dependency, change control, exception and assurance validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "risk-issue-opportunity-dependency-change-control-exception-and-assurance-data", "name": "Risk, issue, opportunity, dependency, change control, exception and assurance data", "description": "Structured programme or portfolio data for risk, issue, opportunity, dependency, change control, exception and assurance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "risk-issue-opportunity-dependency-change-control-exception-and-assurance-record", "name": "Risk, issue, opportunity, dependency, change control, exception and assurance record", "description": "Versioned evidence-bearing program or portfolio record for risk, issue, opportunity, dependency, change control, exception and assurance with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus risk-issue-opportunity-dependency-change-control-exception-and-assurance assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-decisions-performance-and-learning", "name": "Lifecycle, decisions, performance and learning", "description": "Preserves authorized state changes and source-qualified evidence of performance and value.", "rationale": "Proposal, authorization, forecast, target, actual observation, evaluation and decision are different immutable assertions with their own time and provenance.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ], "layers": [ { "id": "lifecycle-membership-and-decision-history", "name": "Lifecycle, membership and decision history", "description": "Records transitions and component changes without rewriting history.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-010", "SRC-012" ], "findings": [ { "id": "propose-authorize-start-pause-rebalance-terminate-close-and-supersede-event", "name": "Propose, authorize, start, pause, rebalance, terminate, close and supersede event", "description": "Typed transition, prior and next state, scope, actor, authority, rationale, event time, knowledge time, evidence and reversibility.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-010", "SRC-012" ], "questions": [ { "id": "propose-authorize-start-pause-rebalance-terminate-close-and-supersede-event-q01", "text": "What identities, types, roles, scope, versions and explicit values define propose, authorize, start, pause, rebalance, terminate, close and supersede event?", "kind": "lifecycle", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "propose-authorize-start-pause-rebalance-terminate-close-and-supersede-event-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support propose, authorize, start, pause, rebalance, terminate, close and supersede event?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "propose-authorize-start-pause-rebalance-terminate-close-and-supersede-event-q03", "text": "How is propose, authorize, start, pause, rebalance, terminate, close and supersede event validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "propose-authorize-start-pause-rebalance-terminate-close-and-supersede-event-data", "name": "Propose, authorize, start, pause, rebalance, terminate, close and supersede event data", "description": "Structured programme or portfolio data for propose, authorize, start, pause, rebalance, terminate, close and supersede event.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-010", "SRC-012" ] } ], "artifacts": [ { "id": "propose-authorize-start-pause-rebalance-terminate-close-and-supersede-event-record", "name": "Propose, authorize, start, pause, rebalance, terminate, close and supersede event record", "description": "Versioned evidence-bearing program or portfolio record for propose, authorize, start, pause, rebalance, terminate, close and supersede event with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus propose-authorize-start-pause-rebalance-terminate-close-and-supersede-event assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-010", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "component-admission-removal-priority-change-successor-and-history", "name": "Component admission, removal, priority change, successor and history", "description": "Immutable membership or priority event, component, criteria version, alternatives, decision, effective interval, predecessor, successor and downstream effect.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-010" ], "questions": [ { "id": "component-admission-removal-priority-change-successor-and-history-q01", "text": "What identities, types, roles, scope, versions and explicit values define component admission, removal, priority change, successor and history?", "kind": "lifecycle", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "component-admission-removal-priority-change-successor-and-history-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support component admission, removal, priority change, successor and history?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "component-admission-removal-priority-change-successor-and-history-q03", "text": "How is component admission, removal, priority change, successor and history validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "component-admission-removal-priority-change-successor-and-history-data", "name": "Component admission, removal, priority change, successor and history data", "description": "Structured programme or portfolio data for component admission, removal, priority change, successor and history.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-010" ] } ], "artifacts": [ { "id": "component-admission-removal-priority-change-successor-and-history-record", "name": "Component admission, removal, priority change, successor and history record", "description": "Versioned evidence-bearing program or portfolio record for component admission, removal, priority change, successor and history with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus component-admission-removal-priority-change-successor-and-history assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "measurement-evaluation-and-learning", "name": "Measurement, evaluation and learning", "description": "Separates metric definitions, observations, conclusions and learning.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "findings": [ { "id": "metric-definition-formula-unit-dimension-baseline-target-forecast-actual-and-aggregation", "name": "Metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation", "description": "Metric ID and version, definition, formula, unit, dimensions, numerator and denominator, baseline, target, forecast, observation link, aggregation and deduplication.", "source_refs": [ "SRC-007", "SRC-009", "SRC-011" ], "questions": [ { "id": "metric-definition-formula-unit-dimension-baseline-target-forecast-actual-and-aggregation-q01", "text": "What identities, types, roles, scope, versions and explicit values define metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation?", "kind": "classification", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "metric-definition-formula-unit-dimension-baseline-target-forecast-actual-and-aggregation-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "metric-definition-formula-unit-dimension-baseline-target-forecast-actual-and-aggregation-q03", "text": "How is metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "metric-definition-formula-unit-dimension-baseline-target-forecast-actual-and-aggregation-data", "name": "Metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation data", "description": "Structured programme or portfolio data for metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-009", "SRC-011" ] } ], "artifacts": [ { "id": "metric-definition-formula-unit-dimension-baseline-target-forecast-actual-and-aggregation-record", "name": "Metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation record", "description": "Versioned evidence-bearing program or portfolio record for metric definition, formula, unit, dimension, baseline, target, forecast, actual and aggregation with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus metric-definition-formula-unit-dimension-baseline-target-forecast-actual-and-aggregation assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-007", "SRC-009", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "performance-observation-evaluation-health-variance-benefit-review-and-lesson", "name": "Performance observation, evaluation, health, variance, benefit review and lesson", "description": "Source dataset, period, observed value, quality, uncertainty, health rule, variance, evaluation method, benefit review, conclusion, decision, lesson and applicability.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "performance-observation-evaluation-health-variance-benefit-review-and-lesson-q01", "text": "What identities, types, roles, scope, versions and explicit values define performance observation, evaluation, health, variance, benefit review and lesson?", "kind": "evidence", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "performance-observation-evaluation-health-variance-benefit-review-and-lesson-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support performance observation, evaluation, health, variance, benefit review and lesson?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "performance-observation-evaluation-health-variance-benefit-review-and-lesson-q03", "text": "How is performance observation, evaluation, health, variance, benefit review and lesson validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "performance-observation-evaluation-health-variance-benefit-review-and-lesson-data", "name": "Performance observation, evaluation, health, variance, benefit review and lesson data", "description": "Structured programme or portfolio data for performance observation, evaluation, health, variance, benefit review and lesson.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "performance-observation-evaluation-health-variance-benefit-review-and-lesson-record", "name": "Performance observation, evaluation, health, variance, benefit review and lesson record", "description": "Versioned evidence-bearing program or portfolio record for performance observation, evaluation, health, variance, benefit review and lesson with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus performance-observation-evaluation-health-variance-benefit-review-and-lesson assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "provenance-interoperability-access-retention-and-agent-operation", "name": "Provenance, interoperability, access, retention and agent operation", "description": "Makes every important claim attributable, exchangeable and governable throughout its information lifecycle.", "rationale": "Mappings are version-pinned and loss-aware; agent authority, access and disposition are policy-bound rather than inferred from technical capability.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ], "layers": [ { "id": "decision-provenance-evaluation-and-crosswalk", "name": "Decision provenance, evaluation and crosswalk", "description": "Supports audit, evaluation and standards alignment without pretending semantic equivalence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "findings": [ { "id": "decision-gate-exception-rationale-alternative-evidence-provenance-and-confidence", "name": "Decision, gate, exception, rationale, alternative, evidence, provenance and confidence", "description": "Decision identity, question, alternatives, criteria, rationale, authority, evidence, supporting and contradicting observations, confidence and PROV links.", "source_refs": [ "SRC-004", "SRC-006", "SRC-010" ], "questions": [ { "id": "decision-gate-exception-rationale-alternative-evidence-provenance-and-confidence-q01", "text": "What identities, types, roles, scope, versions and explicit values define decision, gate, exception, rationale, alternative, evidence, provenance and confidence?", "kind": "decision", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "decision-gate-exception-rationale-alternative-evidence-provenance-and-confidence-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support decision, gate, exception, rationale, alternative, evidence, provenance and confidence?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "decision-gate-exception-rationale-alternative-evidence-provenance-and-confidence-q03", "text": "How is decision, gate, exception, rationale, alternative, evidence, provenance and confidence validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "decision-gate-exception-rationale-alternative-evidence-provenance-and-confidence-data", "name": "Decision, gate, exception, rationale, alternative, evidence, provenance and confidence data", "description": "Structured programme or portfolio data for decision, gate, exception, rationale, alternative, evidence, provenance and confidence.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-010" ] } ], "artifacts": [ { "id": "decision-gate-exception-rationale-alternative-evidence-provenance-and-confidence-record", "name": "Decision, gate, exception, rationale, alternative, evidence, provenance and confidence record", "description": "Versioned evidence-bearing program or portfolio record for decision, gate, exception, rationale, alternative, evidence, provenance and confidence with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus decision-gate-exception-rationale-alternative-evidence-provenance-and-confidence assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-004", "SRC-006", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "iso-programme-portfolio-governance-results-data-cube-and-prov-crosswalk", "name": "ISO programme, portfolio and governance, results, Data Cube and PROV crosswalk", "description": "Pinned source and target versions, term and field mappings, profile guards, omissions, semantic conflicts and round-trip classification.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "iso-programme-portfolio-governance-results-data-cube-and-prov-crosswalk-q01", "text": "What identities, types, roles, scope, versions and explicit values define iso programme, portfolio and governance, results, data cube and prov crosswalk?", "kind": "authority", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "iso-programme-portfolio-governance-results-data-cube-and-prov-crosswalk-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support iso programme, portfolio and governance, results, data cube and prov crosswalk?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "iso-programme-portfolio-governance-results-data-cube-and-prov-crosswalk-q03", "text": "How is iso programme, portfolio and governance, results, data cube and prov crosswalk validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "iso-programme-portfolio-governance-results-data-cube-and-prov-crosswalk-data", "name": "ISO programme, portfolio and governance, results, Data Cube and PROV crosswalk data", "description": "Structured programme or portfolio data for iso programme, portfolio and governance, results, data cube and prov crosswalk.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "iso-programme-portfolio-governance-results-data-cube-and-prov-crosswalk-record", "name": "ISO programme, portfolio and governance, results, Data Cube and PROV crosswalk record", "description": "Versioned evidence-bearing program or portfolio record for iso programme, portfolio and governance, results, data cube and prov crosswalk with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus iso-programme-portfolio-governance-results-data-cube-and-prov-crosswalk assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "access-retention-and-autonomous-operation", "name": "Access, retention and autonomous operation", "description": "Controls views, changes and disposition for people and agents.", "source_refs": [ "SRC-004", "SRC-006", "SRC-010", "SRC-012" ], "findings": [ { "id": "role-view-access-purpose-disclosure-segregation-exception-and-audit", "name": "Role view, access, purpose, disclosure, segregation, exception and audit", "description": "Purpose-bound role views, bundle or field scope, decision segregation, disclosure rule, exception authority, expiry and tamper-evident access log.", "source_refs": [ "SRC-004", "SRC-006", "SRC-010", "SRC-012", "SRC-015" ], "questions": [ { "id": "role-view-access-purpose-disclosure-segregation-exception-and-audit-q01", "text": "What identities, types, roles, scope, versions and explicit values define role view, access, purpose, disclosure, segregation, exception and audit?", "kind": "access", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "role-view-access-purpose-disclosure-segregation-exception-and-audit-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support role view, access, purpose, disclosure, segregation, exception and audit?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "role-view-access-purpose-disclosure-segregation-exception-and-audit-q03", "text": "How is role view, access, purpose, disclosure, segregation, exception and audit validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "role-view-access-purpose-disclosure-segregation-exception-and-audit-data", "name": "Role view, access, purpose, disclosure, segregation, exception and audit data", "description": "Structured programme or portfolio data for role view, access, purpose, disclosure, segregation, exception and audit.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-010", "SRC-012", "SRC-015" ] } ], "artifacts": [ { "id": "role-view-access-purpose-disclosure-segregation-exception-and-audit-record", "name": "Role view, access, purpose, disclosure, segregation, exception and audit record", "description": "Versioned evidence-bearing program or portfolio record for role view, access, purpose, disclosure, segregation, exception and audit with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus role-view-access-purpose-disclosure-segregation-exception-and-audit assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-004", "SRC-006", "SRC-010", "SRC-012", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "retention-legal-hold-disposition-tombstone-agent-authority-and-safe-automation", "name": "Retention, legal hold, disposition, tombstone, agent authority and safe automation", "description": "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.", "source_refs": [ "SRC-004", "SRC-006", "SRC-010", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "retention-legal-hold-disposition-tombstone-agent-authority-and-safe-automation-q01", "text": "What identities, types, roles, scope, versions and explicit values define retention, legal hold, disposition, tombstone, agent authority and safe automation?", "kind": "retention", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "retention-legal-hold-disposition-tombstone-agent-authority-and-safe-automation-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support retention, legal hold, disposition, tombstone, agent authority and safe automation?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "retention-legal-hold-disposition-tombstone-agent-authority-and-safe-automation-q03", "text": "How is retention, legal hold, disposition, tombstone, agent authority and safe automation validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation and profile rules", "access and disclosure", "change and dispute", "lineage", "retention and disposition" ] } ], "data_elements": [ { "id": "retention-legal-hold-disposition-tombstone-agent-authority-and-safe-automation-data", "name": "Retention, legal hold, disposition, tombstone, agent authority and safe automation data", "description": "Structured programme or portfolio data for retention, legal hold, disposition, tombstone, agent authority and safe automation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-010", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "retention-legal-hold-disposition-tombstone-agent-authority-and-safe-automation-record", "name": "Retention, legal hold, disposition, tombstone, agent authority and safe automation record", "description": "Versioned evidence-bearing program or portfolio record for retention, legal hold, disposition, tombstone, agent authority and safe automation with authority, time, provenance and access marking.", "media_or_form": [ "logical program or portfolio assertion", "plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Aggregate identifier plus program-or-portfolio profile plus retention-legal-hold-disposition-tombstone-agent-authority-and-safe-automation assertion, artifact or event identifier; name, date, timestamp and digest never identify the aggregate alone.", "source_refs": [ "SRC-004", "SRC-006", "SRC-010", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-and-profile-aggregate", "name": "Register and profile aggregate", "description": "Establish identity, profile, boundary and source lineage.", "inputs": [ "programme or portfolio proposal", "authoritative source", "profile" ], "outputs": [ "versioned aggregate root" ], "preconditions": [ "identity, duplicate, profile and boundary rules validate" ], "effects": [ "a governed root exists without admitting components" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010" ] }, { "id": "authorize-mandate-and-governance", "name": "Authorize mandate and governance", "description": "Bind accountable authority, governance roles, decision rights and assurance.", "inputs": [ "aggregate root", "mandate", "governing actors", "policy" ], "outputs": [ "authorized governance release" ], "preconditions": [ "mandate, delegation, segregation, jurisdiction and gate controls validate" ], "effects": [ "the aggregate may be governed within explicit limits" ], "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "admit-or-remove-component", "name": "Admit or remove component", "description": "Append a source-qualified component membership decision.", "inputs": [ "aggregate", "external component", "criteria", "decision" ], "outputs": [ "membership event" ], "preconditions": [ "profile, eligibility, authority, effective interval and expected revision validate" ], "effects": [ "membership changes without absorbing or rewriting the component master" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "map-alignment-and-dependencies", "name": "Map alignment and dependencies", "description": "Connect strategy, objectives, components, interfaces and constraints.", "inputs": [ "strategy and objective refs", "components", "evidence" ], "outputs": [ "alignment and dependency graph release" ], "preconditions": [ "source, relation type, direction, validity, assumptions and contradictions validate" ], "effects": [ "coordination and selection reasoning becomes inspectable" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-009" ] }, { "id": "define-outcomes-and-benefit-realization", "name": "Define outcomes and benefit realization", "description": "Release a results chain and benefit or disbenefit realization plan.", "inputs": [ "need", "components", "stakeholders", "evidence" ], "outputs": [ "results framework and benefit plan" ], "preconditions": [ "result levels, owners, baselines, targets, methods, assumptions and causal limits validate" ], "effects": [ "intended change becomes measurable without asserting realization" ], "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011" ] }, { "id": "plan-roadmap-resources-and-transition", "name": "Plan roadmap, resources and transition", "description": "Coordinate tranches or horizons, capacity, milestones and operational adoption.", "inputs": [ "aggregate release", "components", "capacity", "constraints" ], "outputs": [ "roadmap and transition release" ], "preconditions": [ "dependencies, schedule, resources, readiness, ownership and acceptance validate" ], "effects": [ "staged work and adoption are planned without claiming completion" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-012" ] }, { "id": "prioritize-balance-sequence-and-reallocate", "name": "Prioritize, balance, sequence and reallocate", "description": "Apply the profile-appropriate decision method to components and resources.", "inputs": [ "components", "criteria and weights", "constraints", "scenarios" ], "outputs": [ "ranking, sequence or allocation decision" ], "preconditions": [ "programme sequencing or portfolio selection guard, authority, alternatives, evidence and expected revision validate" ], "effects": [ "approved priorities and allocation change with preserved rationale" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "transition-program-or-portfolio-lifecycle", "name": "Transition program or portfolio lifecycle", "description": "Append an authorized proposal, start, pause, rebalance, termination, closure or supersession event.", "inputs": [ "current revision", "transition", "authority", "evidence" ], "outputs": [ "lifecycle event and current-state projection" ], "preconditions": [ "profile transition table, gate, scope, reason, event time and downstream controls validate" ], "effects": [ "operating state changes without rewriting prior history" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-010", "SRC-012" ] }, { "id": "record-evaluate-and-review-performance", "name": "Record, evaluate and review performance", "description": "Attach source-qualified observations and method-bounded performance and benefit conclusions.", "inputs": [ "metric definitions", "source datasets", "evaluation method" ], "outputs": [ "observation, evaluation and review records" ], "preconditions": [ "formula, unit, dimensions, baseline, target, denominator, aggregation, quality and attribution limits validate" ], "effects": [ "decisions can use evidence without confusing outputs, outcomes, benefits or causation" ], "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] }, { "id": "project-validate-correct-retain-and-audit", "name": "Project, validate, correct, retain and audit", "description": "Produce a loss-aware view or execute governed correction, retention and audit operations.", "inputs": [ "aggregate revision", "target profile or policy", "purpose" ], "outputs": [ "projection, validation, correction, disposition or audit event" ], "preconditions": [ "identity, version, mapping loss, access, legal hold, minimum tombstone and post-checks validate" ], "effects": [ "programme or portfolio data remains interoperable and accountable under policy" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-010", "SRC-011", "SRC-012" ] } ], "composition": [ { "target": "Project, Program-as-component, Product, Operation and Campaign models", "relation": "REFERENCE", "purpose": "Resolve component masters while preserving their identity, lifecycle, authority and evidence.", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] }, { "target": "Party, Role, Mandate, Strategy, Objective and Policy models", "relation": "REFERENCE", "purpose": "Resolve accountable actors, decision authority, governing context and strategic alignment.", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] }, { "target": "Outcome, Benefit, Resource, Budget, Contract, Risk, Issue, Decision, Metric, Observation, Dataset and Audit models", "relation": "REFERENCE", "purpose": "Bind external masters to aggregate-scoped plans, allocations, controls, observations and evaluation without copying their lifecycle.", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] }, { "target": "ISO 21500, ISO 21503, ISO 21504 and ISO 21505", "relation": "ALIGN", "purpose": "Project the declared programme or portfolio profile, context and governance with explicit public-source and conformance limits.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ] }, { "target": "OECD results terminology, W3C PROV-O and RDF Data Cube", "relation": "ALIGN", "purpose": "Project results chains, provenance and multidimensional performance observations with declared semantic loss.", "required": false, "source_refs": [ "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, strategy, programme and portfolio governance authority, finance, risk, privacy and records stewards", "Programme-or-portfolio type, objective, benefit, indicator, lifecycle, decision, interoperability, access and retention registries", "Master mappings for parties, roles, strategies, projects, programmes, products, operations, benefits, resources, budgets, contracts, risks, issues, decisions, metrics, observations, policies and audit logs", "Authorization, component admission, prioritization, allocation, lifecycle, measurement, disclosure, retention and agent-operation policies" ], "namespace_guidance": "Mint stable IDs for aggregate roots, releases, memberships, assignments, decisions, events and aggregate-scoped assertions. Preserve authoritative external component and master-system identities; never use an aggregate name, date or digest as identity.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local programme, portfolio, strategy, benefit, metric and policy registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative source plus aggregate identifier, required program-or-portfolio profile and current lineage head, not by name, component list, objective, period or digest.", "Keep proposal, plan, forecast, target, release, observation, evaluation and decision as different assertion classes with source and time." ], "patch_rules": [ "Extensions declare target profile and finding, semantics, authority, lifecycle, finance, privacy, measurement and interoperability impact.", "Released mandates, memberships, allocations, plans, decisions and observations are immutable. Corrections and profile-safe changes create successors with preserved provenance.", "A program-to-portfolio or portfolio-to-program profile change is never an in-place update. It supersedes the aggregate with a new identity and an explicit derivation and migration record." ], "compatibility_rules": [ "Unknown additive fields may be ignored only when identity, profile, mandate, governance, components, decisions, outcomes, lifecycle, measurement and provenance remain intact.", "ISO, OECD, Data Cube and PROV mappings pin versions and declare omissions, semantic conflicts and round-trip limits." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system program or portfolio identifier qualified by source and aggregate class.", "Governed globally resolvable aggregate IRI under a controlled namespace.", "Dimension UUID when no authoritative or governed global identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; separate planned, decision, event, effective, observation, ingestion and knowledge times and preserve source precision.", "serial_naming_rule": "Use {aggregate-id}--{program-or-portfolio}--{component-or-root}--{artifact-kind}--{assertion-or-event-id}; never use name, date, timestamp or digest alone.", "integrity_rule": "Store digest, media type, aggregate and release binding, profile and source versions, authority, event and knowledge times, access marking and provenance." }, "policies": [ "Every root declares exactly one programme or portfolio profile; an ambiguous instance fails validation.", "Programmes coordinate related components for outcomes and benefits; portfolios select, prioritize and balance investments aligned to strategy, and their components need not be related.", "Output, capability, outcome, benefit, disbenefit, impact and causal attribution are separate attributable assertions; completion or spending does not prove benefit realization.", "Aggregate ownership does not transfer ownership of party, strategy, project, programme, product, operation, benefit, resource, budget, contract, risk, issue, decision, metric, observation, policy or audit masters.", "Agents may validate and project allowlisted data, but component admission or removal, authorization, reallocation, lifecycle transition, protected disclosure and destructive disposition require delegated authority and policy controls." ], "crud": { "read": [ "Resolve Dimension policy, aggregate identity and profile, lineage, mandate, governance, strategy, components, outcomes, current release and state, decisions, observations, provenance and access purpose." ], "create": [ "Record identity, profile, boundary, mandate, owner, governance, strategy alignment, components, results chain, benefit plan, metrics and provenance before authorization." ], "update": [ "Append membership, allocation, authorization, lifecycle, observation, evaluation, correction or supersession events with actor, authority, reason, event and knowledge time and expected revision; never overwrite released history." ], "delete": [ "Apply retention, legal-hold and audit policy; terminate live governance separately from removing eligible working copies, and preserve required lineage, decisions, observations and minimum tombstone evidence." ] }, "roles": [ { "name": "Programme sponsor or portfolio owner", "responsibilities": [ "Own mandate, strategic alignment, authorization and accountable closure or continuation." ] }, { "name": "Programme or portfolio manager", "responsibilities": [ "Maintain boundary, components, coordination or selection logic, roadmap and current state." ] }, { "name": "Governing body or investment committee", "responsibilities": [ "Exercise reserved decisions, prioritization, allocation, gates and exceptions." ] }, { "name": "Component owner", "responsibilities": [ "Own the external component master, commitments, evidence and escalations." ] }, { "name": "Benefit and change owner", "responsibilities": [ "Own aggregate-scoped outcome definitions, adoption, baselines, targets and realization evidence without taking ownership of the external benefit master." ] }, { "name": "Finance, resource, risk and assurance stewards", "responsibilities": [ "Control source-qualified constraints, allocations, exposure and independent assurance." ] }, { "name": "Data, privacy and records steward", "responsibilities": [ "Control data quality, protected views, retention, holds, disposition and auditability." ] } ], "access": { "default_rule": "Deny confidential strategy, investment options, bid data, person-level workforce data, security-sensitive dependencies, unpublished decisions and raw cross-component linkage; disclose purpose-bound minimum views under Dimension policy. Field-level redaction is a governed projection of an artifact, not a separate access scope.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Accountable owner, governing body, component owner, assurance, safety response, auditor, regulator or court access cites authority and remains minimum-necessary, time-limited and separately logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, aggregate, operation, policy, RFC 3339 time, release or affected fields, source revision and outcome without copying protected source data unnecessarily." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension strategy, governance, finance, risk, privacy, access, retention and agent-operation policies.", "Read this profile and linked party, strategy, project, programme, product, operation, benefit, resource, budget, risk, issue, decision, metric, observation, policy and audit models before mutation." ] } }, "coverage": { "claim": "Covers the profiled programme-or-portfolio aggregate root as drafted by the single active provider: identity, profile and lineage; mandate, ownership and governance; strategy alignment and declared scope; component membership and dependency; results chain and benefit realization; roadmap, tranches and operating transition; investment, funding, capacity, prioritization and control; lifecycle, decision history, measurement and evaluation; crosswalks, access, retention and agent operation. It does not claim universal completeness: ISO support is abstract-level only, retention and access rules are currently unsourced house policy, stakeholder engagement and communication have no dedicated finding, no relation rows were adjudicated against an empty frozen registry context, and no independent second-provider review exists.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Aggregate, release, membership, assignment, decision, event and assertion identities are distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "The program-or-portfolio discriminator and project, operation, product, campaign and strategy boundaries are explicit." }, { "dimension": "direct properties", "status": "covered", "notes": "Mandate, governance, strategy, scope, components, outcomes, benefits, roadmap, resources, lifecycle and metrics are first-class." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Performance and benefit observations retain source, metric, period, dimensions, denominator, quality and uncertainty." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Register, authorize, admit, map, plan, prioritize, transition, observe, evaluate, project, correct and retain are governed." }, { "dimension": "composition", "status": "covered", "notes": "Party, strategy, project, programme, product, operation, benefit, resource, budget, risk, issue, decision, observation, policy and audit masters remain external." }, { "dimension": "lifecycle", "status": "covered", "notes": "Proposal, authorization, start, pause, rebalance, termination, closure and supersession preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Strategy alignment, component membership, dependencies, results chains, assignments, decisions and external masters use typed links." }, { "dimension": "temporal", "status": "covered", "notes": "Planned, decision, event, effective, observation, ingestion and knowledge times remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Jurisdiction, operating context, component location and benefit geography remain source-qualified." }, { "dimension": "provenance", "status": "covered", "notes": "Mandates, memberships, plans, allocations, decisions, events, observations, evaluations and projections preserve responsible-agent provenance." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Accountable owner, manager, governing body, component, benefit, finance, assurance, privacy and records duties are separated." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, profile, mandate, component eligibility, decision authority, metric, aggregation and stale-head checks are explicit." }, { "dimension": "access and privacy", "status": "covered", "notes": "Purpose-bound views, segregation, minimum disclosure and deny-by-default protected cross-component linkage are explicit." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Live termination, working-copy deletion, retained lineage, legal hold and minimum tombstones are distinguished." }, { "dimension": "interoperability", "status": "covered", "notes": "ISO programme, portfolio and governance, OECD results, Data Cube and PROV projections are versioned and loss-aware." } ], "known_omissions": [ "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." ], "conflicts": [ "Program and portfolio management share governance and component concepts but differ in purpose, relationship assumptions and decision semantics; every instance must declare one profile.", "Strategic alignment, delivery performance, benefit realization and causal attribution can disagree while each remains valid under its source and method.", "Component autonomy and aggregate optimization can produce conflicting priorities, resource allocations, risk tolerances and reporting boundaries." ], "regional_assumptions": [ "Investment approval, public accountability, employment, privacy, procurement, financial reporting, records retention and disclosure depend on jurisdiction and sector.", "UK Government guidance informs public-sector controls but does not define universal commercial or nonprofit practice.", "OECD results language supports evaluation but does not alone establish causal attribution or sector-specific benefit ownership." ], "adversarial_checks": [ "Reject an aggregate without a resolvable identity, required program-or-portfolio profile, mandate, accountable owner, boundary or current lineage head.", "Reject a program profile that treats unrelated investments as sufficient membership, or a portfolio profile that requires program-style outcome interdependency.", "Reject benefit realization or causal impact inferred only from component completion, output delivery, spending, health color or platform attribution.", "Reject silent component, objective, ranking, allocation, schedule, lifecycle, metric or decision mutation and any history rewrite.", "Reject an agent operation that admits or removes components, reallocates resources, authorizes a lifecycle transition, exposes protected data or destroys held evidence without delegated authority." ] }, "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": "Two axes must stay separate. On the record plane the frozen registry classifies this as a standalone model record (standalone-mm); that is a storage and publication classification of the Vercy record and is not a member of the subject-model enum, so it must never be emitted as entry_kind. On the subject plane the modelled thing is an invariant-enforcing root: it owns profile, mandate, governance, membership, allocation, sequencing, lifecycle and evaluation assertions, while every component, party, strategy, benefit, budget, risk, decision and observation master is referenced only by external identity and retains its own lifecycle, owner and evidence. That is an aggregate. It is not an entity, which would not carry the membership and allocation invariants; not a registry, which would hold the catalogue of investments but neither the mandate, reserved decision rights nor the root lifecycle; not a relationship, since membership is one owned assertion class inside the root rather than the root itself; and not a pattern, mixin, classifier or event. Accepted for a reviewable draft. The Programme-versus-Portfolio split remains a deferred contingency guarded by the required profile discriminator and profile-specific rules, not a present reclassification." }, "decisions": [ { "concept": "Aggregate root: one profiled programme-or-portfolio root", "disposition": "accepted", "rationale": "The root owns membership, allocation, sequencing and lifecycle assertions while every component and master is referenced by external identity, which is the defining invariant boundary of an aggregate rather than a plain entity." }, { "concept": "Alternative entry kind: portfolio-as-registry", "disposition": "rejected", "rationale": "A registry would own only the catalogue of investments; this root also carries mandate, governance, reserved decision rights, benefit logic and its own lifecycle, so registry understates the invariants it enforces." }, { "concept": "Record-plane value standalone-mm versus subject-model entry kind", "disposition": "reclassified to the schema kind aggregate", "rationale": "standalone-mm describes how the registry stores and publishes the record, not what the modelled subject is; the two axes must be published separately so the enum value remains a subject-model claim." }, { "concept": "Split into separate Programme and Portfolio models", "disposition": "deferred", "rationale": "The required profile discriminator plus profile-specific selection-versus-sequencing rules suffices for a reviewable draft; a split needs implementation evidence of unsafe ambiguity that this pack does not yet contain." }, { "concept": "ISO SRC-001 to SRC-005 marked primary_source true", "disposition": "rejected as stated; downgrade to abstract-level support", "rationale": "The pinned URLs are catalogue pages and the pack's own omissions admit full text was unavailable, so tier-1 authority is fair but primary-source retrieval is not established and must not underwrite clause-level claims." }, { "concept": "Source refs on the retention and the access findings", "disposition": "rejected as source support; relabel as Vercy house policy", "rationale": "SRC-004, SRC-006, SRC-010 and SRC-012 cover governance, provenance and timestamps; none is a records-retention or privacy authority, so retention class, legal hold, tombstone and minimum-necessary disclosure rules are currently unsourced." }, { "concept": "Templated q02 provenance and q03 validation questions, 48 of 72", "disposition": "accepted for the draft, rewrite deferred", "rationale": "Identical wording across every finding gives no discriminating research prompt, but the questions are not wrong and deleting them would strip provenance and validation coverage before finding-specific replacements exist." }, { "concept": "Uniform six-bundle, two-layer, two-finding lattice", "disposition": "accepted with a deferred depth rebalance", "rationale": "Perfect symmetry indicates generated rather than domain-driven decomposition; component membership and dependency carries far more real variability than profile definition and identity does." }, { "concept": "Programme-or-portfolio profile embedded in the artifact identity strategy", "disposition": "accepted, conditional on an explicit supersession rule", "rationale": "Putting the profile in the identity tuple means reclassification cannot be an update, yet canon_and_patch defines only profile-safe successors and leaves profile-unsafe change entirely undefined." }, { "concept": "Model name Program / Portfolio and the serial_naming_rule token program-or-portfolio", "disposition": "rejected as stated; normalize the spelling", "rationale": "Identity strategies, policies and boundary notes use programme-or-portfolio while the name and naming rule use the US spelling, which breaks deterministic artifact naming and crosswalk round-tripping." }, { "concept": "Access scopes bundle, layer, finding, artifact versus field-level minimum necessary", "disposition": "deferred reconciliation", "rationale": "The default access rule and the audit requirements both assume field-level disclosure control and affected-field logging that the declared scope list cannot express, so one of the two must give." }, { "concept": "Benefit and change owner role responsibilities", "disposition": "accepted with an aggregate-scoped qualifier", "rationale": "Owning outcome definitions, baselines, targets and realization evidence reads as ownership of the external benefit master that out_of_scope explicitly excludes; the qualifier keeps the ownership boundary intact." }, { "concept": "Campaign and product neighbor distinctions in the profile boundary finding", "disposition": "deferred to sibling-model reconciliation", "rationale": "The finding asserts distinctions from campaign and product masters, but its source refs cover only ISO project, programme and portfolio material, leaving those two boundary claims unsupported inside this pack." }, { "concept": "Coverage checklist marking all sixteen dimensions covered", "disposition": "rejected as stated; qualify interoperability, composition and capabilities", "rationale": "The same package admits abstract-only ISO support, unapproved relation rows and no dedicated stakeholder-engagement finding, so a uniform covered status overstates what has actually been verified." }, { "concept": "serial set true on all twenty-four artifacts", "disposition": "accepted for the draft, per-artifact adjudication deferred", "rationale": "The crosswalk and metric-definition records behave like versioned releases rather than serially numbered event artifacts, but a uniform default is safe while the naming token is being normalized." }, { "concept": "Grok waiver text citing a valid Claude plus no-tools result", "disposition": "accepted as recorded, publish a corrected waiver chain", "rationale": "The clause presumes a Claude result that never existed, while active_providers and the review rule remain unambiguous, so the remedy is accurate publication of the real waiver chain rather than a blocking contradiction." } ], "publicationHolds": [ "Re-verify every source URL, edition and version pin live before publication, in particular GovS 002 version 2.1 dated 17 September 2025, the 2017 IPA benefits management PDF on its assets media path, and the five ISO catalogue editions cited as SRC-001 to SRC-005.", "Publish the owner-authorized absence of independent second-provider review in every artifact: neither Claude nor Grok produced an admissible result, and neither the Codex fallback research nor this local no-tools Claude audit may be described as independent external review.", "No ISO conformance claim of any kind until licensed clause-level text has been reviewed; the package currently rests on official abstracts plus public-authority guidance.", "Hold the registry Project parent link and every proposed strategy, component, benefit, finance, risk, decision, observation, policy and audit relation; no approved relation rows were supplied and the frozen registry context arrived empty, so the relationship contract could not be checked.", "Relabel the retention, disposition, tombstone and access rules as Vercy house policy until a records-management authority and a privacy or access-control authority are cited alongside them.", "Normalize the programme-or-portfolio profile token across the model name, the serial naming rule and all identity strategies, and state that a profile change is a supersession rather than an update, before any artifact identifiers are minted.", "Keep the record at reviewable-draft status and block canonical promotion while second-provider review remains waived.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 15, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }