In this document, I've taken a list of all of the org-mode files which are used to construct my CCE environment, organized by purpose, and then spent some time thinking about how those purposes interact and accrete on each other. the idea here is to have a handful of "core" things which someone could build an entirely different version of the CCE with, the scaffold and NixOS core, and the Emacs core which taken together is the minimal set of dependencies for building and managing NixOS systems with Arcology documents. Beyond that "Ryan's Complete Computer" will provide a KDE desktop and Emacs application environment. Yours could provide something else, partially or entirely.
A Holistic View of the Arcology and Complete Computing
The Arcology exists to allow the web to re-wild. We've chosen as society to move in to Google- Apple- and Amazon- branded suburbs full of unhealthy, unserious, inefficient waste. Entrusting our digital environments and physical worlds to these suburbanites have left us culturally isolated and socially at-odds. By re-centering communal knowledge and careful cross-integration of that knowledge, perhaps we could build better communities and better computers or at least better computer communities, right? right??
An Arcology should exist within its environment:
An Environment
At minimum, a complete computer can be built by one person who wants to declare their computer's configuration and applications and have it happen, to maintain a personal wiki, and to publish portions of that wiki to the web. If we are to bridge our a priori environment of knowledge and the technical expertise available on the noosphere we must further complicate this environment with new fundaments.
A scaffold
These fundaments are a set of deployment manifests and a standard Nix configuration environment for your workstation and any other thing that could become a server. It's the bootstrap environment for the Arcology publishing platform which at the very least allows you to deploy more complicated things on top of it. It can start with Ubuntu deployed on an old laptop or a WSL2 VM on your Windows machine or a dedicated piece of hardware and customized Home Lab server build.
These foundations are constructed using org-mode documents and exist within a growing wiki/knowledge base. With these scaffolds in place, new functionality can accrete on top of it, starting with the core blocks required to start running NixOS and deploying new code directly to the hosts.
Industrial Blocks
The industrial blocks bring hardware on-line. I have manifests for my laptops, my server, my Cosmo Communicator 's t184256/nix-on-droid environment, and a Kodi settop box. It's easy to add more specialized systems by writing down what you want the computer to do and adding some metadata markup to the page.
File systems, networking, Nix deployment, and a handful of basic roles for "endpoints" and your own wobserver.
Human Environments
An Arcology is only useful if people use it. Ryan's Complete Computer is
support for various hardware (computers and peripherals)
a KDE desktop
an opinionated emacs application environment
an org-mode productivity environment
a multi-language development environment
an application suite
self-hosted social networking
file-hosting and backups
web publishing and syndication environment
private news reading