Skip to main content

ValorIDE Collaboration Protocol

This page describes a lightweight protocol teams can use to coordinate work between the human manager and ValorIDE (the agent). It is aimed at keeping changes small, traceable and reversible.

Roles and responsibilities​

  • Manager: Defines objectives and acceptance criteria, approves changes, and prioritizes tasks.
  • Executor (ValorIDE/agent): Implements the currently active task, makes focused edits, and records change summaries.

Rules of engagement​

  • Single Active Task: At any time, only one task should be marked active to avoid conflicting edits.
  • Atomic Changes: Make small, testable edits and include a short change summary for traceability.
  • Locking: Use a lightweight lock pattern for large refactors to avoid overlap and race conditions.

Task template (use in the task description)​

- id: T-####
  title: short title
  priority: P0|P1|P2
  files: [list of affected files]
  description: Short summary + why
  acceptance_criteria:
    - observable outcome
    - second outcome
  owner: Executor
  status: queued|active|blocked|done|accepted

Change summaries (examples)​

For each completed task add:

  • date, task id, modified/added file list, validation steps, follow-ups.

Practical tips​

  • Prefer safe, reversible changes and keep each PR focused on one problem.
  • Use CI and pre-commit hooks to prevent accidental edits of generated code.

This protocol is intentionally minimal — it promotes safety by emphasizing small steps, human approval, and clear validation criteria.