17 lines
1.3 KiB
Markdown
17 lines
1.3 KiB
Markdown
# Integration Gate
|
|
|
|
Use this gate to promote completed task facts into canonical project memory.
|
|
|
|
## Requirements
|
|
|
|
- Run in an isolated integration worktree when concurrent edits may overlap. A user-requested direct governance update may run in the current worktree only after the repository-local worktree check confirms existing changes are known and non-overlapping.
|
|
- Do not require or emulate an external integration lock; use Git worktree isolation, visible status, and explicit conflict checks.
|
|
- For a single completed Feature, create the Integration worktree from that Feature commit so its task-owned records are already present. Verify the target default branch is an ancestor or reconcile it explicitly before canonical edits.
|
|
- Verify the task commits being integrated are present.
|
|
- Review source task records, task-prefixed supporting records, promotion candidates, and semantic conflicts in read-only mode.
|
|
- Write integration notes only to the integration task's own task record or `{task_id}__<slug>.md` supporting records.
|
|
- Ask before changing architecture direction, product behavior, or accepted decisions.
|
|
- Record source task or merge commits under `Integrated Through` in `current-state.md`.
|
|
|
|
Do not resolve meaningful document conflicts with `ours`, `theirs`, or union merge rules.
|