Documents that keep themselves current.
A document in Abstract can stay live. Agents run on the schedule you set, read the sources you allow, and propose updates when reality moves. You stay the editor; they do the legwork.
Autonomy is a dial, not a switch.
Some updates are safe to apply silently, like a figure ticking over. Anything that changes meaning waits as a proposal. You choose per workflow what runs on its own and what needs your call. The point is not to remove you from the loop; it is to make the loop cheap.
Agents that come working out of the box.
Abstract ships with a working agent library: a formatting agent that enforces your style rules, a fact-check agent that flags claims against sources, a refresh agent that checks a section against its context, a strategy agent that reads your knowledge base before it critiques a plan. Customise them or build your own; they are instructions and context, not code.
Invoke them where you work.
Type /formatting or /company-strategy in the chat rail and the agent runs against the current document with your project context loaded.
Or let the calendar run them.
A weekly operating summary that updates itself every Monday morning. A board pack that assembles in the week before the meeting. Scheduled runs propose their changes and queue them for review; you open the project home and see what needs you.
Better than a dashboard, because it tells the story.
A dashboard shows the numbers and leaves the interpretation to whoever is squinting at it. A standing document carries the narrative: what changed, why it matters, what happens next.
See standing reports →