Extract is bounded to the ranking: pull → embed → score → extract → score → summarise
The free stages run first and their score bounds the two model stages. Extract reads only the best extract.per_agent roles of each agent at extract.min_score or more, then score runs again so the gates read what it filled; summarise gets a min_score of its own. The cascade steps by position, since score is in it twice. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
1 parent
c4f2bcc0c9
commit
7db77e83a3
15 files changed
+215
-89
No files matched your search
@@ -9,7 +9,7 @@ Built on the [boilerplate](../boilerplate): its job queue and scheduler (`pipeli
|
||||
```bash
|
||||
uv sync --all-extras
|
||||
uv run app companies seed # 186 companies from seed/companies.json, one board each
|
||||
uv run app job pull # read every board and search, then extract, embed and score
|
||||
uv run app job pull # read every board and search, embed and score them, extract the best, rescore, summarise
|
||||
uv run app serve # http://127.0.0.1:8790
|
||||
```
|
||||
|
||||
|
||||
Reference in new issue
Block a user