Applied systems research · San Francisco

Reason through new work. Compile what repeats.

LLM agents discover how to complete a task one decision at a time. Applied Runtime turns the procedures they have already figured out into secure graph runtimes, behind one pipeline that works with the harness and tools you choose.

Read the thesis
A complex agent reasoning trace being compiled into a controlled graph runtime
Fig. 01Reasoning trace to permissioned runtimeActive research

LLMs write a procedure while they solve a task.

An agent interprets the request, decides what to do next, selects tools, transforms data, checks intermediate results, and recovers when something fails. For new and ambiguous work, this flexibility is valuable.

The waste begins after the procedure is known. Most production agents still reconstruct every step for every user, spending tokens and time to rediscover a path that already exists in prior traces.

We treat a successful trace as a candidate program. Stable work is compiled into a graph. Novel work stays agentic. One pipeline chooses the right execution path for each request.

From reasoning trace to reusable runtime.

01

Reason

The agent handles a new request, chooses tools, resolves exceptions, and verifies the result.

02

Observe

The trace records the decisions, tool contracts, data dependencies, checks, and recovery paths that worked.

03

Bound

Repeated traces reveal a stable task with explicit inputs, outputs, permissions, and failure conditions.

04

Compile

The proven procedure becomes a typed graph runtime with tests, versioning, and safe fallback behavior.

05

Run

Known work executes directly. New or uncertain work returns to the agent through the same pipeline.

Bring your agent stack. We improve the system around it.

One agent pipeline chooses the right model and execution path for each request, learns from real use, and makes proven work cheaper and more reliable over time.

01

Any harness

Choose the agent harness you already trust. Connect its tools, CLIs, and skills from a GitHub repository, or start with ours.

02

Model routing

Each user query is routed to the model best suited to the task, balancing capability, speed, and cost.

03

Sandbox portability

Run across major sandbox providers through one consistent execution layer without rebuilding the agent loop for every environment.

04

Workflow compilation

When a process repeats reliably, it becomes a typed, permissioned graph workflow instead of another full LLM reasoning pass.

05

Continuous improvement

We automatically evaluate agent outcomes, find performance gaps, and create or revise the tools, skills, and workflows needed to close them.

The difficult part is deciding what should become infrastructure.

R.01

Task boundaries

Where exactly should a reusable task begin and end inside a long agent trace?

Active
R.02

Compilation thresholds

When is the evidence strong enough to turn a successful procedure into infrastructure?

Active
R.03

Secure execution

How can a graph inherit least privilege, provenance, approvals, isolation, and rollback?

Active
R.04

Organizational memory

How should a runtime move from one user to a team or a trusted set of organizations?

Active

Reuse must follow authority.

A compiled runtime can remain private to one user, move into an organization, or be shared across organizations only when its data, tools, and permissions allow it. Every promotion is explicit, testable, versioned, and reversible.

UserTeamOrganizationTrusted network
AnswerThis logoAnswerThis

Where this thesis began.

While building AnswerThis, we spent roughly half our time reading traces, finding repeated procedures, and asking coding agents to turn them into tools. Applied Runtime is the attempt to automate that entire process.

Visit AnswerThis