From a8c9d3aa442647e70a2b36537a0b638aebfb5c71 Mon Sep 17 00:00:00 2001 From: Vilas Chitrakaran Date: Fri, 20 Sep 2024 11:58:30 +0100 Subject: [PATCH] Refactor: Revise for clarity --- process/process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/process.md b/process/process.md index a4834ec..ee94c37 100644 --- a/process/process.md +++ b/process/process.md @@ -3,7 +3,7 @@ - Follow the [developer's guide](developer_guide.md) for writing software - Build core technologies from first principles - Option to delegate non-core technologies to a ‘few’ third party libraries, but: - - Only choose third-party components that provide mechanisms (atomic capabilities), not policies (architectural limitations, design constraints) + - Only choose third-party components that provide mechanisms (atomic capabilities), not policies (how they are used). Rationale: Policies impose architectural limitations and design constraints - Avoid 'frameworks': ROS, Qt - Use [Layered Databus Architecture](lda.md) for large hierarchical distributed systems. - Prefer behaviour trees over FSMs for task orchestration and fault recovery. Rationale: debuggability, extendabilty