share with provenance 
trystero
parent: 📒📆daily.notes


respond.to-ab@indylab@Telegram

  • I was referencing Feature-First Development in my answer
    • doing web research and thinking about it
      • On the page by the author of the Eidetica Project
        • on the topic of Feature-First Development
          • I introduce the concept of Adjacent Featura-Only Development in an anootation
          • and wish to expand on that concept in its own dot
plex
  • Adjacent Feature-Only Development
    • Is the way autopoietic extensions and new features are 
      • conceived, putatively 
        • formulated, 
        • named and 
        • developed on the IndyWeb for its continual improvement and  autopoiesys
    • this assumes that a
      • minimal 
      • workable
      • interplayeable
      • inter-composable 
      • mutal arisable
      • instance first exemplars of 
        • a named network of
        • holinic integral born 
          • interplayeable 
            • morphic affordances
          • like IndyWiki
          • IndyDrive
            • and other instnace first working exemplars
            • of intentional software structures 
              • that themselves exhibit/manifest a
              • mycelic growth of discovering mutual arising adjacent next features and behaviours
              • instance of this can be manifested bu using existing capabolities
              • to think about IT in writing
              • wth a view to its eventual Fdjacent Next Feaure Only Development

              • which are 
      • that already able to produce, persists and make available for
        • doing by hand what is adjacent features/functions/capabilities
        • that are required that 
        • needed to be developed
  • .

what makes adjacent next feature only development possible
  • is that I have the beginning a number of well explored
  • inrsastructure level constellations co-evolved exhibiting a mutual arising 
    • minimal workable capabilities
    • that can be used to do some of the work(flows)/features required
      • such as
      • ability to compose structured articulations/formulations of ideas
      • in a way that they are able to operate
      • as a meta-reflective tools not only of thought 
      • but instance first autopoietic development
    • made possible by
      • using a workable 
        • universal information presentation/storage/exchange information infrastucture
      • that is able to talk about itself
        • kind of hoiconic as in LISP

      • so that when you create a document with the purpose of articulating
      • your intent and desired behaviour/interactions can
      • gradually be expanded formulated combined and arranged in interactions/workflows
      • that constitute a PUN
        • that makes those description interpretable by the system to
        • actually deliverd the features capabilities it is presenting IT
        • for Symmathetic conversation
      • and actually wowk as a new feature of th entire holonic mutual arisin systme
    •  Held the vie point that regards
    • Softwae a s symmathetic conversation in a way that the
    • conversations eventually produced the feature complexes tht are needed to
    • make the features workable, productive 
  • Without ever needing to be embroiled in pinning down non-unctional requirement and building anew infrastucte
  • Instea of developing and relying of a whole inter dependent set of infrsaturcture constellations
  • that without needing to make any change to existing functional comonents an dtheir operations
  • could be reused combined with addityonal capbailit to produce
  • scaling infrastructure ultimately able to satisfy all conceivbale
  • reasonable non-functional scalein etc requirements
  • all grown for a common seed constellation
  • .
  • the reason why it is ppossible is that ven personal work on a computer by an individual
  • is designed and constructed a s a sweet-spot,
  • that is just above the threshold that coud possibly be required 
    • meeting maximal possible non-functoonal requirements regarding a single individual user
    • who is already supported by a 
      • multiplayer
      • multi threaded
      • evergreen storage constellations
      • enabling sharing and colaboration across all of 1's devices
      • so it its a born inerplayeable construct
  • What make it possible is that this sweetspot vision embodies
  • a Human Actor Model
  • which is inspired by the Actor Model for Machines
  • but at the same time considers the genuine needs of human's first

This human-first design renders problems that are impossible for machines
  • not only possible but inevitable


Just a few example

CAP theorem states that you can have only 2 out of three desired features for data storage
  • availability
  • partition tolerance
  • consistency

If we make the assumption that all information that any individual human being encouteres on the web and is exchanging with others
will have  a complete record on their machines, 
replicated with eventual consistency
privacy
permanent
future compaible
evergreen
with full provnance audint trail of the entire history of its coevolution
which  itself is recapitulable and any part of can be shared by any one that the authors wishes




 of al that information in form that is
  • discoverable
  • shareabe
  • open for colaboration
    • both synchronous and asynchronous ways




regarding, storage, communication, and morphic interactions and trnsformation