Repository navigation
Define and verify the annotation interpretation contract #7
Description
Outcome
Agents can reliably distinguish requested revisions from questions, discussion, and contextual notes in a Markover handoff.
Acceptance criteria
- The protocol or agent-facing contract explicitly distinguishes revision requests, questions, discussion, and source proposals.
- Concrete positive and negative examples cover mixed-feedback reviews.
- Representative automated protocol/evaluation cases fail when questions are treated as edit requests.
- Generic agent instructions and each supported agent example use the same semantics.
- The public workflow no longer over-promises beyond the verified behavior.
Intended PR stack
Bottom to top:
- Centralize the interpretation model and protocol semantics.
- Apply the semantics to agent instructions and examples.
- Add representative evaluation and regression coverage.
Activity
lastobelus commentedon Aug 3, 2026
Stack scaffold initialized locally from origin/main. No empty placeholder PRs were submitted.
Bottom → top:
Begin on the bottom branch, keep each layer independently reviewable, and run gh stack submit once the layers contain their real implementation commits.
lastobelus commentedon Aug 4, 2026
Implementation stack submitted: #47 → #48 → #49. Automated cross-model agent evaluations are tracked separately in #46 under the Broad announcement milestone. Full stack verification: npm test (196 passing) and npm run check.