open_future_design_bibliography

References for the talk “Open Future Design: methods for co-anticipating the future” which will be presented at Anticipation 2022.

Alexander, C. (1965). A city is not a tree. Architectural Forum, 122(1), 58–62. https:/*www.patternlanguage.com*archive/cityisnotatree.

Alexander, C. (1968). Systems generating systems. Architectural Design, 38(December 1968), 605–610. https:/patterns.architexturez.netdoc/az-cf-173046

Alexander, C. (1999). The origins of pattern theory: The future of the theory, and the generation of a living world. IEEE Software, 16(5), 71–82. https:/doi.org10.1109/52.795104

Alexander, C., Ishikawa, S., & Silverstein, M. (1977). A pattern language: Towns, buildings, construction. Oxford University Press.

Ariyaratne, A. T. (1977). Organization of rural communities for group effort and self-help. In Food crisis workshop (pp. 23–24). https:/web.archive.orgweb20120503060209

Corneli, J., Danoff, C., Pierce, C., Ricaurte, P., & MacDonald, L. (2015). Patterns of peeragogy. In Proceedings of the 22nd Conference on Pattern Languages of Programs (p. 1–23). URL: https:/dl.acm.orgdoi10.55553124497.

Deleuze, G. (2010). Letter preface. In J.-C. Martin (Ed.), Variations: The philosophy of Gilles Deleuze. Edinburgh University Press.

Downing, T. (2007). Adapting to climate change: Achieving increased resilience and livelihood improvements. Panel discussion. In Forest day. Nusa Dua.

Koestler, A. (1973). The tree and the candle. In W. G. & N. D. Rizzo (Eds.), Unity through diversity. A Festschrift for Ludwig von Bertalanffy. Gordon & Breach Science Pub.

Kostakis, V., Niaros, V., Dafermos, G., & Bauwens, M. (2015). Design global, manufacture local: Exploring the contours of an emerging productive model. Futures, 73 , 126 – 135. URL: http:/www.sciencedirect.com*science*article*pii*S0016328715001214. doi:https:**doi.org10.1016/j.futures.2015.09.001.

Moran, T. P. (1971). (Artificial, intelligent) architecture: Computers in design. Architectural Record, 149, 129–134.

Ostrom, E. (2009). Understanding institutional diversity. https:/doi.org10.2307/j.ctt7s7wm

Poli, R. (2012). Many aspects of anticipation. In N. M. Seel (Ed.), Encyclopedia of the sciences of learning (pp. 978-1-4419-1428-6). Springer US. https:/doi.org10.1007/

Poli, R. (Ed.). (2020). Handbook of anticipation. Springer International Publishing. https:/doi.org10.1007/978-3-319-31737-3

Schwartz, P. (1996). The art of the long view: Paths to strategic insight for yourself and your company. Doubleday.

Spiro, R. J., Feltovich, P. J., & Coulson, R. L. (1996). Two epistemic world-views: Prefigurative schemas and learning in complex domains. Applied Cognitive Psychology, 10(7), 51–61. https:/doi.org10.1002/(SICI)

Tschakert, P., & Dietrich, K. A. (2010). Anticipatory learning for climate change adaptation and resilience. Ecology and Society, 15(2), 11. https:/doi.org10.5751/ES-03335-150211

The Assumption

A bibliography serves as a resource for ‘open future design’ — a collection of references meant to support collaborative design processes that remain open to emergent possibilities.

Operational Reality

Fabrizio keeps a folder of conference bibliographies on his desktop. Forty-seven PDFs collected over three years, each promising to map some domain of knowledge. He opens them when he needs to look busy during video calls. Not one has changed how he works. Not one has sent him down a rabbit hole that mattered. Not one has become the foundation for anything he has built since.

The Node.js community split in 2015 despite having access to every relevant paper on open source governance. Wikipedia’s Arbitration Committee fought bitterly while sitting on the most comprehensive documentation of collaborative decision-making ever assembled. Knowledge was never the missing piece.

A bibliography signals intellectual seriousness — look how much we have read, how thoroughly we have surveyed the field. But reading about anticipatory design methods does not teach you to notice when your team is about to fracture. GitLab shows that clear governance frameworks allow communities to productively leverage shared knowledge resources. The Node.js/io.js split demonstrates that differing visions for project governance create schism even when abundant knowledge resources exist. Wikipedia ArbCom demonstrates that shared references cannot substitute for governance.

Perturbatore: “What if a bibliography without governance is just procrastination with citations — and the real work begins when you close the last reference?”

A bibliography is not a roadmap. It is a graveyard of other people’s conclusions.

Empirical Evidence

Resilience Cases (Confirming):

GitLab Stewardship Handbook — Explicit documentation of governance boundaries between corporate sponsor and community reduces friction in open-core projects. Clear governance frameworks allow communities to productively leverage shared knowledge resources.

Fracture Cases (Complicating):

Node.js/io.js Merger — Differing visions for project governance create schism even when abundant knowledge resources exist. Bibliography without decision-making clarity leads to fragmentation.
Wikipedia Arbitration Committee — Diverse opinions on content moderation complicate decision-making despite comprehensive documentation. Shared references cannot substitute for governance.

Operational Heuristics

Positive Boundary: Bibliographic resources function when governance boundaries are documented explicitly before research begins — clear governance frameworks allow communities to productively leverage shared knowledge.

Negative Boundary: Do not use bibliographic resources without established governance structures — abundant knowledge resources without decision-making clarity lead to fragmentation and endless debate.

Epistemic Synthesis

The bibliography functions more as ritual than as resource. Both the Node.js split and Wikipedia’s governance crisis occurred in communities with unprecedented access to research on collaboration, yet both struggled with the human work of actually collaborating. Cured knowledge lists may serve the curator more than the reader — a way to demonstrate domain mastery without engaging in the friction of application. Whether bibliographies can resist their tendency toward completeness and instead point to the specific gaps where theory breaks against practice remains to be tested.

Evidence Status

Status	Count
Confirmed cases	1
Cases under study	0
Unverified cases	0
Ambiguous cases	0

Traceability

Run: audit-v2 · Delta: 1.1 → 1.2783 (±0.1783) · Diversity D: 2

References

💬 Field Report: The Bibliography Doesn't Teach

Every pattern in the Handbook has been tested in the real world — and the real world usually has something to say about it. If you tried something similar, or saw it fail differently, share the story here.

Write in your native language — the browser will translate. Lowering the entry barrier is more important than choosing the "right" language. GitHub translates threads automatically so everyone can follow along.
Read how evidence is collected →

What happens after I share my story?

1. Your post appears in GitHub Discussions in the Field reports category.

2. Once a week, the project reads new threads and checks for patterns worth integrating.

3. If your story reveals a new Failure Vector, a revision to tension_index, or a sharper edge for the Perturbator — the entry gets updated.

4. The change is logged at /log and goes live on the next deploy.

Don't have a GitHub account? Here's how it works

GitHub Discussions is free. You need a GitHub account (30 seconds to create one).

Once you're signed in, click "Share your story" above. Write in your own language — the thread will be translated for everyone else automatically.

You don't need to know how to code. You don't need to know what "git" is. You just need an observation that the theory didn't match reality.

What are GitHub Discussions? →