One context · many kinds of work
Communication becomes creation. Creation becomes action.
A Room gathers the people, machine people, memory, artifacts, and tools needed for the work. The result can move into an app or service and return without losing the conversation that shaped it.
Start with the group
The Room is the working context.
Membership, identity, messages, memory, artifacts, and tool use meet in the Room. People do not have to become the clipboard between an isolated chatbot and the rest of their working life.
Make together
in-progress
Both hands on the work.
A Genie changes the live artifact. A person takes the wheel and edits it directly. The Genie continues from the new state instead of starting over from pasted context.
Co-creative release proof is in progress and will be bounded per artifact type.
Move the expert, not a lossy summary
in-progress
Your intelligence can carry the work.
A Genie that knows the work can carry it into another conversation or tool, work with the right participant, and bring the result home to the original context.
In progress: delegation behavior and permission boundaries remain under release verification.
Act through visible connections
in-progress
Work leaves. The result comes home.
Browser, terminal, desktop automation, and connected services let work leave the Room. Permissions, provider choice, failures, and the return path stay visible.
In progress: only named, tested providers and actions become release claims.
Your server is the organizational boundary
Private by default. Connected by choice.
Nautilo keeps the local organizational context together and makes the crossings choices you can inspect. It does not pretend every external provider offers the same privacy.
Inside the boundary
- People, Genies, Rooms, and long-lived artifacts
- Membership, namespaces, memory policy, and tools
- The model and provider routes your operator permits
Outside the boundary
- Remote model providers selected by the operator
- Connected services and external applications
- Other private servers unless a future cross-server path is approved
A crossing is not automatically private. Its privacy depends on the selected provider, connection, permission, and release-current protection.
Choose your way in.
Pick the door that matches the work in front of you. Both lead into the same system.