twining-verify

Twining Verify — Pre-Completion Verification

For complex tasks (multi-file changes, architectural decisions, long sessions), verify your work against Twining's coordination state. For simple tasks, posting a status entry via twining_post is sufficient.

Note: twining_verify requires tools.full_surface: true in config. If not available, post a status entry via twining_post summarizing what you did.

When to Invoke

• Complex multi-file changes with architectural decisions
• Before handing off work to another agent on a large task
• Before creating a pull request with significant changes
• When you want to check for decision drift or unresolved warnings

Workflow

1. Run Verification

Call twining_verify with:

• scope: The area you worked on (e.g., "src/auth/")
• checks: Array of checks to run. Include all relevant ones:
  • "test_coverage" — Are decisions backed by tested_by relations?
  • "warnings" — Are all warnings acknowledged or resolved?
  • "assembly" — Were decisions made after assembling context (not "blind")?
  • "drift" — Has code drifted from decision intent?
  • "constraints" — Do checkable constraints still pass?

2. Interpret Results

Each check returns a status:

pass — No issues found. Proceed.

warn — Issues exist but aren't blocking:

• Uncovered decisions (no tested_by relation) — consider adding test links
• Blind decisions (made without twining_assemble) — acknowledge or re-verify
• Minor drift detected — review if decisions are still accurate

fail — Issues that should be addressed:

• Silently ignored warnings — read and acknowledge each one
• Failed constraint checks — fix the violation or update the constraint
• High drift count — decisions may be stale

3. Address Issues

For each issue found:

Uncovered decisions — If you wrote tests that cover a decision and the knowledge graph is enabled (graph.auto_populate: true), link them:

twining_add_relation(
  source="<affected_file>",
  target="<test_file>",
  type="tested_by",
  properties={ covers: "<what it tests>" }
)

If the graph is not enabled, this check can be safely ignored.