I have been wanting to assemble a new iteration of The Arcology Project, a decade long effort to polish a ball of mud, to be able to publish a thought to my website and to my microblogs at the same time.

I've been in a stall on this project for three reasons lately: because I'm not progressing toward The International Trip; because i want to share this beast with others, to build a journal that i could use and that my sweetheart could use and that even my hacker buddy could use to build things together. Emacs is too much to of ask them, but interstitial journaling with long-term memory augmentation and literate programming is too powerful to leave behind. Because I don't want to be stuck using hardware-based Android keyboard devices running Emacs in CCE in Nix On Droid Termux environment without text input affordances like swipe, autocarrot, voice input, and more™️

so i've been trying to think about how to do a mobile org-roam app... i think i just need to bang out some prototypes based on whatever parser i can get my hands on.

and as long as i'm rethinking the mobile org-roam app, i want to rethink the arcology project's publishing model

2025 Recap

2025's reification of Arcology's development history and for 2026: arcology2go:

• #+TRANSCLUDE: 2025's reification of Arcology's development history :level 2

• #+transclude: for 2026: arcology2go :level 2

web and mobile org-roam "clients"

i really might go for Kotlin on this thing and try to move away from Python.

data layer

processor thread that crawls org-directory and watches it for changes

delight:

• database that models org-roam-schemata

• database that models Arroyo Generators, but bound to headlines now and not just page-level characteristics.

  • used to generate literate programming files

  • the code for generating my site and config moves from python to kotlin but can be distributed as a JAR

• database that models Arcology pages, the ability to publish only one or some subheadings in a file or some subheadings across multiple files, to a URL as html and rss and cross-posted.

web frontend

• simple HTML statically cached but with htmx progressive enhancement

• kotlin web framework (tbd) serves and caches pages

• provides API for Arroyo Generators to query and tangle files

• orgmode-kmp or so used to convert org headings in to HTML w/ Arcology Web Publishing Feature Set:

New ideas

• expiring links, publish a journal page for 1 hour or 1 day or 1 month

• crossposting daemon

  • Post links to pages sometimes

  • email pages to certain groups email links to

  • Publish headings to long-term fediverse threads

  • record replies and interactions to org-mode file

mobile app

• capture:

  • capture to dailies

  • capture URL

  • share file to attach

• search and recall:

  • Dailies calendar

  • find ref URL

  • search for title

  • navigate links

  • see backlinks w/ quick rendering

syncthing handles sync to a web frontend that is watching for changes... voila.