To address challenges with repository bloat, knowledge base persistence, and GitHub issue integration, a new "Hybrid Archival Process" for tickets was defined and documented.
This new strategy ensures that the history of work remains portable and accessible to AI agents while keeping the working repository clean.
Changes
TICKET_STRATEGY.md Created:
- A new file,
.github/TICKET_STRATEGY.md, was created to serve as the single source of truth for the ticketing process.
- It details the three phases of a ticket's lifecycle: Creation, Association (manual linking to a GitHub issue), and Archival (concatenating tickets into a single file post-release).
AGENTS.md Updated:
- The agent's "Session Initialization" process was updated with a new mandatory step: the agent MUST read
.github/TICKET_STRATEGY.md at the start of every session.
Impact
This establishes a clear, scalable, and robust process for managing work items. It solves the problem of losing historical context for the AI, prevents repository bloat, and creates a clear path for linking version-controlled tickets with the GitHub issue tracker.
To address challenges with repository bloat, knowledge base persistence, and GitHub issue integration, a new "Hybrid Archival Process" for tickets was defined and documented.
This new strategy ensures that the history of work remains portable and accessible to AI agents while keeping the working repository clean.
Changes
TICKET_STRATEGY.mdCreated:.github/TICKET_STRATEGY.md, was created to serve as the single source of truth for the ticketing process.AGENTS.mdUpdated:.github/TICKET_STRATEGY.mdat the start of every session.Impact
This establishes a clear, scalable, and robust process for managing work items. It solves the problem of losing historical context for the AI, prevents repository bloat, and creates a clear path for linking version-controlled tickets with the GitHub issue tracker.