Ontology Adapter
Translates method-native outputs into the canonical Integrity construct (ΔI). Methods do not change to conform.
RCCS — The VLAS verification pipeline
Sensor to reported value
Eight layers, three gates. Field measurement enters at the top; nothing reaches Impact NAV without clearing all three.
PLOP governspipeline executeslots formprice setsiNAV publishesgates approve
Data.PLOP — the Project Level Operations Policy
Registered for the place before any pipeline activity. Immutable within a measurement window; amendment is versioned and retained. Every downstream artifact carries plop_id and plop_version.
Input Parser & Governance
Assembles the IndicatorPackage: measurements, provenance, FPIC evidence, method configuration, timestamps.
Gate 1 · Independent Verifier
A verifier independent of the submitter approves or rejects the package. Rejection ends the run — the credit never enters.
Capital Router
Allocates verified ΔI across the Five Capitals using α weights and β spillover dampeners. Non-inflation constraint: Σα ≤ 1.0.
Temporal Engine
Consumes the quantity coefficients — velocity, acceleration, permanence, stewardship, uncertainty. These qualify the quantitative.
Issuance Engine
Executes the issuance kernel and generates the CalcProof.
Gate 2 · CalcProof Approval
A different individual from the Gate 1 verifier signs or rejects the CalcProof. The calculation is re-performable from artifacts alone.
Credit Router & Registry
Forms recognised VLAs into lots under the PLOP.
Pricing & Venue
Admissible marks only — volume-weighted prices from contracted, verified transactions.
Portfolio & Reporting
Computes Impact NAV, produces the NAVSnapshot and the audit pack.
Gate 3 · NAV Committee
The committee approves or rejects the audit pack before the lot's value is recognised in Impact NAV.
Figure 2.2 — The VLAS pipeline: a registered PLOP governs eight processing layers and three approval gates, and only signed output reaches Impact NAV