The Program Statement

The "what" of an undertaking, written before anyone designs anything: the characteristics of the world to be built, the criteria by which it will be judged finished, and the major features required to bring it into existence.

Builders learned this the expensive way. Design begun before the need is written down produces something beautiful and wrong, and the argument about whether it is wrong then has no ground to stand on, because nobody wrote down what was wanted. So programming precedes design: first the statement of what this must do and for whom, agreed and open to challenge; only then the drawings (Design, Plans and Specifications, Conditions of satisfaction).

Applied to a whole civilization, the statement answers an unusual first question — why build anything at all? — and then describes the characteristics of the world to be built: the higher-order arrangement that integrates the underlying systems, resources, and energy into a functioning whole capable of meeting the needs of every person and community on Earth (Higher Order Functional Unity). It describes the programmatic parts of that arrangement and how they answer the whole spiritual, intellectual, and physical need, and it sets the acceptance criteria and major features the work must produce. It carries the design intent forward so that what is eventually built can be checked against what was actually asked for (The Intent, Commander's Intent).

Two properties matter as much as the content. It is living — continuously improved as the elements become clearer or are adjusted, never frozen at the moment of signing (Current Best Articulation, Work In Progress). And it is built from many minds: gathered over years through working sessions across domains and visits to see existing and desired conditions for real, rather than composed by one hand in one room. Its named sections run from why and the basis of design through intention, purpose and meaning, alignment, culture and values, right relationship, learning, wellbeing, living systems, land, air, water, infrastructure, governance, administration, economy, spirituality, reconciliation, the transformation of weaponry, and flourishing — which is a list worth reading twice, because it is what someone thought a civilization's specification must cover.

Also called: the Program Statement · the MPPS · programming precedes design · the "What" of the program Stands on: Design · Plans and Specifications · Conditions of satisfaction · The Intent · Everything Is A Project Opens onto: Design To The Goal · Work Breakdown Structure · Prototype · Kit of Parts · The Meta Project · Higher Order Functional Unity · Interoperability · Quality · Current Best Articulation In play: before any building — and at one table, in miniature: a Quest's "done" written down before the work starts, not after the argument Sources: LIØNSBERG Wiki Books/The Meta Project/Meta Project Program Statement/ — the root page and six sections (unmarked; the Audit Ledger's disposition is archive with provenance) · The Program Delivery Guide/Original IPD Guide/PDG - Program Definition (unmarked; source material dated by the Audit Ledger to a 2009 public-programme delivery guide) Open: Twenty-one sections are named; the folder holds six files, and none of them is the twenty-one. The instrument is a table of contents, not a statement. · Its development is dated from 2017 with an expansion between 2020 and 2022; nothing in it has been revised against what was learned since, so it should be read as that period's articulation. · The discipline (programming precedes design) is sound and inherited from building practice; this particular statement's content is the part that does not yet exist.