Skip to content

Digital & Physical AI Missions (System-2 Planner)

AGBoss is a strictly typed TypeScript application framework designed for complex multi-agent workflows and long-running autonomous missions on top of LangGraph. While lightweight prompt chains and untyped graphs suffice for conversational chatbots, production digital operations and physical autonomous systems require static graph and saga verification (agboss check), automatic LIFO side-effect compensation (compensateWith / committedBy), pre-call FinOps budget reservations, multi-instance lease work-stealing, and two-phase human-in-the-loop pauses with automatic button withdrawal (ChannelHandler.withdraw).

Why do high-consequence digital and physical AI systems need a System-2 orchestrator?

Section titled “Why do high-consequence digital and physical AI systems need a System-2 orchestrator?”

One unified @Application architecture in AGBoss governs both long-running enterprise backend pipelines and high-level physical autonomy:

Capability Digital Autonomous Missions (FinTech, SecOps, Enterprise Ops) Physical AI, Robotics & Smart Devices (System-2 Mission Planner)
Execution Horizon Runs lasting minutes to days across distributed child workflows (.toParallelWorkflows) claimed by idle Kubernetes pods via ExecutionLeaseRepository. Deliberative mission planning (1–10 Hz) layered above 100–1000 Hz real-time hardware controllers, motor drivers, and local safety reflexes.
Multimodal & Multi-Agent Quorum Parallel specialist agents (risk, compliance, fraud) joined via .acceptedBy(Arbiter).joinQuorum({ min, max, deadline }) with instant AbortSignal cancellation of stragglers. Multiple multimodal vision/spatial models cross-checked by a deterministic @Arbiter before executing an irreversible physical maneuver.
Human-in-the-Loop & Withdrawal Two-phase @ChannelRole pauses (Pending → Resolved CAS) in Slack/Teams; ChannelHandler.withdraw removes stale buttons when quorum or FailFast resolves early. Safe mission hold requesting operator confirmation with camera/sensor telemetry; withdraw dismisses the operator prompt if a sibling branch or abort resolves first.
Static Verification (agboss check) Compile-time Path Scope proof ([input.outdated-on-path]), DTO validation, and static saga verification ([flow.uncompensated-action]). Strict coordinate, velocity, and torque bounds verified via DTO schemas and agboss check before any command reaches the hardware bridge.
Automatic LIFO Saga Compensation Reverses external API/database mutations (ReleaseEscrowAction, RevokeOfferAction) in reverse order on app.cancel, FailFast, Surplus, or @Budget breach. Executes deterministic compensating @Action nodes (ReturnToSafeHoldAction, DisarmGripperAction) in LIFO order under a dedicated compensationTimeout cleanup window.

How does AGBoss orchestrate long-running digital missions with transactional sagas?

Section titled “How does AGBoss orchestrate long-running digital missions with transactional sagas?”

In enterprise backend, FinTech, and incident-response pipelines, workflows mutate external systems over hours or days while fanning out into child workflows and waiting on human approvals. AGBoss ensures that every uncommitted external mutation declares its compensateWith rollback action and optional committedBy commit boundary, unwinding side effects in reverse completion order (LIFO) if the mission is cancelled or aborted:

How does the dual-loop architecture work for Physical AI and robotics?

Section titled “How does the dual-loop architecture work for Physical AI and robotics?”

Autonomous robots, drones, and smart industrial devices separate control into two distinct loops:

  1. System 1 — Real-Time Hardware Control Loop (100–1000 Hz): Low-level firmware, PID/MPC controllers, actuator drivers, and hardware safety interlocks handle sub-millisecond stabilization, collision reflexes, and emergency stops.
  2. System 2 — Deliberative Mission Orchestrator (agboss): Runs as the high-level “cerebral cortex” that sequences multi-stage physical missions, fuses multimodal VLM/LLM assessments via .joinQuorum() and @Arbiter, pauses for remote human tele-supervision via @ChannelRole (with withdraw when resolved), verifies all target coordinates through typed DTOs, and triggers deterministic LIFO compensating actions (SafeParkManipulatorAction) whenever a mission is aborted: