You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/theory/why-action-model.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,8 +61,6 @@ The important property: merge strategies are **associative**. Merging result A w
61
61
62
62
In practical terms: when an action's merge is associative and handlers don't depend on each other's output (like independent linters), FineCode can run them **in parallel or sequentially — same result either way**. The framework makes this decision transparently. Handlers don't need to know.
63
63
64
-
For the formal definition of these properties — associativity, identity elements, and the exact conditions under which parallel and sequential execution are equivalent — see [The Action Model](action-model.md#result-algebra).
65
-
66
64
## Three levels of specificity: why swapping tools is painless
67
65
68
66
This is the design decision that has the most direct impact on day-to-day configuration.
0 commit comments