All AI videos

AI video

Inside Arca's Long-Horizon Agents That Run the Business - Aman Singh, Arca

Aman Singh explains how Arca uses signals, persistent state, operational context, tools, and targeted human approvals for work that spans several days.

AI Engineer · 2026 featured video

Watch on YouTube

What this video shows

Singh describes financial-service work where one client outcome may span emails, calls, settlement delays, several specialists, and a final transfer. Arca keeps the agent responsible for the outcome while signals wake it when the outside world or a person changes the state.

The useful design pattern has four parts: observable events, explicit operating context, durable state, and a shared space where an agent can ask the right person to approve or perform a step. Teams should test each transition and keep high-impact financial decisions under accountable human control.

GitHub's cloud agent overview provides a contrasting example of bounded background work in an ephemeral environment. Use Learnetto's agent test-set workflow to test wake-up events, stale state, duplicate signals, and approval boundaries.

What you will learn

  • Model long-horizon work as durable state plus events rather than one continuous model session.
  • Record which signal woke an agent and which goal it may advance.
  • Keep approvals tied to the exact plan, amount, identity, and current state.
  • Test delayed, duplicated, reordered, and missing events before production use.

How to apply this safely

  1. Map one outcome from the first signal to its final verified state.
  2. Name every event source, owner, timeout, retry rule, and idempotency key.
  3. Store task state outside the model conversation and keep an audit trail.
  4. Require a person for regulated advice, asset movement, or any action your policy reserves for them.

Important limitations

  • The talk presents Arca's own operating model and does not provide an independent audit or controlled comparison.
  • Financial workflows involve licensing, suitability, privacy, recordkeeping, and authorization duties that vary by jurisdiction.
  • The video shows an architecture and examples rather than failure-rate, cost, or customer-outcome data.

Sources to check

Continue learning on Learnetto