Skip to content

Fix non-existent IN-001/IN-002 control IDs in governance case file#3

Draft
Copilot wants to merge 2 commits intogovernance-framework-v2from
copilot/sub-pr-2
Draft

Fix non-existent IN-001/IN-002 control IDs in governance case file#3
Copilot wants to merge 2 commits intogovernance-framework-v2from
copilot/sub-pr-2

Conversation

Copy link
Copy Markdown

Copilot AI commented Mar 19, 2026

The case file's intake section referenced IN-001, IN-002 as control IDs, but these don't exist anywhere in the control register. The governance workflow explicitly designates Stage 1 intake artifacts as pre-register with no assigned control IDs.

Change

  • examples/customer-service-chatbot/governance-case-file.md — Replaced *Control IDs: IN-001, IN-002* with *Pre-register artifact — no Control ID. See governance-workflow.md Stage 1.*, consistent with how the governance workflow describes intake-stage artifacts.

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Co-authored-by: sunilp <633213+sunilp@users.noreply.github.com>
Copilot AI changed the title [WIP] Update governance framework v2 documentation and implementation plan Fix non-existent IN-001/IN-002 control IDs in governance case file Mar 19, 2026
Copilot AI requested a review from sunilp March 19, 2026 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants