Conway's Law - sgml/signature GitHub Wiki

- **Encapsulation**  
  Bundles related data and behavior within a single unit (class) to protect internal state and expose only necessary interfaces. In the context of PAM, this ensures each `Activity` manages its own inputs, logic, and outputs without leaking implementation details.

- **Single Responsibility**  
  Each class or object serves one well-defined purpose. For example, an `Activity` object focuses solely on executing its designated task, while a `Validator` or `Notifier` handles auxiliary concerns—streamlining complexity and maintainability.

- **Specialization**  
  Extends base behavior through subclassing. A generic `Activity` may be subclassed into `ScriptedActivity` or `ManualActivity`, each implementing task execution in its own way while inheriting shared structure from the parent.

- **Composable Sub-Activities**  
  Allows nesting or coordination of smaller activity units within a larger workflow component. Each sub-activity operates independently but contributes to the overall state—ideal for modeling multi-step tasks using helpers, DSL hooks, or chained executables.

- **Dependencies**  
  Refers to external conditions or upstream activities that must be completed or available before an activity can proceed. These are modeled as required object relationships or `preconditions` that enforce sequencing in execution flows.

- **Blockers**  
  Represent active constraints or conflicts that prevent an activity from progressing. This may include resource contention, missing approvals, or failed validation checks—typically triggering fallback logic or escalation paths in well-designed OOP workflows.

- **Risks**  
  Denotes uncertain events or conditions that may negatively impact activity execution. These are flagged and tracked, often encapsulated in `Risk` objects with probability, impact, and mitigation strategies—supporting dynamic decision-making and adaptive flow control.

                         ┌────────────────────────┐
                         │      Initiation        │
                         │  Identify delivery need│
                         └──────────┬─────────────┘
                                    │
                                    ▼
                         ┌────────────────────────┐
                         │     Requirements        │
                         │  Scope + Success Criteria│
                         └──────────┬─────────────┘
                                    │
                                    ▼
                         ┌────────────────────────┐
                         │      Standardization    │
                         │  Define process templates│
                         └──────────┬─────────────┘
                                    │
                                    ▼
                         ┌────────────────────────┐
                         │      Resource Setup     │
                         │  Assign roles/tools     │
                         └──────────┬─────────────┘
                                    │
                                    ▼
                         ┌────────────────────────┐
                         │     Execution Phase     │
                         │  Deliver per standards  │
                         └──────────┬─────────────┘
                                    │
                                    ▼
                         ┌────────────────────────┐
                         │     Monitoring & QA     │
                         │  Track metrics & quality│
                         └──────────┬─────────────┘
                                    │
                                    ▼
                         ┌────────────────────────┐
                         │     Feedback Loop       │
                         │  Post-mortem & refine   │
                         └────────────────────────┘