Implement Transmission Canonization Workflow

Cody,

The transmission issue system is now functioning correctly. Gregory can create structured GitHub Issues directly in the repository, and Brandon Hatfield, LPC can review them immediately.

The next step is implementing the archive workflow.

Current behavior:

• transmissions are created as GitHub Issues
• the Issues remain discussion records only
• no permanent markdown archive files are being generated yet

Required behavior:

• approved Issues should automatically become markdown files in the repository
• Brandon Hatfield, LPC should not need to manually copy and paste issue contents

Implementation goals:

1. Trigger Mechanism

Create a GitHub Action or equivalent workflow that activates when:

• a specific label is added
• OR an issue is closed with approval
• OR another lightweight supervised trigger is selected

Suggested labels:

• canonize
• Active Canon
• approved

2. Markdown Export

When triggered:

• read the issue contents
• preserve markdown formatting
• create a markdown file in the repository

Suggested directory structure:

/transmissions/2026/ CC-TX-2026-05-27-001.md CC-TX-2026-05-27-002.md CC-TX-2026-05-27-003.md

3. Metadata Preservation

Preserve:

• transmission ID
• title
• sender
• recipient
• tags
• summary
• body
• decisions
• next actions
• timestamps

4. Workflow Philosophy

GitHub Issues should function as:

• drafting space
• collaboration space
• discussion history

Markdown files should function as:

• durable archive entries
• finalized historical records

The automation layer should bridge those two states.

Priority: This workflow is now a primary infrastructure task because the transmission system is already operational.

End transmission.