orchestrata_ultimate.verification

Reference › orchestrata_ultimate › verification

Verification Agent — Spec 035 (historical label: Spec 007b).

The Verification Agent (Spec 035, historically Spec 007b) is the part of Orchestrata that refuses to accept generated work on faith. It turns requirements into formal constraints, judges them mechanically with Prolog, steps the work through named checkpoints, validates proofs, reviews code deterministically, repairs common defects automatically, and escalates to a human when attempts run out. The orchestrator reaches it through its verification_gate. The curated narrative tells the story with diagrams; this page maps the modules.

The parts, by role:

• Vocabulary and settings: types and config.
• Requirements to constraints: requirements, with integrations for Intent Broker input and Redis state.
• Evaluation: constraints, checkpoints, proofs and the engine and feedback.
• Actors and messaging: agents, models, protocols, orchestration and session.
• Code review and repair: review (no LLM) and autofix.
• Boundary guards: edge_cases, impossibility and the escalation handler.
• Spec conformance, used project-wide: traceability (the @traces scanner and RTM), rtm_constraints, spec_completeness, implementation_scanner and _non_python_scan; the package root re-exports the spec-completeness and traceability API.

Control flows from a session through the engine: constraints are evaluated by Prolog, checkpoints advance or count attempts, and failures become feedback for the executor. There is no CLI. To start, read types, then the verification engine and constraints evaluator.

Curated narrative

The hand-written story of this package: orchestrata_ultimate.verification.

66 modules, 9,151 lines of code.

Subpackages

Modules

Dependency diagram