Reliability and openness

Know what continues when an Agent is interrupted.

Teams need to see what happened, control what an Agent may do, and continue the same work after a restart or hand-off. These needs guide both the product and the way we describe it.

Keep the work, responsibility, and completion decision connected

Each job needs a named owner and a result another person or system can recognize. An Agent may plan and act, but the owner decides whether the work is complete.

Keep deployment and product decisions with the operating team

These rules guide product design and implementation support.

Show the source

Awaken is Apache-2.0. You can read the code, follow a decision, and propose a better one.

Keep operations in your boundary

Run the control plane on infrastructure you choose. Keep Session records and credentials inside that operating boundary.

Leave room to change course

Choose providers and execution backends explicitly. Open protocols and readable formats make later changes easier, though never free.

State product availability and limits

Plain status

We distinguish what is available now, what is still a preview, and what remains a target. When a limit matters to your decision, we state it near the claim instead of hiding it in a footnote.

Read the current implementation boundaries