Repository navigation
docs(build-epilot-journey): document logicsV4 and validationRules as journey sections - #5
Draft
stewarthsoj wants to merge 2 commits into
Draft
stewarthsoj wants to merge 2 commits into
stewarthsoj wants to merge 2 commits into
Conversation
…journey sections The skill only mentioned logicsV4 in passing and never validationRules, so an agent had no reason to send them and no way to notice when the epilot MCP dropped them. Describe both sections, the V4 action kinds and reference shapes, the Validation Rules API operations that own the rules, the reference checks the MCP runs before a write, and that a copied journey keeps its logic only when every section is sent. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UEF58vXyK3iotGjHYYm9j7
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UEF58vXyK3iotGjHYYm9j7
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
Companion to the epilot MCP change for STABLE360-13248 (MR !27), which makes
create_journeyandupdate_journeyacceptlogicsV4andvalidationRulesinstead of dropping them silently.The
build-epilot-journeyskill mentionedlogicsV4in one line and never mentionedvalidationRules, so an agent had no reason to send them and no way to notice they were lost. The anatomy reference now describes both sections: the V4 action kinds, the fact and settings reference shapes, where prefilling lives, the Validation Rules API operations that own the rules, the reference checks the MCP runs before a write, and that a copied journey keeps its logic only when every section is sent. The workflow steps inSKILL.mdname logic and validation as part of the journey rather than follow-up work in the builder.Verification
npm run checkpassesCHANGELOG.mdSafety and compatibility
Documentation only. The described MCP behaviour (strict journey write schemas, reference validation, validation rule id checks,
usedBysync) ships with the linked MCP MR; until that is deployed the sections are still accepted by the tool schema but dropped, which the skill text does not change.Generated by Claude Code