# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T06:09:14Z", "synthesisSha256": "318a5ed2e7faa46127cc59d426697af0bfe901ee07f7b0667b6f6883808d9655", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-030", "registryId": "vr.wm-act-030", "name": "Initiative", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.INI" ], "tags": [ "initiative", "act.ini" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-030-initiative/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-030", "model": { "registry_id": "vr.wm-act-030", "model_id": "WM-ACT-030", "name": "Initiative", "entry_kind": "aggregate", "purpose": "Represent a governed course of coordinated change or exploration that can exist before, outside or across formal projects, programs, campaigns and operations while preserving the identity of every linked master.", "scope_statement": "Owns initiative identity and lineage, source-qualified classification, originating problem or opportunity evidence, case for change, mandate, sponsorship, exploratory scope and guardrails, strategy alignment, options and hypotheses, initiative-scoped stakeholder and result intent, linked-work membership and dependencies, roadmap, gates and experiments, bounded assignments and envelopes, lifecycle, formalization and responsibility-transfer history, initiative metric definitions and evaluation assertions, projections, access and retention. Party, strategy, objective, policy, project, program, portfolio, campaign, operation, activity, experiment, capability, product, service, resource, budget, contract, risk, issue, decision, metric, observation, dataset and generic audit masters remain external.", "in_scope": [ "Initiative identity, profile, originating evidence, mandate, sponsor, scope, strategy alignment, options, assumptions, stakeholders and intended results", "Linked work, dependencies, roadmaps, stages, gates, experiments, roles, resource and funding references, risks, requirements, controls and exceptions", "Proposal, screening, approval, incubation, activation, pause, cancellation, completion, formalization, derivation, observations, evaluation, interoperability, access, retention and agent operations" ], "out_of_scope": [ "Party, strategy, objective, policy, project, program, portfolio, campaign, operation, activity, experiment, capability, product, service, resource, budget, contract, risk, issue, decision, metric, observation, dataset or audit-log master lifecycle", "Treating Initiative as a synonym for Strategy, Objective, Course of Action, Project, Program, Campaign or Operation, or reusing initiative identity after formalization", "Implementing portfolio optimization, project scheduling, accounting, procurement, workforce management, experimentation platforms, analytics engines or universal legal compliance and claiming full ISO or ArchiMate conformance from public sources" ], "boundary_notes": [ { "neighbor": "Strategy / Policy / Objective / Course of Action", "distinction": "The initiative records source-qualified alignment, contribution and selected option assertions; external motivation and course-of-action masters keep their own identity and authority.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ] }, { "neighbor": "Project / Program / Campaign / Operation", "distinction": "An initiative may precede, span or derive formal delivery objects. Formalization creates a new master identity, mapping and responsibility handover rather than renaming the initiative.", "source_refs": [ "SRC-008", "SRC-009", "SRC-011" ] }, { "neighbor": "Activity / Work Package / Experiment / Deliverable", "distinction": "The initiative owns membership, coordination and learning assertions while external work objects keep their executable scope, owner, lifecycle and evidence.", "source_refs": [ "SRC-003", "SRC-005", "SRC-009", "SRC-010" ] }, { "neighbor": "Outcome / Benefit / Impact / Observation", "distinction": "The initiative owns intended results logic and initiative-specific evaluation; observed results and external benefit or observation masters keep source identity and method, and activity does not establish causation.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-012" ] }, { "neighbor": "Resource / Budget / Risk / Decision / Policy", "distinction": "The initiative owns scoped assignments, envelopes and control views; authoritative transactions, capacities, risks, decisions and policies remain external.", "source_refs": [ "SRC-005", "SRC-007", "SRC-008", "SRC-011", "SRC-013" ] } ] }, "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-06T06:04:00Z", "relevance": "Provides the official abstract-level boundary for project, programme and portfolio concepts; it does not define a universal initiative class or support clause-level conformance." }, { "id": "SRC-002", "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-06T06:04:00Z", "relevance": "Provides the official abstract-level project boundary used to prevent Initiative from silently becoming a Project." }, { "id": "SRC-003", "title": "ArchiMate Model Exchange File Format for the ArchiMate Modeling Language", "organization": "The Open Group", "url": "https://www.opengroup.org/xsd/archimate/3.1/html-model/", "version_or_date": "ArchiMate 3.1 exchange schema documentation", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T06:04:00Z", "relevance": "Defines distinct machine concepts for CourseOfAction, Capability, Resource, Goal, Outcome, WorkPackage, Deliverable, ImplementationEvent, Plateau and Gap." }, { "id": "SRC-004", "title": "ArchiMate Certification Program", "organization": "The Open Group", "url": "https://www.opengroup.org/certifications/archimate", "version_or_date": "ArchiMate certification program page, accessed 2026-09-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T06:04:00Z", "relevance": "Establishes ArchiMate as an open independent enterprise-architecture modeling language but is not used as a semantic or crosswalk source." }, { "id": "SRC-005", "title": "IATI Activity Standard: iati-activity", "organization": "International Aid Transparency Initiative", "url": "https://reference.iatistandard.org/en/iati-standard/203/activity-standard/iati-activities/iati-activity/", "version_or_date": "IATI Standard 2.03", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T06:04:00Z", "relevance": "Defines a cross-organizational activity container with identifier, reporting and participating organizations, status, dates, scope, sectors, tags, policy markers, budgets, transactions, conditions, results and related activities." }, { "id": "SRC-006", "title": "IATI Activity Status codelist", "organization": "International Aid Transparency Initiative", "url": "https://reference.iatistandard.org/en/iati-standard/203/codelists/activitystatus/", "version_or_date": "IATI Standard 2.03 core codelist", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T06:04:00Z", "relevance": "Defines pipeline or identification, implementation, finalisation, closed, cancelled and suspended activity states and separates physical completion from financial and evaluation closure." }, { "id": "SRC-007", "title": "The Green Book 2026", "organization": "HM Treasury, United Kingdom", "url": "https://www.gov.uk/government/publications/the-green-book-appraisal-and-evaluation-in-central-government/the-green-book-2026", "version_or_date": "2026 edition", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T06:04:00Z", "relevance": "Defines strategic fit, option generation, longlist appraisal and social cost, benefit and risk evaluation for proposals." }, { "id": "SRC-008", "title": "Guidance on developing business cases", "organization": "HM Treasury, United Kingdom", "url": "https://www.gov.uk/government/publications/guidance-on-developing-business-cases", "version_or_date": "Updated 30 June 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T06:04:00Z", "relevance": "Defines a staged Five Case Model for developing project and programme business cases and moving from case for change through options to delivery arrangements." }, { "id": "SRC-009", "title": "PM2 Project Management", "organization": "European Commission", "url": "https://pm2.europa.eu/pm2-methodologies/pm2-project-management_en", "version_or_date": "PM2 Project Management Guide 3.1", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T06:04:00Z", "relevance": "Defines project governance, lifecycle phases, gates, activities and artifacts and therefore supplies a formalization boundary for initiative-to-project transition." }, { "id": "SRC-010", "title": "Activity Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/activitystreams-vocabulary/", "version_or_date": "W3C Recommendation, 23 May 2017", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T06:04:00Z", "relevance": "Defines objects, activities, actors, targets, results, instruments, contexts, collections, relationships and lifecycle verbs for loss-aware initiative activity exchange." }, { "id": "SRC-011", "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-06T06:04:00Z", "relevance": "Defines entity, activity, agent, responsibility, generation, derivation, revision and attribution provenance for initiative decisions and successor delivery objects." }, { "id": "SRC-012", "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-06T06:04:00Z", "relevance": "Defines results chains, causal links, assumptions, risks, indicators, baselines, targets, data sources and means of verification for interventions." }, { "id": "SRC-013", "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-06T06:04:00Z", "relevance": "Grounds privacy-risk governance, purpose-aware profiles and managed data lifecycle operations including access, disclosure, retention and disposal." }, { "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-06T06:04:00Z", "relevance": "Grounds retention policies and responsible disposition based on business, legal and historical requirements." }, { "id": "SRC-015", "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-06T06:04:00Z", "relevance": "Defines seconds and explicit-offset timestamps for initiative lifecycle, decision, observation and knowledge events." } ], "structure": { "bundles": [ { "id": "identity-definition-intent-and-mandate", "name": "Identity, definition, intent and mandate", "description": "Defines the initiative root, its weakly standardized class and the authority to explore or coordinate change.", "rationale": "An initiative is neither a project nor an objective. It is a governed aggregate of change intent, scoped assertions and linked work that can precede or cross formal delivery objects.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "initiative-definition-identity-and-lineage", "name": "Initiative definition, identity and lineage", "description": "Pins the initiative class, source profile, stable identity and revision chain.", "source_refs": [ "SRC-003", "SRC-005", "SRC-010", "SRC-011" ], "findings": [ { "id": "initiative-definition-profile-classification-and-neighbor-boundary", "name": "Initiative definition, profile, classification and neighbor boundary", "description": "Source-qualified initiative type, inclusion and exclusion criteria, sector profile and distinctions from objective, course of action, activity, project, program, campaign and operation.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009", "SRC-010" ], "questions": [ { "id": "initiative-definition-profile-classification-and-neighbor-boundary-q01", "text": "What identities, types, roles, scope, versions and explicit values define initiative definition, profile, classification and neighbor boundary?", "kind": "classification", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "initiative-definition-profile-classification-and-neighbor-boundary-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support initiative definition, profile, classification and neighbor boundary?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "initiative-definition-profile-classification-and-neighbor-boundary-q03", "text": "How is initiative definition, profile, classification 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": "initiative-definition-profile-classification-and-neighbor-boundary-data", "name": "Initiative definition, profile, classification and neighbor boundary data", "description": "Structured initiative data for initiative definition, profile, classification and neighbor boundary.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "initiative-definition-profile-classification-and-neighbor-boundary-record", "name": "Initiative definition, profile, classification and neighbor boundary record", "description": "Versioned evidence-bearing initiative record for initiative definition, profile, classification and neighbor boundary with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus initiative-definition-profile-classification-and-neighbor-boundary assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "initiative-identifier-name-alias-version-source-predecessor-and-successor", "name": "Initiative identifier, name, alias, version, source, predecessor and successor", "description": "Authoritative identifier, governed names and aliases, profile and schema versions, source system, predecessor, successor, duplicate and split or merge assertions.", "source_refs": [ "SRC-005", "SRC-010", "SRC-011" ], "questions": [ { "id": "initiative-identifier-name-alias-version-source-predecessor-and-successor-q01", "text": "What identities, types, roles, scope, versions and explicit values define initiative identifier, name, alias, version, source, predecessor and successor?", "kind": "identity", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "initiative-identifier-name-alias-version-source-predecessor-and-successor-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support initiative identifier, name, alias, version, source, predecessor and successor?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "initiative-identifier-name-alias-version-source-predecessor-and-successor-q03", "text": "How is initiative identifier, name, alias, version, source, predecessor and successor 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": "initiative-identifier-name-alias-version-source-predecessor-and-successor-data", "name": "Initiative identifier, name, alias, version, source, predecessor and successor data", "description": "Structured initiative data for initiative identifier, name, alias, version, source, predecessor and successor.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "initiative-identifier-name-alias-version-source-predecessor-and-successor-record", "name": "Initiative identifier, name, alias, version, source, predecessor and successor record", "description": "Versioned evidence-bearing initiative record for initiative identifier, name, alias, version, source, predecessor and successor with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus initiative-identifier-name-alias-version-source-predecessor-and-successor assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-005", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "originating-need-mandate-sponsorship-and-scope", "name": "Originating need, mandate, sponsorship and scope", "description": "Records why the initiative exists, who may sponsor it and the boundary of authorized exploration.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011", "SRC-012" ], "findings": [ { "id": "problem-opportunity-driver-assessment-evidence-and-case-for-change", "name": "Problem, opportunity, driver, assessment, evidence and case for change", "description": "Observed or asserted problem or opportunity, originating driver, baseline evidence, urgency, affected context, assessment and falsifiable case for change.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ], "questions": [ { "id": "problem-opportunity-driver-assessment-evidence-and-case-for-change-q01", "text": "What identities, types, roles, scope, versions and explicit values define problem, opportunity, driver, assessment, evidence and case for change?", "kind": "evidence", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "problem-opportunity-driver-assessment-evidence-and-case-for-change-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support problem, opportunity, driver, assessment, evidence and case for change?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "problem-opportunity-driver-assessment-evidence-and-case-for-change-q03", "text": "How is problem, opportunity, driver, assessment, evidence and case for change 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": "problem-opportunity-driver-assessment-evidence-and-case-for-change-data", "name": "Problem, opportunity, driver, assessment, evidence and case for change data", "description": "Structured initiative data for problem, opportunity, driver, assessment, evidence and case for change.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ] } ], "artifacts": [ { "id": "problem-opportunity-driver-assessment-evidence-and-case-for-change-record", "name": "Problem, opportunity, driver, assessment, evidence and case for change record", "description": "Versioned evidence-bearing initiative record for problem, opportunity, driver, assessment, evidence and case for change with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus problem-opportunity-driver-assessment-evidence-and-case-for-change assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "mandate-sponsor-owner-authority-scope-guardrail-and-jurisdiction", "name": "Mandate, sponsor, owner, authority, scope, guardrail and jurisdiction", "description": "Mandate source, accountable sponsor and steward, delegated exploratory authority, intended and excluded scope, guardrails, jurisdiction and effective interval.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011" ], "questions": [ { "id": "mandate-sponsor-owner-authority-scope-guardrail-and-jurisdiction-q01", "text": "What identities, types, roles, scope, versions and explicit values define mandate, sponsor, owner, authority, scope, guardrail and jurisdiction?", "kind": "authority", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "mandate-sponsor-owner-authority-scope-guardrail-and-jurisdiction-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support mandate, sponsor, owner, authority, scope, guardrail 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-authority-scope-guardrail-and-jurisdiction-q03", "text": "How is mandate, sponsor, owner, authority, scope, guardrail 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-authority-scope-guardrail-and-jurisdiction-data", "name": "Mandate, sponsor, owner, authority, scope, guardrail and jurisdiction data", "description": "Structured initiative data for mandate, sponsor, owner, authority, scope, guardrail and jurisdiction.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011" ] } ], "artifacts": [ { "id": "mandate-sponsor-owner-authority-scope-guardrail-and-jurisdiction-record", "name": "Mandate, sponsor, owner, authority, scope, guardrail and jurisdiction record", "description": "Versioned evidence-bearing initiative record for mandate, sponsor, owner, authority, scope, guardrail and jurisdiction with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus mandate-sponsor-owner-authority-scope-guardrail-and-jurisdiction assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "strategy-options-hypotheses-and-stakeholders", "name": "Strategy, options, hypotheses and stakeholders", "description": "Connects intent to strategy, alternatives, affected parties and testable value claims.", "rationale": "Alignment, option, assumption, output, outcome, benefit and observed impact are different assertions and remain source-qualified.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ], "layers": [ { "id": "strategy-objectives-options-and-assumptions", "name": "Strategy, objectives, options and assumptions", "description": "Represents the logic and alternatives considered before or during formalization.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ], "findings": [ { "id": "strategy-policy-goal-objective-alignment-contribution-and-priority", "name": "Strategy, policy, goal, objective, alignment, contribution and priority", "description": "External strategy, policy, goal and objective references, alignment or contribution hypothesis, priority, conflict and trade-off.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-012" ], "questions": [ { "id": "strategy-policy-goal-objective-alignment-contribution-and-priority-q01", "text": "What identities, types, roles, scope, versions and explicit values define strategy, policy, goal, objective, alignment, contribution and priority?", "kind": "requirement", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "strategy-policy-goal-objective-alignment-contribution-and-priority-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support strategy, policy, goal, objective, alignment, contribution and priority?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "strategy-policy-goal-objective-alignment-contribution-and-priority-q03", "text": "How is strategy, policy, goal, objective, alignment, contribution 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-goal-objective-alignment-contribution-and-priority-data", "name": "Strategy, policy, goal, objective, alignment, contribution and priority data", "description": "Structured initiative data for strategy, policy, goal, objective, alignment, contribution and priority.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-012" ] } ], "artifacts": [ { "id": "strategy-policy-goal-objective-alignment-contribution-and-priority-record", "name": "Strategy, policy, goal, objective, alignment, contribution and priority record", "description": "Versioned evidence-bearing initiative record for strategy, policy, goal, objective, alignment, contribution and priority with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus strategy-policy-goal-objective-alignment-contribution-and-priority assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "option-scenario-course-of-action-hypothesis-assumption-constraint-and-appraisal", "name": "Option, scenario, course of action, hypothesis, assumption, constraint and appraisal", "description": "Option set, no-change comparator, course-of-action reference, hypothesis, assumptions, constraints, appraisal criteria, uncertainty and selection state.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "questions": [ { "id": "option-scenario-course-of-action-hypothesis-assumption-constraint-and-appraisal-q01", "text": "What identities, types, roles, scope, versions and explicit values define option, scenario, course of action, hypothesis, assumption, constraint and appraisal?", "kind": "decision", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "option-scenario-course-of-action-hypothesis-assumption-constraint-and-appraisal-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support option, scenario, course of action, hypothesis, assumption, constraint and appraisal?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "option-scenario-course-of-action-hypothesis-assumption-constraint-and-appraisal-q03", "text": "How is option, scenario, course of action, hypothesis, assumption, constraint and appraisal 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": "option-scenario-course-of-action-hypothesis-assumption-constraint-and-appraisal-data", "name": "Option, scenario, course of action, hypothesis, assumption, constraint and appraisal data", "description": "Structured initiative data for option, scenario, course of action, hypothesis, assumption, constraint and appraisal.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "option-scenario-course-of-action-hypothesis-assumption-constraint-and-appraisal-record", "name": "Option, scenario, course of action, hypothesis, assumption, constraint and appraisal record", "description": "Versioned evidence-bearing initiative record for option, scenario, course of action, hypothesis, assumption, constraint and appraisal with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus option-scenario-course-of-action-hypothesis-assumption-constraint-and-appraisal assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "stakeholders-value-and-results-intent", "name": "Stakeholders, value and results intent", "description": "Defines who is affected and what change is intended without claiming realization.", "source_refs": [ "SRC-003", "SRC-008", "SRC-009", "SRC-012" ], "findings": [ { "id": "stakeholder-beneficiary-affected-party-need-influence-concern-and-engagement", "name": "Stakeholder, beneficiary, affected party, need, influence, concern and engagement", "description": "External actor or group reference, role, need, influence, concern, expected effect, engagement intent, consent or other authority and safeguard.", "source_refs": [ "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-013" ], "questions": [ { "id": "stakeholder-beneficiary-affected-party-need-influence-concern-and-engagement-q01", "text": "What identities, types, roles, scope, versions and explicit values define stakeholder, beneficiary, affected party, need, influence, concern and engagement?", "kind": "ownership", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "stakeholder-beneficiary-affected-party-need-influence-concern-and-engagement-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support stakeholder, beneficiary, affected party, need, influence, concern and engagement?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "stakeholder-beneficiary-affected-party-need-influence-concern-and-engagement-q03", "text": "How is stakeholder, beneficiary, affected party, need, influence, concern and engagement 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": "stakeholder-beneficiary-affected-party-need-influence-concern-and-engagement-data", "name": "Stakeholder, beneficiary, affected party, need, influence, concern and engagement data", "description": "Structured initiative data for stakeholder, beneficiary, affected party, need, influence, concern and engagement.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-013" ] } ], "artifacts": [ { "id": "stakeholder-beneficiary-affected-party-need-influence-concern-and-engagement-record", "name": "Stakeholder, beneficiary, affected party, need, influence, concern and engagement record", "description": "Versioned evidence-bearing initiative record for stakeholder, beneficiary, affected party, need, influence, concern and engagement with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus stakeholder-beneficiary-affected-party-need-influence-concern-and-engagement assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "output-capability-outcome-benefit-disbenefit-impact-value-and-causal-link", "name": "Output, capability, outcome, benefit, disbenefit, impact, value and causal link", "description": "Typed intended-result nodes and causal links, value recipient, positive or negative direction, assumptions, dependencies, evidence and attribution limit.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ], "questions": [ { "id": "output-capability-outcome-benefit-disbenefit-impact-value-and-causal-link-q01", "text": "What identities, types, roles, scope, versions and explicit values define output, capability, outcome, benefit, disbenefit, impact, value and causal link?", "kind": "relationship", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "output-capability-outcome-benefit-disbenefit-impact-value-and-causal-link-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support output, capability, outcome, benefit, disbenefit, impact, value and causal link?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "output-capability-outcome-benefit-disbenefit-impact-value-and-causal-link-q03", "text": "How is output, capability, outcome, benefit, disbenefit, impact, value 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": "output-capability-outcome-benefit-disbenefit-impact-value-and-causal-link-data", "name": "Output, capability, outcome, benefit, disbenefit, impact, value and causal link data", "description": "Structured initiative data for output, capability, outcome, benefit, disbenefit, impact, value and causal link.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ] } ], "artifacts": [ { "id": "output-capability-outcome-benefit-disbenefit-impact-value-and-causal-link-record", "name": "Output, capability, outcome, benefit, disbenefit, impact, value and causal link record", "description": "Versioned evidence-bearing initiative record for output, capability, outcome, benefit, disbenefit, impact, value and causal link with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus output-capability-outcome-benefit-disbenefit-impact-value-and-causal-link assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "composition-roadmap-experiments-and-coordination", "name": "Composition, roadmap, experiments and coordination", "description": "Groups initiative-scoped work while preserving every external work object's master identity.", "rationale": "The initiative owns membership and coordination assertions, not the project, program, campaign, activity, work package, experiment, deliverable or product masters it references.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-009", "SRC-010", "SRC-011" ], "layers": [ { "id": "linked-work-membership-and-dependency", "name": "Linked work, membership and dependency", "description": "Records work relationships and interfaces without silently creating a formal project.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-009", "SRC-010", "SRC-011" ], "findings": [ { "id": "work-object-identity-type-membership-basis-role-status-and-validity", "name": "Work object identity, type, membership, basis, role, status and validity", "description": "External work object ID and type, membership or association, inclusion basis, initiative role, source state, effective interval, owner and source authority.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-009", "SRC-010" ], "questions": [ { "id": "work-object-identity-type-membership-basis-role-status-and-validity-q01", "text": "What identities, types, roles, scope, versions and explicit values define work object identity, type, membership, basis, role, status and validity?", "kind": "composition", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "work-object-identity-type-membership-basis-role-status-and-validity-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support work object identity, type, membership, basis, role, status and validity?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "work-object-identity-type-membership-basis-role-status-and-validity-q03", "text": "How is work object identity, type, membership, basis, role, status and validity 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": "work-object-identity-type-membership-basis-role-status-and-validity-data", "name": "Work object identity, type, membership, basis, role, status and validity data", "description": "Structured initiative data for work object identity, type, membership, basis, role, status and validity.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "work-object-identity-type-membership-basis-role-status-and-validity-record", "name": "Work object identity, type, membership, basis, role, status and validity record", "description": "Versioned evidence-bearing initiative record for work object identity, type, membership, basis, role, status and validity with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus work-object-identity-type-membership-basis-role-status-and-validity assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "dependency-interface-sequence-shared-change-conflict-and-external-relation", "name": "Dependency, interface, sequence, shared change, conflict and external relation", "description": "Typed dependencies, interfaces, sequence, shared capabilities or change, conflicts, assumptions, external relationships and coordination owner.", "source_refs": [ "SRC-003", "SRC-005", "SRC-009", "SRC-010" ], "questions": [ { "id": "dependency-interface-sequence-shared-change-conflict-and-external-relation-q01", "text": "What identities, types, roles, scope, versions and explicit values define dependency, interface, sequence, shared change, conflict and external relation?", "kind": "relationship", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "dependency-interface-sequence-shared-change-conflict-and-external-relation-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support dependency, interface, sequence, shared change, 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-sequence-shared-change-conflict-and-external-relation-q03", "text": "How is dependency, interface, sequence, shared change, 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-sequence-shared-change-conflict-and-external-relation-data", "name": "Dependency, interface, sequence, shared change, conflict and external relation data", "description": "Structured initiative data for dependency, interface, sequence, shared change, conflict and external relation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "dependency-interface-sequence-shared-change-conflict-and-external-relation-record", "name": "Dependency, interface, sequence, shared change, conflict and external relation record", "description": "Versioned evidence-bearing initiative record for dependency, interface, sequence, shared change, conflict and external relation with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus dependency-interface-sequence-shared-change-conflict-and-external-relation assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-003", "SRC-005", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "roadmap-gates-options-tests-and-learning", "name": "Roadmap, gates, options, tests and learning", "description": "Plans progressive evidence acquisition and controlled transition decisions.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-015" ], "findings": [ { "id": "roadmap-stage-workstream-milestone-decision-gate-window-and-review-point", "name": "Roadmap, stage, workstream, milestone, decision gate, window and review point", "description": "Versioned high-level roadmap, stage, workstream, milestone, dependency, planned and actual window, gate criteria and review cadence.", "source_refs": [ "SRC-003", "SRC-008", "SRC-009", "SRC-015" ], "questions": [ { "id": "roadmap-stage-workstream-milestone-decision-gate-window-and-review-point-q01", "text": "What identities, types, roles, scope, versions and explicit values define roadmap, stage, workstream, milestone, decision gate, window and review point?", "kind": "temporal", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "roadmap-stage-workstream-milestone-decision-gate-window-and-review-point-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support roadmap, stage, workstream, milestone, decision gate, window and review point?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "roadmap-stage-workstream-milestone-decision-gate-window-and-review-point-q03", "text": "How is roadmap, stage, workstream, milestone, decision gate, window 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-stage-workstream-milestone-decision-gate-window-and-review-point-data", "name": "Roadmap, stage, workstream, milestone, decision gate, window and review point data", "description": "Structured initiative data for roadmap, stage, workstream, milestone, decision gate, window and review point.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-008", "SRC-009", "SRC-015" ] } ], "artifacts": [ { "id": "roadmap-stage-workstream-milestone-decision-gate-window-and-review-point-record", "name": "Roadmap, stage, workstream, milestone, decision gate, window and review point record", "description": "Versioned evidence-bearing initiative record for roadmap, stage, workstream, milestone, decision gate, window and review point with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus roadmap-stage-workstream-milestone-decision-gate-window-and-review-point assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-003", "SRC-008", "SRC-009", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "experiment-prototype-pilot-option-test-learning-question-evidence-and-pivot", "name": "Experiment, prototype, pilot, option test, learning question, evidence and pivot", "description": "Test identity and method, hypothesis, variant, population or context, evidence threshold, observation, learning result, decision and pivot or stop consequence.", "source_refs": [ "SRC-007", "SRC-008", "SRC-012" ], "questions": [ { "id": "experiment-prototype-pilot-option-test-learning-question-evidence-and-pivot-q01", "text": "What identities, types, roles, scope, versions and explicit values define experiment, prototype, pilot, option test, learning question, evidence and pivot?", "kind": "decision", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "experiment-prototype-pilot-option-test-learning-question-evidence-and-pivot-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support experiment, prototype, pilot, option test, learning question, evidence and pivot?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "experiment-prototype-pilot-option-test-learning-question-evidence-and-pivot-q03", "text": "How is experiment, prototype, pilot, option test, learning question, evidence and pivot 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": "experiment-prototype-pilot-option-test-learning-question-evidence-and-pivot-data", "name": "Experiment, prototype, pilot, option test, learning question, evidence and pivot data", "description": "Structured initiative data for experiment, prototype, pilot, option test, learning question, evidence and pivot.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-008", "SRC-012" ] } ], "artifacts": [ { "id": "experiment-prototype-pilot-option-test-learning-question-evidence-and-pivot-record", "name": "Experiment, prototype, pilot, option test, learning question, evidence and pivot record", "description": "Versioned evidence-bearing initiative record for experiment, prototype, pilot, option test, learning question, evidence and pivot with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus experiment-prototype-pilot-option-test-learning-question-evidence-and-pivot assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-007", "SRC-008", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-resources-risks-and-controls", "name": "Governance, resources, risks and controls", "description": "Makes decision authority and bounded commitments explicit during uncertain change.", "rationale": "Initiative records bind approved envelopes, assignments and control views; finance, resource, contract, risk, issue, requirement and policy masters remain external.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011", "SRC-013" ], "layers": [ { "id": "roles-decisions-resources-and-funding", "name": "Roles, decisions, resources and funding", "description": "Defines accountability and references the capacity made available to the initiative.", "source_refs": [ "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-011" ], "findings": [ { "id": "role-assignment-responsibility-delegation-decision-right-and-segregation", "name": "Role assignment, responsibility, delegation, decision right and segregation", "description": "External actor, initiative role, accountable, responsible, consulted or informed assignment, delegated authority, reserved decision and segregation rule.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-011" ], "questions": [ { "id": "role-assignment-responsibility-delegation-decision-right-and-segregation-q01", "text": "What identities, types, roles, scope, versions and explicit values define role assignment, responsibility, delegation, decision right and segregation?", "kind": "authority", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "role-assignment-responsibility-delegation-decision-right-and-segregation-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support role assignment, responsibility, delegation, decision right and segregation?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "role-assignment-responsibility-delegation-decision-right-and-segregation-q03", "text": "How is role assignment, responsibility, delegation, decision right and segregation 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-assignment-responsibility-delegation-decision-right-and-segregation-data", "name": "Role assignment, responsibility, delegation, decision right and segregation data", "description": "Structured initiative data for role assignment, responsibility, delegation, decision right and segregation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-011" ] } ], "artifacts": [ { "id": "role-assignment-responsibility-delegation-decision-right-and-segregation-record", "name": "Role assignment, responsibility, delegation, decision right and segregation record", "description": "Versioned evidence-bearing initiative record for role assignment, responsibility, delegation, decision right and segregation with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus role-assignment-responsibility-delegation-decision-right-and-segregation assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "resource-capability-capacity-budget-funding-cost-commitment-and-envelope-reference", "name": "Resource, capability, capacity, budget, funding, cost, commitment and envelope reference", "description": "External resource, capability, budget, fund, contract and commitment references, approved envelope, demand, allocation, forecast, actual, currency and valuation basis.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-008" ], "questions": [ { "id": "resource-capability-capacity-budget-funding-cost-commitment-and-envelope-reference-q01", "text": "What identities, types, roles, scope, versions and explicit values define resource, capability, capacity, budget, funding, cost, commitment and envelope reference?", "kind": "measurement", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "resource-capability-capacity-budget-funding-cost-commitment-and-envelope-reference-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support resource, capability, capacity, budget, funding, cost, commitment and envelope reference?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "resource-capability-capacity-budget-funding-cost-commitment-and-envelope-reference-q03", "text": "How is resource, capability, capacity, budget, funding, cost, commitment and envelope 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": "resource-capability-capacity-budget-funding-cost-commitment-and-envelope-reference-data", "name": "Resource, capability, capacity, budget, funding, cost, commitment and envelope reference data", "description": "Structured initiative data for resource, capability, capacity, budget, funding, cost, commitment and envelope reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "resource-capability-capacity-budget-funding-cost-commitment-and-envelope-reference-record", "name": "Resource, capability, capacity, budget, funding, cost, commitment and envelope reference record", "description": "Versioned evidence-bearing initiative record for resource, capability, capacity, budget, funding, cost, commitment and envelope reference with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus resource-capability-capacity-budget-funding-cost-commitment-and-envelope-reference assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "risk-requirement-compliance-and-change-control", "name": "Risk, requirement, compliance and change control", "description": "Records uncertainties and controls proportionate to the initiative's profile and authority.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-013" ], "findings": [ { "id": "risk-opportunity-issue-dependency-likelihood-impact-response-and-residual-state", "name": "Risk, opportunity, issue, dependency, likelihood, impact, response and residual state", "description": "External risk or issue reference, cause, consequence, likelihood, impact, owner, response, residual exposure, trigger and escalation.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "risk-opportunity-issue-dependency-likelihood-impact-response-and-residual-state-q01", "text": "What identities, types, roles, scope, versions and explicit values define risk, opportunity, issue, dependency, likelihood, impact, response and residual state?", "kind": "relationship", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "risk-opportunity-issue-dependency-likelihood-impact-response-and-residual-state-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support risk, opportunity, issue, dependency, likelihood, impact, response and residual state?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "risk-opportunity-issue-dependency-likelihood-impact-response-and-residual-state-q03", "text": "How is risk, opportunity, issue, dependency, likelihood, impact, response and residual state 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-opportunity-issue-dependency-likelihood-impact-response-and-residual-state-data", "name": "Risk, opportunity, issue, dependency, likelihood, impact, response and residual state data", "description": "Structured initiative data for risk, opportunity, issue, dependency, likelihood, impact, response and residual state.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "risk-opportunity-issue-dependency-likelihood-impact-response-and-residual-state-record", "name": "Risk, opportunity, issue, dependency, likelihood, impact, response and residual state record", "description": "Versioned evidence-bearing initiative record for risk, opportunity, issue, dependency, likelihood, impact, response and residual state with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus risk-opportunity-issue-dependency-likelihood-impact-response-and-residual-state assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "requirement-constraint-policy-compliance-safety-privacy-control-and-exception", "name": "Requirement, constraint, policy, compliance, safety, privacy, control and exception", "description": "External requirement or policy reference, applicability, jurisdiction, control, evidence, control owner, exception, expiry and residual concern.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-013" ], "questions": [ { "id": "requirement-constraint-policy-compliance-safety-privacy-control-and-exception-q01", "text": "What identities, types, roles, scope, versions and explicit values define requirement, constraint, policy, compliance, safety, privacy, control and exception?", "kind": "constraint", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "requirement-constraint-policy-compliance-safety-privacy-control-and-exception-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support requirement, constraint, policy, compliance, safety, privacy, control and exception?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "requirement-constraint-policy-compliance-safety-privacy-control-and-exception-q03", "text": "How is requirement, constraint, policy, compliance, safety, privacy, control and exception 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": "requirement-constraint-policy-compliance-safety-privacy-control-and-exception-data", "name": "Requirement, constraint, policy, compliance, safety, privacy, control and exception data", "description": "Structured initiative data for requirement, constraint, policy, compliance, safety, privacy, control and exception.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-013" ] } ], "artifacts": [ { "id": "requirement-constraint-policy-compliance-safety-privacy-control-and-exception-record", "name": "Requirement, constraint, policy, compliance, safety, privacy, control and exception record", "description": "Versioned evidence-bearing initiative record for requirement, constraint, policy, compliance, safety, privacy, control and exception with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus requirement-constraint-policy-compliance-safety-privacy-control-and-exception assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-formalization-performance-and-learning", "name": "Lifecycle, formalization, performance and learning", "description": "Preserves the initiative from proposal through formal delivery or closure and separates evidence from conclusions.", "rationale": "Formalization creates a derived Project, Program, Campaign or Operation with its own identity; it does not rename, overwrite or erase the Initiative.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-015" ], "layers": [ { "id": "lifecycle-transition-and-formalization-history", "name": "Lifecycle transition and formalization history", "description": "Records authorized state transitions and transfers into neighboring delivery models.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-015" ], "findings": [ { "id": "propose-screen-sponsor-assess-approve-incubate-activate-pause-cancel-complete-and-supersede", "name": "Propose, screen, sponsor, assess, approve, incubate, activate, pause, cancel, complete and supersede", "description": "Typed lifecycle event, prior and next state, actor, authority, rationale, scope, event and knowledge time, evidence and reversibility.", "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-015" ], "questions": [ { "id": "propose-screen-sponsor-assess-approve-incubate-activate-pause-cancel-complete-and-supersede-q01", "text": "What identities, types, roles, scope, versions and explicit values define propose, screen, sponsor, assess, approve, incubate, activate, pause, cancel, complete and supersede?", "kind": "lifecycle", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "propose-screen-sponsor-assess-approve-incubate-activate-pause-cancel-complete-and-supersede-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support propose, screen, sponsor, assess, approve, incubate, activate, pause, cancel, complete and supersede?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "propose-screen-sponsor-assess-approve-incubate-activate-pause-cancel-complete-and-supersede-q03", "text": "How is propose, screen, sponsor, assess, approve, incubate, activate, pause, cancel, complete and supersede 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-screen-sponsor-assess-approve-incubate-activate-pause-cancel-complete-and-supersede-data", "name": "Propose, screen, sponsor, assess, approve, incubate, activate, pause, cancel, complete and supersede data", "description": "Structured initiative data for propose, screen, sponsor, assess, approve, incubate, activate, pause, cancel, complete and supersede.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-015" ] } ], "artifacts": [ { "id": "propose-screen-sponsor-assess-approve-incubate-activate-pause-cancel-complete-and-supersede-record", "name": "Propose, screen, sponsor, assess, approve, incubate, activate, pause, cancel, complete and supersede record", "description": "Versioned evidence-bearing initiative record for propose, screen, sponsor, assess, approve, incubate, activate, pause, cancel, complete and supersede with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus propose-screen-sponsor-assess-approve-incubate-activate-pause-cancel-complete-and-supersede assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "formalize-derive-transfer-absorb-split-merge-successor-and-responsibility-handover", "name": "Formalize, derive, transfer, absorb, split, merge, successor and responsibility handover", "description": "Typed derivation to or from a Project, Program, Campaign, Operation or successor Initiative, mapping, responsibility transfer, effective time and unresolved obligations.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008", "SRC-009", "SRC-011" ], "questions": [ { "id": "formalize-derive-transfer-absorb-split-merge-successor-and-responsibility-handover-q01", "text": "What identities, types, roles, scope, versions and explicit values define formalize, derive, transfer, absorb, split, merge, successor and responsibility handover?", "kind": "lifecycle", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "formalize-derive-transfer-absorb-split-merge-successor-and-responsibility-handover-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support formalize, derive, transfer, absorb, split, merge, successor and responsibility handover?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "formalize-derive-transfer-absorb-split-merge-successor-and-responsibility-handover-q03", "text": "How is formalize, derive, transfer, absorb, split, merge, successor and responsibility handover 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": "formalize-derive-transfer-absorb-split-merge-successor-and-responsibility-handover-data", "name": "Formalize, derive, transfer, absorb, split, merge, successor and responsibility handover data", "description": "Structured initiative data for formalize, derive, transfer, absorb, split, merge, successor and responsibility handover.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-008", "SRC-009", "SRC-011" ] } ], "artifacts": [ { "id": "formalize-derive-transfer-absorb-split-merge-successor-and-responsibility-handover-record", "name": "Formalize, derive, transfer, absorb, split, merge, successor and responsibility handover record", "description": "Versioned evidence-bearing initiative record for formalize, derive, transfer, absorb, split, merge, successor and responsibility handover with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus formalize-derive-transfer-absorb-split-merge-successor-and-responsibility-handover assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008", "SRC-009", "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "measurement-observation-evaluation-and-learning", "name": "Measurement, observation, evaluation and learning", "description": "Defines how evidence is collected and how bounded conclusions influence the initiative.", "source_refs": [ "SRC-005", "SRC-007", "SRC-008", "SRC-011", "SRC-012" ], "findings": [ { "id": "metric-indicator-definition-formula-unit-baseline-target-window-and-data-source", "name": "Metric, indicator, definition, formula, unit, baseline, target, window and data source", "description": "Metric ID and version, result level, formula, unit, numerator and denominator, baseline, target, period, segment, data source, owner and quality rule.", "source_refs": [ "SRC-005", "SRC-007", "SRC-012" ], "questions": [ { "id": "metric-indicator-definition-formula-unit-baseline-target-window-and-data-source-q01", "text": "What identities, types, roles, scope, versions and explicit values define metric, indicator, definition, formula, unit, baseline, target, window and data source?", "kind": "classification", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "metric-indicator-definition-formula-unit-baseline-target-window-and-data-source-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support metric, indicator, definition, formula, unit, baseline, target, window and data source?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "metric-indicator-definition-formula-unit-baseline-target-window-and-data-source-q03", "text": "How is metric, indicator, definition, formula, unit, baseline, target, window and data source 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-indicator-definition-formula-unit-baseline-target-window-and-data-source-data", "name": "Metric, indicator, definition, formula, unit, baseline, target, window and data source data", "description": "Structured initiative data for metric, indicator, definition, formula, unit, baseline, target, window and data source.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-007", "SRC-012" ] } ], "artifacts": [ { "id": "metric-indicator-definition-formula-unit-baseline-target-window-and-data-source-record", "name": "Metric, indicator, definition, formula, unit, baseline, target, window and data source record", "description": "Versioned evidence-bearing initiative record for metric, indicator, definition, formula, unit, baseline, target, window and data source with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus metric-indicator-definition-formula-unit-baseline-target-window-and-data-source assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-005", "SRC-007", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "observation-progress-health-variance-evaluation-finding-decision-lesson-and-recommendation", "name": "Observation, progress, health, variance, evaluation, finding, decision, lesson and recommendation", "description": "Source-qualified observation, period, value, uncertainty, progress or health method, variance, evaluation question and method, finding, decision, lesson and applicability.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-012" ], "questions": [ { "id": "observation-progress-health-variance-evaluation-finding-decision-lesson-and-recommendation-q01", "text": "What identities, types, roles, scope, versions and explicit values define observation, progress, health, variance, evaluation, finding, decision, lesson and recommendation?", "kind": "evidence", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "observation-progress-health-variance-evaluation-finding-decision-lesson-and-recommendation-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support observation, progress, health, variance, evaluation, finding, decision, lesson and recommendation?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "observation-progress-health-variance-evaluation-finding-decision-lesson-and-recommendation-q03", "text": "How is observation, progress, health, variance, evaluation, finding, decision, lesson and recommendation 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": "observation-progress-health-variance-evaluation-finding-decision-lesson-and-recommendation-data", "name": "Observation, progress, health, variance, evaluation, finding, decision, lesson and recommendation data", "description": "Structured initiative data for observation, progress, health, variance, evaluation, finding, decision, lesson and recommendation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "observation-progress-health-variance-evaluation-finding-decision-lesson-and-recommendation-record", "name": "Observation, progress, health, variance, evaluation, finding, decision, lesson and recommendation record", "description": "Versioned evidence-bearing initiative record for observation, progress, health, variance, evaluation, finding, decision, lesson and recommendation with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus observation-progress-health-variance-evaluation-finding-decision-lesson-and-recommendation assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "provenance-interoperability-access-retention-and-agent-operation", "name": "Provenance, interoperability, access, retention and agent operation", "description": "Supports attributable exchange and safe information lifecycle management.", "rationale": "Mappings are version-pinned and loss-aware; agent authority, access and disposition follow Dimension policy and are never inferred from technical capability.", "source_refs": [ "SRC-003", "SRC-005", "SRC-010", "SRC-011", "SRC-013", "SRC-014", "SRC-015" ], "layers": [ { "id": "source-provenance-and-interoperability", "name": "Source, provenance and interoperability", "description": "Keeps source authority and semantic loss visible across initiative projections.", "source_refs": [ "SRC-003", "SRC-005", "SRC-010", "SRC-011" ], "findings": [ { "id": "source-assertion-evidence-agent-activity-derivation-revision-confidence-and-contradiction", "name": "Source assertion, evidence, agent, activity, derivation, revision, confidence and contradiction", "description": "Assertion identity, source, responsible agent, generating activity, evidence, derivation, revision, confidence, uncertainty and supporting or contradicting claims.", "source_refs": [ "SRC-005", "SRC-010", "SRC-011" ], "questions": [ { "id": "source-assertion-evidence-agent-activity-derivation-revision-confidence-and-contradiction-q01", "text": "What identities, types, roles, scope, versions and explicit values define source assertion, evidence, agent, activity, derivation, revision, confidence and contradiction?", "kind": "provenance", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "source-assertion-evidence-agent-activity-derivation-revision-confidence-and-contradiction-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support source assertion, evidence, agent, activity, derivation, revision, confidence and contradiction?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "source-assertion-evidence-agent-activity-derivation-revision-confidence-and-contradiction-q03", "text": "How is source assertion, evidence, agent, activity, derivation, revision, confidence and contradiction 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": "source-assertion-evidence-agent-activity-derivation-revision-confidence-and-contradiction-data", "name": "Source assertion, evidence, agent, activity, derivation, revision, confidence and contradiction data", "description": "Structured initiative data for source assertion, evidence, agent, activity, derivation, revision, confidence and contradiction.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "source-assertion-evidence-agent-activity-derivation-revision-confidence-and-contradiction-record", "name": "Source assertion, evidence, agent, activity, derivation, revision, confidence and contradiction record", "description": "Versioned evidence-bearing initiative record for source assertion, evidence, agent, activity, derivation, revision, confidence and contradiction with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus source-assertion-evidence-agent-activity-derivation-revision-confidence-and-contradiction assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-005", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "archimate-iati-activitystreams-prov-project-and-results-crosswalk", "name": "ArchiMate, IATI, ActivityStreams, PROV, project and results crosswalk", "description": "Pinned source and target versions, identity, activity, lifecycle, relation and result mappings, profile guards, omissions, semantic conflicts and round-trip classification.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ], "questions": [ { "id": "archimate-iati-activitystreams-prov-project-and-results-crosswalk-q01", "text": "What identities, types, roles, scope, versions and explicit values define archimate, iati, activitystreams, prov, project and results crosswalk?", "kind": "interoperability", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "archimate-iati-activitystreams-prov-project-and-results-crosswalk-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support archimate, iati, activitystreams, prov, project and results crosswalk?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "archimate-iati-activitystreams-prov-project-and-results-crosswalk-q03", "text": "How is archimate, iati, activitystreams, prov, project and results 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": "archimate-iati-activitystreams-prov-project-and-results-crosswalk-data", "name": "ArchiMate, IATI, ActivityStreams, PROV, project and results crosswalk data", "description": "Structured initiative data for archimate, iati, activitystreams, prov, project and results crosswalk.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "archimate-iati-activitystreams-prov-project-and-results-crosswalk-record", "name": "ArchiMate, IATI, ActivityStreams, PROV, project and results crosswalk record", "description": "Versioned evidence-bearing initiative record for archimate, iati, activitystreams, prov, project and results crosswalk with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus archimate-iati-activitystreams-prov-project-and-results-crosswalk assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null } ] }, { "id": "access-privacy-retention-and-safe-automation", "name": "Access, privacy, retention and safe automation", "description": "Controls views, correction and disposition for people and agents.", "source_refs": [ "SRC-011", "SRC-013", "SRC-014", "SRC-015" ], "findings": [ { "id": "role-view-purpose-access-disclosure-redaction-exception-and-audit", "name": "Role view, purpose, access, disclosure, redaction, exception and audit", "description": "Purpose-bound role views at allowed scopes, governed field redaction through projection, disclosure rule, exception authority, expiry and tamper-evident access log.", "source_refs": [ "SRC-011", "SRC-013", "SRC-015" ], "questions": [ { "id": "role-view-purpose-access-disclosure-redaction-exception-and-audit-q01", "text": "What identities, types, roles, scope, versions and explicit values define role view, purpose, access, disclosure, redaction, exception and audit?", "kind": "access", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "role-view-purpose-access-disclosure-redaction-exception-and-audit-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support role view, purpose, access, disclosure, redaction, 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-purpose-access-disclosure-redaction-exception-and-audit-q03", "text": "How is role view, purpose, access, disclosure, redaction, 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-purpose-access-disclosure-redaction-exception-and-audit-data", "name": "Role view, purpose, access, disclosure, redaction, exception and audit data", "description": "Structured initiative data for role view, purpose, access, disclosure, redaction, exception and audit.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-011", "SRC-013", "SRC-015" ] } ], "artifacts": [ { "id": "role-view-purpose-access-disclosure-redaction-exception-and-audit-record", "name": "Role view, purpose, access, disclosure, redaction, exception and audit record", "description": "Versioned evidence-bearing initiative record for role view, purpose, access, disclosure, redaction, exception and audit with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus role-view-purpose-access-disclosure-redaction-exception-and-audit assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-011", "SRC-013", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "retention-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check", "name": "Retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check", "description": "Retention class and trigger, legal or policy hold, deletion eligibility, minimum tombstone, delegated agent scope, precondition, dry run, idempotency key, expected revision and post-check.", "source_refs": [ "SRC-011", "SRC-013", "SRC-014", "SRC-015" ], "questions": [ { "id": "retention-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check-q01", "text": "What identities, types, roles, scope, versions and explicit values define retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check?", "kind": "retention", "answer_data": [ "identifiers and classifications", "roles and scope", "versions and validity", "values and explicit unknowns" ] }, { "id": "retention-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check?", "kind": "provenance", "answer_data": [ "authority", "source and method", "supporting and contradicting evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "retention-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check-q03", "text": "How is retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check 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-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check-data", "name": "Retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check data", "description": "Structured initiative data for retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-011", "SRC-013", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "retention-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check-record", "name": "Retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check record", "description": "Versioned evidence-bearing initiative record for retention trigger, legal hold, disposition, tombstone, agent authority, idempotency and post-check with authority, time, provenance and access marking.", "media_or_form": [ "logical initiative assertion", "proposal, plan, assignment, decision, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Initiative identifier plus retention-trigger-legal-hold-disposition-tombstone-agent-authority-idempotency-and-post-check assertion, artifact or event identifier; name, date, timestamp and digest never identify the initiative alone.", "source_refs": [ "SRC-011", "SRC-013", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-and-classify-initiative", "name": "Register and classify initiative", "description": "Establish source-qualified initiative identity, profile, boundary and lineage.", "inputs": [ "initiative proposal", "source authority", "profile" ], "outputs": [ "versioned initiative root" ], "preconditions": [ "identity, duplicate, profile and neighbor-boundary rules validate" ], "effects": [ "a governed root exists without creating a project or authorizing delivery" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-011" ] }, { "id": "record-case-for-change-and-mandate", "name": "Record case for change and mandate", "description": "Bind evidence of need or opportunity to sponsor authority, scope and guardrails.", "inputs": [ "initiative root", "problem or opportunity evidence", "sponsor", "mandate" ], "outputs": [ "case-for-change release" ], "preconditions": [ "baseline, source, authority, scope, exclusions, jurisdiction and uncertainty validate" ], "effects": [ "exploration has an explicit purpose and authority boundary" ], "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-011", "SRC-012" ] }, { "id": "develop-and-appraise-options", "name": "Develop and appraise options", "description": "Create comparable options, hypotheses and no-change evidence.", "inputs": [ "case for change", "strategy refs", "constraints", "evidence" ], "outputs": [ "versioned option set and appraisal" ], "preconditions": [ "criteria, alternatives, assumptions, uncertainty, risk, cost and benefit methods validate" ], "effects": [ "an option decision can cite transparent evidence without claiming authorization" ], "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ] }, { "id": "map-stakeholders-outcomes-and-value", "name": "Map stakeholders, outcomes and value", "description": "Define affected parties and the intended results chain.", "inputs": [ "initiative", "stakeholders", "options", "evidence" ], "outputs": [ "stakeholder and results-intent release" ], "preconditions": [ "actor identity, authority, safeguards, result levels, indicators, assumptions and causal limits validate" ], "effects": [ "intended value and adverse effects become testable assertions" ], "source_refs": [ "SRC-003", "SRC-005", "SRC-008", "SRC-009", "SRC-012", "SRC-013" ] }, { "id": "link-work-and-coordinate-dependencies", "name": "Link work and coordinate dependencies", "description": "Append initiative membership and dependency assertions for external work objects.", "inputs": [ "initiative", "external work objects", "membership basis" ], "outputs": [ "membership and dependency graph release" ], "preconditions": [ "source identity, type, owner, relation, direction, effective interval and expected revision validate" ], "effects": [ "coordination changes without absorbing or rewriting external masters" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-009", "SRC-010", "SRC-011" ] }, { "id": "plan-roadmap-gates-and-experiments", "name": "Plan roadmap, gates and experiments", "description": "Coordinate staged learning, evidence thresholds and transition reviews.", "inputs": [ "initiative release", "options", "constraints", "resources" ], "outputs": [ "roadmap, gate and experiment release" ], "preconditions": [ "schedule, dependencies, criteria, method, safeguards, evidence threshold and owner validate" ], "effects": [ "initiative learning becomes executable without asserting results" ], "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-012", "SRC-015" ] }, { "id": "assign-governance-resources-and-controls", "name": "Assign governance, resources and controls", "description": "Bind delegated roles, bounded envelopes, risks and controls.", "inputs": [ "initiative", "actors", "resource and policy refs" ], "outputs": [ "governance and control release" ], "preconditions": [ "authority, segregation, capacity, budget, currency, risk, compliance, privacy and exception rules validate" ], "effects": [ "approved initiative commitments and controls become auditable" ], "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-013" ] }, { "id": "transition-initiative-lifecycle", "name": "Transition initiative lifecycle", "description": "Append an authorized initiative state event without rewriting prior history.", "inputs": [ "current revision", "transition", "authority", "evidence" ], "outputs": [ "lifecycle event and current-state projection" ], "preconditions": [ "profile transition table, gate, scope, rationale, time and downstream controls validate" ], "effects": [ "the initiative state changes with preserved provenance" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-015" ] }, { "id": "formalize-or-transfer-initiative", "name": "Formalize or transfer initiative", "description": "Create a typed derivation and responsibility handover to a Project, Program, Campaign, Operation or successor Initiative.", "inputs": [ "initiative release", "formalization decision", "target master", "mapping" ], "outputs": [ "derivation, handover and residual-obligation records" ], "preconditions": [ "target identity, authority, scope mapping, effective time, unresolved obligations and no-rename rule validate" ], "effects": [ "formal delivery begins without losing initiative lineage" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-008", "SRC-009", "SRC-011" ] }, { "id": "observe-evaluate-project-correct-retain-and-audit", "name": "Observe, evaluate, project, correct, retain and audit", "description": "Record source-qualified evidence or execute governed projection and information-lifecycle operations.", "inputs": [ "initiative revision", "metric or target profile", "purpose", "policy" ], "outputs": [ "observation, evaluation, projection, correction, disposition or audit event" ], "preconditions": [ "metric, source, mapping loss, access, expected revision, legal hold, minimum tombstone and post-checks validate" ], "effects": [ "initiative evidence remains interpretable, interoperable and accountable" ], "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ] } ], "composition": [ { "target": "Strategy, Policy, Objective, Goal, Course of Action and Requirement models", "relation": "REFERENCE", "purpose": "Resolve external motivation and constraints while keeping initiative alignment and option assertions source-qualified.", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-012" ] }, { "target": "Project, Program, Portfolio, Campaign, Operation, Activity, Work Package and Experiment models", "relation": "REFERENCE", "purpose": "Resolve external work masters and formalization targets while preserving their identity, lifecycle, authority and evidence.", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-009", "SRC-010", "SRC-011" ] }, { "target": "Party, Role, Outcome, Benefit, Resource, Budget, Contract, Risk, Issue, Decision, Metric, Observation, Dataset, Policy and Audit models", "relation": "REFERENCE", "purpose": "Bind external masters to initiative-scoped plans, controls and evaluation without copying their lifecycle.", "required": false, "source_refs": [ "SRC-005", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ] }, { "target": "ArchiMate 3.1 CourseOfAction, WorkPackage, Deliverable, Outcome, Capability and ImplementationEvent", "relation": "ALIGN", "purpose": "Project strategy and implementation concepts with explicit omission and non-equivalence rules.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "IATI Activity, ActivityStreams, PROV-O and OECD results frameworks", "relation": "ALIGN", "purpose": "Project activity reporting, lifecycle actions, provenance and result-chain evidence with declared semantic loss.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-010", "SRC-011", "SRC-012" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, initiative governance authority, strategy, finance, risk, privacy and records stewards", "Initiative type, objective, option, stakeholder, work relation, lifecycle, metric, interoperability, access and retention registries", "Master mappings for parties, strategies, objectives, policies, projects, programs, campaigns, activities, experiments, capabilities, products, services, resources, budgets, risks, decisions, metrics, observations and audit logs", "Sponsorship, option appraisal, work linkage, formalization, lifecycle, measurement, disclosure, retention and agent-operation policies" ], "namespace_guidance": "Mint stable IDs for initiative roots, releases, memberships, assignments, options, gates, decisions, events and initiative-scoped assertions. Preserve authoritative external work and master-system identities; never use initiative name, date or digest as identity.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local initiative, strategy, objective, option, metric and policy registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative source plus initiative identifier, source profile and current lineage head, not by name, objective, linked project, sponsor, date or digest.", "Keep proposal, hypothesis, option, appraisal, 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, options, memberships, plans, decisions and observations are immutable. Corrections and profile-safe changes create successors with preserved provenance.", "Formalization into another model is a typed derivation and handover to a new master identity, never an in-place Initiative type change." ], "compatibility_rules": [ "Unknown additive fields may be ignored only when identity, mandate, boundary, options, work relations, decisions, lifecycle, measurement and provenance remain intact.", "ArchiMate, IATI, ActivityStreams, PROV, project and results mappings pin versions and declare omissions, semantic conflicts and round-trip limits." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system initiative identifier qualified by source and initiative class.", "Governed globally resolvable initiative 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 {initiative-id}--{stage-or-root}--{artifact-kind}--{assertion-or-event-id}; never use initiative name, date, timestamp or digest alone.", "integrity_rule": "Store digest, media type, initiative and release binding, source and profile versions, authority, event and knowledge times, access marking and provenance." }, "policies": [ "An Initiative is not automatically a Project, Program, Campaign, Operation, Strategy or Objective; formalization creates a new master identity and typed derivation.", "Problem, opportunity, option, output, outcome, benefit, disbenefit, impact, target, observation and causal attribution are separate attributable assertions.", "Initiative ownership does not transfer ownership of party, strategy, project, program, campaign, operation, activity, experiment, product, resource, budget, risk, decision, metric, observation, policy or audit masters. Initiative cancellation, closure or disposition never cascades to linked work masters.", "Agents may validate, link and project allowlisted data, but sponsorship, option selection, formalization, funding commitment, lifecycle transition, protected disclosure and destructive disposition require delegated authority and policy controls." ], "crud": { "read": [ "Resolve Dimension policy, initiative identity and lineage, mandate, case for change, options, stakeholders, linked work, roadmap, current state, controls, observations, provenance and access purpose." ], "create": [ "Record identity, boundary, originating evidence, sponsor, authority, scope, strategy alignment, options, stakeholders, intended results, linked work and provenance before approval or formalization." ], "update": [ "Append option, membership, authorization, gate, lifecycle, observation, evaluation, correction, formalization or supersession events with actor, authority, rationale, event and knowledge time and expected revision; never overwrite released history." ], "delete": [ "Apply retention, legal-hold and audit policy; cancel or close the live initiative separately from removing eligible working copies, preserve required lineage, decisions, derivations, observations and minimum tombstone evidence, and never cascade deletion or lifecycle change to a linked work master." ] }, "roles": [ { "name": "Initiative sponsor or accountable owner", "responsibilities": [ "Own the case for change, mandate, strategic alignment, authorization and accountable closure or formalization." ] }, { "name": "Initiative lead or steward", "responsibilities": [ "Maintain boundary, options, stakeholders, linked work, roadmap, evidence and change lineage." ] }, { "name": "Option, architecture or subject-matter steward", "responsibilities": [ "Own appraisal criteria, assumptions, solution-neutral option evidence and domain constraints." ] }, { "name": "Work-object or delivery owner", "responsibilities": [ "Own each external project, program, campaign, activity or experiment master and provide source-qualified commitments and evidence." ] }, { "name": "Outcome, benefit and evaluation steward", "responsibilities": [ "Own initiative-scoped result definitions, baselines, targets, evaluation methods and attribution limits without taking ownership of external masters." ] }, { "name": "Finance, resource, risk and assurance stewards", "responsibilities": [ "Control source-qualified envelopes, constraints, exposure, compliance and independent review." ] }, { "name": "Data, privacy and records steward", "responsibilities": [ "Control data quality, protected views, retention, holds, disposition and auditability." ] } ], "access": { "default_rule": "Deny confidential strategy, unselected options, commercial data, person-level stakeholder data, security-sensitive dependencies, unpublished decisions and raw cross-work linkage; disclose purpose-bound minimum views under Dimension policy. Field redaction is a governed artifact projection, not a separate access scope.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Sponsor, initiative lead, work 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, initiative, 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, initiative governance, finance, risk, privacy, access, retention and agent-operation policies.", "Read this model and linked party, strategy, objective, policy, project, program, campaign, activity, experiment, capability, product, resource, budget, risk, decision, metric, observation and audit models before mutation." ] } }, "coverage": { "claim": "Covers one source-grounded Initiative aggregate across six bundles, twelve layers, twenty-four findings and ten functions: origination evidence, mandate and sponsorship, options and hypotheses, stakeholders and intended results, linked work and dependencies, roadmap, gates and experiments, governance, resources, risks and controls, lifecycle and formalization handover, measurement and evaluation, provenance, interoperability, access, retention and agent operation, resting on fifteen tier-1 sources of which thirteen are marked primary. This is explicitly not universal or exhaustive: it is a single-provider reviewable draft whose sector profiles, jurisdictional and legal treatment, benefits-attribution methods, approved relation rows and live version pins remain untested, with no independent second-provider review.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Initiative, release, option, membership, gate, decision, event and assertion identities are distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Source-qualified initiative profiles and objective, course-of-action, project, program, campaign and operation boundaries are explicit." }, { "dimension": "direct properties", "status": "covered", "notes": "Intent, case for change, mandate, scope, options, stakeholders, results intent, linked work, roadmap, resources, controls, lifecycle and metrics are first-class." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Progress and result observations retain source, metric, period, dimensions, denominator, quality and uncertainty." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Register, mandate, appraise, map, link, plan, assign, transition, formalize, observe, evaluate, project, correct and retain are governed." }, { "dimension": "composition", "status": "gap", "notes": "Party, strategy, objective, policy, project, program, campaign, activity, experiment, product, resource, budget, risk, decision, observation and audit masters remain external. Proposed relations or mapping versions remain held for review." }, { "dimension": "lifecycle", "status": "covered", "notes": "Proposal, screening, sponsorship, assessment, approval, incubation, activation, pause, cancellation, completion, formalization and supersession preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Strategy alignment, stakeholder effects, work membership, dependencies, results chains, assignments, decisions and derivations 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, affected context, work location and result geography remain source-qualified." }, { "dimension": "provenance", "status": "covered", "notes": "Mandates, options, memberships, plans, decisions, events, observations, evaluations, formalizations and projections preserve responsible-agent provenance." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Sponsor, initiative lead, option, work, outcome, finance, assurance, privacy and records duties are separated." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, profile, mandate, option comparability, work identity, gate authority, metric and stale-head checks are explicit." }, { "dimension": "access and privacy", "status": "covered", "notes": "Purpose-bound views, stakeholder protection, field-redacted projections and deny-by-default protected linkage are explicit." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Cancellation or closure, working-copy deletion, retained lineage, legal hold and minimum tombstones are distinguished." }, { "dimension": "interoperability", "status": "gap", "notes": "ArchiMate, IATI, ActivityStreams, PROV, project and results projections are versioned and loss-aware. Proposed relations or mapping versions remain held for review." } ], "known_omissions": [ "No successful independent Claude or Grok result was available; cross-sector transformation, finance, organizational-change, benefits-attribution, regional and legal review is required before canonical promotion.", "Initiative has no universal cross-sector definition. This package uses an explicit Vercy root boundary and source profiles rather than claiming terminology equivalence.", "No approved relation rows were supplied; the registry Project parent link and proposed strategy, program, campaign, work, outcome, finance, risk, decision, observation, policy and audit links remain holds.", "The ISO pages are catalogue abstracts, not licensed clause text, so no ISO conformance claim is made and their references only identify the neighboring standards.", "The ArchiMate crosswalk is pinned to the 3.1 exchange schema because the 3.2 certification page is not a semantic specification.", "Sector profiles need their own governance, funding, safety, privacy, appraisal, evidence and formalization rules." ], "conflicts": [ "Initiative may mean a proposed change, a strategic course of action, a funded intervention, a loose activity collection or an already formal project; the source profile and formalization state must disambiguate it.", "Exploration autonomy, sponsor control, affected-party protection, speed, evidence quality and formal delivery governance can conflict.", "A formal Project or Program may continue, absorb or supersede an Initiative while their records and responsibilities remain distinct." ], "regional_assumptions": [ "Public investment approval, grants, procurement, employment, privacy, safety, records, financial reporting and disclosure depend on jurisdiction and sector.", "UK business-case and EU PM2 guidance inform public-sector appraisal and project formalization but do not define a universal Initiative lifecycle.", "IATI describes development and humanitarian activities and is an interoperability profile rather than a universal Initiative master." ], "adversarial_checks": [ "Reject an initiative without a resolvable identity, source profile, case for change, mandate or accountable sponsor.", "Reject silent conversion of an Initiative into a Project, Program, Campaign or Operation and reject identity reuse across the formalization boundary.", "Reject approval, delivery, outcome, benefit or causal impact inferred only from a label, budget line, activity completion or linked project state.", "Reject silent option, scope, membership, roadmap, lifecycle, metric or decision mutation and any history rewrite.", "Reject an agent operation that selects an option, admits work, commits funding, formalizes delivery, 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 not be conflated. On the record plane the registry classifies how Vercy files the record (the standalone-mm family of values); that is a filing classification and never a valid subject-model entry kind. In this pack frozen_context arrived empty, so the record-plane value could not be re-read and is carried as a publication hold. On the subject-model axis the defensible schema enum is aggregate: one Initiative root owns a bounded cluster of initiative-scoped assertion classes (mandate, case for change, options, memberships, dependencies, roadmap and gates, assignments and envelopes, lifecycle and formalization events, metric definitions, evaluations, access and retention state) under a single consistency and authority boundary, while every party, strategy, objective, policy, project, program, portfolio, campaign, activity, experiment, capability, product, service, resource, budget, contract, risk, issue, decision, metric, observation, dataset and audit master stays external and is referenced by identity. entity would understate the owned child-assertion classes and the append-only released-history invariant; relationship would misread the membership assertions as the subject rather than as owned children; pattern or mixin would deny the model its own identity and lifecycle; registry would misread a governed subject as an index of others. Aggregate is accepted as stated by the active provider." }, "decisions": [ { "concept": "Aggregate root is Initiative, not a work-collection index", "disposition": "accepted", "rationale": "The consistency boundary is the initiative itself: it owns identity, lineage and initiative-scoped assertions, and every neighbour is referenced rather than contained. That is what makes a single root defensible instead of a thin index over external work." }, { "concept": "Formalization mints a new master identity with typed derivation and handover", "disposition": "accepted as the load-bearing invariant", "rationale": "This is the one rule preventing Initiative from collapsing into Project, Program, Campaign or Operation. It is asserted consistently in scope_statement, boundary_notes, patch_rules, policies, adversarial_checks, the formalize-derive finding and the formalize-or-transfer function. Cross-read for contradiction and none found." }, { "concept": "Ownership boundary excludes all neighbour master lifecycles", "disposition": "accepted", "rationale": "Twenty-four findings touch strategy, work, resources, budgets, risks, requirements and metrics, which invites drift into a universal work model. Each finding is written as a reference plus an initiative-scoped assertion, and the policies block states ownership does not transfer, so the breadth is contained." }, { "concept": "Composition by membership assertion without lifecycle cascade", "disposition": "accepted with a required explicit non-cascade rule", "rationale": "The linked-work finding says the initiative owns membership of externally owned work. The delete rule covers the initiative's own working copies but never states that cancelling, closing or disposing of an initiative must not cascade to member work objects. Add that sentence before canonical promotion." }, { "concept": "Templated question layer (25 of 72 provenance, 24 of 72 validation, near-identical q02 and q03)", "disposition": "rejected as canonical-grade, deferred for remediation", "rationale": "Every finding repeats the same two boilerplate questions with only the finding name substituted, so the interrogative layer carries little finding-specific content and cannot drive differentiated research. Tolerable in a reviewable draft, not acceptable for canonical promotion." }, { "concept": "SRC-001 and SRC-002 ISO catalogue abstracts cited as boundary support", "disposition": "downgraded to citation-of-existence only", "rationale": "Both are flagged primary_source false and are catalogue abstracts, yet they support the Project and Program boundary distinction and three functions. An abstract can evidence that a standard exists and what it is titled; it cannot support a semantic distinction. Extend the existing no-conformance omission to these specific support claims." }, { "concept": "ArchiMate version split between SRC-003 (3.1 exchange schema) and SRC-004 (3.2 certification program)", "disposition": "hold on crosswalk target version, SRC-004 rejected as a semantic source", "rationale": "A certification-program page is not a language specification, while the crosswalk finding promises pinned source and target versions. Either pin 3.1 to match the only specification-bearing source or add a 3.2 specification source before the interoperability claim is published." }, { "concept": "Retention, disposition and tombstone rules grounded in SRC-014 UK National Archives guidance", "disposition": "accepted as jurisdiction-scoped, rejected as a universal basis", "rationale": "The guidance is UK public-records specific. The model already delegates retention class and trigger to Dimension policy and lists jurisdiction dependence under regional assumptions, so the citation must stay scoped rather than be generalized into a cross-sector retention rule." }, { "concept": "Access default deny with field redaction modelled as artifact projection rather than a fifth scope", "disposition": "accepted", "rationale": "Keeping redaction as a projection over the four declared scopes (bundle, layer, finding, artifact) avoids a scope taxonomy that would drift from the structure, and the exception rule already demands cited authority, minimum necessary, time limits and separate logging." }, { "concept": "Artifact identity rule versus uniform artifact form across all twenty-four artifacts", "disposition": "identity accepted, form deferred", "rationale": "The identity strategy (initiative id plus assertion or event id, never name, date, timestamp or digest alone) is correct and applied consistently. But a tamper-evident access log, a retention tombstone and a crosswalk record are not one artifact form, and an append-only log is poorly described as a serial assertion record. Differentiate before promotion." }, { "concept": "Registry Project parent link versus the Initiative-is-not-a-Project invariant", "disposition": "deferred to relationship-contract adjudication, published as a hold", "rationale": "The declared omissions state no approved relation rows exist and that the Project parent link remains a hold. A Project parent for an object that may precede or span projects would contradict the central invariant, so it must not ship as approved; as an unapproved hold it does not block a reviewable draft." }, { "concept": "Coverage checklist marking all sixteen dimensions covered", "disposition": "rejected, downgrade composition and interoperability to partial", "rationale": "The same package admits unapproved relation rows and an unpinned ArchiMate target version, which contradicts a blanket covered status for those two dimensions. The self-assessment must match the omissions block or the draft misrepresents its own maturity." }, { "concept": "Operation named as a formalization target but absent from the out-of-scope master list", "disposition": "accepted with a required editorial fix", "rationale": "The formalize-or-transfer function and the lifecycle finding both target an Operation master and the synonym exclusion names Operation, yet the out-of-scope master-lifecycle list omits it. Add Operation so the ownership boundary is symmetric across all named formalization targets." }, { "concept": "Source pins dated at or near the audit date (Green Book 2026, business-case guidance updated 30 June 2026, NIST PF 1.1 draft, ArchiMate 3.2 accessed 2026-09-06)", "disposition": "deferred to live verification", "rationale": "A no-tools audit cannot confirm these editions, update dates or access dates. They are plausible and internally consistent, but the version pins carry real weight in the crosswalk and appraisal findings, so they must be re-fetched before the draft leaves reviewable status." }, { "concept": "Single-provider merge posture", "disposition": "accepted with empty add_findings and add_functions", "rationale": "Codex is the sole active provider under the owner waiver, so there is no second stream to merge from and no synthetic contributions may be invented. The ten functions already trace register, mandate, appraise, map, link, plan, assign, transition, formalize and observe across all six bundles with source_refs, leaving no orphan finding ungoverned." } ], "publicationHolds": [ "Live source and version verification is unresolved. Every URL, edition, update and access date must be re-fetched and confirmed before the draft leaves reviewable status, in particular The Green Book 2026, the business-case guidance updated 30 June 2026, NIST Privacy Framework 1.0 with the 1.1 initial public draft, the ArchiMate 3.2 certification page accessed 2026-09-06, and the IATI 2.03 activity and status codelist pages.", "No independent second-provider review exists. The repository owner authorized waivers for Claude after repeated failures at 1800s, 900s, bounded 600s Sonnet and 300s Haiku, and for Grok. This local Codex adversarial audit is same-provider self-review and must never be presented as external validation; every publication artifact must carry a visible absence-of-external-review notice.", "Relation rows remain held. No approved rows were supplied, and the proposed registry Project parent link stands against the model's own Initiative-is-not-a-Project invariant, so the relation set must publish as explicitly empty and held pending relationship-contract adjudication.", "No ISO 21500 or ISO 21502 conformance or clause-level claim may appear anywhere in the published artifact, since only catalogue abstracts were read and those citations are existence references only.", "The coverage checklist must be corrected from all-covered to partial for composition and interoperability before publication so the self-assessment matches the declared omissions rather than overstating maturity.", "The frozen registry record could not be re-read because frozen_context arrived empty in this audit pack. The record-plane classification and registry_id vr.wm-act-030 must be re-confirmed against the frozen record before publication, independently of the accepted aggregate subject-model kind.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Cross-sector definitional review of Initiative outside public-investment appraisal, covering private-sector transformation portfolios, R&D and product discovery, humanitarian and development programming, and defence course-of-action practice, to test whether the single root and the formalization boundary hold outside UK and EU public-sector framing.", "Rewrite the templated provenance and validation question pair into finding-specific questions, since twenty-four findings currently share two boilerplate questions that cannot drive differentiated downstream research.", "Benefits and impact attribution methodology beyond the OECD and Green Book framing, including contribution versus attribution analysis, counterfactual and comparator design, and the evidence thresholds that permit an initiative to assert a causal claim rather than a correlation.", "Jurisdictional retention, records-schedule and privacy review beyond UK National Archives guidance and the NIST Privacy Framework, covering EU, sectoral and public-procurement regimes that bind disposition, legal hold and tombstone minimums.", "Pin and test the interoperability crosswalk against an ArchiMate 3.2 specification source plus a project-management ontology, with explicit round-trip loss classification, omissions and semantic-conflict records.", "Differentiate artifact forms and identity handling for tamper-evident access logs, retention tombstones and crosswalk records, which currently share one media_or_form pair and one serial identity strategy with all other assertion records." ] }, "statistics": { "sources": 15, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }