01 / Research environments
Let an investigation grow.
Develop a question across conversations, sources and competing explanations. Return to the point where your understanding changed.
For individuals & research teamsMachine / knowledge that continues
What you discover
should remain useful.
Ideas develop. Research changes direction. Organizations learn. Give that knowledge a place to continue, with its context, alternatives and history intact.
One platform.Many investigationsShared understanding
ONE QUESTION. SEVERAL WAYS TO UNDERSTAND IT.Illustrative
Keep the difference.
Develop the understanding.
World 01One interpretation
World 02Another explanation
MetaWhat their relationship reveals
The next step
Compare assumptions. Find the gap. Explore an alternative.
Context · Evidence · HistoryExplore the example ↗
Choose the work you want to do
Two starting points.
A shared foundation.
02 / Organizational knowledge
Establish what the organization knows.
Bring procedures, records and experience into view. Examine different interpretations before changing the way work gets done.
For leaders & organizationsBeyond a collection of conversations
The value is in what you can return to, connect and develop.
Context
Keep the reasoning.
Retain the question, the evidence and the assumptions behind a conclusion.
Plurality
Hold alternatives open.
Explore distinct interpretations without merging away the differences that matter.
Continuity
Make change inspectable.
Follow how understanding develops and which decisions move the work forward.
Research environments
Your work shouldn’t end
when the conversation does.
For independent thinkers, scientific researchers and teams whose questions take more than one conversation to answer.
Start with a question
Follow the investigation.
Keep evidence, uncertainty and decisions connected as a question develops across disciplines and working sessions.
Keep distinct interpretations
Compare before concluding.
A World holds a context for interpretation. A Meta examines relationships across those contexts, including incompatible assumptions and missing evidence.
A research workflow
From a promising explanation
to a better question.
01
Constitute a context.
Define the research question, source material and assumptions that make an interpretation meaningful.
02
Develop an alternative.
Use a Fork to explore another direction while retaining its relationship to earlier work.
03
Review what changed.
Compare interpretations, record a State and decide what evidence the next investigation needs.
Machine is presented here as a research environment. Illustrative explanations are not scientific findings or a substitute for validation.
Independent work
A place for the long question.
Build a body of thinking you can revisit, connect and extend. Start with one investigation and add capacity as the work grows.
Compare personal plansProgrammes & labs
Continuity across people and projects.
Explore a scoped pilot for investigations that span contributors, methods and research contexts. Agree access, provenance and review rules at the outset.
Discuss a research pilotOrganizational knowledge
Does your organization
know what it knows?
Procedures describe one version of the work. Systems record another. Experienced people understand what happens between them.
A familiar situation
Everyone completed their part.
The customer is still waiting.
Sales / formal process
“The contract is signed.”
Sales understands the handoff as complete when the commercial agreement is finished.
Operations / records
“We cannot begin yet.”
Onboarding records show repeated delays while the team gathers missing operational information.
Experience / working knowledge
“Complete means ready.”
Experienced employees distinguish a signed contract from a customer who is ready to onboard.
The disagreement is in the definition of a completed handoff. Making it visible changes what the organization can decide.
Inspect the organizational example What an engagement establishes
A baseline for understanding
and changing the work.
The knowledge baseline
A defined operational scope.
Traceable sources, working definitions, dependencies, gaps and conflicting interpretations, with explicit boundaries on what has been examined.
The continuing practice
A way to develop it.
Named contributors and reviewers, recorded decisions and a process for revisiting the baseline as evidence, roles and operating conditions change.
Begin with one consequential question.
01 / Diagnostic
Identify the scope.
Choose a function or decision chain. Establish source availability, participation and the question the engagement must resolve.
02 / Functional baseline
Establish the knowledge.
Compare procedures, records and experience. Review interpretations with the people accountable for the work.
03 / Knowledge operations
Maintain continuity.
Agree governance, review intervals and change procedures. Extend coverage when the baseline proves useful.
Proposed engagement model. Scope, delivery, access controls and commercial terms are agreed before a pilot.
Prepare a diagnostic requestInteractive examples
See what the differences reveal.
Select a context, compare interpretations and inspect an alternative. These are illustrative walkthroughs; your real Machine examples can replace them later.
Illustrative walkthrough
Switching views keeps the selected context. Alternatives retain their lineage.
All content is invented for explanation. No real research, customer records, account or AI processing is used.
Research
Develop the investigation.
See how individual research grows into a programme or laboratory environment.
Explore researchOrganizations
Establish a baseline.
See how a scoped engagement becomes a continuing organizational practice.
Explore organizational knowledgeProposed commercial models
Choose the work.
Then the capacity.
Research plans support developing investigations. Organizational engagements establish knowledge across a defined operational scope.
Explorer
Get to know the approach.
Free
Explore a bounded starting environment.
Discuss this planPersonal
Develop your own work.
€15 / mo
For ongoing individual investigations.
Discuss this planResearch
Keep several inquiries moving.
€39 / mo
For deeper comparative research.
Discuss this planProgramme
Coordinate a research programme.
€99 / mo
For connected investigations and contributors.
Discuss this planLab
Explore an institutional environment.
€299 / mo
For a scoped research team pilot.
Discuss this planWorking price hypotheses for validation, excluding VAT. No purchase or subscription is activated by this demo. Final entitlements and availability remain to be defined.
How capacity will be specified
| Dimension | What the plan must define |
|---|---|
| Machines & Worlds | Active environments and distinct interpretation contexts |
| Metas & Forks | Comparison capacity and concurrent alternative developments |
| Contributors | Participation, permissions and review responsibilities |
| Execution & storage | Bounded processing and retention allowances |
| Roads & States | Governed transitions and recorded conditions, rather than a per-step price |
Numerical quotas are intentionally awaiting capacity and cost validation.
Diagnostic
Define the engagement.
A focused examination of one question, the sources available and the people needed. Receive a scope and proposed baseline approach.
Scope a diagnosticFunctional baseline
Establish what is known.
Coverage agreed by operational domains, decision chains, sources, contributors and review responsibilities. Priced after scoping.
Discuss a baselineKnowledge operations
Keep it developing.
Continuing maintenance, governed change and agreed expansion of the established baseline. Commercial terms follow the operating scope.
Discuss continuityProposed scoped engagements, with no implied fixed fee or instant subscription. Delivery cost and workflow must be validated in a pilot.
Different buying decisions.
The same underlying platform.
A researcher chooses capacity to pursue questions. An organization defines the coverage and continuity it needs. The architecture supports the work in both cases.
The shared foundation
Knowledge develops.
Its structure should, too.
Start with the work. Introduce the concepts when they help you understand a difference, preserve an alternative or make a decision.
Machine
A persistent environment in which work and its history develop.
World
A distinct context within which knowledge is constituted and interpreted.
Meta
A way to examine relationships between interpretations and contexts.
Fork
An alternative development that retains its relationship to the original.
Road
A possible, admitted, rejected or travelled transition within the governed development.
State
A recorded condition of the work at a particular point in its evolution.
One object / several ways to inspect it
Choose the view that fits
the question.
Read an interpretation. Inspect its relationships. Follow its development. The object and its context remain the reference as the projection changes.
TextWhat does this mean?
RelationshipsWhat does this depend on?
TimelineHow did this develop?
This demo illustrates three projections. Additional interfaces, including voice and spatial views, belong to the longer-term product direction.
The environment is the continuity.
The interface is a way in.
Machine is intended to keep knowledge useful as AI models and interfaces change. Browser, conversational and future voice access are channels into that environment.
Model independence is a design direction. Specific integrations and export guarantees require release-level verification.
Ownership & governance
Your knowledge.
Explicit boundaries.
Customer ownership of content is central to the intended model. Sensitive knowledge also needs clear rules for contribution, interpretation, access and continued use.
Ownership
Define what belongs to you.
Terms should address contributed content, derived structures and the rights required to operate the service. Customer knowledge should not become a proprietary content resource for the platform.
Sharing
Keep contribution deliberate.
Private work, selected contributions and shared environments need distinct boundaries. A joint discussion should not imply access to a participant’s wider private knowledge.
History
Make provenance inspectable.
Sources, interpretations, review decisions and changes should remain traceable within the agreed scope and retention policy.
Portability
Agree an exit path.
Export formats, retention, deletion, recovery and access after termination should be explicit before relying on the service.
Before real data is entrusted
Principles need operational evidence.
This prototype describes intended principles, not verified contractual or security guarantees.
| Area | To confirm for a deployment or engagement |
|---|---|
| Data processing | Processors, hosting locations, model access and training terms |
| Permissions | Identity checks, roles, private/shared boundaries and revocation |
| Continuity | Backups, recovery, export coverage and deletion procedures |
| Legal terms | Ownership, derived structures, retention and service termination |
Account access
Continue in the service.
Sign in to access your conversation machines and their current views.
Existing service
Open your working environment.
Continue to your private machine catalogue using Google sign-in.
Open your machines ↗First visit
Explore before signing in.
The walkthroughs run entirely in this file, so you can inspect the proposed experience before entering the service.
Explore the examplesThe examples on this page are illustrative. Account access opens the live service; billing is not enabled.
Start a conversation
Give the next step
a useful shape.
Prepare a short enquiry about research capacity, a laboratory pilot or an organizational diagnostic.