# Telegram Output and Documentation Flow

## Purpose
Define the default delivery pattern for long-form work so Telegram stays readable while durable process documentation lives in the right system.

## Operating Rule
Use this default pattern in Braden's Telegram DM:
- Short outputs in Telegram
- Long drafts in workspace artifacts
- Finalized procedures in Notion

## Definitions
### Telegram
Use for:
- decisions
- approvals
- short summaries
- status updates
- next actions

### Workspace artifacts
Workspace artifacts are local files created in the OpenClaw workspace.
Use them for:
- drafts
- schemas
- SQL
- technical specs
- runbooks in progress
- intermediate structured deliverables

### Notion
Use Notion for:
- finalized processes
- SOPs
- reusable procedures
- living operational documentation
- reference pages meant to be revisited

## Delivery Standard
### Default
When output is long or highly structured:
1. Send a concise Telegram summary
2. Store the full draft as a workspace artifact
3. If the content is a process/procedure worth keeping, publish the cleaned version to Notion

### Telegram-specific rule
Keep visible Telegram replies to a single message when practical.
If content risks message splitting:
- compress the in-chat summary
- move large code/spec/SQL blocks to a workspace artifact
- publish final process docs to Notion when appropriate

### Technical material
For highly technical deliverables:
- workspace first for drafting and revision
- Notion second for finalized human-facing procedure docs

## Why
This pattern:
- avoids Telegram multi-part message sprawl
- preserves detailed drafts locally
- creates a clean final home for durable documentation
- separates working artifacts from polished operating documentation

## Decision Rule
Choose the destination by intent:
- Need fast conversation or approval -> Telegram
- Need editable draft or machine-friendly file -> Workspace artifact
- Need stable long-term procedure/reference -> Notion

## Recommended Default Workflow
1. Draft locally
2. Review in summary form over Telegram
3. Publish final version to Notion
4. Keep the workspace draft when technical fidelity matters

## Notes
- Telegram message length limits still apply even when streaming is off
- Streaming and length splitting are separate behaviors
- Not every long artifact belongs in Notion; only durable process/procedure/reference material should be promoted