“Explain the next action before showing every possibility.”
Connected to: learning · a personal product ideaBRAINOS / CONTEXT & INTELLIGENCE
BrainOSWorking name · Product direction
Your context, useful across life and work.
The context and intelligence layer across LSSM: personal knowledge, company memory and product evidence made useful to each experience. The Company assistance family and the other products and areas connect to this role, while access and sharing stay explicit.
The guides below document existing foundations; this page describes how they can come together into personal and company brain experiences.
CONTEXT YOU CHOOSE TO CARRYOne person.
One person.
Different parts of life.
Move a sample piece of knowledge between contexts. See what travels with it, and what stays private.
PERSONAL CONTEXTA note from a course
A useful idea, in your own context.
Private by default
Private journal and family commitments stay in this context.
A product-direction illustration using synthetic notes. The sharing choice changes this local example only; it never infers consent from a role or interest.
01 / THE CONTEXTSPersonal. Company.
Personal. Company.
Connected to life and work.
A personal brain
Keep a useful view of your goals, commitments, experience and everyday life, shaped around what matters to you.
- Projects, learning and career direction
- Personal administration and financial context
- Health records, routines and wellbeing context
A company brain
Help a team work from shared knowledge, decisions and current operating context, with access that reflects each person’s responsibilities.
- Documents, conversations and organizational memory
- Goals, projects, decisions and commitments
- Relevant context for people and agents
Continuity across your roles
Move between personal projects, professional work, ventures and collaborations with the context you choose to carry into each situation.
- A goal that spans personal and professional life
- A founder working across several ventures
- Selected experience carried into a new project
02 / FROM CONTEXT TO ACTION
From context to a useful next step.
- 01
Connect
Bring in the sources and records that matter to the current person, project or organization.
- 02
Remember
Retain useful knowledge and decisions with their source, scope and history.
- 03
Understand
Retrieve relevant context, surface uncertainty and prepare an answer or a proposed next step.
- 04
Act
Carry that context into an authorized workflow, with the person’s review where it matters.
03 / SHAPE IT TO THE PERSON
Useful connections. Clear boundaries.
Personal and company contexts need their own access rules. Sharing is an explicit choice about the information, purpose and audience, and it needs a way to expire or be withdrawn.
- Personal goals and sensitive life context stay under the person’s authority.
- Shared company context follows the responsibilities and access of the workspace.
- A connection between contexts carries the permitted information and its source.
Prebuilt for the domain
Start with defined behavior, schemas, modules and integration points.
Customizable by the team
Adapt rules, providers, workflows and interfaces to the product.
Personalizable for people
Use roles, preferences and permitted context to shape the experience.
Carry the context you choose, with its boundaries.Explore a situation · 3 ways to look closer＋
A founder is preparing a project discussion. Personal commitments and company knowledge may both be relevant, without becoming one unrestricted pool.
What context should travel?
A CONCRETE SITUATION
Keep the person in control of their context.
A personal commitment affects when the founder can contribute.
What changes
A selected availability constraint could help the project plan.
What stays explicit
The surrounding personal records need not be shared to communicate that constraint.
FOLLOW THE CONSEQUENCE
Choose the information, purpose and audience explicitly. The product direction includes a way for sharing to expire or be withdrawn.
CONTINUE WITH THE DETAIL
Where this explanation comes from
Authored example from the BrainOS scope and sharing boundaries in portfolio-v4.json. BrainOS remains a working-name product direction; linked areas document captured foundations.
04 / THE EXISTING FOUNDATIONSFollow the pieces
Follow the pieces
behind the direction.
Knowledge & retrieval
Source records, evidence, indexing and grounded answers.
Personal workflows
Subject-owned goals, personal knowledge and controlled sharing.
Company & work
Company knowledge, decisions, commitments and operating context.
Agents & context
Context compilation, memory boundaries and agent execution.
Governance & access
Permissions, review decisions and the authority to act.
THE ECOSYSTEM ARCHITECTURE
Distinct roles. One operating architecture.
Contracts, intelligence and shared infrastructure and data come together in LSSM OS. Product experiences keep their own purpose and identity.
LSSM One owning ecosystem · distinct responsibilities
Context & intelligence
BrainOS
Knowledge, memory and intelligence, available within the right context.
Contracts & build
ContractSpec
Define behaviour, build reusable capabilities and verify the work.
Specialized domain & platform specsShared infrastructure & data
Patio
LSSM’s specialized holding for infrastructure, data, transmission and streams. Shared roles across every area.
Infrastructure & data scopeBROUGHT TOGETHER BY
LSSM OS
Composes contracts, intelligence, infrastructure and data. Runs and operates the environments that bring them into use.
RUNTIME & OPERATIONSTarget ecosystem architecture. ContractSpec specializes into domain and platform contracts. The foundation roles come together through LSSM OS; each technical relationship carries its own evidence.
Patio: the specialized infrastructure and data holding within LSSM, with focused product brands. Implementation and availability are recorded per service. Inspect the scope ↗ · Explore the products ↗