This is a series of Videos and documents I would like to produce about the development of the Concept Operating System and community building. this will take years to complete. and the joke in the structure and tone of this probably will feel dated by the end, the recordings uselessly outta date.

This is a design document and installation guide for the next phase of my long-term computing environment and philosophy of life in the technologic world. This project will be conducted throughout the late stages of the development of the next iteration of The Arcology Project. These docs serve as the sales pitch for the Arcology and Arroyo while describing in detail how others could use it to build thaeir own computer community.

The Complete Computer 0x01: You Can (Not) Compute

You Can (Not) Compute is an ideological overview of the Concept Operating System and the Complete Computer.

INPROGRESS The Complete Computer 0x02.2: This Is (Not) Advanced

This is (Not) Advanced is a walk-through of the layers and construction of the Concept Operating System. This is basically a long boring presentation, a chain of connected things which lead to a rat's nest or a social operating system

WAITING The Complete Computer 0x03: We Can (Not) Do It

We Can (Not) Do It will describe how to use the Concept Operating system to construct a system, and a network, and deploy them.

WAITING Shin Arcology

Shin Arcology describes The Arocology Project web publishing platform and what a social/conversational operating system could look like

WAITING The Complete Computer 0b100: The Net is Vast and Infinite

Vast and Infinite: Where does the newborn go from here?

Documentation Project/Devstream Updates

Rebuild of the Complete Computer 0x02: devstream 1

2024-10-24 Today the Rebuild of The Complete Computer 0x02: This Is (Not) Advanced devstream began, with the goal to produce a sort of video and document documentation combo to go from "zero to nixos running on a publishing platform".

After an hour of playing Caves of Qud and dying mercilessly in Golgotha, we progressed through Phase 0 of the Bootstrap over two hours where you start with a Fedora VM or any other Linux you want and progress to being able to query a local Arcology instance, query a local org-roam metadata database to generate a minimal Emacs init.el

Next time I stream, I'll likely be working on a game jam game, taking another swipe at Group B Pace Notes for the Autumn Lisp Game Jam. But after that I'll start on Arcology Bootstrap Phase 1 where home-manager takes over the system, and then the arcology takes over home-manager.

Tune in some other time!

Rebuild of the Complete Computer 0x02: devstream 2

2024-11-07 Today we tried untangling the deployment of Arcology under home-manager and basically failed, it was a bit of a mess... I have a plan to get things in to a more reasonable state, but there are some little issues that still needs to be resolved to ensure these systems will be long-term sustainable.

The problem is that I have a few dependencies I refuse to put in nixpkgs because I refuse to put things in nixpkgs. So there are two deps that I need to vendor, the The arroyo_rs Native Org Parser, and sqlite-vec for the crappy RAG search thing I've been building in the Arcology.

I have two or three important paths in a home directory of the admin of a system running the arcology:

~/org where the org files are placed, ~/org/arcology contains the Arcology code documents and the service code itself
~/arroyo-nix this is where the Nix manifests will be tangled to. This doesn't need to be here, it might be easier to put in ~/org...? TBD
~/src contains checkouts for dependencies that I'll probably vendor in to the Arcology repo this week and try to eliminate.

The main thing, the main problem is that Nix and Org can't really work well with "dynamic" directories; tangle paths have to be hard-coded relative or absolute in the file (but at least tilde is expanded). Nix can refer to relative paths and absolute paths and can contain Nix variables, but Nix does not expand tilde and the way it treats paths in the language is not really what you would want anyways. I'll probably just vendor the stuff that is in ~/src to be submodules of the arcology repo; I'm not sure what to do about the non-org-file directories that I want to ensure can be directly referenced from within the ~/org directory. this probably means that everything is best under ~/org...

So this week I'll figure out how to organize these files better so that the Arcology Bootstrap Phase 1 leaves us in a position where it is easy to get a local instance of the Localhost API for the Arcology running on a port that Emacs expects to talk to so that it can generate a fresh Emacs init, and a home-manager configuration on which more features can be brought in and we'll try that again next Thursday.