= integral auto-poietic meta-design | 📆daily.notes | start-all | ✍️  🧊 = integral auto-poietic design   https://bafybeiarzefuy2xwoaqtrw54fiktdya36r7ucg2nvly3rzhs3l2dlphf44.ipfs.dweb.link Comming to full cycle for the past 4 years using existing capabilities I've been practicing integral omni-optional exploratory experiential experimental auto-poietic emergent meta-reflective permanent evergreen future proof unenclosable unstopable unsurveillable user centric, as opposed to provider centric services and inrastructures empowering the people, the real  participants  so that they can connect with each other and the network effect arising will benefit the particpants first and foremost,  and empowe and provide for each other co-creating their  commons owned,  co-created,  co-evolved constellations  both for infrastructe and affordances in fact the focuos is on interplayability across and heterogeneous systems all over the web incoprorating, bringing more and more of their work and the value people can derive from that together into their own(ed) autonomous spaces these capabilities should play nicely with existing capabilities act as am omni present user owned companion to anything worth engaging with on the web support mutual discoverability, act as a serendipity engine,  a digital pensive, if you like, bring permanence and provenance to the existing web and allow people to self-archive anything and everything they find valueable from their engagements on the web Ultimately enable People to experience the Web as an extension of their Minds, both  as individual learners and  in interpersonal ad hoc circles, communiti of interest, practie and pursuances, improving the intellectual capabilities  of  the individual human beings, but weaving an interpersonal externalization of human inter intellect.  constructive meta-design deeloping instance first exemplars for everything I needed to develop next in the expectation that eventually it will all connect focused not so much on the quality of the component do by hand that would eventually need to be automated through that practice use the eperiential feedback to drive the design focus on doing not just thinking about possibilities this continuous practical feedback loop ensured that what ever needs to be eventually developed could be attempted with demonstrable viability of what is working so it is not top down, but inside out, middle out  exploratory design through practice Instead of rushing to code some new features I focused on Technology Scouting My bet was that anything worth doing had already been coded by someone so learning about other's people's work was a top priority I did have a clear vision of the kind of system I was aiming at the search was value driven great example of this is Peergos instead of writing a book as I developed it focused on the ability to write a HyperBook which would not only be born collabortive supporting inline threaded linked meaningfully linked  Symmathetic conversations grounded in the conviction that Software itself is a Symmathatic conversation and to become a Symmatheticist in the Medium of Software which also requires a new ability to articulate and formulate ideas about desired systems, refine them until evntually they would be REALized in working sytem delivering envisaged expirence and outcomes which can be summarised by saying that I was seeking  universal intentional conceptualization of  a Human Centric   human-scalable  info-collaboration-storage infrastructures Simplicity  Coherence mutual arising that supports siultaneously single user autnonomy and multiplayer collaboration at  scaled  both in terms of reach the number of participants and how people can be connected with each other with strong guaranties for security privacy local-first availability eventual consistent collaboration with full provenance of all contributions version control is integral to the workflow not in terms of reach that are just above the threshold of what is required the sweet spot