Skip to content

Discussion: validation-ledger semantics for multi-agent setups #4

@Wynelson94

Description

@Wynelson94

Context

v0.11's validation ledger records {at, by} per re-validation. On a single-operator machine, by is one model name at a time. A reader asked about multi-agent workflows, and it's a good question:

  • Should N validations from the same agent identity count differently than N from distinct agents? (Distinct reviewers with different blind spots are stronger evidence than one reviewer repeating itself.)
  • Should confirm optionally capture what was checked (e.g. the diff base it was read against), so a validation is itself auditable?
  • Display: validated 3× vs validated by 3 distinct agents — does the summary line need a diversity signal?

Constraints

Whatever the answer: plaintext + git + stdlib, no new deps, no required ceremony (the gate blocks lies, not chores). Open to design discussion before any code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions