docs(13-process-blueprint): drop validation rule BP-012#15
Merged
Conversation
BP-012 warned on every aspect entry referencing a single stage and suggested inlining it into the stage description. A single-stage aspect is normal, valid blueprint content — the notation maps each stage to its aspects regardless of whether they are shared. The rule fired on the common case, producing a wall of warnings on correct files and training authors to ignore the warning panel. Removed. BP-011 remains the last rule; no renumbering.
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
1 participant
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
Removes the
BP-012validation rule fromnotations/13-process-blueprint.md§6.BP-012 (
warn) fired on every aspect entry whosestages: [...]references a single stage, suggesting it "may be a candidate for inlining into the stage's description." But a single-stage aspect — a barcode scanner used only in one stage, a payment gateway used only at order intake — is normal, valid blueprint content. The notation maps each stage to its supporting aspects regardless of whether those aspects are shared across stages. The rule therefore fired on the common case, producing a wall of warnings on entirely correct files (observed during hand-testing: 8 BP-012 warnings on a valid 3-stage blueprint) and training authors to ignore the warning panel.Change
One row deleted from the §6 validation-rules table.
BP-011remains the last rule — no renumbering. No other part of the spec references BP-012.Downstream
The Transitrix Studio validator (
packages/diagrams/src/process-blueprint/validate.ts) implements BP-012 faithfully and is being updated to match intransitrix/transitrix-studio(the BP-012 emission and its test removed there). Merge order is not strict — the two changes are independent — but merging this first keeps the canonical spec ahead of the implementation.Decision by Valerii, 2026-05-21, during 1.0.0 pre-release hand-testing.