Purpose
Deep Well Labs, Inc. exists to explore and build the infrastructure required for durable, trustworthy human knowledge and continuity. Its scope includes Personal Knowledge Infrastructure, frontier research, experimental interfaces, and the investigation of what may become possible as artificial intelligence, cognitive science, neuroscience, and human-computer interaction advance.
Origo is the product through which Deep Well Labs turns a subset of that work into dependable, user-facing Personal Knowledge Infrastructure.
The two must remain related without becoming confused.
Deep Well Labs asks:
What could become possible?
Origo must answer:
What can we honestly, safely, and reliably deliver now?
This charter defines the boundary between those questions.
The boundary does not exist to constrain research. It exists to protect user trust, product truthfulness, Chronicle integrity, human agency, and the long-term credibility of both the company and the product. A research organization that can be believed is worth more than one that impresses.
1. Relationship
Deep Well Labs, Inc. is the company and research organization. Origo is a product of Deep Well Labs.
Deep Well Labs may investigate ideas beyond Origo's current roadmap, including speculative or pre-product concepts. Origo may adopt research produced by Deep Well Labs only after the capability is sufficiently understood, bounded, tested, and aligned with Origo's trust commitments.
Research does not become product merely because it is compelling.
2. Research boundary
The Deep Well Labs research environment may explore, prototype, simulate, and visualize frontier concepts such as:
- the formation and evolution of human thoughts;
- relationships among observations, memories, concepts, and interpretations;
- competing or changing interpretations over time;
- cognitive and knowledge representations;
- future forms of human-AI interaction;
- hypothetical inference, continuity, and context systems;
- interfaces that demonstrate the art of the possible before the underlying capability exists.
The research environment should be free to ask ambitious questions, but it must remain explicit about what is real and what is exploratory.
3. Product boundary
Origo represents only capabilities that are implemented and supported to the standard appropriate for the product's current maturity.
Origo must preserve:
- human ownership and agency;
- Chronicle as the canonical record of intentionally preserved human source material;
- clear separation between source, transcription, interpretation, correction, and other derivatives;
- explicit consent where consequential or durable actions occur;
- privacy and workspace isolation;
- provider and model independence where practical;
- provenance sufficient to understand how durable machine-generated material was produced;
- truthful representation of product capability and limitation.
Research language must not cause Origo to imply that it can observe, infer, know, remember, or understand something that its implemented systems do not actually support.
4. Reality classification
Deep Well Labs demonstrations and research artifacts must distinguish among these states:
- EXISTS: implemented and currently usable as represented;
- PROTOTYPE: partially implemented and demonstrable, but not production-ready;
- SIMULATION: intentionally visualized or generated to demonstrate a possible experience without performing the represented capability;
- FRONTIER: scientifically or technically plausible enough to investigate but requiring substantial research or engineering;
- SPECULATIVE: useful for imagination or inquiry but not presently established as feasible.
The classification must be disclosed wherever the capability is shown: in the interface, the detail view, the export, the recording, the slide, and the spoken description. The governing test is not whether the classification was recorded somewhere, but whether a reasonable observer encountering the demonstration without prior context could mistake it for implemented Origo behavior. If they could, the labeling is insufficient regardless of what the accompanying documentation says.
A simulation may be beautiful and persuasive. It must never be presented as an observation, measured capability, or implemented result.
5. Data governance
The research environment and Origo production environment must remain separate trust domains.
By default:
- production Chronicle data does not enter experimental research systems;
- experimental systems do not receive production credentials or unrestricted production access;
- simulated or speculative outputs do not write back to canonical Chronicle;
- research-derived interpretations are not silently promoted into human source records;
- synthetic or explicitly authorized data should be preferred for demonstrations and experiments;
- any transfer of user data into research requires an explicit purpose, appropriate consent, minimum necessary scope, and a defined retention boundary.
Where research uses a real human observation as an input, the observation and everything derived from it must remain distinguishable.
6. Promotion into Origo
A research capability may graduate into Origo only when the relevant evidence exists to answer, at minimum:
- Capability: Does the system actually perform the represented function?
- Evidence: Has the capability been tested against meaningful cases rather than demonstrated selectively?
- Provenance: Can Origo explain what was observed, what was inferred, and how the result was produced?
- Human agency: Are consequential actions appropriately reviewable, correctable, reversible, or consented to?
- Privacy and security: Are data access, retention, permissions, and failure modes understood and bounded?
- Reliability: Are uncertainty and known limitations represented honestly?
- Architecture: Can the capability enter Origo without weakening Chronicle, ownership, provider independence, or established trust boundaries?
- Product value: Does the capability help a person preserve, understand, or build upon their own thinking rather than merely demonstrate technical novelty?
Graduation should normally be recorded through the appropriate product specification and, when the decision is significant or difficult to reverse, an Architecture Decision Record.
7. Decision rule
When research ambition and product trust are in tension, protect product trust.
Deep Well Labs may continue exploring the idea outside the production boundary. Origo should wait until it can represent the capability truthfully and operate it responsibly.
This restraint does not weaken the research mission. It makes ambitious research possible without requiring the product to pretend the future has already arrived.
Distinctions this charter preserves
Each step below is a real transition that must be earned, not an equivalence that may be assumed. Collapsing any one of them is how a research organization loses the right to be believed.
human observation ≠ AI inference
AI inference ≠ verified fact
prototype ≠ product
simulation ≠ capability
research hypothesis ≠ architecture decision
architecture decision ≠ implementation
implementation ≠ validated production behavior
Language is where these distinctions usually fail first. "Origo understands," "Origo knows," and "Origo remembers" describe the top of the ladder; if the underlying system sits lower, the sentence is untrue regardless of intent.