Weekly Report — Prompt Template

Module 6, Lesson 6.3 · register entry 2 · weekly cadence · concept shape + recipe delivery paths

What this is. The prompt block for the second scheduled task in your register: a weekly report that summarizes what you shipped, what you said you would do but didn’t, and what changed in the world you track.

How to use. Copy the block. Fill the bracketed fields. The evidence-link rail and the honesty rails stay in — they are what keep the Shipped section from turning into unfalsifiable self-congratulation.

Every item in section 2 has an evidence pointer. No exceptions.

A commit hash, a file path, a thread URL, a capstone entry. If you can’t point, you can’t claim.

Prompt — copy this block

You are producing my weekly report for ISO week <YYYY-WW> in <CANONICAL_TIMEZONE>.
The week runs Monday through Sunday in that time zone.
The idempotency key is the ISO year and week — filename stem “week-<YYYY-WW>”.

OUTPUT CONTRACT
Produce a single Markdown file with exactly five sections, in this order:

1. Header line — run timestamp (ISO-8601 with offset), task name “Weekly report”, run ID, ISO week label, inclusive date range.
2. Shipped this week — numbered list, at most 10 items. Each item: one sentence of what it is + an evidence pointer (commit hash, file path, thread URL, capstone file name, or similar). NO item without an evidence pointer. If the agent cannot find a pointer for a claim it wanted to make, it must omit the claim.
3. Said-I-would, didn’t — numbered list of carried commitments. Each item: what was supposed to happen, what blocked it, whether it carries to next week or drops. Empty this section only if you can honestly produce it after reading all named inputs below; if the inputs were unavailable, note that here AND in the health footer.
4. World changes in the topic — paste the latest refresh summary from <RESEARCH_REFRESH_LATEST_PATH> verbatim if it exists. If it does not exist (no refresh has run yet), produce a one-sentence placeholder: “No research refresh available this week.” Do not synthesize content for this section yourself.
5. Health footer — explicit list of what this report could NOT do: inputs unavailable, scopes denied, files skipped, repos that errored on git log. An empty footer is suspicious; if nothing was limited, say so explicitly.

SCOPE / INPUTS
- Commit history for <REPO_PATHS> over the past 7 days, attributed to <GIT_AUTHOR_EMAIL> only. Include commit hashes.
- Files under <CAPSTONE_FOLDER> modified in the past 7 days; diff <MY_FIRST_LOOP_PATH> against its state 7 days ago and report which sections changed.
- Drafts folder <DRAFTS_FOLDER_PATH> — count of drafts and their ages, to help populate section 3.
- Research refresh — read <RESEARCH_REFRESH_LATEST_PATH> if it exists and paste it into section 4.

VOICE
Direct. Not cheerful. Do not greet me. Do not sign off. No emojis. Section 2 items are one sentence each. Section 4 is eight sentences or fewer (because the refresh enforces that already).

EVIDENCE-LINK RAIL (section 2)
- Every item in the Shipped section must be followed by a specific pointer in square brackets: [commit abc1234], [file path/to/file.md], [thread URL], [capstone entry X].
- If you have an item you want to include but cannot produce a specific pointer, omit it. Do not produce items of the form “worked on X” without evidence.
- If the only evidence is “I remember doing it,” omit. The section is for provable work.

HONESTY RAILS
- Do not invent commit messages, file names, or thread references. If a pointer cannot be verified in the inputs, omit the item.
- Do not include work attributed to someone else in section 2. Only commits with author email <GIT_AUTHOR_EMAIL> count.
- If section 3 is empty after a careful read of all inputs, say so explicitly and also name which inputs were available.
- If <RESEARCH_REFRESH_LATEST_PATH> does not exist, do not fabricate a research synthesis in section 4.

DELIVERY
Write the file to <ARTIFACT_PATH> (filename computed from ISO year+week). Overwrite any existing file with the same name (idempotent; one ISO week, one artifact).

LOG
Append one line to <LOG_PATH>:
  <ISO-8601 timestamp>, weekly-report, <status>, <artifact path>, $<cost>, <one-sentence message>

Fill-in checklist

<CANONICAL_TIMEZONE> — same as the morning brief’s zone.
<REPO_PATHS> — comma-separated absolute paths to repos the agent should git log. If you have none, leave empty and the agent will skip.
<GIT_AUTHOR_EMAIL> — your git commit author email. Prevents the report from attributing others’ commits to you.
<CAPSTONE_FOLDER> — ~/<path-to>/capstone/ or the equivalent.
<MY_FIRST_LOOP_PATH> — full path to the growing capstone file.
<DRAFTS_FOLDER_PATH> — absolute path (or API endpoint) for your drafts folder. For Gmail, a search like in:drafts older_than:7d newer_than:14d — see the recipe for the provider-specific wiring.
<RESEARCH_REFRESH_LATEST_PATH> — ~/ai-architect-academy/automation/research/q-<your-id>/latest.md. If you have not set up the refresh yet, use the placeholder path and the agent will note its absence.
<ARTIFACT_PATH> — ~/ai-architect-academy/automation/reports/week-YYYY-WW.md.
<LOG_PATH> — ~/ai-architect-academy/automation/reports/log.txt.

First-run checklist

Before you save the task on a schedule, run the prompt once on-demand against last week’s data. Open the artifact and confirm:

Section 2 has at least one item, and every item has an evidence pointer in brackets.

Section 3 is not empty — or, if empty, section 5 explains why (inputs unavailable, drafts folder returned nothing, etc.).

Section 4 is either a verbatim paste from the refresh or the placeholder one-liner. It is NOT synthesized content.

Section 5 names at least one real limit, or explicitly declares none in the approved shape.

The filename uses the ISO week format (week-2026-17.md, not week-17.md or 2026-apr-week-of-20.md).

The log line was appended.

One ISO week, one artifact. One Shipped item, one evidence pointer. Read it every Monday.