NatusAIRequests and decisions
Conversations, issues, requirements, acceptance criteria and approvals retain separate meanings and clear ownership.
Orion Workspace · The connected experience inside OrionPlatform vision
One request. A traceable path forward.
A conversation should not lose its meaning when work becomes a task, a code change or a deployment. Orion Workspace is the intended connected place for the people, decisions and evidence behind an application.
The experience described here is our direction for NatusAI Orion. Product scope and availability are qualified separately; it is not a release announcement.
Follow the work
“Tell our team when a shipment may miss its arrival window.”
An illustrative request shows the intended chain. Each stage produces something the next person, or authorised agent, can inspect.
Request & acceptance
Record the need. Agree which shipments, what counts as a delay and who can receive the information. Incoming feedback becomes a requirement only when accepted.
Change & evidence
Associate the exact source change with a preview, test results and the decision to promote it. Failed verification stays visible.
Release & deployment
Create an immutable release, record the target environment and observe whether the application meets its acceptance checks there.
Outcome & next request
Keep the resulting health, support and usage observations connected to the release. Use new evidence to shape the next improvement.
Illustrative workflow, not a live workspace or a demonstration of a released application.
Context that survives the session
Keep the reason beside the result.
Four kinds of record stay connected, so anyone reviewing an application can see why it changed, not only that it changed.
Knowledge and source
Documentation, source references and engineering history stay versioned and attributable. Git-backed collaboration is intended; the forge has not been selected.
AI work and evidence
Tasks, attempts, checkpoints, diagnostics, evaluations and verification artefacts are linked to the inputs and source version they concern.
Releases and environments
A merged change, a published release and a healthy deployment are distinct outcomes, with separate records and checks.
Auriga in the workspace
AI gets the context it needs, and the boundaries it must respect.
A task should find the relevant capability and version first, then retrieve the schemas, examples or evidence it needs. A small change should not require loading an entire repository or conversation history.
Durable attempts, cancellation, checkpoints and budgets make ongoing work understandable. Summaries keep source references and freshness, while application knowledge remains visible only to authorised participants.
Compact diagnostics and precise diffs help people and agents inspect the result without hiding important correctness or permission information.
Human ownership
The workspace coordinates authority. It does not invent it.
People retain control of business intent, access, budgets and operating policies. Platform visibility does not grant access to confidential application data.
The agent proposing a change cannot approve its own expanded permissions, weaken its acceptance criteria or activate its own successor.
Keep exploring
Layer 03 · ApplicationsRoadmap
NatusAI Orion
Describe the application you need, review the result, release it with approval, then run and improve it.
Explore NatusAI Orion
Layer 02 · IntelligenceRoadmap
NatusAI Auriga
AI assistants and tools that work within the permissions and budgets your people set.
Explore NatusAI Auriga
Across layersRoadmap
NatusAI Gemini
Backups you can prove you can restore, with evidence for auditors.
Explore NatusAI Gemini
Build your next chapter
Let’s connect the possibilities
Tell us what your business needs. We’ll help you find a practical place to start.
Or write to contact@natusai.com
