OIM: intelligence that stays with the work.

Early access is granted individually, one person at a time, while OIM is proven in real use. The access page composes your request as an email and opens it in your own mail app. Nothing is stored on the page, and there is no automated queue or waiting-list position. A request does not create an account or promise a place.

1. Open oim.ozlili.com/access.
2. Write your name, your email, your organization (optional) and what you would use OIM for.
3. Choose Compose access request. Your mail app opens a message addressed to hello@ozlili.com. If it shows any other address, change it to hello@ozlili.com.
4. Send it yourself. Access is granted individually.

Once access is granted, you enter with your one OZLILI account. The workspace reports each capability with its real state, and that report is real today: the public capability map and the panel inside the workspace are read from one measurement. Conversation is not yet available on the hosted product. Without access, you can read the public home and request access. The workspace requires access and your OZLILI account.

1. Access is granted individually, by request.
2. When access is granted, choose Sign in to OIM and use your OZLILI account.
3. Open the capability panel to see what is Live, In development or Planned.
4. Treat that panel, not marketing copy, as the source of truth. Anything not marked Live is not something to rely on yet.

OIM is designed to begin from the context you choose to bring in, not from what it assumes about you. Chosen context is in preview. Memory recall is explicit and off by default in early access, and durable memory foundations are in development and testing. Typed conversation is not available today, so the steps below describe the design, not a live round-trip. Designed to surface the risks, deadlines, follow-ups and changes that need your attention. Proactive suggestions are in development.

1. As designed: you bring a question, a half-formed plan, or a decision you are considering, with the context you choose.
2. As designed: the workspace is designed to use that context to identify the kind of help you need.

Governed actions are in development. They are designed to keep people in control before execution: an action is prepared as a concrete step, shown in full, and runs only after your approval. It never acts on your tools without the approval that applies.

1. As designed: you state an objective.
2. As designed: OIM prepares it as a concrete step, not run yet.
3. As designed: the action is shown in full, and is armed only on a second, deliberate press.
4. As designed: only then does it run. Anything with a side effect runs only with the approval, authority or policy that applies.

Named, not available today.

1. Memory: designed for continuity across your work. Durable memory foundations are in development and testing.
2. Files and images: file and image workflows are planned.
3. Structured work: turning substantial work into a piece of work you can open, copy and keep is planned.
4. Voice: voice foundations are in development; hosted voice acceptance is still underway.
5. Presence: a presence layer is in development, designed to keep presence separate from inference.
6. Desktop and mobile: desktop and mobile foundations are in development.
7. Research, vision and screen understanding are not available today.