Update from code changes: rules-as-substrate doctrine and new rule actions#61
Open
mintlify[bot] wants to merge 1 commit into
Open
Update from code changes: rules-as-substrate doctrine and new rule actions#61mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
Update the rules and series docs to reflect the rules-as-universal-substrate refactor — new actions, renamed condition fields, and the removal of series detection plus series tags.
Changes
transactions/rules.mdx— rewritten around the "provider data is immutable; intelligence accrues as rules" doctrine. Adds the full action catalog (assign_series,assign_counterparty,set_metadata,remove_metadata,flag,unflagalongside the existing actions), the renamed condition fields (provider_name,provider_merchant_name,provider_category_primary,provider_category_detailed), the newseries/in_series/counterparty/has_counterparty/ date-part /metadata.<key>fields, theapprox/betweennumeric operators, the match-stability classification, and last-writer-wins semantics.guides/understanding-rules.mdx— adds the doctrine intro, updates every example to the new field names, replaces the threshold-tag example with aflagexample, and adds a recurrence-idiom subscription example (amount approx+day_of_month approx+assign_series).guides/tracking-subscriptions.mdx— series are now thin, rule-maintained entities (name + type). Removes the detector / candidate-verdict / cadence / expected-amount / next-expected-date model, theadd_series_tag/remove_series_tag/review_series/rekey_series/split_series/set_series_type/explain_series_candidatesflows, and the inherited-series-tag surface. Replaces the agent surface with the trimmedlist_series/get_series/assign_series/update_series/unlink_series_transactionsset and points users at addingadd_tagto the same rule that doesassign_series.mcp/tools.mdx— replaces the stale series tools table with the rule-maintained equivalents and adds a new Counterparties subsection mirroring the same model.mcp/reference/rules-write.mdxandmcp/reference/rules.mdx— adds the new action shapes, fixes the renamed field names in examples, and rewrites the condition grammar short-form with the match-stability classes, new operators, metadata conditions, and the recurrence idiom.guides/breadbox-in-a-nutshell.mdxandguides/single-routine-reviewer.mdx— replace stray references to the oldname/merchant_namefield names.Context
Tracks the rules-as-universal-substrate sprint (#1906) and the destructive series-tags removal (#1918) in the source repo.