Rules stay versioned
Every encoded obligation retains its source, effective date, jurisdiction, interpretation owner, and applicability decision.
New design-partner application · controlled beta
Make every ecological compliance conclusion inspectable.
Viridis connects a business's activities, obligations, operational and ecological evidence, calculations, formal checks, external reviews, decisions, and monitoring into one Verified Ecological Compliance Chain.
Viridis is not a regulator, law firm, accredited compliance auditor, certification body, or field-science authority. Lean checks conditional logic; it does not establish that evidence is true, interpret law, or grant regulatory or certification acceptance.
The product
One compliance cycle. Every warrant attached.
The engagement starts with one business activity, reporting cycle, accountable compliance owner, and consequential decision. It produces a Compliance Decision Record—not a certificate or legal opinion.
Evidence stays attributable
Every input carries provenance, permission, date, authority, uncertainty, hash, and visible gaps.
Logic stays checkable
Suitable rule relationships can be encoded and kernel-checked without overstating what the proof establishes.
Authority stays external
Counsel, regulators, certifiers, accredited auditors, scientists, and business owners keep their actual decisions.
Full-cycle architecture
From scope to monitoring and re-audit.
01 · SCOPE
Scope the cycle
Which activities, assets, jurisdictions, reporting periods, and decisions are in scope?
Record: Authorized boundary, accountable owner, review period, exclusions, and decision deadline
Authority: Business compliance owner
02 · OBLIGATIONS
Version the obligations
Which laws, permits, contracts, standards, policies, and voluntary commitments apply?
Record: Source authority, effective date, jurisdiction, interpretation owner, rule version, and applicability decision
Authority: Qualified legal, regulatory, certification, or policy authority
03 · EVIDENCE
Bind the evidence
What operational and ecological evidence supports each control?
Record: Source, date, collection authority, permissions, hash, coverage, uncertainty, and missing evidence
Authority: Authorized data owner and qualified evidence reviewer
04 · COMPUTE
Recompute the controls
Do the declared measurements satisfy the versioned thresholds and calculations?
Record: Executable method, full-precision inputs and outputs, units, tolerances, exceptions, and recompute hash
Authority: Named technical reviewer
05 · FORMAL CHECK
Check the logic
Does the conclusion follow from the encoded rule and its stated hypotheses?
Record: Lean theorem identity, hypotheses, axiom set, source hash, build receipt, and result
Authority: Formal-method reviewer
06 · EXTERNAL REVIEW
Preserve external authority
Which conclusions require counsel, regulator, certifier, accredited auditor, or field-science acceptance?
Record: Required reviewer, submitted package, response, conditions, unresolved questions, and authority receipt
Authority: The qualified external party responsible for the decision
07 · DECISION RECORD
Issue the decision record
What passed, failed, remains held, or is not applicable—and why?
Record: Control matrix, exceptions, corrective actions, limitations, approvals, decision owner, and signed release
Authority: Business decision owner
08 · MONITOR
Monitor and re-audit
What evidence, operational, or rule change reopens the chain?
Record: Monitoring cadence, change triggers, expiring evidence, rule updates, incidents, corrections, and superseding record
Authority: Business compliance owner with named external escalation path
Fail-closed findings
Unknown is a result—not an invitation to guess.
PASS
The encoded control passes on complete declared evidence and all required authority is resolved.
HOLD
A rule, input, hypothesis, reviewer, or approval is missing, stale, or unresolved.
FAIL
Declared evidence fails the encoded control, or the responsible external authority rejects it.
NOT APPLICABLE
The accountable interpretation authority records why the control is outside this scope.
Compliance Decision Record
What the business receives.
- A versioned obligation and applicability register
- An evidence inventory with permissions, provenance, uncertainty, and gaps
- A recomputable control matrix with explicit thresholds and exceptions
- Lean identities and build receipts for the logic that is suitable for formal checking
- PASS / HOLD / FAIL / NOT APPLICABLE findings with corrective actions
- A signed Compliance Decision Record and monitoring/re-audit triggers
What Lean contributes
Lean can check that an encoded compliance conclusion follows from the named rule, declared inputs, and stated hypotheses. The receipt identifies the theorem, source hash, assumptions, and build result.
What remains human and institutional
Applicability, legal interpretation, evidence authenticity, ecological validity, materiality, corrective action, certification, regulator acceptance, and the final business decision remain with their accountable authorities.
Founding design-partner audit
Start with one business activity and one reporting cycle.
We will scope one consequential ecological compliance decision, identify which controls are computable or formally checkable, and agree the evidence, external reviewers, fee, timeline, and acceptance criteria in writing.
No public price or delivery guarantee is claimed. Sensitive records stay out of the public intake.
Best early fit
- A land-, water-, biodiversity-, emissions-, or restoration-dependent operation
- A repeat compliance or assurance cycle with explicit rules
- A named internal owner and qualified external review path
- Authority to discuss a bounded, non-sensitive example first