Start with ContractSpec.
Contracts make behavior explicit. Runtime components, interfaces, agents, integrations and authoring tools turn those definitions into useful building blocks.
Adopt one operation in an existing application, then compose the additional capabilities your product needs.
Explore the building blocks →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.
You can inspect the promise before enabling an effect.
The capability is described, but no active installation or provider has been selected.
Name the operations, capabilities and required ports.
The product can discover the capability and its requirements.
A declaration alone does not send a message or initialize a provider.
Use the dependency map to choose what to bind. Do not treat catalogue presence as runtime readiness.
Where this explanation comes from
An authored situation, grounded in the linked source guides. Choosing a case explores its expected responsibilities; it does not execute an operation.
The names describe capabilities inside the system.
Connect, RoleMorph and Feature Hubs deepen the common model. They are not a sequence of mandatory products to buy.
| Capacité | Job | What remains explicit |
|---|---|---|
| Relier | Review scope and decisions; verify configured authority | Host policy, persistence and real effects |
| RoleMorph | Resolve a useful surface for an actor and context | Backend authorization and supported components |
| Feature Hubs | Compose related capabilities and interfaces | Ports, dependencies, readiness and effects |
| Créateur | Support authoring and inspection | Current write/apply maturity and release scope |
Use the integrated product: LSSM OS.
LSSM OS is the integrated operating environment built from the ecosystem’s pieces. Its website should explain workflows, roles and deployment choices to the people using and operating the product.
Developer reference belongs here in ContractSpec. Product procedures belong with LSSM OS and should match the capabilities available in a selected deployment.
Explore the LSSM OS direction →Find the right part of the ecosystem.
Each site has a distinct job and a useful next step. Shared technical details have a canonical owner.
| Destination | Objectif | Explorer |
|---|---|---|
| lssm.co | Company, portfolio and working together | Company direction |
| lssm.tech | Architecture, projects and source | Technical ecosystem |
| contractspec.io | Specifications and reusable blocks | Documentation |
| os.lssm.tech | The integrated LSSM OS product | Product direction |
| lssm.world | Thesis, principles and evidence | Worldview direction |
Inspect a specific composition in CompanyOS.
CompanyOS is a distinct source component and architecture case within this ecosystem. Its workflows can illustrate how capabilities compose; it does not stand for the whole LSSM OS product.
The case study explains source evidence and its limits, including what requires a real configured environment.
Read the CompanyOS architecture case →Keep the answers connected to their source.
The proposed DocSpec evolution connects technical reference, examples and product guidance through one versioned documentation graph. Humans receive useful pages; agents receive precise, applicable context.
Give an agent a coherent slice of the system.Trace the mechanism · 3 ways to look closer＋
An agent is asked to change one operation. A useful context packet keeps the task, source identity and execution responsibilities together.
Start with orientation and a bounded reference.
The task names a capability but not the package that owns it.
Read the relevant area and task context.
An area overview and package overview narrow the source set.
A package listing does not establish registry availability or permission to edit it.
Choose the relevant package and source identity, then follow the exact manual or structured source data.
Where this explanation comes from
An authored situation, grounded in the linked source guides. Choosing a case explores its expected responsibilities; it does not execute an operation.