North-star principles
The rules above every feature.
These principles govern architecture, model choice, evaluation, public claims, and the Path to Mastery. They apply equally to a quiet conversation and a specialist capability pack.
01Local first, not local only
Deliver meaningful capability without requiring a cloud account, paid API, or permanent internet connection. External help must be explicit, inspectable, and approved; nothing silently leaves the machine.
02The user owns the intelligence
Chats, memories, knowledge, models, skills, projects, data, generated work, preferences, and evaluation history must remain inspectable, portable, editable, and deletable.
03Understand before answering
Resolve the user's real intent, current context, approved memory, relevant evidence, required tools, expected format, and missing information before producing an answer.
04Truth before confidence
Never invent data, citations, memories, actions, current information, tool execution, or model capability. State what is known, inferred, missing, and verifiable.
05Make every model better
Memory, retrieval, planning, tools, validation, and recovery must improve many supported models rather than encode answers for one model, benchmark, or demonstration.
06Respect every model's strengths and limitations
Do not force one model to pretend it can do everything. Qualify models by task, context, reliability, resources, and known limitations, then compose their strengths honestly.
07Use the smallest capable intelligence
Prefer deterministic local operations and efficient qualified models. Larger models or external services must justify their quality, compute, cost, latency, and privacy trade-offs.
08Tools over hallucination
When a task requires calculation, retrieval, code execution, inspection, or validation, trusted tools should produce the evidence and the model should plan and interpret it.
09Personal without becoming intrusive
Learn only through approved and inspectable memory. Current instructions always override memory, and unrelated personal information never enters an answer merely because it was remembered.
10One coherent mind, many capabilities
Conversation, teaching, analysis, coding, writing, and creation should feel like one assistant coordinating typed expert capabilities—not disconnected applications or hidden agents.
11Capabilities are earned through evidence
Code is not mastery. Reliability, privacy, usefulness, recovery, model portability, and consumer-hardware performance must pass explicit gates without weakening difficult tests.
12Meaningful work is the final measure
Optimize for helping ordinary people learn, decide, analyze, build, create, organize knowledge, and save time—not impressive demos, benchmark trivia, or unnecessarily long answers.