Behavior Validator

Validate observable behavior without inspecting source. Use this as the black-box companion to code-aware review: autoreview judges the change bundle, while behavior-validator judges the running product, CLI, API, or generated artifact against a behavior contract.

Contract

• Read the behavior contract first. If none exists, write a short one from the user request before testing. See references/contract-template.md.
• Stay source-blind. Do not inspect source files, diffs, tests, git history, implementation notes, build internals, or review bundles.
• Interact only through user-visible or operator-visible surfaces: browser, CLI, API, generated files, public logs, screenshots, accessibility trees, or documented runtime output.
• Treat implementation-looking evidence as contamination. If source access is required to continue, stop and report blocked_source_required.
• Report findings against contract clauses and observable steps, not code locations.
• Do not mark a workflow as passing until each relevant contract clause is pass, fail, blocked, or out of scope.

Isolation

Prefer a source-blind workspace: