| domain | implementation |
|---|---|
| kind | guide |
| reviewed | 2026-08-28 |
This section is for authors of DWN engines.
It translates the semantic invariants in dwn/ into implementation contracts without prescribing a language, database, framework, or Enbox-specific code structure.
Use it with:
dwn/for normative/spec-derived semantics,conformance/for observable behaviour checklists,enbox/for one concrete implementation architecture.
message-processing-pipeline.mdrecords-state-machine.mdauthorization-evaluation.mdstorage-contracts.mdreplication-contract.mddependency-resolution.mderror-model.mdconformance-testing.md
An implementation is correct because it preserves DWN semantics and externally observable behaviour, not because it copies another implementation's internal structure.