Call for field testers: replayable agent orchestration ledgers

[HarperZ9]

Project Telos is looking for field testers for forum: model-agnostic agent orchestration with a replayable, verifiable causal ledger.

The question this repo should help answer:

Can a multi-agent run leave a receipt that shows route, context, action, stop reason, and verification state instead of only a fluent summary?

Useful test lanes:

• Agent coding workflows: capture task, route, tool calls, changed files, checks, and handoff state.
• DevOps/DevSecOps: distinguish read-only work, write actions, external calls, and human approval boundaries.
• Token economy/routing: test how an agent should decide which service/tool call is allowed before spending tokens or money.
• Reasoning workflows: compare what an agent claims it did against the observed ledger.

What I am looking for:

• Verification against real or synthetic multi-agent workflows.
• Places where the ledger misses an important boundary.
• Cases where a run should stop as UNVERIFIABLE instead of continuing.
• Better schemas for policy decisions, stop reasons, retry events, and handoff packets.
• Early users who want accountable agent orchestration rather than another chat transcript.
• Pointers to modest grassroots research funding or labs that would stress-test this properly.

Project links:

• Main site: https://harperz9.github.io
• Field guide: https://harperz9.github.io/field-guide.html
• GitHub profile: https://github.com/HarperZ9
• Related flagships: https://github.com/HarperZ9/gather https://github.com/HarperZ9/index https://github.com/HarperZ9/crucible https://github.com/HarperZ9/telos

Stage label: public, solo, early, pre-revenue, not independently audited. Please test with public repos, synthetic tasks, or non-sensitive local workflows.