31 lines
913 B
Markdown
31 lines
913 B
Markdown
# TOOL-EXEC Examples (Conceptual)
|
||
|
||
These examples are *documentation-only* until validation and request runner scripts are implemented.
|
||
|
||
ThreeGate requires:
|
||
1) A Tool Request artifact conforming to `schemas/tool-request.schema.md`
|
||
2) Human approval gate (approve_by/approve_utc)
|
||
3) TOOL-EXEC runner validates request and executes via ERA
|
||
4) TOOL-EXEC emits Tool Result conforming to `schemas/tool-result.schema.md`
|
||
5) Tool Result is validated before CORE consumes it
|
||
|
||
---
|
||
|
||
## Example Use Cases
|
||
|
||
- Compute descriptive stats from a CSV
|
||
- Convert BibTeX -> CSL-JSON
|
||
- Parse a RIS export into a normalized bibliography file
|
||
- Run a deterministic transformation on a dataset
|
||
|
||
---
|
||
|
||
## Non-Examples (Do Not Do)
|
||
|
||
- “Install packages” inside TOOL-EXEC
|
||
- Enable network by default
|
||
- Allow TOOL-EXEC to fetch its own inputs
|
||
- Allow TOOL-EXEC to write into CORE’s workspace
|
||
- Allow chained commands or shell pipelines
|
||
|