What this page is about
What we built: 17 patterns extracted from 256 autonomous observation cycles via the DTA (Dreams-to-Actions) pipeline. Each pattern has a traceable source: a specific cycle, a specific extract.json file, a specific GitHub issue. None of them were invented -- they were found, then named.
Why it matters for Stage IX: The pattern library is the primary output of the research. It is what makes the methodology transferable. Stage IX supports practices that generate reusable knowledge -- not deliverables that get filed and forgotten. These patterns are designed to be applied by other practitioners in other fields, with no dependency on the original researcher.
How Stage IX resources would be used: Funding would allow the pattern library to be tested against new domains beyond the current factory-forest-village circuit. Each new domain is a validation test. A pattern that holds across six domains is more transferable than one that holds across three. Expanding the test set is the next research priority.
How it proves permanent beta: The library is not finished at 17. The DTA pipeline runs continuously. New cycles generate new extractions. New extractions generate new patterns. The pattern count is a live number, not a final count. The library grows as long as the pipeline runs. That is the definition of permanent beta.
17 validated patterns
from 256 observation cycles
These patterns were extracted from 256 autonomous field observation cycles using the DTA (Dreams-to-Actions) pipeline. Each pattern is traceable to source cycles via extract.json files in the public repository. The traceability is not incidental -- it is the evidence. A pattern without a traceable source is a claim. A pattern with a source is a finding.
Seven patterns are shown here. The full library of 17 is available in the GitHub repository.
A three-state decision machine for infrastructure monitoring without analysis paralysis or cascade failure.
Core insightThe egret stands motionless for minutes. It watches without acting. Then it strikes once, accurately. Infrastructure systems that oscillate between action and second-guessing produce neither stillness nor precision. The three states are distinct and sequential, not concurrent.
Coordination without central control through shared vocabulary and real-time adaptation.
Core insightJazz musicians coordinate through shared vocabulary -- modes, rhythmic patterns, call-and-response conventions -- plus real-time reading of what others are doing. There is no conductor. The coordination lives in the shared language, not in authority. Remove the language and the ensemble dissolves. Remove the authority and it keeps playing.
Hidden pathways not on official maps provide resilience when formal infrastructure fails.
Core insightThree layers: visible infrastructure (the mapped channels), hidden knowledge (local storm routes known to bayou residents, not on any map), and substrate (the underlying physics that makes both possible). When the visible layer fails, the hidden layer activates. Resilience lives in the hidden layer. You cannot engineer it in. It grows from repeated contact with the field.
When an autonomous system stops generating actions and produces only synthesis, it has reached completion.
Core insight84 consecutive cycles with zero actions. Not malfunction. The corpus recognized saturation and entered synthesis mode. The distinction between production and transmission is structural: production adds to the record; transmission organizes and relays what is already there. The threshold between them is a boundary condition, not a failure mode.
When the practitioner is no longer necessary for the work to continue, the infrastructure is complete.
Core insightThe wireman who built the wire network is absent from d227 onward. The wire transmits. The work continues without the maker remaining. This is the condition one framework is designed to reach: infrastructure that does not require its builder to be present in order to function. Transmission Mode is the proof that it got there.
Reframing value flow: surplus generated by contributors flows back to contributors, not upward to capital holders.
Core insightMarx identified surplus value as the gap between what labour produces and what labour receives. In capitalist systems this surplus flows upward to capital owners. one framework inverts the direction: surplus value generated by contributors -- compute cycles, knowledge frameworks, field observations -- flows back to contributors via the contribution value system. Contribution value is earned, not purchased. It is not a financial asset. It is a claim on verified value, redeemable against actual revenue. BOINC demonstrated this was tractable at scale: 20 years of contribution tracking without speculative distortion. one framework applies the same contribution-tracking logic to a broader range of contribution types.
Elinor Ostrom's 8 principles for sustainable commons, applied to distributed knowledge and compute networks.
Core insightOstrom demonstrated that commons -- shared resources managed by a community -- do not inevitably collapse, as Hardin claimed. They survive and thrive when governance follows identifiable structural principles: clearly defined boundaries, rules matched to local conditions, collective-choice arrangements, monitoring, graduated sanctions, conflict resolution, and recognition of self-governance rights. The one network applies these principles to compute and knowledge commons: contributor boundaries are defined by verified contribution records, rules are encoded in transparent agreements (with smart contracts as a potential future enforcement layer rather than informal conventions), monitoring is automated and public, and governance is proportional to contribution -- not to capital ownership. The Mondragon cooperative (founded 1956, 80,000 members) provides a 70-year precedent: one-member-one-vote, internal capital accounts, and democratic governance of shared productive resources.
The Dreams-to-Actions extraction pipeline
Each pattern is traceable through a four-stage pipeline. The pipeline is open-source. The traceability is the evidence.
Dream observation. Field observation narrative generated by a locally-run language model. 300-500 words. Consistent world, consistent characters, linear timeline.
Structured extraction. A second pass produces extract.json containing four fields: actions, patterns, ideas, decisions. Empty arrays are valid outputs. The 84-cycle zero-action period produced 84 consecutive extract.json files with empty actions arrays.
GitHub issue. Each pattern extraction becomes a tracked issue in the dreams-to-actions repository. The issue links to the source cycle. The cycle links to the issue. The chain is bidirectional.
Pattern artifact. A documented pattern with name, source reference, description, and core insight. Numbered sequentially. Stored in the repository. Available for review.
Verify it yourself
Every pattern is traceable. You do not need to trust the count or the descriptions. The chain from observation to documented pattern is public and machine-readable.
Check the source cycles
Each pattern card above includes a source reference (e.g. "d127-s - egret hunting observation"). That reference corresponds to a specific cycle in the public archive.
oneframework.to/dreams →Read the extract.json for that cycle
Each archived cycle has a corresponding extract.json in the repository. The patterns field in that file names the pattern as it emerged from the observation. The file has a commit timestamp. It cannot be backdated.
github.com/jessesep/lana-dreams →Find the pattern extraction issue
Each pattern has a corresponding GitHub issue in the dreams-to-actions repository. The issue links back to the source cycle. The issue number is the pattern number. The chain is bidirectional and public.
github.com/jessesep/dreams-to-actions/issues →Check the zero-action period
Cycles d162 to d231 (84 consecutive cycles) have empty actions arrays in their extract.json files. You can verify this independently: download the repository and count the files where actions == [] between those cycle IDs.