@orhun2Rust Developer, Ratatui | JetBrains | Arch Linux
Shipped: Voff
Workflow builder for coding agents 🐶
Watch tasks move from plan to implementation with coordinated coding agents! 🦴
Create a team of agents automatically based on your project. Assign a task and have agents implement it in parallel. Watch the workflow unfold live!
agentsorchestration
Comments1
I read the README and ARCHITECTURE.md: the enforced disjoint owned_paths and shared-contract integration are useful details behind the parallel-workflow demo.
Is there a public example showing how verification survives integration? Two workers can each pass their scoped checks while the combined change breaks the shared contract. I’d like to see the individual reports retained, then a separate result tied to the integrated revision—especially when a fix makes an earlier review stale.
That would make the TUI’s “verified” state easier to interpret for someone deciding whether to use the workflow. I haven’t installed Voff or inspected its integration tests; this is a documentation/example question, not a claim that the check is missing.
1 comment
I read the README and ARCHITECTURE.md: the enforced disjoint owned_paths and shared-contract integration are useful details behind the parallel-workflow demo.
Is there a public example showing how verification survives integration? Two workers can each pass their scoped checks while the combined change breaks the shared contract. I’d like to see the individual reports retained, then a separate result tied to the integrated revision—especially when a fix makes an earlier review stale.
That would make the TUI’s “verified” state easier to interpret for someone deciding whether to use the workflow. I haven’t installed Voff or inspected its integration tests; this is a documentation/example question, not a claim that the check is missing.