Repository navigation
spec(FIX-1833): record best fit's question as "Who should take the post?" #3006
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -76,8 +76,13 @@ often enough to notice. | |
| - **It is keyed by its worker id and picked by its description**, the way a delegate is picked by | ||
| its note or description. A coordinator with no description isn't offered, and neither is one | ||
| with no delegate to choose: then there is no choice to make, and today's misses apply. | ||
| - **Best fit's question stays as #2955 words it.** A question that names the coordinator lowered | ||
| Jev's confidence on both kinds of ask (POC, set S2 against S1). | ||
| - **Best fit's question asks "Who should take the post?"** *(Amended 2026-10-10, in | ||
| implementation; this spec first kept #2955's wording.)* #2955's question asks which delegate | ||
| should answer, which no longer fits once the coordinator is one of the choices. The POC's | ||
| objection was to a question that *names* the coordinator: that lowered Jev's confidence on both | ||
| kinds of ask (set S2 against S1). The new wording names nobody. On the goal it held: the chief | ||
| of staff picked itself for its own asks at 0.8 to 1, plain asks still went to the EM, and legs | ||
| a, c, g and h each passed 6 of 6 (#2997, `goal.md`). | ||
|
Comment on lines
+79
to
+85
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Worth cross-linking implementation once in the amend PR body (#2997) so this does not read like a silent doc tweak — behavior-bearing, even though code already shipped. |
||
| - **The DevTeam's `routeModel` is `typesafe-ai/jev`.** It is the gateway's evaluation model that | ||
| reports confidence; `openai/gpt-5.4-mini` can't evaluate through the gateway | ||
| ([Evaluation models](../../../apps/docs/docs/fundamentals/models.md#evaluation-models)). | ||
|
|
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simplify: This bullet is doing normative lock-in + amendment provenance + POC narrative + goal evidence (#2997). Neighboring “Locks in” bullets are mostly one rule each; consider:
## How it got here(FIX-1481 does this after merge).Same facts, less cognitive load when someone scans D1.