All reference builds

Our reference application

Awaken Pilot

A task interface for progress, approvals and deliverables.

Pilot keeps the product surface thin: a Mission becomes an Awaken Session and a Project chooses the Deployment. Users see the plan, progress, files, approvals, and result without a second task engine underneath.

Best for: Agent product teams that want the shortest path from product UX to durable execution.

Source-archive reference build

The situation

You have the product idea, but the first prototype still needs task state, progress, approval, schedules, files, and recovery.

First useful result

Run one bounded Mission in Plan or Execute mode, then review its progress and result in the same Session.

Product shape

Create a thin Agent application

Your application keeps

Product copy, Mission interaction flow, acceptance criteria, and UI projections.

Awaken provides

Agent, Deployment, Session, Run, events, files, tools, policy, Worker, Sandbox, and recovery.

What is available today

Check the status before you invest more.

A fixed committed source archive includes the shared build inputs and passed a clean source installation, local checks and build. This published snapshot still has runtime compatibility gaps and has not passed a full real-Agent journey. It is available as a source reference while that qualification remains pending.

Committed application baseline
973dc96aa2041b20e1e377aa876178dfe0a1d8b1

Each application has its own code and qualification. The Agents documentation revision is a separate baseline.

Source archive SHA-256: 17c8303bd6f45955be26ddeeb709b7778d101978d4a5250c9794a2ef48396a02

Download the fixed source Read the implementation decisions and failure modes
  • Tested

    Execute and Plan paths share one Session log.

    Where to check: Pilot web and API test suites

  • Tested

    Approvals, budgets, Skills, MCP, subagents, artifacts, and schedules use Awaken-owned contracts.

    Where to check: pnpm check

  • Live gate pending

    The real-stack acceptance protocol includes interruption and recovery; its live result is not published yet.

    Where to check: docs/real-stack-acceptance.md

Use this reference

Start with one clear build and validation path.

  1. 01Start with one Mission and one visible acceptance criterion
  2. 02Interrupt or approve it once, then confirm the same Session continues
  3. 03Keep only the product projections your users need

Run one bounded Mission in Plan or Execute mode, then review its progress and result in the same Session.

Run the Awaken quickstart Learn Session management