Primitive
Export Execution
Send broker-ready exports downstream.
POST /api/exports/execute creates importable commercial invoice data, package outputs, and broker handoff with the customs treatment already carried forward.
BorderBuddy is integrated on execute, BYOB is still supported, and the goal is cheaper, faster broker intake instead of another cleanup workflow.
Execution is the side-effecting protocol action. It takes the approved plan and runs the workflow that creates durable export state and faster broker intake.
POST /api/exports/execute
Execution is where broker handoff becomes real
Execution is where the protocol stops computing and starts acting. It creates broker-ready handoff, records operational state, and hands downstream systems something importable instead of something to fix.
Create broker-ready outputs
Materialize commercial invoice data, package records, and supporting outputs brokers can actually import.
Carry compliance treatment forward
Carry PGA and Section 232 treatment into the handoff so the broker is not rebuilding compliance context from scratch.
Make brokerage intake easier
Give the broker one cleaner intake path so filing moves faster and costs less to coordinate.
Cleaner upstream export state is cheaper than correction-driven broker intake.
Use EntryGo execute as a direct path into BorderBuddy when that broker path fits.
Keep existing broker relationships when merchants need their own customs brokerage workflow.
Importable invoice data plus carried-forward customs treatment gives brokers a faster intake surface.
Execution keeps the broker handoff cheaper and cleaner.
After planning succeeds, execution is the point where packages, notifications, and broker-facing outcomes are written. The handoff includes commercial invoice data, carried-forward customs treatment, and durable status so brokers spend less time reconstructing the file.
That keeps downstream handoff inside one controlled primitive instead of scattering it across queues, email threads, and broker-specific operator workflow. The result is faster brokerage intake and less coordination drag for the team managing the handoff.
Starter Prompt
Copy an execution prompt
Paste this into your LLM to model execution workflow, handoff steps, and output contracts.
You are helping me design an EntryGo Export Execution integration.
Goal:
- model the workflow behind POST /api/exports/execute
- define downstream handoff and artifact creation
- structure execution outputs and operational state
- think in protocol stages instead of ad hoc side effects
- prepare the integration for production rollout
Tasks:
1. Map what should happen during execution after planning succeeds.
2. Define the downstream handoff points for warehouses, brokers, and operator systems.
3. Propose an execution response shape with artifacts, notifications, and lifecycle state.
4. Show how execution should be inspected through events and export state.
5. Produce a draft implementation checklist for a production integration.