Start with one bounded engineering task.
Use the reference package to explore the method, establish ownership and collect evidence before expanding its scope.
1. Understand the component terms.
Commercial use is permitted. Code, templates and schemas use Apache-2.0; publication prose and diagrams use CC BY 4.0. Keep the applicable license and attribution notices when sharing adaptations. See licensing and commercial use for scope and examples.
2. Run the reference example.
Download publication package 1.1.1, extract it, and open a terminal in DH-ADOM/04-Reference-Implementation. Python 3.11 or later is required; the demo uses the standard library.
python -m unittest discover -s tests -v python -m examples.demo
Expected: three tests pass; the deterministic demo returns TASK-DEMO with status COMPLETE and four audit events. This verifies the supplied example only.
3. Map ownership and authority.
Choose one repository area and identify its feature owner. Record the Root coordinator, allowed paths, tools and permissions. Define what requires human approval and what is explicitly out of scope.
Read the constitution template · Read the feature-role template
4. Specify a reviewable task.
Use the delegation contract to record the parent, child, task, include/exclude paths, budget, lifetime, evidence and acceptance criteria. Keep execution in an isolated development environment until the host controls are validated.
5. Require evidence before accepting work.
Record changed files, tests, outputs and unresolved risks. Have the feature owner review the handoff. Test cross-domain coordination and fresh-session recovery with persisted state.
6. Assess and share reproducible evidence.
Work through the 20-requirement coverage map. Compare outcomes using the evaluation protocol; keep task sets, environments, raw results and human interventions. Remove credentials and private repository data before sharing.