Validation and Integrity
Holochain validation is where a distributed network application (DNA) decides whether data is acceptable inside a shared application space. The Holochain validation guide treats validation rules as core application logic for data integrity.
Civic Meaning
Section titled “Civic Meaning”For this project, validation should answer questions such as:
- Is the author a member of the relevant organization?
- Does the author hold a role that can create this record?
- Does the record point to the agreement or resolution it depends on?
- Does the expense approval stay within the budget and role scope?
- Does a stewardship review avoid exposing private household fields to the wrong audience?
Validation turns institutional rules into software checks. It does not make a record legally valid by itself.
Boundary
Section titled “Boundary”A valid Holochain record can still need an external filing, bank transaction, accounting entry, lease, title record, or legal signature. That is why Boundaries and Bridges is part of the validation story.
Design Rule
Section titled “Design Rule”Place validation near the smallest rule that can honestly enforce it.
| Rule kind | Likely home |
|---|---|
| Agent identity and membership format | Shared kernel. |
| Proposal, vote, and resolution rules | Governance domain. |
| Expense approval authority | Treasury workflow. |
| Waitlist, resale, and stewardship review constraints | Housing stewardship. |
| Economic event vocabulary | Holochain Resource-Event-Agent (hREA) or ValueFlows reference layer. |
| External legal sufficiency | External system or professional review. |
Read What Holochain Is for the underlying Holochain model and Why Holochain Fits before promoting a domain rule into a shared protocol rule.