Concept
Building
How organisations construct Thoughtware without drowning in demos.
Cover for Building12 concepts in this section.
All sections
Illustration for Start from decisions, not from modelsWorkshop before wireframes
11 minStart from decisions, not from models
Teams that start AI work with model choice or feature lists build demos without architecture. This page owns the full framing workshop, decision map, terrain, leadership, and Thoughtware Map, before substrate is selected.
Illustration for Start from the result, not the feature listName the result first
10 minStart from the result, not the feature list
When teams start AI work with a feature list or model choice, they build demos without systems. This page teaches the outcome sentence and boundary, the second step in framing, without repeating the full workshop.
Illustration for Start with one bounded judgmentShip one call end to end
11 minStart with one bounded judgment
After framing names the outcome, the first construction move is one cognitive unit with a contract, evaluation suite, and declared gaps, not a platform diagram with nothing measurable.
Illustration for Abstraction does not remove responsibilityHiding does not transfer blame
10 minAbstraction does not remove responsibility
Generators, libraries, and agent loops make cognition easier to compose. They do not transfer ownership of outcomes, authority, or evaluation to the model or the tool that invokes it.
Illustration for Making the specification executableSpecs that compile to checks
10 minMaking the specification executable
A Thoughtware Map and specification hold framing. Making them executable means deriving runnable architecture with traceability, not slide decks that never become contracts, suites, and gates.
Illustration for The Thoughtware architectVocabulary above the code
9 minThe Thoughtware architect
Someone must own decision maps, cognitive unit boundaries, library strategy, evaluation policy, and human authority placement, not model selection alone.
Illustration for The Thoughtware specificationBeyond the feature list
10 minThe Thoughtware specification
A Thoughtware specification records outcomes, decision maps, cognitive units, memory, authority, and evaluation hooks, not a feature list dressed as requirements.
Illustration for From experimenting to governingFrom hack to gate
10 minFrom experimenting to governing
Pilots prove capability exists. Governing proves judgments are named, shared, evaluable, and owned when consequences grow, not before understanding is earned, and not after user complaints force it.
Illustration for Adopting cognitive units in existing codeInventory before framework
10 minAdopting cognitive units in existing code
Most systems already contain unnamed judgments inside prompts and scripts. Adoption names them, shadow-evaluates them, and cuts over incrementally, not by rewriting everything behind a new framework.
Illustration for Behavioural standards across teamsPosture that travels
9 minBehavioural standards across teams
Shared cognitive units without shared conduct produce one brand and many personalities. Standards must travel with libraries, not live as local prompt preferences.
Illustration for Premature disciplineName the judgment before the tooling
10 minPremature discipline
Full Thoughtware apparatus before the decision map stabilises kills learning. Discipline follows repeated eval and composition pain, not ambition, and not the first prototype.
Illustration for Loop compressionSettled work leaves the loop
9 minLoop compression
When applicability guards pass, expertise-backed strategy can replace full deliberation, explicit in code, eval-backed, and reversible when terrain shifts.