SOURCE REPOSITORY // OPEN SPECIFICATION
The specification layer of the Dream Machine OS, public on GitHub: twelve modules, patches with their evidence tier, the glossary, the audit logs and the errata. Printed in the book as dreammachine.systems/source. The URL never changes.
The book is the implementation. The repository is the specification.
>_ Open vs. closed
OPEN · CC BY-NC-SA 4.0 · GITHUB
- Modules 01–12 · the specification of every chapter (
modules/) - Glossary and error codes (
glossary/) - Patches with their evidence tier (
patches/) - Audit logs (
audit/) and RFCs (rfcs/) - Errata · every confirmed fix, with its build
CLOSED · © DREAM MACHINE SYSTEMS FLEXCO
- The manuscript · the prose of the book (CC BY-NC-ND 4.0, no derivatives)
- The audiobook (CC BY-NC-ND 4.0, no derivatives)
- The Human Debug Deck · the card texts
- The Deployment Masterclass
>_ Report a bug · with or without Git
NO GIT ACCOUNT?
USE THE FEEDBACK COMPILER
The same report, no account. Pick the edition (eBook, audiobook, print or the open specification), name the place, describe the bug. Every report is checked against the manuscript and the spec.
./feedback
[ QUICK FIX ]One error, about a minute: where it is, what is wrong, how to fix it.
[ DEEP REVIEW ]Logic gaps, sources, tone, safety, in your own words.
GITHUB · ISSUE
ERRATA
A wrong number, a typo, a broken reference in a module or patch. The same categories as the Feedback Compiler; one place, one fix.
issues/new?template=errata.yml
GITHUB · ISSUE
EVIDENCE
A source that does not say what the spec claims, a logic gap, a tier that is too high. Quote the paper, name the module.
issues/new?template=evidence.yml
GITHUB · ISSUE
RFC
A change to the model or a new patch. State the problem, the proposal and what it would break; the RFC is discussed before anything is merged.
issues/new?template=rfc.yml
GITHUB · PULL REQUEST
PULL REQUEST
A fix you already wrote. Read CONTRIBUTING.md first. Sign the CLA once: on your first pull request, a bot asks you to post one sentence as a comment (CLA.md).
| CONCERN | WITHOUT A GIT ACCOUNT | WITH GITHUB |
|---|---|---|
| Error in the text (Quick Fix) | /feedback · Quick Fix | Errata issue |
| Logic gap, source, tone (Deep Review) | /feedback · Deep Review | Evidence issue or pull request |
| Change to the model, new patch | /feedback · Deep Review, “Other” | RFC issue |
| Safety concern | ONLY /feedback (private) | never public |
| Personal experience | ONLY /telemetry | never public |
// CREDIT: both routes land in the changelog. The form by opt-in (name me if fixed), GitHub by the merged pull request and the CLA.
// Every accepted contribution stays public under CC BY-NC-SA 4.0.
>_ Boundary
No personal or health data in public issues. A safety concern (a protocol could harm someone) goes through the Feedback Compiler, which is private, never through a public issue. A field report (how a protocol worked for you) goes to /telemetry, never to the repository.
If a protocol is harming you right now: stop it and talk to a doctor or a licensed therapist. In acute crisis, contact your local emergency number (112 in the EU).
>_ License
CC BY-NC-SA 4.0 · FREE
For private use, study groups and non-profits: read, share and adapt the specification, with attribution and under the same license. Not for commercial use. Contributions need the CLA on the first pull request.
creativecommons.org/licenses/by-nc-sa/4.0ENTERPRISE LICENSE · COMMERCIAL
Coaching, seminars, corporate trainings and every other commercial use of the specification run on an Enterprise License, in four tiers:
- Solo Practitionerone coach, trainer, consultant or therapist
- Studiotraining and consulting firms up to 10 trainers
- Corporatecompanies and public authorities, internal programs
- Productapps, courses, certifications, translations for sale
// Licenses run per year. Prices on request.
> OPEN_DIRECT_CHANNEL · ENTERPRISE LICENSE Full terms · COMMERCIAL-USE.md
Applying the method in conversation needs no license. Using the material or the names Dream Machine® / Love Protocol® commercially does.
Dream Machine® (EUTM 019307121) and Love Protocol® (EUTM 019307122) are registered trademarks of Dream Machine Systems FlexCo. The license covers the text of the specification, not the marks.
STATUS LEGEND · ALL TABLES BELOW
- PLANNED no spec yet
- DRAFT spec exists, not yet audited against the current build
- STABLE matches the tagged build
Current spec version and changelog: GitHub Releases CHANGELOG.md
>_ Module status
modules/status.json · synced at build time>_ SYSTEM DIRECTORIES
spec-status.json · synced at build timeThe book closes with eleven System Directories, A to K. Directories with their own system logic are specified here; the rest live elsewhere.
| DIR | DIRECTORY | PARTITION | STATUS | BRIEFING | SPEC |
|---|---|---|---|---|---|
| A | Backend Schematic (Multi-Agent Architecture) | I | STABLE | /briefings/dira | directories/a-backend-schematic/ |
| B | System Glossary (A-Z Index) | I | — | — | glossary/ |
| C | Technical Specification: Love Protocol | I | — | /briefings/ch9 | Module 09 (sections C.3 to C.7 = procedures 3.1 to 3.6) |
| D | Theoretical Sandbox (End-of-Lifecycle Theories) | I | STABLE | /briefings/dird | directories/d-theoretical-sandbox/ |
| E | Practical Command Set (Exercise Repo) | II | STABLE | — | directories/e-command-set/ |
| F | Troubleshooting Guide (System Error Logs) | II | STABLE | — | directories/f-troubleshooting-guide/ |
| G | System Telemetry & KPIs | II | STABLE | — | directories/g-telemetry-kpis/ |
| H | System Peripherals & Utilities (Hardware & Software) | III | — | — | Website: Bill of Materials |
| I | Resource Repositories (Third-Party Libraries) | III | — | — | Website: Bill of Materials |
| J | Visual Schematics (The Carbon/Silicon Synthesis) | III | — | — | Book only (third-party illustrations) |
| K | Network: Acknowledgments & Support Cluster | III | — | — | Book only (private persons) |
>_ DEPLOYMENT RUNBOOK & OPERATIONAL TOOLKIT
spec-status.json · synced at build time| PART | BOOK | STATUS | SPEC |
|---|---|---|---|
| Deployment Runbook | CH 13–19 | STABLE | runbook/ |
| Operational Toolkit | CH 20–24 | STABLE | toolkit/ |
Toolkit templates (incident reports A–C, daily log) are copyable from toolkit/templates/ .
// No personal or health data in public issues.