Repository navigation
[Governance] Add lightweight governance revision log process #423
Description
Summary
Add a lightweight governance/process change-tracking mechanism so policy changes are auditable without heavy overhead.
Scope
- Define the minimal revision-log format (date, change summary, rationale, issue/PR links).
- Add a governance revision log file under docs/.
- Document when entries are required.
Acceptance Criteria
- Governance revision log process is documented.
- Owners/review cadence is clear.
- Guidance is linked from CONTRIBUTING.md or governance docs.
Parent
Metadata
Metadata
Assignees
Type
Fields
Priority
None yet
Activity
linear-code commentedon May 27, 2026
LS-717
ashleyshaw commentedon May 27, 2026
Triage complete: moved to
status:readyand assigned to @ashleyshaw.\n\nDependency order agreed for execution: #422 -> #423 -> #424.\n- #422 defines canonical reference policy first (single source of truth + examples).\n- #423 implements the governance revision log process based on #422 policy.\n- #424 performs stale-link/path sweep after #422/#423 wording lands.ashleyshaw commentedon May 27, 2026
Completed in #440.\n\nDelivered:\n- new lightweight governance revision log at docs/GOVERNANCE_REVISION_LOG.md\n- minimal required entry format (date, summary, rationale, links)\n- explicit rules for when entries are required\n- owner and review cadence definition\n- cross-links from CONTRIBUTING.md and docs/AUTOMATION_GOVERNANCE.md\n\nValidation run:\n- markdownlint on changed docs passed\n- local relative-link checks passed\n- git diff --check passed
ashleyshaw commentedon May 27, 2026
Follow-up closeout after merge of #439:\n\n- #422 is now merged/closed and the canonical instruction reference policy is in place.\n- #423 remains the next dependent task (governance revision log process) and is unblocked by policy clarity.\n\nStatus: keep open and proceed as next execution step in the milestone sequence.