Repository navigation
Require happy-path scenarios and mapped KQL in post-implementation pre-mortems, Fixes AB#3824306 - #497
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
❌ Work item link check failed. Description does not contain AB#{ID}. Click here to Learn more. |
|
✅ Work item link check complete. Description contains link AB#3824306 to an Azure Boards work item. |
Contributor
|
Could we explicitly require a rollout plan in the pre-mortem content contract? Alongside the monitoring and rollback requirements, it should include proposed exposure stages/audience, observation periods, and promotion/hold criteria, with a justified alternative when a staged rollout does not apply. This would make the expected rollout guidance explicit for the authoring agent. Please carry the requirement consistently into the repository/plugin guidance and author/reviewer prompts. |
Sowmya Malayanur (somalaya)
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
healthyOperationAndFailureDetectionreview criterion. Require the later pre-mortem to contain feature-specific happy-path and failure/degradation scenarios with stable IDs mapped to actual Kusto (KQL) draft text/query IDs, output columns/units, healthy baselines or unconfirmed targets, detection signals, and owned investigation/stop-expansion/rollback actions.design-feature-v12, invalidate earlier prompt outputs, and preserve master's paired Human Design Review Brief/publication behavior. Update repository/plugin design and PBI contracts consistently.Scope and integration
Cherry-picked only source commit
2cc691d7cbea1052407339dfceb468151611e1a4onto current master, resolving checkpoint-version/documentation conflicts while preserving paired-review behavior. Exactly seven existing files changed; no Requirements Builder, application, or nested-repository changes.Validation
node --test .github\extensions\DevDesignDoc\workflow.test.mjs— 66 passed, 0 failed, 0 skipped on the final integrated content, including paired-document regressions.node --check .github\extensions\DevDesignDoc\workflow.mjs— passed.node --check .github\extensions\DevDesignDoc\workflow.test.mjs— passed.node --check .github\extensions\DevDesignDoc\extension.mjs— passed.git diff --checkandgit diff origin/master --check— passed.nodefilesystem/heading-anchor validation — all 5 local design-skill documentation links/anchors passed.These are mocked workflow regressions and static/documentation checks, not live model evaluation or KQL semantic/query-output validation. No paid dynamic workflow, live Kusto queries, or production activation was run.
Tracking
Fixes AB#3824306
Tracking PBI: https://dev.azure.com/IdentityDivision/Engineering/_workitems/edit/3824306
Parent Feature: https://dev.azure.com/IdentityDivision/Engineering/_workitems/edit/3797944
The PBI tracks this workflow enhancement and is linked to this PR as a GitHub Pull Request artifact. Work-item linkage does not imply review, merge, query validation, or rollout approval.