Skip to main content

ADR 0001 — Route Code Readiness Separately from Engineering Initiatives

Context​

Chatbot has two engineering-owned Q3 Epics with different purposes. Without an explicit boundary, internal tooling and repository work can be attached to the systemic Engineering Initiatives Epic, making future sprint planning and Jira alignment inconsistent.

Decision​

  • Route repository workflows, tests, MCP, hooks, agent skills, and internal operational/admin tooling to Code Readiness, BOT-4500.
  • Route runtime, framework, dependency, security, reliability, performance, and architectural modernization to Engineering Initiatives, BOT-4620.
  • Route customer-facing outcomes to the relevant product initiative.
  • Split independently deliverable mixed outcomes; otherwise use the primary outcome.
  • Keep Code Readiness open to every discipline. Puji owns routing as EM, while each story records its actual Scope and contributors. QA is named when QA participates, not required by default.

Consequences​

Sprint planning discovers Code Readiness through a formal classed bucket. Jira alignment checks the routing charter before recommending an Epic change. Existing Engineering Initiatives retain their current standing QA model; Code Readiness opts into scoped QA ownership.