Skip to content

Manifiesto

Menu

Search the site

Reading path · Understand

Manifesto map

The core's cover page, its identifiers, and the complete journey through its nine divisions.

Version 2.1 · 2026-09

The core

Link to this section

This is the map of the manifesto core. The core is read in nine divisions, in order: each one brings together complete sections of the original document, without splitting or repeating them. “Next” takes you through the whole core, and the complete core can be downloaded from the footer of each page.

Canonical text · translation

PRODUCT AND DEVELOPMENT FRAMEWORK CORE

Core of the manifesto for human software development with artificial intelligence

Principles, product foundation, Job Stories and decision tests for building products centered on people's situated progress

We build tools to extend what people are capable of, not to display what software is capable of.

Version 2.1

September 2026

The nine divisions

Understand

  1. Manifesto map The core's cover page, its identifiers, and the complete journey through its nine divisions.
  2. The manifesto The problem the manifesto seeks to solve, who it is for, how to read it, where the core ends, and the text of the manifesto.

Decide

  1. Principles The manifesto's ten principles, in their canonical order.
  2. Product foundation What must be defined before building, and Job Stories as the reference form.

Build

  1. Building with AI Doctrine for developing with AI, the workflow, when to stop, and the agent contract.

Verify

  1. Verify Twelve dimensions for accepting a solution, a decision scorecard, and the signs that the product is moving away from the manifesto.

Put it into practice

  1. Worked example The complete method in one case: a calculus tutor for a person who does not yet understand.
  2. Governance How to turn the manifesto into a regular practice: responsibilities, checkpoints, evolution, and definition of done.
  3. Pocket guide Fourteen questions before accepting a decision, seven reasons to stop, and the manifesto's closing statement.

Download the core

Identifier index

Link to this section

Explanation

Every core obligation has a stable identifier, such as P03, CR05, or STOP02, which makes it possible to cite it unambiguously. The table shows their families; on the site, each identifier leads to the division where its passage is read.

Canonical text · translation

This navigation layer lets people, agents and adapters cite core obligations in a stable way. The identifiers add no doctrine, priority, stages, artifacts or criteria: they only point to content that has already been approved. A reference by identifier never replaces reading the passage cited, nor does it modify the authority of the text.

Family Identifiers Content
Navigation SH-INDEX Operational index and rule for using identifiers
Principles P01–P10 Ten commitments that govern decisions
Foundation SH-FUND Product definition, authority, scope and reference Job Stories
AI directives D01–D06 Doctrine for teams and agents
Flow F01–F08 Eight steps from the foundation to verification
Artifacts A01–A08 Eight documentary answers matched to context
Stop conditions SH-STOP, STOP01–STOP07 Conditions that prevent proceeding or accepting
Agent contract CR01–CR08 Reusable instructions for development
Agent output O01–O09 Expected content of results in natural language
Verification V01–V12 Dimensions of evidence for accepting a solution
Cross-cutting controls SH-SCORE, SH-AP, SH-GOV, SH-DONE, SH-POCKET Decision, anti-patterns, governance, done and short guide

Adapters may indicate which identifiers require attention in a particular operation. That selection guides what is loaded and does not authorize ignoring any other provision of the core that applies by reason of context, risk or contradiction.

Contents