+Roadblock™

Reference Architecture

Outside, control plane, inside. Explore the interlock that prevents simultaneous inside and outside connections.

Outside. Control plane. Inside.
A staged handoff between them.

Explore a complete transfer.
The connection indicators follow the job state.

Illustrative simulation
No live connections or jobs
ROADBLOCK REFERENCE ARCHITECTURERB-001 · API SOURCE
01 / OUTSIDE
External API sourceApproved source endpointRecords · files · event feeds
NO ACTIVE CONNECTION
External pull containerNot createdCreated per collection job
Compare source → pull the diff
Write changed data to staging
Outside connection: CLOSED
02 / CONTROL PLANE
Roadblock™Schedule · initiate · enforce · audit
Connection interlockWorker lifecycleRelease authority
Commands both workers
No direct source-to-lake session
Isolated staging

Waiting for a new batch

Customer security scansData & content inspectionPolicy clearance
Release gate: LOCKED
03 / INSIDE
Internal delivery containerNot createdCreated only after clearance
NO ACTIVE CONNECTION
Hawkeye private data lakeApproved tenant destinationData · databases · local AI
Pick up the cleared batch
Write, acknowledge, disconnect
Inside connection: CLOSED
OUTSIDE WORKERSTAGINGCollection phase only
CLEARED STAGINGINSIDE WORKER → LAKEDelivery phase only
Blue = active data connectionClosed = no active sessionOutside and inside cannot overlap
RB-001 · PHASE 01 / 08Every hour

Roadblock owns the start.

A scheduled or manual job enters the control plane. Roadblock checks that both connection paths are closed before creating any worker.

Acquire the transfer lock; select the source, diff checkpoint, destination, and inspection policy.
Demonstration only. Schedule and inspection choices do not configure Hawkeye.

Test the connection interlockAdvance to Collect or Deliver to test a conflicting connection request.

01Schedule
02Collect
03Disconnect
04Inspect
05Release
06Deliver
07Teardown
08Complete