How Software Gets Built Here
This is where software gets designed, built, and understood. Not just coded — understood. The distinction matters.
The Philosophy
Most development processes optimize for shipping features. This one optimizes for accumulating understanding. Features ship as a consequence of understanding, not instead of it.
Design comes before implementation. Specifications are written before code. Event models are drawn before functions are created. The design is the source from which implementation is generated — not documentation produced after the fact to explain code that already exists.
Nothing is lost. Every decision, every conversation that produced insight, every limitation discovered and turned into a requirement — all of it is preserved and traceable. Six months from now the reasoning behind any choice is findable. A year from now the history of how the system evolved is readable. This is not optional overhead. It is the core discipline.
The Methodology
NEXUS — see the NEXUS category for the full methodology. Event sourcing applied to the development process itself. Paths as first-class design artifacts. AI-assisted implementation from typed specs. Continuous knowledge accumulation.
The Knowledge System
LOGOS is where NEXUS methodology lives in practice. Design happens in LOGOS. Specs are written in LOGOS. Decisions are recorded in LOGOS. Limitations discovered become requirements documented in LOGOS. LOGOS is simultaneously the forum, the wiki, the knowledge base, and the software being built to replace the current Talkyard installation.
Current Projects
NEXUS — the framework and methodology itself. Being proven through its own projects.
LOGOS — the knowledge and communication system. The forum, wiki, helpdesk, planning space, and event store. Currently running on Talkyard as interim platform. LOGOS software is being designed and built to replace it.
CORTEX — the personal AI system. Feeds from LOGOS, grows more capable through use, contributes back to LOGOS when it discovers something new.
LaundryLog — expense tracking for truckers. First APPS-category proof of the framework. Real user, real data, real IRS audit stakes.
How a Project Moves Forward
- Idea or problem gets discussed in the relevant category
- Event model is drawn — the shape of the domain in events, commands, and read models
- Paths are identified — named user journeys through the system
- Specs are written — typed Spec topics with workflow states (Draft → Under Review → Approved → Linked to Implementation)
- AI implements from approved specs
- Implementation is linked back to the spec that produced it
Every step produces artifacts that live in LOGOS. Every artifact is traceable to the conversation that produced it.
See: NEXUS for the full methodology
See: LOGOS for the knowledge system
See: APPS for software built within the framework
- Progress