Terra Vita Hub v521.3.1 · Runtime Canonical Claim Reconciliation

Institutional Action Orchestration

Controlled execution from assignment through attributable evidence, independent completion review, handover, dependency release and escalation history, with package scope reconciled against the current canonical blocker universe.

Resolve closed sources

Authority boundary. Actions organise work only. Evidence review and completion review do not approve the underlying governed source, determine admissibility, issue a release, authorise funding, certify performance or alter programme governance status.

Preparing protected action reconstruction…

Execution front door

Operational action posture

Execution controlOwner → evidence → review

Operational completion requires attributable evidence, an owner submission and an independent reviewer decision.

Separation of dutiesNo self-review

Evidence submitters cannot review their own evidence, and completion submitters cannot decide their own submission.

Authority boundaryExecution, not approval

Completion closes only the action. Formal review, evidence, release and programme-governance status remain separate.

Transparent highest-impact work plan

Recommended operational sequence

Generated from current governed blockers. Portfolio packages create non-duplicating programme child actions and disclose their exact record scope before creation.

Portfolio and programme action registers

Action register

Filter by programme, owner, priority, state and deadline. Select actions for bulk assignment or deadline updates.

OwnerOrganisationDue date

	Priority	Programme	Action	Owner	Status	Due	Evidence

Attributable evidence check

Evidence review queue

Reviewers accept or reject completion evidence independently from its submitter before operational completion can be accepted.

Independent operational decision

Completion review queue

Review evidence and completion submissions without substituting for the formal governance route.

Attributable intervention history

Open escalations

Overdue, blocked, dependency, evidence and ownership concerns remain visible until acknowledged and resolved.

Controlled responsibility transfer

Handover history

Every owner transfer preserves the previous owner, receiving owner, organisations, handover note and acceptance basis.

Reconciled execution progress

Programme and portfolio completion

Completion counts only closed operational actions; it does not imply programme readiness or governance approval.

Operational closure is not source resolution

Closed action—source unresolved

These actions were operationally closed, but the underlying governance gap or source remains open until changed through its formal route.

Exact source required

Create a source-linked action

Use this only for an exact source already present in an approved governed table or programme-binding exception registry. The backend verifies ownership and route before creation.

ProgrammeAction typePriority Action titleDescription Owner emailResponsible organisationDue date Source classA derived gap must use an exact gap key already reconstructed by the portfolio engine.Source typeThe selected type must match a verified governed source.Exact source referenceUse the document ID, review reference, mapping reference, release reference, event reference, binding-exception reference or exact derived gap key.Source labelOptional. The verified source label will prevail.Source routeA typed route cannot establish a governed source relationship.

Source validation. Manual action creation fails when the source class or reference is missing, ambiguous, belongs to another canonical programme or is not present in an approved governed, exception or derived-gap registry.

Inline operational dossier

Selected action

Select an action from the register.

Attributable chronology

Action audit events

View machine-readable action register