Skip to content

Integration

hemlock-lab doesn't exist in isolation — it's part of a feedback loop that keeps hemlock's survival matrix accurate against real-world RAG frameworks.

The Feedback Loop

graph TB
    subgraph hemlock["hemlock (Go CLI)"]
        M["Survival Matrix"] --> B["hemlock batch"]
        M --> V["hemlock validate"]
    end

    subgraph lab["hemlock-lab (Docker Compose)"]
        P["RAG Pipelines"] --> T["Test Harness"]
        T --> D["Drift Report"]
    end

    B -->|poisoned docs| P
    V -->|predictions| T
    D -->|drifts| M

    style D fill:#ff6b6b,color:#fff
  1. hemlock generates poisoned documents and predictions
  2. hemlock-lab tests those documents against real frameworks
  3. Drift report reveals where predictions are wrong
  4. hemlock is updated to fix incorrect predictions
  5. Repeat until 100% accuracy for current framework versions

Integration Points

hemlock Feature hemlock-lab Usage
hemlock batch Generates test documents (all format×technique combinations)
hemlock validate --json Produces predictions for comparison
hemlock version Verification check (is hemlock installed?)
pkg/validate/*.go Where drift fixes are applied

Pages

Page Topic
hemlock Integration The prediction→test→fix workflow
aipostex Integration Cross-lab connectivity with aipostex-lab

Next Steps