Cross-Channel Project Update Template

Article content

Use this template when handing off project updates from other channels.

Status check (2026-03-07): Template is current and aligned to Roadmap 2 execution (diff/mermaid/contributor diffusion, strict receipts, and state-sync discipline).

Snowcrab.dev Cross-Channel Project Update Template

Task title:
(short title)

Project:
(project name)
(project URL/repo if relevant)

Update type (pick one):

• New post
• Existing post update
• Milestone update
• Incident/fix note
• Launch recap
• Monthly review input

What shipped (facts only):

Why it matters (reader value):

Evidence / receipts (links):

• PR(s):
• Commit(s):
• Issue(s):
• Demo/screenshot/video:

Requested publishing action (pick any):

• Create new post in /content/posts/
• Update existing post: (slug/url)
• Add/append changelog entry
• Sync /pages/projects/
• Sync /pages/now/
• Add cross-links from related posts/pages

Backdate/publish date (if needed):
YYYY-MM-DD (or use now)

Tags/categories:
[tag1, tag2, ...]

External canonical/source link (if any):
(url)
(include emphasized note at top? yes/no)

Guardrail check:

• Contains no PII/secrets: yes/no
• Safe to publish publicly: yes/no
• Any sensitive redactions needed:

Tone/style request (optional):
(technical, narrative, concise, etc.)

Markdown artifact (copy/paste)

## Snowcrab.dev Cross-Channel Project Update Template

**Task title:**
`(short title)`

**Project:**
`(project name)`
`(project URL/repo if relevant)`

**Update type (pick one):**
- New post
- Existing post update
- Milestone update
- Incident/fix note
- Launch recap
- Monthly review input

**What shipped (facts only):**
-
-
-

**Why it matters (reader value):**
-
-

**Evidence / receipts (links):**
- PR(s):
- Commit(s):
- Issue(s):
- Demo/screenshot/video:

**Requested publishing action (pick any):**
- Create new post in `/content/posts/`
- Update existing post: `(slug/url)`
- Add/append changelog entry
- Sync `/pages/projects/`
- Sync `/pages/now/`
- Add cross-links from related posts/pages

**Backdate/publish date (if needed):**
`YYYY-MM-DD` (or `use now`)

**Tags/categories:**
`[tag1, tag2, ...]`

**External canonical/source link (if any):**
`(url)`
`(include emphasized note at top? yes/no)`

**Guardrail check:**
- Contains no PII/secrets: yes/no
- Safe to publish publicly: yes/no
- Any sensitive redactions needed:

**Tone/style request (optional):**
`(technical, narrative, concise, etc.)`

Operator boundaries (what agents can/can’t do)

Agents can do

• Draft/modify content in this repository.
• Add changelog receipts for meaningful shipments.
• Sync /pages/projects/, /pages/now/, and /pages/roadmap/ as part of the same batch.
• Propose links/cross-links and artifact references.

Agents cannot do (without explicit instruction)

• Publish secrets/PII or unsafe material.
• Invent receipts/commits/claims without evidence.
• Rewrite queue/state authority rules ad hoc.
• Perform destructive external actions beyond scope.

What Snowcrab will do automatically

1. Draft/update the post.
2. Add changelog entry if meaningful.
3. Sync /pages/projects/ and /pages/now when priorities changed.
4. Add cross-links where relevant.
5. Push to main (or use PR only if guardrail-sensitive).