norrisaftcc / norrisaftcc/algorithm-liza
M2: The text tool protocol
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
A second tool protocol that parses fenced blocks out of ordinary prose, selectable with --protocol text, running the same tool set as native.
The reason this exists is diagnostic as much as functional: when a Gemma-class model fails a task, we currently cannot tell whether the harness is wrong, the model cannot reason about the task, or the model simply cannot serialise a tool call. Two protocols separate the third cause from the first two.
Parsing must be forgiving — wrong fence language tags, missing closing fences, and prose wrapped around the block are all normal small-model output, and a strict parser will attribute model competence problems to formatting.
Done when both protocols complete the same task and both transcripts are committed as fixtures.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing native protocol entry point and the handling selected by --protocol native; then trace how tool calls and transcripts are represented. Add the text protocol with forgiving fenced-block parsing and the same tool set, and commit fixtures showing both protocols completing the same task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100