A Large Social Systems Model is a way to think about goals, people, institutions and technology together, including how they respond to the consequences of their actions.
EXPLORE THE IDEA
What changes when you look at the relationships?
Imagine a person learning a new skill, a team trying to deliver useful work and a community creating opportunities. Each can improve locally; the relationships determine what becomes possible together.
LIFE & SYSTEMSA person
○A person◇A group□A system
Trace a relationship. Examine a decision.
UNDERSTAND THE RELATIONSHIP
A person
Begin with attention, capability and the choices a person can actually make.
IN A CONCRETE SITUATIONA learning tool is useful when it helps someone take a next step in their own circumstances.
An organization does not improve simply because one component becomes more capable. Outcomes also depend on who can decide, how people coordinate, what information they can use and how they learn from results. The model asks us to make those relationships explicit, so a technical change can be understood in the social system it enters.
↳Follow the relationship, not only the tool.Trace the mechanism · 3 ways to look closer＋
Imagine a person learning a skill, a team doing useful work and a community creating opportunities. A local improvement depends on the connections around it.
Which relationship are you examining?
A CONCRETE SITUATION
Capability needs a useful place to go.
A person learns something new but cannot see how it connects to a next step.
01 / Capability
What can the person now do or understand?
What changes
Relevant context and understandable opportunities can make the learning actionable.
What stays explicit
More information alone does not guarantee access, readiness or a good fit.
FOLLOW THE CONSEQUENCE
Ask whose goal is served, which next choice becomes easier and what conditions still block it.
Hypothetical relationships from the World model and company purpose. These questions explore a thesis rather than asserting an observed social outcome.
02
Connect intention with observation
A goal expresses a desired direction. Contracts make parts of that intention specific enough to implement. Observation shows what actually happened, including unexpected effects and unmet expectations. Learning then proposes a change. These links provide a useful design framework; they do not make a complex social outcome fully predictable or reducible to a single score.
03
Keep the thesis open to evidence
LSSM is a worldview and system-design approach, not a claim that every proposed capability is already deployed. Read the Manifesto for its values and the evidence approach for how claims should be assessed. [ContractSpec](/) and LSSM OS are practical places to examine how parts of this thinking are being translated into software.
◉How much does this piece of support establish?Examine the support · 3 ways to look closer＋
Consider the claim: “This workflow reduces repeated work in a weekly update.” Different evidence answers different parts of that claim.
What do you have in hand?
A CLAIM TO EXAMINE
You have a direction to examine.
The intended benefit is described for a recognizable person and recurring task.
MATCH THE CONCLUSION TO ITS SUPPORTYou have: A direction
01A directionWhat might help
02An artifactWhat was implemented
03An observationWhat happened in context
THE QUESTION IT CAN ADDRESS
Could this reduce repeated work in a weekly update?
Make the proposed workflow inspectable.
KEEP WITH THIS SUPPORT
The person and recurring task
What should become easier
What would count against the idea
An illustrative evidence map, with no measured time-saving result claimed.
Inspect the claim’s limits＋
What it supports
The claim can guide what to build and what to observe.
What it leaves open
It does not show that an implementation exists or that the benefit occurred.
WHAT WOULD HELP YOU DECIDE
Name the repeated work and the conditions that would make the improvement recognizable. Ask what would weaken the claim.
Proposed page for lssm.world, based on the existing source narrative at bcc79fcc. Source describes intent and scope; it does not independently qualify a deployed feature.