Simon
c2c7e654cb
|
2 weeks ago | |
|---|---|---|
| .. | ||
| adr | 2 weeks ago | |
| 00-glossary.md | 2 weeks ago | |
| 01-system-model.md | 2 weeks ago | |
| 02-state-model.md | 2 weeks ago | |
| 03-subscription-model.md | 2 weeks ago | |
| 04-packet-and-stream-model.md | 2 weeks ago | |
| 05-data-packet-policy.md | 2 weeks ago | |
| 06-mesh-model.md | 2 weeks ago | |
| 07-reporting-model.md | 2 weeks ago | |
| 08-api-control-model.md | 2 weeks ago | |
| 09-security-model.md | 2 weeks ago | |
| 10-runtime-and-concurrency.md | 2 weeks ago | |
| 11-testing-and-release-gates.md | 2 weeks ago | |
| 12-migration-plan.md | 2 weeks ago | |
| 13-worker-process-scaling.md | 2 weeks ago | |
| README.md | 2 weeks ago | |
README.md
FreeDMR 2 Architecture Notes
This directory contains the distilled FreeDMR 2 design notes. The older notes in docs/codex-notes.md, docs/freedmr-2-architecture-decisions.md, and the test/API docs remain source material and engineering history.
FreeDMR 2 is not a blind rewrite of packet behaviour. The protected asset is the FreeDMR operating model: DMR packet semantics, dial-a-TG, TG/DMR-ID-centric routing, loop control, source quench, mesh behaviour, RF-side tolerance, data forwarding, and practical amateur-radio interoperability.
Recommended reading order:
00-glossary.md01-system-model.md02-state-model.md03-subscription-model.md04-packet-and-stream-model.md05-data-packet-policy.md06-mesh-model.md07-reporting-model.md08-api-control-model.md09-security-model.md10-runtime-and-concurrency.md13-worker-process-scaling.md11-testing-and-release-gates.md12-migration-plan.md
Architecture Decision Records live in adr/. They record proposed FreeDMR 2 decisions separately from implementation work.
Current FreeDMR 1.x remains live until FreeDMR 2 is tested. Compatibility adapters are allowed where useful, but old HBLink object layout, dashboard socket assumptions, and legacy BRIDGES structure should not define the FreeDMR 2 core.
FreeDMR 2 keeps Twisted initially but is designed for eventual worker-process scaling. Non-packet-path workers such as reporting/global export move first; packet-plane routing workers are a later stage after state ownership and message-boundary tests are proven.