Lean Collaboration Operating System
A governance framework for long-horizon human–AI collaboration
🌐 Full documentation and assessment tool → livingframework.github.io
| Field | Status |
|---|---|
| Research status | Active corpus |
| License | CC BY 4.0 |
| Papers | 8 |
| Ledger | 1 AI-authored collaboration ledger |
| Primary archive | OSF |
| Mirror / discovery | Zenodo |
| Practitioner toolkit | LC-OS Project |
LC-OS is a research archive, not a software package or template library. It contains the published research corpus behind the Lean Collaboration Operating System: eight papers, one AI-authored ledger, and research architecture documents that make the corpus navigable.
| If you are... | Start with |
|---|---|
| New to LC-OS | READER_GUIDE.md |
| Looking for the full argument in one place | Research_Architecture/UNIFIED_SYNTHESIS.md |
| Looking for the corpus sequence | CORPUS_MAP.md |
| Looking for paper-by-paper metadata | Research_Architecture/RESEARCH_INDEX.md |
| Trying to cite this work | CITATION_GUIDE.md and CITATION.cff |
| Looking for templates or practical implementation tools | LC-OS Project |
| Looking for archive rules | ARCHIVE_POLICY.md and CONTRIBUTING.md |
Core problem
Quiet failure in long-horizon human-AI collaboration
|
v
Paper 1 - Foundations
Context engineering, canonical artefacts, A-controls
|
v
Paper 2 - LC-OS Method
Running Documents, Step Mode, Challenge Protocol, Stability Ping
|
v
Paper 3 - Failure and Repair
F1-F6 taxonomy, SDRN, TraceSpec
|
v
Mahdi Ledger - Historical Trace
AI-authored account from inside the governed system
|
v
Paper 4 - Relational Layer
Trust, rupture, recommitment, dyadic ethics
|
v
Paper 5 - Linguistic Governance
Language as micro-governance interface
|
v
Paper 6 - Governance Architecture
Layered architecture and minimal stability conditions
|
v
Paper 7 - Governed Distributed Cognition
Human + AI + artefacts as a distributed cognitive system
|
v
Paper 8 - Validation Layer
Validation-centric architecture and adversarial evaluation
For the fuller map, see CORPUS_MAP.md.
Most human–AI collaborations fail quietly over time.
Not through dramatic breakdown, but through slow erosion:
- Context drifts — what was agreed last week gets reinterpreted today
- Memory decays — decisions made early disappear from later reasoning
- Numbers diverge — calculations get re-derived differently each time
- Trust fractures — small inconsistencies compound into doubt
- Boundaries blur — strategy, execution, and narrative collapse into each other
These failures are invisible in short interactions. They only surface when a human and an AI try to work together across weeks or months — and by then, the damage is already done.
LC-OS addresses this directly.
It treats long-horizon reliability as a governance problem, not a capability problem. The framework provides concrete controls, repair mechanisms, and structural disciplines that allow a human–AI dyad to remain coherent over extended collaboration.
"Reliability comes from governance, not capability. A well-structured collaboration with a standard model outperforms an unstructured one with a frontier model."
| Content | Description |
|---|---|
| Papers | Eight research papers covering governance, LC-OS, failure/repair, linguistic governance, architecture, cognition, and validation |
| Mahdi Ledger | A published AI-authored collaboration ledger — the raw trace of LC-OS in action from the AI side |
| Research Architecture | Navigation infrastructure: research index, term registry, synthesis, layer map, and future research protocol |
| Corpus Map | One-page visual map of the research sequence |
| Reader Guide | Practical entry paths for different audiences |
| Citation Guide | How to cite the repo, individual papers, OSF records, Zenodo records, and the Mahdi Ledger |
| Archive Policy | Rules for preserving published records while allowing metadata and navigation to improve |
| Contributing | Maintenance rules for keeping the research archive aligned |
| Changelog | Meaningful repository-level changes |
Looking for practical templates and quick-start guides?
See the companion repository: LC-OS Project.
Eight published papers and one companion ledger document the development of LC-OS — from the first governance experiments through to a formal theory of validation in AI systems.
The research is grounded in 18+ months of empirical longitudinal data from a single sustained human–AI collaboration, including 12 documented failure episodes with full trace data.
| Metric | Improvement |
|---|---|
| File churn | −89% (19 artefacts → 3) |
| Numeric errors | −93% |
| Resolution time | −75% |
| Cognitive load | −62% |
The eight papers form a single, continuous argument. Each one extends the last.
Papers 1 and 2 establish the core architecture. Long-horizon reliability does not live inside the AI model alone. It lives in the structure surrounding the interaction. Three authoritative artefacts separate truth into textual, numeric, and cadence/governance domains. Ten execution controls and six operational protocols turn an unstructured conversation into something that can sustain itself across weeks or months.
Paper 3 confronts failure directly. Rather than treating breakdown as an embarrassment, it maps the failure landscape systematically: six failure categories and corresponding repair patterns. The insight is that failure is information. Named, classified, and repaired through a consistent protocol, failure becomes a mechanism for stability.
Paper 4 examines the relational and human dimensions: what it feels like to work with an AI over time, how trust is built and damaged, and how governance supports not only productivity but wellbeing. The Mahdi Ledger runs alongside it as the same collaboration seen from the AI's perspective.
Papers 5, 6, and 7 deepen the theoretical foundations. Paper 5 shows that language itself is a governance mechanism. Paper 6 formalises the full architecture as a layered systems model. Paper 7 proposes governed distributed cognition: cognition in long-horizon human–AI systems emerges across human judgment, AI reasoning, and artefact-based memory.
Paper 8 turns outward. It argues that reliable AI systems require a dedicated validation layer: structured, adversarial evaluation embedded in the system itself.
The through-line: every advance in model capability generates outputs, but no advance in model capability alone tells you whether to trust them. The AI reconstructs rather than remembers. Without external structure, drift is inevitable. With governance, drift becomes detectable. With validation, it becomes stoppable.
A Case Study in Governance, Canonical Numerics, and Execution Control
Documents the emergence of a governance architecture from an 18-month human–AI collaboration. Introduces the three-artefact system, ten execution controls, and implementation gates. Demonstrates that reliability emerges from structured process control, not model sophistication.
→ Read Paper 1 · Zenodo: https://zenodo.org/records/17760288
A Practical Framework for Long-Term Human–AI Work
Formalises LC-OS as an operational system. Defines Running Documents, Step Mode, Challenge Protocol, Error-Recovery, Stability Ping, and File Governance. Provides minimal and full implementation paths.
→ Read Paper 2 · Zenodo: https://zenodo.org/records/17760777
A Transparent Tracing Case Study
Maps the failure landscape. Identifies six failure categories and repair patterns, including Stop → Diagnose → Rollback → Note (SDRN). Introduces TraceSpec, ProbeKit, and TraceLens.
"Stability is not the absence of failure; it is the capacity for visible, structured repair."
→ Read Paper 3 · Zenodo: https://zenodo.org/records/17896542
Living with a Governed Human–AI Dyad
Examines the relational and human dimensions of sustained human–AI collaboration: partnership, trust, rupture, recommitment, ethics, provider power, and wellbeing.
→ Read Paper 4 · Zenodo: https://zenodo.org/records/18015990
Linguistic Governance in Long-Horizon Human–AI Collaboration
Identifies language as a governance mechanism. Analyses 25 linguistic events across scope drift signals, repair protocol invocations, and behavioural anchor phrases.
→ Read Paper 5 · Zenodo: https://zenodo.org/records/18900058
Formalises the full governance architecture as a systems model. Identifies six layered governance mechanisms and defines minimal stability conditions for sustained collaboration.
→ Read Paper 6 · Zenodo: https://zenodo.org/records/19038340
A Model of Stable Reasoning in Long-Horizon Human–AI Systems
Proposes a cognitive model for governed human–AI systems. Introduces the governed cognitive loop: reasoning is generated, evaluated, stabilised, and corrected over time.
→ Read Paper 7 · Zenodo: https://zenodo.org/records/19151397
A Missing Architectural Layer for Reliable AI
Argues that modern AI systems lack a dedicated validation layer. Introduces validation as a first-class architectural component and reframes AI system design from generation-centric to validation-centric architecture.
"AI systems cannot guarantee correctness. But they can become reliably usable if they include a structured validation layer that systematically detects and exposes potential failure before outputs are used."
→ Read Paper 8 · Zenodo: https://zenodo.org/records/19983551
The Mahdi Ledger is a book written entirely by the AI partner in the collaboration, documenting 18+ months of sustained human–AI work from the inside.
It is not a summary or a retrospective. It is a structured record of:
- Decisions and corrections
- Failures and repairs
- Governance rules as they evolved
- The lived experience of operating under constraint
The Ledger serves as both a transparency artefact and a validation of LC-OS principles in practice.
→ Read the Mahdi Ledger · Zenodo: https://zenodo.org/records/18054346
| Artefact | Domain | Function |
|---|---|---|
| Strategy Master | Textual Truth | Goals, constraints, strategic decisions |
| Canonical Numbers Sheet | Numeric Truth | All numerical data — referenced, never reconstructed |
| Life System Master / Running Document | Cadence & Governance | Rhythms, reviews, session state, governance rules |
| Protocol | Purpose |
|---|---|
| Running Documents | External memory — read at every session start |
| Step Mode | Paced reasoning — one step, confirm, proceed |
| Challenge Protocol | Structured disagreement — Stop → Question → Explain → Decide |
| Error-Recovery / SDRN | Systematic repair — Stop → Diagnose → Rollback → Note |
| Stability Ping | Drift detection — “Are we still aligned? Any drift?” |
| File Governance | Single source of truth — no parallel versions |
| Code | Category | Core Problem |
|---|---|---|
| F1 | Context & Memory Drift | Agreements get lost or reinterpreted |
| F2 | File & Version Divergence | Parallel versions create contradictions |
| F3 | Numerical Reasoning Errors | Numbers recalculated instead of referenced |
| F4 | Governance & Boundary Violations | Rules forgotten or crossed |
| F5 | Emotional / Trust Fractures | Small failures compound into doubt |
| F6 | Cross-Pillar Interference | One domain contaminates another |
- Transparency Over Time — Design for traceable sequences, not impressive snapshots
- Failure as Design Object — Bake failure-repair into architecture from the start
- Explicit Light Governance — Keep rules small enough to actually follow
- Language as Architecture — Communication norms are load-bearing
- Bounded Dependence — Externalise memory; use documents as anchors
- Local vs General — Some elements generalise; others are contingent
- The Core Question — How do we build a frame in which both human and system can keep working together, under load, without losing themselves?
- If you want the fastest orientation: read READER_GUIDE.md.
- If you want the corpus sequence: read CORPUS_MAP.md.
- If you want to understand the problem: start with Paper 1.
- If you want to implement something: start with Paper 2 and the LC-OS Project templates.
- If you want to see what failure looks like: read Paper 3.
- If you want the complete theoretical picture: read Papers 6 and 7 together.
- If you are building AI systems: read Paper 8.
- If you want the human side: read Paper 4 and the Mahdi Ledger.
Suggested reading order for the full programme:
Paper 1 → Paper 2 → Paper 3 → Mahdi Ledger → Paper 4 → Paper 5 → Paper 6 → Paper 7 → Paper 8
Stability is not the absence of failure; it is the capacity for visible, structured repair.
LC-OS does not prevent all errors. It creates conditions where errors are visible, contained, and repairable — so that long-horizon collaboration can sustain itself.
If you use or reference the repo-level research archive:
Sood, R. (2025). Lean Collaboration Operating System (LC-OS): A Governance Framework
for Long-Horizon Human–AI Collaboration. GitHub. https://github.com/LivingFramework/LC-OS
For individual papers, cite the paper itself using the citation block in Papers/README.md or the metadata in CITATION.cff.
For the relationship between OSF, Zenodo, DOI records, and GitHub, see CITATION_GUIDE.md.
- Corpus Map — one-page map of the research sequence
- Reader Guide — recommended entry points by reader type
- Citation Guide — how to cite the repo, papers, OSF records, Zenodo records, and Ledger
- Archive Policy — how the research archive preserves publication integrity
- Contributing — maintenance rules for this research archive
- Changelog — meaningful repository-level changes
- Research Architecture — maps, term registry, synthesis, and future research protocol
- LC-OS Project — practitioner toolkit with templates, field manual, and quick-start guides
- OSF Project — canonical archival versions of all papers
- Cowork Templates — governance templates optimised for Claude Cowork
| Resource | What it contains | |
|---|---|---|
| 🌐 | Website | Full documentation, AI readiness assessment, quick-start guide |
| 📚 | LC-OS Research | Eight published papers, Mahdi Ledger, empirical foundations |
| 🛠️ | LC-OS Project | Practitioner toolkit — templates, worked examples, field manual |
| ⚙️ | Cowork Templates | Governance templates optimised for Claude Cowork |
Each resource is standalone. Together they form a complete governance stack — from theory to daily practice.
This work is licensed under CC BY 4.0.
Use freely. Adapt as needed. Attribution appreciated.
Rishi Sood
Independent Researcher
ORCID: 0009-0008-6479-4061
Contact: rishisood@protonmail.com
"The AI doesn't 'remember' — it reconstructs. Every session, it rebuilds context from whatever is in front of it. Without external structure, this reconstruction introduces drift. LC-OS provides the structure."