Skip to content

Vision#

MSX exists to make great software delivery the default — easy, fast, and safe — for every developer and every agent.

This page is the why. It is the most stable thing on this site: products, languages, and tools change, but the reason they exist does not. Everything else — the Ways of Working, the Coding Standards, and the Initiatives — flows from here.

Start with Why#

Work at every level is grounded in three concentric questions — the Golden Circle:

  • Why — what change in the world are we trying to make? Make the right thing the easy thing, so good software ships fast and safely.
  • How — what approach makes that change happen? Everything as code, context before code, deterministic automation first, AI where judgment is needed, humans in the loop.
  • What — what concrete thing are we delivering right now? The frameworks, actions, modules, and tools in the Initiatives.

The Why is constant. The How is the way of working. The What is replaceable.

The mission#

Make great software delivery the default — easy, fast, and safe — for every developer and every agent.

A mission is something anyone can read and immediately have ideas about how to contribute. It is not a roadmap and it is not a product. It is the direction every product points toward. How the mission turns into measurable objectives and concrete work is described in the Goal-Setting Framework.

The three words#

Every decision is filtered through easy, fast, and safe — in tension, and on purpose.

Word What it asks of every decision
Easy Is the right thing also the easy thing? Is the safe, smart choice the default choice?
Fast Does this shorten the loop between intention and feedback? Can we ship a thinner slice now?
Safe Is this reversible? Is it observable? Will a failure teach us something instead of hurting?

The words pull against each other, and that is the point. Easy without safe is reckless. Safe without fast is paralysis. Fast without easy burns people out. Holding all three at once is the discipline.

AI-first, determinism-first#

Two beliefs sit underneath everything:

  • AI is a first-class participant. Agents are part of how we think, build, and deliver — not a feature bolted on at the end. Every workflow and every document is designed so an agent can read it and act.
  • Determinism comes first. A script that always produces the correct answer beats a prompt that usually does. We use AI to build deterministic tools, then run the tools. AI earns its place by handling what deterministic logic cannot — ambiguity, judgment, natural language, and search spaces too large for hand-written rules.

The result is automation for the predictable and repeatable, and intelligence for the genuinely variable. Both, always available, each used where it is strongest. The full reasoning lives in Principles → AI-first development.

How the vision cascades#

The vision is inherited, not copied. It is written once, here, and referenced everywhere:

Vision (this site)            the why — stable, evergreen
└── Ways of Working           the how — workflow, principles, conventions
    └── Coding Standards      the how, applied to code
        └── Initiatives       the what — the products
            └── Repositories  each README is the local source of truth
                └── Agents    read the same docs as context before acting

Each layer references the one above instead of restating it. A repository's README does not re-explain the principles — it links to them. An agent definition does not embed a style guide — it points to one. This keeps a single source of truth and lets the whole system evolve without drifting out of sync.

Where it comes to life#

A vision that stays on a page is just words. This one is meant to be demonstrated. Each initiative in the Initiatives is a concrete answer to one question:

What would this look like if it were easy, fast, and safe?

Go see the answers in the Initiatives.