The Route Map turns Terra Vita's architecture into a repeatable institutional operating system. Each route defines who enters, what they may see, what they may change, what they must verify, which output may pass forward, and where the record must stop when evidence or authority is insufficient.
A route may complete, remain in review, be held, or escalate. It may not silently skip a required gate or convert a downstream narrative into upstream evidence.
One vocabulary across ministries, funds and operators.
Not enteredThe route's entry conditions have not yet been met.In reviewAn authorised reviewer is testing the required conditions.Held / escalatedA material gap, contradiction, conflict or authority issue stops progression.CompleteThe route's bounded exit gate is met; this is not external institutional approval.
Route specifications
Permissions, duties and exit gates.
Open each route to see the institutional workflow. Every route uses the same programme_code and carries forward open limitations and exceptions.
TV-R01
Governance Route
Controlled output: Governance Context Record
Entry pointA mandate, programme code and accountable institution or authority are identified.
May seeAuthority profiles, mandates, decision rights, evidence rights, conflicts and continuity dependencies.
May changeGovernance metadata only through an authorised, versioned source.
Must verifyLegal identity, mandate, scope, signatory authority, reviewer appointment and retained decision authority.
ProhibitedCreating evidence, validating technical results or assigning external approval.
Exit gateMandate and authority boundary are explicit; unresolved authority gaps are logged.
TV-R02
Evidence Route
Controlled output: Evidence Maturity Record
Entry pointA source object enters controlled intake under a programme code.
May seeOriginal evidence, metadata, custody history, completeness checks and limitations.
May changeAnnotations, classifications and controlled correction records; never the original source object.
Must verifySource, time, context, integrity, completeness, custody and admissibility for the stated purpose.
ProhibitedRewriting source evidence, suppressing adverse material or importing communication claims as evidence.
Exit gateEvidence is attributable, preserved and either reviewable or formally held with gaps.
TV-R03
Attribution Route
Controlled output: Attribution Defensibility Record
Entry pointEvidence objects have identifiable actors, sites, assets or institutional relationships requiring resolution.
May seeIdentity records, role histories, relationship records, site bindings and provenance references.
May changeResolution links and reviewer findings; source identities remain preserved.
Must verifyWho did what, where, when, under which role and with which evidentiary support.
ProhibitedInferring identity without a recorded basis or collapsing conflicting identities for convenience.
Exit gateAttribution is reconstructible or the unresolved ambiguity is explicitly retained.
TV-R04
MRV Route
Controlled output: MRV Alignment Record
Entry pointEvidence is linked to an indicator, baseline, methodology, target or monitoring obligation.
May seeMethods, indicator definitions, baselines, measurements, QA records, limitations and version history.
May changeMethodology or QA records through controlled versions; never historical observations.
Must verifyMethod suitability, baseline source, measurement lineage, QA outcome and limits on interpretation.
ProhibitedConverting planned monitoring into observed performance or treating incomplete lineage as validated results.
Exit gateThe evidence-to-indicator lineage is complete enough for the stated review purpose.
TV-R05
Communication Route
Controlled output: Controlled Communication Claim
Entry pointA claim, report, narrative, dashboard or external statement is proposed.
May seeGoverned evidence references, approved interpretations, limitations, audience and release purpose.
May changeWording and presentation within the approved evidence and authority boundary.
Must verifyEvery material claim is evidence-linked, uncertainty is retained and no authority is implied beyond the record.
ProhibitedAdding unsupported certainty, hiding exceptions, altering evidence or presenting readiness as approval.
Exit gateThe claim is traceable, bounded, reviewable and approved for the named audience and purpose.
TV-R06
Assurance Route
Controlled output: Assurance Statement or Controlled Release Recommendation
Entry pointThe preceding routes have produced reviewable records and open exceptions are visible.
May seeRoute outputs, reviewer findings, exceptions, protocols, reliance conditions, releases and withdrawals.
May changeAssurance findings, conditions, release posture and withdrawal status within delegated authority.
Must verifyRoute completion, reviewer independence, exception materiality, purpose-bound reliance and authority retention.
ProhibitedIssuing external institutional approval, funding decisions, ratings or regulatory determinations without the relevant mandate.
Exit gateA bounded human determination is recorded; the receiving institution retains its own decision.
Contamination barriers
What cannot cross the boundary.
These controls prevent evidence from being changed by the narrative, and prevent the platform from inheriting authority it does not hold.
B-01 / B-02
Source preservation
Original evidence is never overwritten by interpretation or communication. Communication cannot flow backward and become evidence.
B-03 / B-04
Role and exception integrity
Dual roles are disclosed and controlled. Open exceptions, adverse findings and limitations persist into downstream outputs.
B-05 / B-06
No automatic promotion
Status advancement is a recorded human determination. Controlled outputs are purpose-bound, version-bound, logged and revocable.
Handoff contract
What moves between routes.
From
Controlled handoff
Required references
Cannot be passed as
Governance → Evidence
Mandate, authority profile, purpose and evidence rights
programme_code · profile version · responsible institution
Automatic legal, fiduciary, funding or regulatory decision
IAS interlock
Operational routes feed institutional acceptance.
The six-route map protects how evidence is produced and moved. IAS determines whether a particular receiving institution can rely on the resulting outputs under its own criteria and mandate.
Operational spine
Six routes
Governance, Evidence, Attribution, MRV, Communication and Assurance produce controlled, reconstructible records.
Institutional acceptance
IAS Step 0–6
Institutional context, evidence maturity, attribution defensibility, assurance pathways, capital-flow readiness, authority lock and module-specific evidence are assessed for reliance.
Every ministry, MDB, fund, NGO or private institution may add its own criteria and reviewers. The route identities, handoff controls and contamination barriers remain stable, allowing training, deployment and audit across different institutional environments.
Controlled public rendering of TV-RRM-1.0. Machine-readable version: /assets/reviewer-route-map-v1.json
