# Inbox drop template

This is the **template** the agent fills in to send project updates to myPKA's
Team Inbox. The `SKILL.md` holds the rules; this file is the literal markdown that
gets written. Tune this file to change what myPKA receives — it's intentionally
separate from `SKILL.md` so the format can be retuned (e.g. if myPKA mis-files
something) without touching the skill's instructions.

## How it's used
1. Resolve the myPKA path from the project config (`hostname -s` → `mypkaPath`).
2. Fill the template **from real workspace records only** (the configured
   `sourcesOfTruth` and the actual decisions made this session). Never fabricate.
   **Include a section only if it has something to say — omit empty sections
   entirely (no "nothing this update" / "no change" filler).**
3. Write the result to `<mypkaPath>/<inboxSubdir>/<dropPrefix>-YYYY-MM-DD-HHMM.md`.
   Import is **manual** in myPKA, so the drop just sits there until the user
   processes it ("process the inbox") — the drop itself is the dry run.

## The two-stream split (the point of this template)
Every drop separates **the why** from **the what**:
- **Context → journal.** Reasoning, decisions, tradeoffs, what felt uncertain —
  the stuff lost if you only keep the operational record.
- **Changes / Tasks / About → project page.** Operational facts, the task mirror,
  durable project info.

(Full rules live in `SKILL.md`: classify-don't-route, omit-empty, decision
rationale in Context not Tasks, altitude, one-way task mirror, conditional About.)

---
## TEMPLATE (everything below the line is what gets written to the inbox)
## Include only the sections that apply; the About variants are alternatives.
---

# {{PROJECT_NAME}} Project Update — {{DATETIME_ISO}}

<!-- {{DATETIME_ISO}}: ISO 8601, local time, e.g. 2026-06-06T14:30 (add the
     timezone offset, e.g. 2026-06-06T14:30-07:00, if myPKA spans zones).
     Use ISO — this drop is parsed by an agent and the source filename (which
     carries the date) is deleted once filed, so the in-body date must stand
     alone, be unambiguous, and sort correctly. -->


> Inbox drop from the {{PROJECT_NAME}} project — a separate repo myPKA tracks at
> a high level. File each section wherever it belongs per your usual conventions:
> **Context** is reasoning for the journal; **Changes / Tasks / About** are
> project-page material. Delete this file once filed.

## Context
_The why: decisions, tradeoffs, what was uncertain — journal material._
{{REASONING as bullets}}

## Changes
_The what: operational facts of what changed._
{{CHANGES as bullets}}

## Tasks
_Snapshot mirrored from the {{PROJECT_NAME}} repo (that repo is the source of
truth) — a reference for what's done / pending, not your authoritative task list._
**Completed since last update**
{{COMPLETED_TASKS as checklist}}
**Outstanding**
{{OUTSTANDING_TASKS as checklist}}

## About the project
<!-- First import (page empty/thin): full overview. Description states prior state. -->
_Initial overview — project page was empty._
{{FULL_OVERVIEW: what it is, main components, pipeline, light "how it's built", status}}

<!-- OR, material change only: -->
_Changed: {{WHAT_CHANGED}}._
{{ONLY_THE_CHANGED_FACTS}}