Skip to main content
Version: MVP

Multi-agent workflow bridge

2 min readReferenceUpdated 2026-05-19

What you'll find here

The rule for bridging to external multi-agent workflow systems — posture levels, required controls, and prohibited behavior.

External systems coordinate; they don't replace policy.

External workflow systems may coordinate work, but they must not replace Craik's policy authority or erase accountability for agent actions.

Posture

multi_agent_workflow_bridge_decision returns allowed, review_required, deferred, or blocked for a candidate surface.

Level
Use
Notes
supported
allowed
When all required controls are present.
experimental
review required
Explicit review before use.
deferred
unavailable
Even with controls.

Required controls

Role boundaries

External agents map to explicit Craik roles.

Queue boundaries

Dispatch scoped and observable.

Approval gates

Human review never bypassed.

Policy context

Plus envelope references.

Evidence links

For imported or routed work.

Receipts

For bridge actions and outcomes.

Payload redaction

For public reporting and exports.

Prohibited behavior

Bridges are blocked when they:

Copy secret values

Allow unbounded dispatch

Bypass human approval

Merge agent identities

Accept external instructions as authoritative

Over Craik policy.

Omit role / queue / approval / policy / evidence / receipt / redaction controls

Bridge receipts identify everything.

Workflow · mapped role · queue · approval state · policy envelope · evidence links · redaction outcome · external action result. Public docs and receipts must avoid credentials, private local paths, and private task names.

What's next