Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Keep structural and behavioral tool validity separate
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
A schema-valid tool call can still violate behavioral policy. Preserve structural validity and behavioral correctness as separate typed fields through scoring, persistence, projection, and UI. Use canonical models and projection-parity tests so an explanation is not lost or contradicted downstream. Missing or ambiguous execution evidence remains unresolved rather than being converted into either field.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review