NEXUS — Start Here: The Framework at the Center of Everything

NEXUS is the methodology and framework that governs how software gets designed, built, and understood here. It is not a product — it is the approach. The discipline. The set of principles that makes everything else coherent.

The Problem NEXUS Addresses

Most software development loses knowledge. Design decisions are made in meetings that aren't recorded. Architecture choices are buried in Slack threads that expire. The reasoning behind a particular approach evaporates when the developer who made it moves on or forgets. Six months later the team is relitigating decisions already made, re-learning lessons already learned, rebuilding understanding already built.

NEXUS treats this as a fundamental architectural failure, not a cultural one. The solution is not better meetings or more discipline — it is making knowledge accumulation a first-class design requirement, as important as the software itself.

Event Sourcing as the Foundation

NEXUS applies event sourcing principles not just to the software it produces but to the development process itself.

Every design decision is an event. Every discovered limitation is an event. Every specification change is an event. Every conversation that produces insight is preserved. Current understanding is always a projection from the history of events that shaped it — traceable, auditable, and recoverable.

This is not theoretical. LOGOS, the knowledge system that runs alongside NEXUS, is the event store for the development process itself. The conversations that produced this methodology are preserved there. The decisions made along the way are traceable to the conversations that spawned them.

The Methodology

NEXUS extends Adam Dymetrik's Event Modeling methodology with several key additions:

Paths as first-class artifacts — A path is a named, purposeful journey through a system from a user's perspective. Not just a user story, not just a flow diagram — a typed design artifact that connects intent to implementation at every step.

Design before implementation — Specs are written before code. Event models are drawn before functions are coded. The design is the source from which implementation is generated, not documentation produced after the fact.

AI-assisted implementation — Approved specs and event models serve as inputs to AI code generation. NEXUS is designed from the ground up for a world where AI implements what humans design. The methodology produces artifacts that AI can act on correctly.

Continuous accumulation — Nothing is lost. Every conversation, every decision, every iteration is preserved and linked. The knowledge base grows continuously and becomes more valuable over time.

The Tools

LOGOS — The knowledge and communication system where NEXUS methodology lives in practice. Forum, wiki, helpdesk, planning space, event store, AI training corpus, and the software being built to replace the current Talkyard installation. NEXUS without LOGOS is theory.

CORTEX — The personal AI system that feeds from and contributes to LOGOS, becoming progressively more capable through use. CORTEX is the AI that knows the codebase, the methodology, the decisions, and the person behind it all.

F# — The implementation language of choice. Functional, expressive, excellent for event sourcing patterns, and well-suited to AI-assisted code generation from typed specs.

The Vision

A development framework where:

• Design and implementation are clearly separated and connected
• Knowledge accumulates rather than evaporates
• AI does the implementation work guided by human design
• Every decision is traceable to the conversation that produced it
• The system gets smarter and more capable through continuous use
• Nothing is lost and everything is findable

NEXUS is being proven at scale through its own projects. LOGOS is the first major implementation — a forum and knowledge system built entirely using NEXUS methodology. Every design decision is made in LOGOS, every spec is written there, every limitation becomes a requirement, and the resulting software will be event sourced at the foundation.

Current Status

LOGOS infrastructure is in place using Talkyard as interim platform. LaundryLog is the active first APPS implementation. CORTEX architecture is defined. The pipeline from conversation to code is being proven through use.

See: LOGOS for the knowledge and communication system
See: CORTEX for the personal AI system
See: APPS for software built within the framework