IndrasNet Governance Validation Demonstrator
IndrasNet is a research demonstrator for governance validation in AI-enabled infrastructures.
The focus is on decision traceability, explicit boundaries between advisory AI and the enactment boundary, and reproducible validation artifacts.
Example: governance rule validation. Artifact: reproducible FSM audit record.
All terms are used in a research and validation context only.
Project scope
This project investigates governance validation mechanisms for contexts where:
- decisions may involve advisory AI components
- responsibility and authority boundaries must be explicit
- post-hoc verification of decisions is required
- on-chain enactment remains outside the governance layer
The work is implemented as a research demonstrator with on-chain and off-chain evidence artifacts and a DevNet-based evidence layer.
What this project does
- Validates governance rules and decision traces
- Records decisions with auditable artifacts
- Provides reproducible verification steps
- Defines explicit boundaries and responsibilities
What this project does not do
- No on-chain enactment or operational automation
- No financial control or automation
- No decision enforcement or authority enactment
- No economic activity, tokens, or incentive layer
Validation and evidence
A DevNet-based validation dashboard provides verifiable evidence of the demonstrator state.
This dashboard exists as an evidence layer only and does not represent an interactive governance setup.
- Validation dashboard: dao.indrasnet.ee
- Open-source governance engine: fsm-governance-engine-lib
- Governance core repository: indrasnet-dao
- What is being validated: validation scope
Evidence artifacts overview
- Verification manifest: manifest — proves reproducible validation state; does not prove production readiness.
- On-chain demonstrator state: DevNet dashboard — proves a demonstrator instance; does not prove operational deployment.
- Repository + commit reference: indrasnet-dao — proves source availability; commit reference anchored in the manifest.
- Validation steps: documentation — proves the verification procedure; does not guarantee external audit completion.
How to review this project
- Read the explicit non-goals to understand scope boundaries.
- Open the validation scope and confirm what is being tested.
- Inspect the validation dashboard for demonstrator evidence.
- Download the verification manifest and review the artifacts listed.
- Cross-check repositories and commit references in the manifest.