Purpose, Participation, and Judgment

The three Chirality theses — an iterative undertaking

The three theses examine how agent capability becomes purposeful work whose grounds and consequences remain open to understanding and correction. Root gives the argument its normative emphasis, the App its operative emphasis, and Piping its evaluative emphasis as an instance of domain software. Iteration connects them: experience can revise the work, its methods, and the understanding of its purpose. Each perspective also requires the others.

Start with the shared introduction. Read the Root chapters below, then the App thesis and Piping thesis. The worked example follows an illustrative undertaking across all three. The shared conclusion brings their contributions and remaining questions together.

Ontology, epistemology, praxeology, and axiology apply throughout this account. They ask what the work concerns, what supports understanding, how intent becomes usable action, and what makes its consequences worth pursuing. The glossary states the distinctions used across the collection.

Root's research question

What makes agent capability into purposeful, accountable work, and why should its supporting environment develop through revisable roles, methods, tools and artifacts?

Warrant status

This is explanatory, agent-drafted research under the owner's direction. It is nonbinding and does not establish regulatory endorsement, professional acceptance or a controlled productivity result. Development remains governed by the conversation, repository instructions and adopted product commitments.

Reading the Root thesis

The Chirality Framework presents the conceptual account in one document. Systems Engineering Design Analysis is its shorter technical companion. There is no Appendix B; current role instructions are indexed in AGENTS.md.

Source basis and historical editions

Product and implementation observations use repository revision a602024416ace9652f61bb2043889c307fd4e09d. Later development may change their standing. This revised manuscript does not advance the implementation evidence to its own publication revision. Regulatory discussion retains its identified July 2, 2026 basis and source editions. Older editions remain in Git; the development history identifies historical sources and distinguishes observations from the owner's account.

App v4's foundation copy retains its historical source basis unchanged. January–April history comes from the owner's account; surviving Git history begins with the migrated May snapshot.

Particular applications

All three carry the same kernel. Its formulas and approved definitions are unchanged; the interpretation follows the owner's clarification of temporal contingency. G remains undefined.