https://github.com/ll782/dc5b-protocol

DC5B Protocol
https://github.com/ll782/dc5b-protocol

Last synced: 2 months ago
JSON representation

DC5B Protocol

• Host: GitHub
• URL: https://github.com/ll782/dc5b-protocol
• Owner: LL782
• License: gpl-3.0
• Created: 2023-09-28T21:15:26.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2023-11-01T08:13:35.000Z (over 1 year ago)
• Last Synced: 2025-01-27T07:42:01.151Z (4 months ago)
• Homepage:
• Size: 24.4 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# DC5B Protocol

Systematic decision making for DC5B

## Comms routines

> I picture a flow diagram, state machines, a system with queues, triggers and tasks that makes sending comms almost habitual.

>

> We need to do this and need to do it well so I think a designed system that we can evaluate, reason about and refine is the way to go.

>

> Don't get me wrong, the content must be heartfelt and real, but the routine is automatic. Feels like one of those examples where defining your own boundaries benefits your creativity within.

_[@LL782](https://github.com/LL782) Sept 2023_

### DC5B comms in context

![DC5B - Comms](https://github.com/LL782/dc5b-protocol/assets/353044/604b5883-bbd2-4faf-8956-983f1686dd6f)

For Communication Channels in a broader context checkout [Miro > DC5B > Comms](https://miro.com/app/board/uXjVO3dkXBo=/?moveToWidget=3458764560836836090&cot=14)

### Working draft

```mermaid

graph LR;

    E[External Communications] --> F[P1: Social media & marketing presence];

    E --> G[P2: Customer newsletters];

    E --> H[P3: Press releases];

    

    A[Internal Communications] --> B[P1: Regular team meetings];

    A --> C[P2: Internal messaging platform];

    A --> D[P3: Email updates];

```

P1 = highest priority based on impact on reputation, money-flow and productivity. _Maybe somekind of happiness index too?_