Three shared foundations. One connected ecosystem.
ContractSpec powers the ecosystem, LSSM OS provides its infrastructure, and BrainOS brings context and intelligence. Follow these roles across the products, audiences and work they support.
Composes contracts, intelligence, infrastructure and data. Runs and operates the environments that bring them into use.
RUNTIME & OPERATIONS
Target 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 ↗
EXPLORE THE IDEA
How do the shared roles come together?
BrainOS brings context and intelligence, ContractSpec defines and builds, and Patio supplies shared infrastructure and data. LSSM OS composes these inputs, then runs and operates their environments. This is the target architecture; product pages record the inspected implementations.
MEANING & CONTEXTContractSpec
○ContractSpec◇LSSM OS□BrainOS
Select a part. See how it connects.
UNDERSTAND THE RELATIONSHIP
ContractSpec
Define shared behaviour through specifications and reusable capabilities across the ecosystem.
IN A CONCRETE SITUATIONFollow a product capability to its contracts, component source and implementation boundary.
ContractSpec: specifications and reusable capabilities
[ContractSpec](/) powers the ecosystem through explicit product behaviour, typed specifications and reusable capabilities. A career experience, a company assistant and a product workspace can share these foundations while keeping their own interface and audience. Explore the domain pieces, then follow the Documentation and Examples for a specific implementation.
↳A reusable piece comes with a set of relationships.Trace the mechanism · 3 ways to look closer＋
A communication capability might need an operation, a provider port and a policy binding. Explore what happens when one piece is missing.
What is ready in the composition?
A CONCRETE SITUATION
You can inspect the promise before enabling an effect.
The capability is described, but no active installation or provider has been selected.
01 / Declare
Name the operations, capabilities and required ports.
What changes
The product can discover the capability and its requirements.
What stays explicit
A declaration alone does not send a message or initialize a provider.
FOLLOW THE CONSEQUENCE
Use the dependency map to choose what to bind. Do not treat catalogue presence as runtime readiness.
LSSM OS is the infrastructure layer beneath the ecosystem’s products, capabilities and experiences. Its responsibilities include the operating environment, integrations and the connection between intended work and runtime conditions. Explore its infrastructure relationships and deployment guidance.
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.
Product decisions and delivery have their own place
ContractSpec Studio connects product signals, briefs, priorities, issues and approved handoffs. It belongs to Product & delivery, with product owners and managers as explicit audiences. The current name is retained while a rename is considered. Its repository provides existing source for revival; the inspected PM feature is experimental.
Source & scope
Website direction updated with founder-confirmed ecosystem roles and the shared portfolio taxonomy. The original ContractSpec narrative and the separate Studio source are linked below. ContractSpec Studio has existing source with revival requested; its inspected PM feature is experimental. These relationships do not by themselves qualify a deployed integration.