docs(evaluator): clarify the display-only boundary - #134
Merged
Merged
Conversation
Fix the architecture link, which pointed at ./workspace_unifier_architecture.md while the merged page lives at docs/architecture/workspace_unifier_architecture.md. Replace the "immutable workspace packet" description with the more precise boundary the merged architecture uses: TriageCore exports a selective, static evaluator-input packet, and does not invoke the evaluator or produce evaluator results. Evaluator execution and result production remain external. State plainly that PASS, FAIL, AMBIG, and any score are observational results only: none grants, withholds, or implies execution authority, and a PASS is neither human approval nor a required precondition for execution. TriageDesk remains display-only and the human operator remains the sole approval authority. The JSON example and its contract identifiers (result_type=workspace_packet_evaluation_result, packet_id) are unchanged, so the prose cannot drift from the schema. Documentation only: one path, no runtime, schema, test, workflow, or dependency change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
✅ Deploy Preview for poetic-quokka-0fd859 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
Documentation-only correction to the parked evaluator-panel follow-up.
Scope
One documentation path:
docs/evaluator_panel.mdNo runtime, schema, test, workflow, dependency, or configuration change. No
CR-DD-012B work — that slice still requires its own explicit approval, which
this PR neither seeks nor supplies.
What changed
Corrected architecture link. The page linked to
./workspace_unifier_architecture.md, but the merged page lives atdocs/architecture/workspace_unifier_architecture.md. The link is nowarchitecture/workspace_unifier_architecture.md, verified to resolve againstthe merged tree.
Selective static evaluator-input terminology. The page described step 1 as
exporting an "immutable workspace packet." It now describes a selective,
static evaluator-input packet — "a deliberately narrowed artifact assembled
for evaluation, not a complete or authoritative copy of workspace state" —
matching the boundary the merged architecture uses.
TriageCore does not invoke evaluators or produce evaluator results. A new
paragraph states the step-1 boundary is one-way: TriageCore writes the input
artifact and stops there, and evaluator execution and result production are
external to it.
TriageDesk remains display-only. Unchanged and preserved: the
[!WARNING]observation-only block and the "Strict Display-Only Rules"section, including the no-execution, no-inferred-approval, and
no-target-invocation rules.
Evaluator outcomes and scores are evidence, not authority. A new paragraph
after the status list reads:
followed by an explicit restatement that a human operator remains the sole
approval authority.
The JSON example and contract identifiers are unchanged.
"result_type": "workspace_packet_evaluation_result"and"packet_id"areleft exactly as they were. They are the real contract values — verified against
triage_core/evaluator_result.pyanddocs/examples/evaluator_result_observation_only.example.json— andharmonizing them with the new prose would have made the documentation
contradict the schema.
Validation
git diff --check— clean, staged and unstagedgit diff --cached --name-only— exactly one pathorigin/main—docs/evaluator_panel.mdonlyexisting file in the merged tree
./workspace_unifier_architecture.mdlink form and 0 occurrences of "immutable workspace packet"
Runtime tests were not run: the change is documentation-only and touches no
code, test, schema, or workflow path.
🤖 Generated with Claude Code