Skip to content

chore(scribe): mandate YYYY-MM-DD date format in charter#60

Closed
diberry wants to merge 1 commit intodevfrom
squad/24-scribe-date-format
Closed

chore(scribe): mandate YYYY-MM-DD date format in charter#60
diberry wants to merge 1 commit intodevfrom
squad/24-scribe-date-format

Conversation

@diberry
Copy link
Copy Markdown
Owner

@diberry diberry commented Mar 27, 2026

Updates Scribe charter to explicitly mandate date format for decision entries. Prevents archival bugs from undated entries.

Closes #24

Explicitly requires all merged decision entries to use the format '### YYYY-MM-DD: Topic'.
Specifies handling for missing dates and undatable entries to prevent archival bugs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@diberry
Copy link
Copy Markdown
Owner Author

diberry commented Mar 27, 2026

✅ APPROVED

Minimal and correct:

  • Single commit: chore(scribe): mandate YYYY-MM-DD date format in charter
  • Only text updates to Scribe charter files (scribe/charter.md and templates/scribe-charter.md)
  • Clear mandate added: decision headings must follow ### YYYY-MM-DD: Topic\ format
  • Guidance for missing dates and undatable entries is explicit
  • No code changes, no unrelated files

All criteria met for issue #24.

@diberry
Copy link
Copy Markdown
Owner Author

diberry commented Mar 27, 2026

APPROVED

Quality gate verification for PR #60 (chore(scribe): mandate YYYY-MM-DD date format in charter):

  • ✅ Exactly 1 commit on branch (squad/24-scribe-date-format)
  • ✅ Only 2 files changed (scribe charter + template, as expected)
  • ✅ Mandate is clear and actionable: Scribe knows the format ('### YYYY-MM-DD: Topic'), has guidance for missing dates, and knows to log warnings for undatable entries
  • ✅ Charter and template both updated consistently
  • ✅ No junk files

Ready to merge.

@diberry
Copy link
Copy Markdown
Owner Author

diberry commented Mar 27, 2026

Retargeted to bradygaster#649

@diberry diberry closed this Mar 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants