Skip to content

Issue 6: ORACLE Integration Adapter #7

Description

@Rajkoli145

1. Title

Build a normalized ORACLE integration adapter for the MAIN Agent.

2. Purpose

Create the adapter that converts ORACLE outputs into stable inputs the MAIN Agent can safely use for orchestration.

3. Background Context

The MAIN Agent must never duplicate ORACLE analysis. It should only consume normalized ORACLE outputs such as viva targets, observable signals, failure scenarios, and evidence traces.

This adapter is the contract boundary between the intelligence layer and the orchestration layer. It should absorb schema variability and expose safe, versioned fields to MAIN.

4. Responsibilities

  • normalize ORACLE outputs
  • expose viva targets
  • expose observable signals
  • expose failure scenarios
  • validate schema shape
  • handle malformed payloads safely

5. Technical Requirements

  • the adapter must not duplicate ORACLE logic
  • schema validation must be strict and explicit
  • malformed payloads must fail safely
  • normalized outputs should be simple for MAIN to consume
  • the adapter should remain modular and independently testable
  • if schemas evolve, the adapter should be the first compatibility layer updated

6. Acceptance Criteria

  • integration remains stable across expected ORACLE output shapes
  • malformed payloads are rejected or normalized safely
  • MAIN receives normalized interfaces only
  • evidence links remain intact after normalization
  • adapter behavior is deterministic and auditable

7. Non-Goals

  • no ORACLE implementation duplication
  • no AST parsing
  • no viva orchestration logic
  • no hidden confidence calculation
  • no candidate response scoring

8. Suggested File Structure

backend/src/agents/main_agent/integration/
  oracle_adapter.py
  oracle_schema.py
  payload_normalizer.py
  validation.py
  compatibility.py

9. Integration Notes

  • the adapter should sit between ORACLE output models and MAIN orchestration logic
  • the adapter should be the only place where ORACLE payload shape differences are handled
  • if ORACLE adds a new field, update the adapter and shared schema intentionally
  • do not let MAIN reach into ORACLE internals directly

10. Testing Expectations

  • valid payload normalization tests
  • malformed payload rejection tests
  • schema compatibility tests
  • regression tests for evidence mapping
  • deterministic output tests
  • adapter isolation tests

Metadata

Metadata

Assignees

Fields

No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions