Sanespace Team Onboarding Handbook

1. The person - Identify who SaneSpace is helping and what part of their life they are trying to handle. This keeps the work grounded in real needs rather than isolated features. 2. The space - Identify the personal context involved: life, school, work, relationships, decisions, creativity, growth, everyday questions, reflection, or emotional support. This matters because the same request can mean different things in different settings. 3. The companion - Identify how SaneSpace should help. SaneSpace combines AI conversation with memory, context, personality, and personalization so the experience can grow with the person instead of resetting at every exchange. 4. The next contribution - Identify the specific action your work should enable. A design review, research note, code change, test, content revision, or product decision should make the next step clearer.

The North Star starts with the person, not the task list. For example, “improve onboarding” is too broad to guide good work. “Help a new user understand what SaneSpace remembers and give them control over that memory” gives the team a clearer product question. It also explains why the work matters: trust depends on people understanding how their personal context is used.

SaneSpace is an AI life companion that grows with you. It is a personal space for the parts of life that do not fit neatly into separate apps. Someone might use it to think through a difficult decision, prepare for a work conversation, explore a creative idea, reflect on a relationship, ask an everyday question, or get emotional support. The product should recognize that these moments connect. A person is not a different person simply because the topic changed from school to work or from planning to reflection.

That continuity requires care. Memory means the product may retain useful information across conversations. Context means it should understand what a person is discussing now and how that relates to their situation. Personality and personalization mean the experience can feel more natural and relevant without forcing everyone into the same style. These ideas do not give us permission to guess, stereotype, or overreach. SaneSpace should understand different cultural, linguistic, social, and everyday contexts without reducing people to assumptions.

Use the North Star as a quick test: Does this work help SaneSpace understand or support a person more clearly, safely, and respectfully? If the answer is unclear, pause and ask what user need the work serves.

Applying the North Star on Your First Task

Suppose your first assignment involves reviewing a proposed SaneSpace conversation flow. The flow asks a user what they need help with and then guides them toward a useful starting point. Do not begin by checking only whether each screen looks complete. Apply the North Star in order.

1. Read the product context first. Review the current product brief, the task description, and any linked design or technical notes. Spend about 20 minutes identifying the user need, the current product stage, and the decision the team needs to make. The expected outcome is a short list of facts, not a long summary. 2. Write the person and space in one sentence. For example: “This flow helps a person who has an unclear everyday question decide whether to reflect, plan, or ask for direct help.” The expected outcome is a clear user situation that the team can discuss. 3. Check the companion behavior. Look for memory, context, personality, and personalization. Ask what SaneSpace knows, what it does not know, and what it should ask before responding. The expected outcome is a list of assumptions that need confirmation. 4. Check respect and control. Look for language that treats the person as an individual rather than assigning a cultural, social, emotional, or professional label. Confirm that the user can correct, clarify, or change the direction of the conversation. The expected outcome is a set of specific wording or interaction changes. 5. Name your contribution. State what you will deliver, such as “I will mark unclear prompts, suggest two alternatives, and list the decisions the product team must make.” The expected outcome is a review that others can act on. 6. Share the result in the team’s working space. Link the source material, describe what you checked, and separate observations from open questions. This helps teammates review your thinking without reconstructing your process.

A practical review might find that a prompt says, “Tell me your goal so I can help you succeed.” That wording sounds useful, but it may push a person toward a task before they have explained what is happening. A person may need to vent, sort through feelings, or describe a situation before naming a goal. A stronger alternative could offer several entry points: “What would help right now - thinking something through, making a plan, asking a question, or simply putting your thoughts into words?” The change supports the product principle because it gives the person room to choose the kind of help they need.

Quick checklist

• Read the current brief before producing work. - Name the person and the life context involved. - Check how memory, context, personality, or personalization affect the experience. - Look for assumptions about culture, language, relationships, work, or emotions. - State the concrete output you will provide. - Link your source material and list open questions. - Confirm how your work supports the current priority.

If you can complete this checklist, you have moved from “I received a task” to “I understand why this task exists.” That difference helps the team make consistent decisions while the product is still taking shape.

Common Orientation Mistakes

Starting with a feature instead of a person

A teammate may describe SaneSpace as “a chatbot with memory” and then evaluate every idea through that lens. The description misses the wider purpose: SaneSpace is a personal space for life, school, work, relationships, decisions, creativity, growth, everyday questions, reflection, and emotional support. Memory supports that purpose; it does not define the whole product.

Do this: Describe the user situation first, then explain the feature that helps.

Not this: “We need a memory feature because competitors have one.”

Ask instead: “What continuity would help this person feel understood, and what control do they need over it?” That question keeps memory connected to trust and usefulness.

Treating the handbook as a complete product specification

This document gives orientation, not every implementation detail. A new teammate may read a principle such as “Person before task” and assume it answers every product question. It does not. The team still needs current requirements, technical constraints, design decisions, safety guidance, and feedback from the people using the product.

Do this: Use the handbook to understand direction, then check the linked source of truth for the task you own.

Not this: Make a large product decision from a general statement without confirming the current priority.

When the handbook and a current task brief appear to differ, do not silently choose one. Point out the difference and ask the responsible teammate to clarify it. The goal is not to defend a document; the goal is to keep the team working from the same understanding.

Confusing personalization with guessing

Personalization should make SaneSpace more relevant, not more presumptuous. A response can become less helpful when it assumes a person’s culture, family structure, language preference, emotional state, or goals from limited information.

Do this: Use what the person has shared, state uncertainty when it matters, and offer a way to correct the context.

Not this: Fill in missing details because they seem likely.

For example, if someone asks for help with a family decision, do not assume who is involved or what role each person has. Ask a focused question or provide options that work across several situations. Respectful understanding grows through clear conversation, not confident guessing.

The Orientation North Star gives you a reliable starting point: begin with the person, locate the life context, understand the companion behavior, and define your contribution. Carry that sequence into the pages that follow, the tools you use, and the conversations you have with the team. SaneSpace becomes clearer when every teammate can connect a daily task to the personal space we are building.

End of chapter one. 4 more chapters in the full book.