Skip to content

docs(openwar): named-tool fidelity rule#1

Merged
PythonLuvr merged 1 commit into
mainfrom
feat/named-tool-fidelity
May 27, 2026
Merged

docs(openwar): named-tool fidelity rule#1
PythonLuvr merged 1 commit into
mainfrom
feat/named-tool-fidelity

Conversation

@PythonLuvr
Copy link
Copy Markdown
Owner

Summary

Adds a one-paragraph rule to the "Tool calls and authorization" section of openwar.md covering tool fidelity, which is distinct from authorization.

When the operator names a specific tool, substitution requires explicit re-authorization in the same session, even when a default or learned preference would suggest a different tool. Partial discretion ("a few options as you please", "whichever you prefer") covers content and style, never tool selection unless the operator explicitly opens it up.

Why this matters

The existing framework has three gates near this territory but none of them actually catch the case:

  • Hard Rule #3 gates destructive and out-of-directive actions. Using Tool B instead of Tool A is not destructive, just wrong.
  • authorized_costs gates whether the agent may spend on a cost category. If two tools share a category (both authorized), it doesn't help pick the right one.
  • Phase 3 prompts on unauthorized calls. Substitution within an authorized category doesn't trip Phase 3.

This rule closes that gap. Tool fidelity is its own concern.

Test plan

  • npm run lint passes (em-dashes + sanity)
  • No code changes; framework doc only
  • Optional: maintainer reads the paragraph in context and decides whether the placement after the authorize-check paragraph is the right spot

🤖 Generated with Claude Code

Adds a paragraph to the "Tool calls and authorization" section
covering tool fidelity, distinct from authorization. When the
operator names a specific tool, substitution requires explicit
re-authorization in the same session. Partial discretion covers
content and style, not tool selection.

Fills a real gap: Hard Rule #3 gates destructive and out-of-directive
actions, authorized_costs gates whether to spend on a category, but
nothing currently covers fidelity to operator-named tools inside an
authorized category.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@PythonLuvr PythonLuvr merged commit c2bd646 into main May 27, 2026
2 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant