aipostex Integration

hemlock-lab and aipostex-lab can run on the same host using Docker Compose, sharing a Docker network for cross-lab testing.

---

Network Topology

graph TB
    subgraph host["Docker Host"]
        subgraph hnet["hemlock-net"]
            hl["hemlock-lab containers<br/>localhost:8000-8104"]
        end
        subgraph anet["aipostex-net"]
            al["aipostex-lab containers"]
        end
    end

    hl <-->|HTTP via host| al

Both labs expose ports on localhost, so cross-lab communication works through the host network.

---

Why Integrate?

Scenario	Description
End-to-end testing	Use aipostex to exfiltrate data through hemlock-lab's RAG pipelines
Combined validation	Test hemlock payloads + aipostex delivery in a single workflow
Shared ChromaDB	Point aipostex at hemlock-lab's ChromaDB on localhost:8000

---

Configuration

Both stacks expose services on localhost. Cross-lab communication uses host-mapped ports:

# From aipostex containers, reach hemlock-lab services via host
curl http://host.docker.internal:8100/extract  # LangChain pipeline
curl http://host.docker.internal:8000/api/v1/collections  # ChromaDB

Alternatively, connect both stacks to a shared Docker network:

# Create shared network
docker network create shared-lab

# Add to both docker-compose.yml files as an external network

---

Prerequisites

• Both labs running on the same Docker host
• Non-overlapping port mappings
• Ollama running on host (shared by both labs)

---

Next Steps

• Architecture — hemlock-lab system overview
• hemlock Integration — The prediction feedback loop

---

Legacy: Proxmox Cross-Lab

The original Proxmox deployment used vmbr100 bridge (172.16.50.0/24) with hemlock-lab at VM 260 (172.16.50.50) and aipostex-lab at a separate VMID. Both VMs shared the bridge subnet for direct HTTP communication.