Repository navigation
[Task] Align AI branch selection with the branch policy #900
Description
title: "AI Branch Selection Guardrails"
description: "Task proposal for forcing explicit branch intent and aligning AI behaviour with the repo's branch lifecycle policy."
file_type: "documentation"
version: "1.0.0"
last_updated: "2026-06-03"
created_date: "2026-06-03"
authors: ["LightSpeed Team"]
maintainer: "LightSpeed Team"
license: "GPL-3.0"
tags: ["ai", "branching", "guardrails", "governance"]
domain: "governance"
stability: "experimental"
status: "draft"
AI Branch Selection Guardrails
Scope
Make branch choice explicit for AI-assisted work so the agent does not infer
or reuse a branch from stale context.
Requirements
- require explicit branch selection before starting a new batch
- prefer the current
developtip as the base for a fresh batch - block continuation of a new batch on an old
codex/*branch - keep the branch choice visible in the issue pack and run log
- align the agent instructions with the branching strategy docs
Acceptance Criteria
- the agent cannot start a new batch without an explicit branch decision
- branch reuse is treated as a policy violation, not a convenience
- the branch policy is reflected in the repo-local instructions
- the AI branch choice contract is clear enough to test
Notes
- The problem is not only branch naming; it is branch intent and lifecycle.
- This task should make "new batch means new branch" an explicit contract.
Activity
linear-code commentedon Jun 8, 2026
LS-964
github-actions commentedon Jun 8, 2026
🚫 This issue does not follow a required issue template and has been closed automatically.
Missing required section(s): Definition of Ready (DoR), Definition of Done (DoD)
Please reopen with one of the official templates:
If this was opened by automation, update the automation to preserve the template sections.
ops(governance): harden branch naming, merge-target and reuse enforce…
ashleyshaw commentedon Jun 8, 2026
Project archive sync: the Branch Governance Hardening project pack is now archived at
.github/projects/archived/branch-governance-hardening-2026-06-08.The archived issue register is the canonical mapping for this chain and has been updated to reflect closed status across #897-#901.
ops(governance): harden branch naming, merge-target and reuse enforce…
ops(governance): harden branch naming, merge-target and reuse enforce…
ops(governance): harden branch naming, merge-target and reuse enforce…
ops: branch governance hardening — rulesets, validation enhancements,…