How Entee Works

This page is the technical and philosophical spec for Entee. It is written for people who already want to understand how the product is designed, what assumptions it makes, and where the current boundaries are.

What Entee Is

This section will describe what Entee is in plain language.

The Memory Architecture

This section will explain how Entee's memory works technically.

Private memory

This subsection will explain how private memory works - what is stored, where it lives, and how long it is kept.

Public room memory

This subsection will explain how public room memory works - what is recorded, how it is anonymised, and how it can be used.

Privacy Architecture

This section will explain the current privacy model in practical terms and document where guarantees begin and end.

This item will describe what information is stored when you use Entee.
This item will describe where that information is stored and what systems are involved.
This item will describe which obligations apply under the Australian Privacy Act.
This item will describe who can access data and under what controls.
This item will describe what deletion means in practice and the steps a person takes to request it.

The Three Rules

These rules are permanent and non-negotiable. This section will later define how each rule is enforced in product behavior.

Entee never claims authority she does not have This paragraph will describe what it means for Entee to never claim authority she does not have. This paragraph will describe the kinds of language boundaries and confidence signals this rule requires.

Entee never judges a person This paragraph will describe what it means for Entee to never judge a person. This paragraph will describe how the team intends to keep responses practical without becoming moralistic.

Collective intelligence is always transparent about its origins This paragraph will describe what transparency means when knowledge comes from a public room. This paragraph will describe how origin and attribution cues are shown so users can tell private from collective context.

What Entee Is Not

This section will define the product boundaries clearly so people understand what Entee is built for and what it is not built to replace.

Not a search engine
Not a productivity tool
Not a therapist
Not a judge
Not a replacement for human relationships

Who Built Entee

RACMUP PTY LTD - Perth, Western Australia

This section will explain what RACMUP stands for and why those principles shaped the product decisions.

The founding question is: "Why should an AI that knows your private thoughts live on someone else's infrastructure?" This section will expand on how that question shaped Entee's design.

This section will also reference existing RACMUP and founding-question copy already published on the current homepage and about content.

Open Questions

This section lists unresolved questions the team is still working through. The items below are placeholders.

Placeholder: how to explain memory in a way that is technically accurate and still easy to understand.
Placeholder: how much implementation detail to publish without making the page too dense for non-technical readers.
Placeholder: how to document trade-offs between privacy guarantees, performance, and user experience.

Version Log

This log records changes to the spec over time.

Date	What changed	Why
27 April 2026	Spec page created	Content to follow