Binding conduits

Conduits are scoped doors into tools you already keep. Zeus does not become the system of record.

A conduit is a named door. It is not an integration marketplace and it is not a migration. Your mail stays mail. Your sheet stays the sheet. Zeus only holds the thread.

Scope before you bind

For each tool, write what the desk may do:

Read a label, not the whole inbox
Append a row, not delete one
Post to a channel, not rewrite history

If you cannot write the scope in one sentence, do not bind it yet.

Cutting a binding

You can cut a conduit without moving data. The source of truth never lived on the desk. After a cut, in-flight relays on that rail stop and mark drift. That is the correct failure.

What we will not bind

Anything that can move money
Anything that can destroy a record without a hold
Personal accounts dressed up as a floor tool

Pantheon floors can request a private binding. Scout and Night Watch use the published doors.

Names

Call conduits what the floor calls them: “Mail rail,” “Harbor sheet,” “Quiet channel.” Do not name them after vendors in the brief. The ledger should still make sense if you change the door later.