01. Chat, requests, issues and knowledge
Owner Orion Workspace
Keep conversations, feedback, accepted requirements, decisions, documentation and support history connected. Incoming feedback only becomes a requirement after deliberate acceptance.
The NatusAI constellation is designed to connect what people ask for, what AI and engineering produce, what is verified, what is released and what actually happens in operation.
Platform vision · scoped foundations. This map describes the intended seven-role platform. NatusAI Lyra UI is an existing component system; NatusAI Cygnus 1.0 is planned and gated; the wider Orion experience remains a vision.
The Orion vision connects user intent to source changes, evidence, releases and observed outcomes.
Owner Orion Workspace
Keep conversations, feedback, accepted requirements, decisions, documentation and support history connected. Incoming feedback only becomes a requirement after deliberate acceptance.
Owner Orion Workspace
Link versioned source and engineering documents to exact changes, reviews and work items. The Git forge and integration approach remain unselected.
Owner Auriga
Coordinate exact model bindings, authorised tools, relevant versioned context, durable attempts, cancellation, checkpoints and budgets.
Owner Orion · Auriga
Produce candidate changes and previews in isolated workspaces; retain test evidence; promote immutable application releases through independent authority.
The planned Cygnus release and existing Lyra components have different availability and qualification boundaries.
Owner Cygnus · Lyra
Cygnus is designed for typed language, data and services. Lyra already supplies reusable interface components; each application composes them for its own work.
Owner Orion · Cygnus
Discover exact compatible modules, retain dependency and provenance records, and reuse independently verified releases. Private customer data and logic stay separate.
Owner Aquila
Retain source bytes and provenance, produce separately identified text or chunk derivatives, and scope document interpretation to the application. Exact formats and providers need qualification.
Owner Shared libraries
Connect external services and deliver authorised notifications while tracking credentials, external effects and delivery failures.
Deployment success, observed health, a completed backup and verified restoration are different pieces of evidence.
Owner Draco
Manage environments, deployments, networking, domains, certificates, capacity and desired versus observed operational state.
Owner Cygnus · Orion · Auriga
Use planned durable jobs and schedules for recurring work and admitted retries; show their status in Orion and allow authorised AI steps through Auriga.
Owner Orion · Draco
Connect runtime telemetry, infrastructure observations and application acceptance checks to the affected release and application.
Owner Gemini
Preserve data, configuration, application releases and recovery points together. Prove a restore through drills; backup completion alone is insufficient.
One connected experience still needs scoped access, accountable usage and an independent path back from failure.
Owner Orion · Cygnus
Govern organisation and application membership, scoped agent delegation, secrets and audit. Platform visibility never implies access to tenant-confidential content.
Owner Orion
Attribute hosting, AI-assisted development, ongoing maintenance and AI used inside customer applications to organisations, applications and jobs as distinct records. Provider-side costs and customer invoices are separate; funding, rates and billing policy remain open commercial decisions.
Owner Orion · Gemini · Draco
Retain installation, promotion and recovery paths usable when Orion or its AI provider is unavailable.
Owner Orion and every role
Identify owners and export paths for source, requirements, releases and data under access policies. Portable tenant export is beyond planned Cygnus 1.0.
These seven principles guide the platform vision. They do not claim a measured token saving or that every existing part was built by AI.
Typed, versioned, permission-aware API, MCP and CLI surfaces describe capabilities, effects and structured outcomes.
Discover an exact capability first, then retrieve only the needed schema, source range, example or evidence.
Requirements, decisions, task state and verified results survive sessions with source references and freshness.
Bounded diagnostics, precise diffs, pagination and artefact references carry enough detail for correction.
Find compatible libraries, components, contracts and proven workflows before producing another copy.
Keep exact inputs and provenance; test and review changes under authority that the proposing agent cannot grant itself.
Evaluate successful completion alongside tokens, retries, latency and cost. A shorter prompt is not useful if errors and rework rise.
Useful automation depends on more than a larger prompt: the same contracts, evidence and approvals that people rely on are what AI agents use. No measured token-saving or cost-reduction claim is made.
The seven names describe responsibilities within one intended system. NatusAI Cygnus has a separate first-release plan and qualification gates; NatusAI Lyra’s current components have their own documentation.

Tell us what your business needs. We will help you find a practical place to start, and tell you plainly which capabilities exist today.
Or write to contact@natusai.com
