Skip to content

Commit 78c8915

Browse files
committed
Remove not existing link on page 'why-action-model.md'
1 parent 63f6816 commit 78c8915

1 file changed

Lines changed: 0 additions & 2 deletions

File tree

docs/theory/why-action-model.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,6 @@ The important property: merge strategies are **associative**. Merging result A w
6161

6262
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.
6363

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-
6664
## Three levels of specificity: why swapping tools is painless
6765

6866
This is the design decision that has the most direct impact on day-to-day configuration.

0 commit comments

Comments
 (0)