Skip to content

feat(validation): add post-execution business task validation (VALIDATE-001) - #344

Merged
vybe merged 2 commits into
mainfrom
feature/294-business-validation
Apr 14, 2026
Merged

vybe merged 2 commits into
mainfrom
feature/294-business-validation

Conversation

@vybe

@vybe vybe commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add post-execution validation phase that runs clean-context Claude session with auditor framing to verify business task completion
  • Separate technical success (Claude ran without errors) from business success (intended work was done)
  • Track validation via business_status field and linked validation execution records
  • Notify operator queue when validation fails for human review

Changes

Backend:

  • src/backend/services/validation_service.py — Core validation service with auditor prompt
  • src/backend/routers/internal.py/api/internal/validate-execution endpoint
  • src/backend/routers/schedules.py — Updated response models with validation fields
  • src/backend/db/schedules.py — New DB operations for validation
  • src/backend/db/schema.py — Validation columns in schedules/executions
  • src/backend/db/migrations.py — Migration Quick Instance Deploy #32

Scheduler:

  • src/scheduler/service.py — Trigger validation after successful execution

Tests:

  • tests/test_validation.py — Unit tests (19 passed, 3 skipped)

Docs:

  • docs/memory/feature-flows/business-validation.md — Feature flow documentation

Test Plan

  • Unit tests pass: pytest tests/test_validation.py -v (19 passed)
  • Integration tests pass against running backend
  • Manual verification: Create schedule with validation_enabled=true, trigger, verify validation runs

Closes #294

Generated with Claude Code

vybe and others added 2 commits April 14, 2026 20:51
…TE-001)

Adds a post-execution validation phase that runs a clean-context Claude
session to verify business task completion. This separates technical success
(Claude ran without errors) from business success (the intended work was done).

Backend:
- Add ValidationService with auditor-framed prompt
- Add /api/internal/validate-execution endpoint for scheduler
- Add business_status field to executions (pending_validation, validated, failed_validation, skipped)
- Add validation config to schedules (validation_enabled, validation_prompt, validation_timeout_seconds)
- Add linked validation execution records via validates_execution_id/validation_execution_id
- Operator queue notification on validation failure

Scheduler:
- Trigger validation after successful execution completion
- Call backend internal API for validation orchestration

Database:
- Migration #32 adds validation columns to schedules and executions tables
- Add indexes for business_status and validates_execution_id

Tests:
- Add test_validation.py with unit tests for prompt building, response parsing, status mapping
- Integration tests for schedule/execution API contracts

Closes #294

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@vybe
vybe merged commit 84ca389 into main Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: Business task validation — post-execution verification session (VALIDATE-001)

1 participant