# 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](INTRODUCTION.md). Read the Root chapters
below, then the [App thesis](../../projects/chirality-app-v4/docs/thesis/THESIS.md)
and [Piping thesis](../../projects/chirality-piping/docs/thesis/THESIS.md). The
[worked example](WORKED_EXAMPLE.md) follows an illustrative undertaking across
all three. The [shared conclusion](CONCLUSION.md) 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](glossary.md) 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

| Chapter | Subject |
|---|---|
| [Front matter](00_front_matter.md) | Abstract, author's note and contents |
| [1. Introduction](01_introduction.md) | Question, contribution and limits |
| [2. Literature review](02_literature_review.md) | Precedents and scope of comparison |
| [3. Philosophical framework](03_philosophical_framework.md) | Four perspectives; reckoning, judgment and situated knowing |
| [4. Architecture](04_architecture.md) | Responsibilities, artifacts, queries and host boundaries |
| [5. Epistemic architecture](05_epistemic_architecture.md) | Evidence, uncertainty, interpretation and reliance |
| [6. Professional practice](06_professional_practice.md) | The bounded professional-practice interpretation |
| [7. Systems engineering analysis](07_se_design_analysis.md) | Design methods, contributions and limits |
| [8. Evidence and evaluation](08_implementation.md) | Observed implementation and limits of the findings |
| [9. Discussion](09_discussion.md) | Tensions, generalisation and evaluation |
| [10. Conclusion](10_conclusion.md) | What the case supports and what remains open |
| [Appendix A](appendix_a_invariant_catalog.md) | Historical controls and present interpretation |
| [Appendix C](appendix_c_apega_mapping.md) | Regulatory mapping and limitations |
| [Appendix D](appendix_d_framework_s.md) | Bounded philosophical conjecture |
| [Appendix E](appendix_e_development_history.md) | Development history, retired arrangements and lessons |
| [References](references.md) / [Glossary](glossary.md) | Sources and terms |

[The Chirality Framework](CHIRALITY_FRAMEWORK.md) presents the conceptual account
in one document. [Systems Engineering Design Analysis](SE_Design_Analysis.md)
is its shorter technical companion. There is no Appendix B; current role
instructions are indexed in [AGENTS.md](../../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](appendix_e_development_history.md) identifies historical
sources and distinguishes observations from the owner's account.

App v4's [foundation copy](../../projects/chirality-app-v4/foundation/thesis/README.md)
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

| Thesis | Subject |
|---|---|
| Root — this set | Shared means for developing work, methods and applications |
| [App v4](../../projects/chirality-app-v4/docs/thesis/README.md) | Workflow authoring and agent participation within applications |
| [SWBPIPE](../../projects/chirality-piping/docs/thesis/README.md) | Engineering design, numerical evidence and professional use |

All three carry the same [kernel](appendix_d_framework_s.md#d1-framework-relationships-with-respect-to-s).
Its formulas and approved definitions are unchanged; the interpretation follows
the owner's clarification of temporal contingency. G remains undefined.