Changelog

Dated DRAFT entries recording what landed on main, generated by scripts/kb-sync.sh and then fleshed out by hand.

Git already records what changed. These entries exist to capture the why — intent, user-facing impact, and follow-ups.

File naming

knowledge/changelog/YYYY-MM-DD-<short-sha>.md

<short-sha> is the abbreviated main HEAD at sync time, so entries are unique and traceable even with several syncs in one day. If a name somehow collides, the script appends -2, -3, …

The example entry in this folder uses -example instead of a SHA; it is illustrative only and is not produced by automation.

Hand-written entries that record a documentation or knowledge-base event rather than a sync window use a descriptive slug instead of a SHA (for example 2026-07-30-knowledge-base-seed.md). They are written directly and do not touch .kb-state.

Entry anatomy

1. Sync metadata — branch, previous SHA, new HEAD SHA, commit count, generated timestamp.
2. Commits — abbreviated SHA + subject, oldest first.
3. Changed files — deduplicated path list for the range.
4. TODO sections — what shipped and why, architecture/integration impact, follow-ups.

Workflow

1. Sync runs (manually, via the post-merge hook, or via a Cursor Automation) and commits a DRAFT.
2. You edit the TODO sections while the context is fresh.
3. Remove the DRAFT marker from the heading once it reads as a real record.
4. If the change altered the stack or a vendor, update ../architecture/ or ../integrations/, and add an ADR under ../decisions/ if a real decision was made.

Index

Date	Entry	Notes
2026-07-30	2026-07-30-example.md	Format example only
2026-07-30	2026-07-30-ead6c62.md	Sync-generated initial backfill (6 commits); TODO sections still open
2026-07-30	2026-07-30-knowledge-base-seed.md	Hand-written: KB seeded from the GEO Agency Playbook; records playbook-vs-repo divergences and the open pricing decision
2026-08-01	2026-08-01-product-launch-checklist.md	Hand-written: product launch / GEO / demo readiness master tracker added under operations