aylee Weekly review
- Read the week’s receipts, active and newly closed workstreams, project binders, decisions, weekly plan, commitments, and backburner.
- Compare planned versus actual work. Distinguish outcomes from activity and surface unplanned work, carried work, stale state, and missing evidence.
- Identify corrections or recurring patterns. Propose system changes, but do not rewrite skills or policy without explicit approval.
- Ask for next week’s priorities and reconcile them with open commitments and workstream next actions.
- Always write
memory/reviews/YYYY-WNN.md, whether or not Git exists. Update weekly plans without deleting prior reviews, corrections, or backburner history; use status/tombstones where needed. - Do not create receipts for review or planning documents. If the review also changes a workstream, create a receipt only for that workstream revision transition.
Git may provide supplemental evidence or an optional commit after authorization. It is never the reason history is safe to delete.