/hyperpost/🌐/🎭/gyuri/do/web/search/📅/2025/09/2/0/

 

:links: web, edit

:created: 

 

.purpose - origo.folder

• this page is the instance first exemplar of an 
  • entry point to all information that needs to be  written/formulated 
    • about the enclosing named folder
  • It is dedicated to meta-level articulation
    • a holder/folder space for all that is needed to
      • make/create/curate/do/morph/co-eveolve.laborate on
        • emergent sense through engagement
        • with what is contained in the folder.
      •  
    • It is also a space where pertinent links to both
      • information
      • affordances
      • people
      • ideas
      • formulations
        • intent
        • learnings about  things
      • designated/named 
        • communication channels
        • participant actors
          • can be added
      • without interfering with narrative/explicative flows
        • pertaining to the intent/propose/content that is
          • contained in the parent folder.
    • .
  • exemplar - constructive discovery through meta-reflective/fofmulative 
    • focal attention/care/engagement
    • this, again is an example of the primacy of
      • do how as oppose to questions of what
      • Let the what emerge and being shaped by tacit intent purpose
      • and engagement
  • As a an instance first exemplar it will have links to meta-meta-level elaboration
    • seeding a template in its own subfolder 0
  • Every folder created on the IndyWeb will have such an origo/meta folder
    • and if need be further meta/level folders
    • so that templates, generators etcs can be added for its replication in other contexts
    •  
• meta.plex-named-folder.space for the parent folder of the current folder
• Intentional info-structuring-communcaiton-end development work flows and practices are documented elaborated interplayed and gathered under a named folder
• a practice we like o call making by doing
• experientially exploreing instance first construction of intentional morphic info spaces primarily by doing things and reflect the results in morphic document struxtures
•  
• and progressively make those steps that we accomplished and documented by hand to be transformed into functions and affordances the availability of these affordances can then be communicated to users so thay can infoke them in context whre they are appropriate to produced desired morphic transformation
•  
• As we are thus making IT as we go along, in meta-infostructure folders like here we have a space where necessary templates and ways of workign in context with named intentional info structures in a way that can then be “copied” distributed and emulated by others
•  
• this is what we call not only Open Source, but Open Constructs (constructs that are formulated in a ways that aims to make it readily understandable, tinkereable customizable personalizable extensible by others, and even Open Sauce, all infrastructural setups that are required are shared in a form that are easy to understand, emulate, and compelling to use