Recoverable work
Autosave, conflict recovery, durable artifacts, and explicit deletion keep work from disappearing silently.
Astra 1.1: Operational Trust
Work that recovers. Evidence you can inspect. Knowledge that stays inside its governed scope.
August 30, 2026
The release
Trust is something the workflow has to earn.
Astra 1.1 strengthens the workspace around the model: preserving unfinished work, exposing admitted evidence, tracing failures, and keeping sensitive drafts inside explicit ownership and retention boundaries.
Governed knowledge
Approved policy and published equipment records are admitted only through their applicable scope.
Inspectable support
Stable references and content-free diagnostics make failures traceable without copying the conversation.
Responsive at scale
Earlier streaming, mode-aware context, prompt caching, and latency alarms make performance observable.
Inspectable evidence
See what supported the turn—and what did not.
Global Admin diagnostics connect a response to its applied site, routing, model, policy sources, equipment records, privacy controls, and a stable support reference. No-match states stay visible instead of being presented as grounded evidence.
ASTRA-…-REFERENCEPolicy evidence
Approved sources, applicability scope, and retrieval score remain attached.
Equipment evidence
Published version, business unit, site type, country, and source identity.
Support trail
Status and classification without storing prompt or response content.
Recovery by design
Failure should leave a recovery path.
Astra now keeps artifacts and conversation history durable, preserves useful failure context, and lets people remove records intentionally. Private workflows add a second browser recovery path while the server remains authoritative.
- 01Save continuously
Bounded mutations preserve completed fields as the work changes.
- 02Reconcile conflicts
Optimistic versions stop one tab from silently replacing another.
- 03Continue deliberately
Retry paths and visible save state keep the human in control.
Private monthly 1:1
A structured artifact that can survive the interruption.
Interview answers, fixed and custom metrics, and prior-month context live in an owner-scoped draft. The artifact autosaves, recovers unsent browser changes, and stays outside general Astra history.
- 650 ms
- debounced field autosave
- 30 days
- private draft lifecycle
- encrypted, owner-scoped storage
Completed answers are preserved · stale unanswered prompts can be rebuilt · generation failures leave a retry path
Capability proposalChanges requested
- SubmittedProposal and supporting material received
- Global Admin reviewDecision note retained for the submitter
- ResubmissionReview history remains visible
Closed-loop capability review
Submitting an idea is no longer a one-way door.
Employees can see the status of proposals tied to their account and read Global Admin approval, rejection, or requested-change notes. Reviewed packages remain quarantined; feedback does not bypass validation or publication controls.
Governance in the runtime
More context, with the same human boundary.
Knowledge turns consult approved policy and published equipment records through jurisdiction and site scope. Astra’s versioned identity kernel keeps its constitution and persona ahead of per-turn context. None of that turns a model response into an approval, a record decision, or a substitute for qualified review.
Also in 1.1
The operational details that make trust usable.
- Open, resume, and delete saved conversations from one workspace history.
- Attach images through signed uploads and send supported media to Bedrock inline.
- Reuse referenced historical files without resending every earlier attachment.
- See policy and equipment evidence admitted to supported turns.
- Give capability submitters their status and Global Admin decision notes.
- Keep Astra’s constitution and persona versioned independently from the product release.