an experiment in my free time to optimize various issues with current ocracies/isms/archies, governments, social constructs, towards the human condition/psyche and not towards any one person, group, or type. this will probably take the resource/energy systems thought of in technocracy as a foundation.
this is a conceptual model, not software (the only code is the viewer below). there is no "v1" - it evolves through continuous refinement. git history serves as the audit trail for how the model changes over time.
each package is a distinct functional domain, decomposed by function rather than traditional political categories. documents use markdown with YAML frontmatter and [[wiki links]] for cross-references.
| package | scope |
|---|---|
| foundations | axioms: human needs, human nature, ethics |
| autonomy | individual freedoms, rights, privacy, identity |
| decision-making | how groups make choices: consensus, delegation, participation, accountability |
| resource-systems | material needs: accounting, distribution, production, ownership |
| law | rule lifecycle: creation, amendment, constitutional, statutory, codification |
| justice | when things break: conflict resolution, enforcement, restoration |
| knowledge | how society learns: education, information flow, research |
| community | how people relate: belonging, culture, support |
| health | physical, mental, preventive, emergency |
| ecology | environmental constraints: sustainability, resource limits, stewardship |
| infrastructure | physical/digital systems: communication, energy, water, food, housing, mobility |
| security | protection: defense, resilience, threat response |
| relations | inter-community: diplomacy, migration, trade, borders |
| technology | tech governance: governance, automation, ethics, deployment |
| transition | (deferred) how to get from here to there |
a self-contained go binary serves a local wiki viewer for browsing the model. build and run:
go build -o eudemics .
./eudemics --port 8080
flags:
--port- server port (default 8080)--content- path to content directory (default.)--repo- git repo URL to clone if content dir is empty
the viewer renders markdown server-side, provides a navigable tree, and displays concept relationships in a canvas graph. content changes are hot-reloaded via filesystem watcher.
cross-platform binaries are built on tag push via github actions.
each document follows this structure:
---
status: draft | review | stable | deferred
tags: [parent-package, ...]
builds_on: [concept-path, ...]
constrains: [concept-path, ...]
implements: [concept-path, ...]
related: [concept-path, ...]
---
# Title
content with [[wiki links]] for inline cross-references