This is a public explanation of Terra Vita’s architecture, not evidence of deployment, institutional acceptance or an external assurance opinion.
1. The gap between activity and institutional use
A programme can have capable teams, relevant data and a clear intended outcome while still leaving a receiving institution unable to establish the basis for a particular decision.
One possible gap is the connection between evidence and its permitted use: records may exist without clear attribution, review scope, responsibility or unresolved conditions. Finance, capacity and other requirements may also remain unresolved.
The question here is not whether a project is good or bad. It is whether the record allows the relevant institution to assess the case within its own mandate.
2. Why Terra Vita describes more than one missing layer
Each layer answers a different institutional question. Combining them into one generic platform label would hide the very distinctions that reviewers need to see.
- The Governance Spine asks: how are evidence, authority, review, exception handling, and execution connected?
- The Evidence Maturity Layer asks: what can this evidence currently support, and what remains unresolved?
- The Attribution Layer asks: who did what, in which role, under which relationship, at what time, and against which source?
- The Capital-Flow Readiness Layer asks: what prevents this programme or project from moving responsibly toward capital?
- The Reviewer Route asks: in what controlled sequence must a reviewer examine the case?
- The Institutional Assurance Spine asks: what may a receiving institution accept, rely on, release, or formally determine under its own authority?
- The IAS Registry and acceptance pathways ask: where are authority profiles, assessments, exceptions, assurance statements, controlled releases, and institutional outcomes recorded?
These are distinct questions. Keeping them separate helps preserve authority boundaries.
3. The Governance Spine: the load-bearing structure
The Governance Spine is the architecture that connects field evidence to institutional review without pretending that evidence alone creates a decision. It holds the relationships between:
- programme mandates and authority profiles;
- actor identities, roles, and time-bound responsibilities;
- evidence objects, source references, and provenance;
- reviewer actions, findings, exceptions, and corrections;
- capital-flow gates, release conditions, and controlled outputs; and
- institutional acceptance and reliance boundaries.
The Spine is not an approval engine. It is the structure that makes it possible to reconstruct how a case moved, what evidence supported that movement, which human reviewer acted, and where authority remained.
4. The Evidence Maturity Layer: evidence is not binary
Evidence should not be treated as either present or absent. A photograph, field form, registry entry, contract, geospatial record, invoice, validation report, or sensor reading may all exist while supporting very different levels of institutional reliance.
The Evidence Maturity Layer distinguishes between evidence that is merely captured and evidence that is:
- attributable to a known actor, place, activity, and time;
- complete enough for its stated purpose;
- internally consistent and externally corroborated where required;
- reviewed against defined criteria;
- locked or controlled against silent alteration;
- admissible within the relevant reviewer route; and
- capable of supporting a specified reliance condition.
This helps distinguish captured records from evidence suitable for a stated decision. It also allows a project to show progress honestly: not “ready” or “not ready,” but which evidence has matured, what it can support, and what must happen next.
5. The Attribution Layer: identity must survive complexity
Climate and development programmes operate through networks of borrowers, operators, farmers, field officers, aggregators, service providers, validators, government bodies, and funding institutions. Names alone are not enough.
Institutional attribution requires the system to distinguish clean matches from weak overlaps, near-duplicate records, genuine multi-role actors, changing relationships, and contradictions. It must preserve the timestamps, source references, and metadata needed to reconstruct the actor-resolution judgement.
This is not only an identity-management problem. It is a governance problem. When an actor changes role, acts for more than one entity, appears under inconsistent records, or is linked to conflicting evidence, the reviewer must be able to see what was resolved, what remains uncertain, and who accepted the residual risk.
6. The Capital-Flow Readiness Layer: translating evidence into governed movement
A compelling narrative is not sufficient to establish suitability for a funding pathway. The relevant institution must assess the case under its own requirements.
The Capital-Flow Readiness Layer therefore turns governed evidence into controlled outputs such as:
- decision-ready dossiers;
- capital-flow readiness assessments;
- failure-mode diagnostics;
- operator upgrade plans;
- portfolio evidence summaries; and
- sovereign or institutional reporting outputs.
These outputs expose blockers and required upgrades. They do not constitute a credit rating, investment recommendation, funding approval, or guarantee that capital will be deployed. Their function is to make the basis for further institutional review visible and reconstructable.
7. The reviewer route: make scope and responsibility explicit
Publicly, the principle is straightforward: establish the decision and authority boundary; identify the evidence and its limitations; record human assessment; preserve exceptions; and state the permitted use of the output.
The detailed review instruments and acceptance criteria belong in an appropriately controlled institutional process, not in this public article. A review finding does not transfer decision authority to Terra Vita, an operator or an automated system.
8. Institutional reliance is separate from execution
A programme may have a coherent evidence chain and still not satisfy a receiving institution’s mandate, criteria or approval requirements.
Terra Vita’s Institutional Assurance Spine is an architecture for recording the scope of review, relevant conditions and limits on reliance. It does not itself confer institutional acceptance or issue an independent assurance opinion. Any formal decision remains with the institution or authorised professional responsible for it.
A review record should show what was assessed, by whom, against which applicable criteria, with which exceptions and for what purpose. An institutional outcome should be recorded as confirmed only when the responsible institution has determined it.
9. Why the layers must exist together
The layers form a governed chain:
- Field activity produces evidence.
- Attribution connects that evidence to actors, roles, relationships, places, and time.
- Evidence maturity determines what the evidence can support.
- The Governance Spine routes evidence, review, authority, correction, and execution.
- Capital-Flow Readiness identifies blockers and produces controlled readiness outputs.
- The reviewer route structures human assessment.
- The Institutional Assurance Spine structures the record of acceptance review, reliance conditions, exceptions and controlled sharing.
- The receiving institution makes any formal decision that belongs to it.
Removing one layer weakens the chain. Attribution without maturity may identify the source of evidence without proving what it can support. Maturity without governance may produce validated evidence with no route to authority. Readiness without assurance may expose blockers without establishing institutional acceptance. Assurance without a governed evidence chain may create confidence that cannot be reconstructed.
10. What changes when the architecture is present
When these layers operate together, institutions can ask better questions:
- Which evidence is available, and at what maturity?
- Who is attributable for each action, record, and exception?
- Which blocker prevents movement, and who owns its resolution?
- What has a reviewer actually assessed?
- What may the receiving institution rely on?
- What remains conditional, disputed, or outside scope?
- Who retains the authority to approve, release, insure, fund, or adopt?
This does not eliminate risk. It makes risk, evidence, judgement, and authority visible enough to govern.
About this version
This archive article has been revised for clarity and scope. Its original publication date is not recorded; the date shown identifies this revision, not an inferred first publication.
Fracture → Signal → Spine → Assurance