Working map · v0

The words that define thought

Each judgment instrument names a question you answer before a thought is clear enough to share, build on, or act on. This page is one picture for review — we learn from using it and tightening what did not land.

Integrity stack (define knowledge): ontology → epistemology → taxonomy → nomenclature → axiology. Perception and perspectives feed the stack. Phronesis is fitting action after deliberation. Learning returns to the next read.

Relationship map

FEED → STACK → ACT → LEARNPerceptionWhat is happening?PerspectivesOntologyEpistemologyTaxonomyNomenclatureAxiologyTopologyPhronesisFitting actionActionLearningWHAT WE BUILDMeaningBriefMessageProduct

What these words mean for the build

MeaningOwn the instruments and evidence gates before anything public widens the claim.

BriefOne reader, one misconception, one free next step — then craft the page.

MessageThis site expresses; it does not invent warrants. Strangers meet the thought here.

ProductNames, routes, and receipts must stay aligned or agents and teams drift apart.

Perception

What is happening here?

Observations before interpretation. Name what is seen and what signal is missing.

In the buildBriefs and reviews start with facts, not slogans.

Perspectives

What shows from this lens?

Declared views and dissent. Many lenses do not mean many truths.

In the buildMatrices and roles challenge blind spots; they do not inherit your purpose.

Ontology

What exists and relates?

Entities, relationships, boundaries. You cannot reason about what you have not named.

In the buildAgreement on what is in the product before architecture arguments.

Epistemology

How do we know?

Evidence, confidence, unknowns, falsifiers. Separate observed from assumed.

In the buildReceipts and proof — why a move was allowed, not only that it shipped.

Taxonomy

Where does it belong?

Class and owner. A tool is not an agent; a receipt is not a log.

In the buildOne owner per subject in the site and in the platform.

Topology

How should it connect?

Boundaries and paths across a connected system.

In the buildHow pages, capabilities, and traces find each other.

Nomenclature

What do we call it?

One concept, one name humans and agents can decode.

In the buildRoutes, labels, and stable IDs that expand back to meaning.

Axiology

Why does it matter, for whom?

Beneficiary, good served, protected constraints.

In the buildPrinciples and values — what must not be traded away.

Phronesis

What is the fitting move here and now?

Practical wisdom in action — not another box in the stack.

In the buildSmallest responsible next move before the moment hardens.