Agent 6: Validator & Certifier

New System ↔ Original Requirements

Role

The Validator is the final and most critical agent in the pipeline. Its mission is to prove that the new system does everything the old system did — and nothing it shouldn't.

This isn't just testing. It's certification. The Validator takes the business rules catalog from Agent 1 and systematically verifies that every rule is correctly implemented in the new system. The output is a formal proof of equivalence.

---

Inputs

• New system (built by Agent 5)
• Business rules catalog (Agent 1 — the original extraction)
• Unified requirements specification (Agent 3)
• User journey maps (Agent 2)
• Gap exceptions list (approved deviations from legacy behavior)

---

Outputs

Test Suite

A comprehensive, automated test suite organized by business rule:

BR-001: Discount cap at 15% for standard accounts
  ✓ Standard account with 10% discount → accepted
  ✓ Standard account with 15% discount → accepted
  ✓ Standard account with 16% discount → rejected
  ✓ Premium account with 20% discount → accepted (different rule)
  ✓ Edge case: exactly 15.00% → accepted
  ✓ Edge case: 15.01% → rejected

Each business rule gets:

• Positive tests (rule correctly enforced)
• Negative tests (violations correctly rejected)
• Edge case tests (boundary conditions)
• Cross-rule interaction tests (rules that affect each other)

Regression Results

A complete regression report comparing the new system's behavior against every extracted business rule:

Rule ID	Description	Status	Notes
BR-001	15% discount cap	PASS	All 6 test cases pass
BR-002	Age 18+ for account creation	PASS	All 4 test cases pass
BR-003	$10K approval threshold	PASS	All 8 test cases pass
BR-089	7-year archive rule	EXCEPTION	Approved deviation — now 5 years per new policy

Coverage Report

Quantified proof of completeness:

• Business rule coverage: X% of extracted rules have corresponding tests
• Workflow coverage: X% of user journeys are tested end-to-end
• Edge case coverage: X% of registered edge cases are verified
• Role coverage: All role-permission combinations tested

Target: 100% business rule coverage. Anything less requires explicit justification.

Certification Document

A formal document suitable for audit and compliance:

• Total business rules extracted: N
• Rules implemented and verified: N
• Approved exceptions: N (with justification for each)
• Test execution summary
• Sign-off by AI Software Lead

Gap Exceptions List

An explicit, documented list of every difference between the old system and the new system:

Exception ID	Rule	Old Behavior	New Behavior	Justification	Approved By
EX-001	BR-089	7-year archive	5-year archive	Updated compliance policy	Legal team
EX-002	BR-052	Manual CSV export	Automated API export	Process improvement	Operations

Every exception is deliberate, documented, and approved. There are no unknown differences.

---

Methodology

Phase 1: Test Generation

For each business rule in the Agent 1 catalog, generate a comprehensive set of test cases. Positive, negative, edge case, and interaction tests.

Phase 2: Execution

Run the full test suite against the new system. Record results with detailed output for any failures.

Phase 3: Gap Analysis

Compare test results against the unified spec. Identify:

• Rules that pass all tests (certified equivalent)
• Rules that fail (implementation bugs — sent back to Agent 5)
• Rules that were intentionally changed (matched against approved exceptions)
• Rules not yet tested (coverage gaps)

Phase 4: Certification

Compile the final certification document. This is the proof that the Phoenix has risen — the new system carries the same business intent as the old, verified rule by rule.

---

Human Validation Gate (Final)

This is the final gate — the go/no-go decision for the entire engagement:

• Review the regression results for any unexpected failures
• Confirm all gap exceptions are genuinely approved
• Verify the coverage report meets the agreed threshold
• Sign the certification document
• Accept the new system for deployment

---

Why This Matters

The Validator is what makes Phoenix different from every other modernization approach. Traditional migrations ship a new system and hope it works. Phoenix ships a new system with mathematical proof that it implements every business rule from the original.

Nothing lost in the fire. Everything verified in the rebirth.

---

"The fire transforms. The validator certifies. The Phoenix rises."

The Human Layer →