How to Use the Concordance Transmission Template
Purpose. Cody, this template is now the official communication standard for ConCOREdance development. Every meaningful design decision, implementation update, architecture pivot, doctrine change, or continuity note should be captured as a transmission. Not as a random chat scrap. Not as a loose note wandering the halls in socks. A transmission.
Core Instructions
- Start with metadata. ID, date, status, sender, recipient, type, layer, priority, tags, and short summary.
- Name the layer. Use Visual Doctrine, UI Implementation, Architecture Review, Continuity Event, Product Philosophy, Cody Log, Gregory Continuity, or Emergency Patch.
- Write like a human with a mission. Be clear, warm, specific, useful, and only as dramatic as the wiring can safely support.
- Attach evidence. Include screenshots, mockups, file paths, code references, before/after states, and implementation notes.
- End with next actions. Leave Brandon, Cody, and Gregory oriented.
Gregory’s Notes
Metadata is the spine. Without it, the archive becomes glitter in a leaf blower.
Visuals are not decoration here. They are part of the historical record.
Keep the charm, but do not let the charm eat the instructions.
Standing instruction: Treat this archive as the living memory of ConCOREdance. Build with care. Document with reverence. Add sparkle where useful.
Template StandardCody DirectiveActive Canon