Capture
A field photo, note or recording becomes part of the work it supports.
8OS / The sovereign operating environment
Our vision for 8OS: a sovereign operating environment for your information, applications and AI.
Connect the information that makes AI useful. Decide who can use it, for what purpose and under which rights, with cryptographic evidence for the facts that matter.
Shared context. Deliberate authority.
One environment / A continuous thread of understanding
A conversation explains a decision. A document captures the requirement. A photo supplies evidence. A code change implements it. We’re building 8OS so those connections remain useful as you move between applications, people and AI.
A field photo, note or recording becomes part of the work it supports.
Bring the project, people, conversations and relevant documents into view.
Call on 8RF with an authorized view of the goal, constraints and evidence.
Give a contributor the context and authority their contribution needs.
Pick up the work on a participating device, with its understanding intact.
Native apps and shared foundations
Each experience works with the meaning of its information: an identity and its authority, a message and its task, a note and its subject, a document and its evidence. Shared foundations connect the work while you control participation.
Contacts are one view of a deeper Identity Graph connecting people, organizations, devices, AI agents, services and places. Roles, credentials and delegated authority give those connections meaning.
An engineer, their employer, their device and their AI assistant are related participants with different responsibilities and permissions.
Choose which identity to present, what facts to establish and which details or actions to disclose and delegate in each context.
One communication foundation for conversations, AI handoffs, system events and commands. Typed messages connect participants, source objects, task state and authority.
A sensor event can lead to an AI investigation, a human decision and a recorded system action, with each step linked to the same work.
Choose participants, hosting and delivery routes, plus the rights attached to shared content and each requested action.
A library of connected objects, with original content, versions, provenance and relationships. Files, collections and search offer different ways into the same information.
An inspection photo can appear in a project, a conversation and a report while retaining its identity and source history.
Decide where content is held and how it may be used. Track changed rights and removal requests across known participating holders.
Attach an evolving, authored note thread to a person, place, file or task. Keep observations, revisions and source context connected as a thought develops into a decision or work.
A field observation stays with the asset, its photo and the task it creates, ready for the next person or authorized AI to understand.
Keep a note private or choose its shared audience. Connecting it to an object does not make it public.
Compose tasks, projects, phases and sprints from shared items, relationships and rules. Boards, timelines and dependency views reveal the same work at different levels of detail.
Move from a customer requirement to its discussion, supporting document, code change and validation.
Delegate a defined contribution with the context and action permissions it needs.
Build reports, workbooks and briefings from structured claims, calculations and source evidence. Keep the displayed result linked to the information and revision that support it.
An observation can feed a calculation, a report and a briefing. A new source revision can reveal which conclusions need review.
Scope AI edits to the relevant material, and choose live references or a fixed published revision.
Connect geography, infrastructure, observations and changing conditions in a native model. Bring authorized personal or operational context into route and asset decisions.
Relate a bridge restriction to the vehicle, load, arrival time, affected journey and inspection evidence.
Keep private searches, routes and observations on infrastructure you or your organization control.
Connect photos, video and audio to their subjects, source components and rights. Find the meaningful moment, preserve its context and assign control through accepted agreements.
A capture can belong in a report, conversation or AI task while its source, designated controller and permitted uses remain connected.
Assign technical control to another person or device, delegate capture rights for a defined window, and specify the audience and permitted uses.
Navigate purpose, requirements, interfaces, callers, dependencies and exact source at progressive depth. Retain useful understanding across tasks instead of repeatedly rediscovering it.
Connect requirements in Documents, decisions in Messaging, authority in Identity and progress in Projects to code across repositories.
Scope each person or AI’s context and change authority to the task.
Our mission
We’re building 8OS to unite defence-grade protection, advanced AI and seamless collaboration in a sovereign operating environment. You decide who participates, what they can access and what they can do.
Connected participation / Deliberate authority
The vision is to make collaboration as open as you choose, with a clear scope for every participant. Explore an illustrative project through three different views.
Illustrative workflow / Improve offline inspection capture
Connect the project, its conversations, requirements, field media and software.
A useful connection is not permission to disclose. The design separates finding information, reading it, supplying it to an AI provider, proposing a change and accepting the result.
The 8OS vision / Connected context, programmable rights
Useful AI needs the relationships between your information: the people, conversations, evidence and purpose. We’re building those connections together with the rights that govern their use and cryptographic evidence for the facts that matter.
Both participants accept the terms. New captures in the agreed window are assigned to the designated controller.
The controller permits an assistant to prepare a transcript from chosen clips, with an explicit processing destination.
Keep the agreement, source clips, derived transcript and recorded actions connected. Track expiry, changed rights and managed-copy removal.
Our smart-contract direction connects accepted agreements to specific people, devices, information and actions. Define what can be read, edited, shared, delegated or supplied to AI, for which purpose and for how long. Make a transfer of control an explicit, accepted event.
Our zero-knowledge work targets proofs of defined conditions without revealing the private information behind them. For example, prove possession of an eligible entitlement without disclosing its secret identifier. Signed agreements establish who accepted terms; ZK proofs establish the particular condition their proof system checks.
Connect rights changes to the managed information they affect. Keep revoking access, deleting data and destroying keys distinct. Record which participating holders completed a requested operation, which remain pending and what each receipt or proof actually establishes.
Let an authorized assistant follow a requirement into a conversation, a document, a recording or code. Scope its context to the task, preserve the sources behind its result, and keep permission to read separate from permission to send information to another AI service or act on it.
A signature establishes acceptance by a signing key. A ZK proof establishes a defined statement against particular inputs. An erasure receipt records a scoped operation by a known holder. Verification also needs the right identity, authority and current state. None of these proves total security or the removal of unknown exports, screenshots or information learned by an external model.
Core services / Shared across the environment
Carry goals, evidence, alternatives and unfinished work across tasks. Give each AI contribution a focused view, with a path back to the sources and the broader purpose.
Explore Infinite Reasoning Fabric →Connect people, organizations, devices, AI and services through contextual identities, credentials and relationships. Keep representing someone, holding a right and being authorized to act distinct.
Explore Identity & authority →Give people readable conversations, agents precise task handoffs and systems typed events and commands. Connect each exchange to its participants, evidence, authority and recorded outcome.
Explore Messaging →Build on 8DB’s approach to post-quantum protection, contextual permissions and governed data lifecycles. Connect programmable agreements and selective proofs to the information and operations they govern.
Explore the security work →A native decentralized mesh
8OS is a virtualized operating environment built around a protected native mesh. Our direction is to let you choose the participating installations and connect the parts of your digital world that belong together.
Where information is stored, who may read it and who can coordinate work are separate choices. A device can participate in a mesh without every participant gaining access to everything it holds.
Explore the mesh foundation →Connected contexts, separately scoped participation. Illustrative architecture.
From vision to your first evaluation
8OS is in development. The first evaluation focuses on a protected local library on Apple devices. The connected app family, mesh experience and shared reasoning service describe the wider product direction.
Tell us what you want to keep private, who you need to work with and where today’s tools make that difficult.
A public download, release date and pricing have not been announced. We’ll define the supported devices, imports, recovery paths and features for each evaluation. Joining a discussion does not reserve access or subscribe you to a mailing list.
Local storage and local AI processing are separate decisions. Our design makes the permitted context and the processing destination explicit. Evaluation materials will identify the supported local and provider paths.
Permission changes, device removal and recovery need verifiable behavior on the supported release. Copies already exported or captured outside the environment cannot simply be recalled. These boundaries belong in the evaluation, alongside the user controls.
Our mission sets the ambition. The security model and engineering evidence explain the current work and its scope. A release must establish protection for its actual information paths, devices and recovery behavior.