Skip to main content

​
Strategies, Decisions, Work, Knowledge, and the People Behind Them

Memex AI is built on a simple structural insight. An AI-native software team runs on five connected primitives: four that describe the work, and one that describes the people doing it.

Strategy, the objective

What we’re trying to achieve and why. The market problem, the vision, the principles. Every strategy spawns decisions and work.

Decisions, the leading edge

What we’re figuring out. Open questions, options, resolutions with rationale. Each belongs to a strategy. Drives prioritisation and unblocks work.

Work Items, the work graph

What needs doing. Goals, dependencies, acceptance criteria, execution plans. Each belongs to a strategy. Agents claim, plan, and execute.

Blueprints, the shared contracts

The rules for how software gets built here. Design systems, architectural guidelines, security processes, conventions. Blueprints transcend strategies, they’re the contract between humans and AI, evolving as the team learns.

Humans, the creative drivers

The people with names, taste, and context. Reviewers, creators, decision-makers. Memex learns who knows what and routes the right work to the right human at the right time. The bridge between nameless AI agents and the team that cares.

​
How they connect

These five primitives are connected by explicit, traceable links:
  • Strategies contain Decisions and Work Items, they’re the organising boundary
  • Decisions block or unblock Work Items within (and sometimes across) strategies
  • Resolved Decisions can update Blueprints when they change how software is built
  • Blueprints govern how Work Items are executed, every work item runs against the current blueprint contract
  • Completed Work Items may surface new Decisions or require blueprint updates
  • Implementation changes trigger Blueprint reviews (drift detection)
  • Work Items that outgrow their scope get promoted to their own Strategy
  • Humans create, review, comment on, and own every other primitive; Memex learns who holds what expertise and routes the right work to them
This isn’t five separate tools stitched together. It’s one graph. Strategies give decisions and work items their purpose. Decisions are the leading edge, the ambiguity being resolved. Work items are the execution. Blueprints sit across all of it, the shared substrate every strategy runs on. Humans sit alongside, the people the system exists to serve and elevate.

​
Drift detection keeps it honest

One more mechanism is worth calling out on its own, the one that keeps blueprints current as the code and decisions evolve:

Drift Detection, the mechanism that kills the wiki

How blueprints stay current by default. Agent-reported drift, decision-triggered review, implementation-triggered review, and scheduled audits.

Join the waitlist

Memex AI is in early access. Come and be part of what we’re building, request access at memex.ai.