Chirality library 1.1.0

Chirality library 1.1.0

Source: 897f98417d8a83f0bf93445b5bcf3a07672cb91b
Tag: library-v1.1.0
Archive: chirality-library-1.1.0-source.tar (1,083 files)
SHA-256: ac115b90083a0f5541712c05198e91f95f91d9c12717fda3ec39856223a55918

The owner authorized this publication: “I approve publishing v1.1.0”.
The attached source archive and SHA256SUMS identify the delivered material.
The archive retains preparation-era wording at its exact source; this release
records the subsequent publication decision without changing those bytes.
Publication does not assert full R18/A9 fulfillment.

The comparison basis is published 1.0.2, source
59433388627773f008f550481c4159514f43c7e5. The functional and instructional
changes below are integrated through e57e0b783cc50a354819bc83bd38bd86a063ad77;
the publication preparation reconciles their current descriptions and adds bounded report
rendering evidence. Earlier editions retain their bytes and original standing.

What changes for a consumer

• Optional repository-change evaluation. PR #1799
  adds a local CLI and
  evaluation workflow.
  Inspect selected committed Git states, bind supplied outcome evidence, optionally
  import selected Codex response-usage records and compare identified reports.
  The tool exposes observations and limits; it neither judges improvement nor
  starts agents or adopts methods. PR #1798
  adds DEL-03-02 and extends DEL-04-02 under accepted PRD R18/A9. Acceptance of
  that scope is distinct from fulfillment of the new capability.
• Current-locality scope amendments. PR #1797
  gives scope-change, audit-scope-closure, project-setup and scope-of-work methods
  an explicit route for current ScopeOfWork/Work/native-needs localities. It avoids
  imposing retired lifecycle files on that route. Retained legacy contracts keep
  their applicability; the selected project's actual authority still governs
  commitment changes.
• Courses for sustained and delegated agent work. PR #1795
  repairs stale course-entry rendering, qualifies memory/capability and historical
  claims, and distinguishes authorized agent actions from human accountability.
  Courses 08 and 11 add optional coordinated-agent examples; Course 10 adds a
  separately labelled post-acceptance exercise. Course 12's production-involvement
  and examination rules cover agent-written briefs and consequential returns
  relied on, without requiring every child transcript. Instructor companions and
  reading editions align with these changes. The Northbank case records and
  numerical answers are unchanged. Instructors should read the revised Course 12
  rules and companion before assessing new work. No App course integration is
  claimed.
• Book subtitle. PR #1796
  adopts the author's title, Chirality in Practice: Extending Human Capability
  with Agents, in the Markdown and rendered book. The argument and reflective
  character are unchanged. The book is not a replacement for project instructions.

Use and dependencies

Obtain the complete source archive of this named release, or clone its
exact tag/commit. Preserve relative paths, resources, MIT notice
and applicable component notices. Start with the
consumer route, then the
selected holding's own guide. Reading the book, courses and workflows requires
no Git or private operational records. Agents can read their maintained Markdown.

The new evaluation CLI needs Python 3.10+ and Git, using only the Python standard
library. Repository inspection requires actual Git commit objects: an extracted
source archive alone does not contain the Git history being examined. Supply a
separate authorized Git repository, or use a clone. Workflow selection through
the existing resolver retains its own documented dependencies and host limits.

inspect and compare create private report.json and report.html files in a
new directory outside Git working trees; its parent must already exist. Inputs,
raw records, assessments and derived reports remain private unless separately
examined and authorized for disclosure. Preserve the original inputs while their
findings need to remain inspectable. The public source and tests contain no
private pilot records and ordinary use needs no undisclosed sibling checkout.

Qualification and adoption limits

The supported first record adapter reads explicitly selected Codex desktop JSONL
per-response token_usage_record events. It does not establish support for all
host versions, full-session coverage, monetary cost, elapsed work or human
attention. Committed-file observations do not establish behavior or value.
Working-tree capture, a trial runner, automated semantic evaluation and automatic
method adoption are not supplied. Output precautions are not a sandbox against
hostile concurrent processes.

The first actual private Library-maintenance comparison was inconclusive: its
case omitted a governing amendment contract, and an independent assessor withdrew
a categorical ranking. The useful finding was the missing case basis, not an
efficiency gain. Full R18/A9 fulfillment remains unestablished. Representative
HTML reports have subsequently been examined in a browser using labelled cases
over public source; this is representation evidence, not renewed examination of
the private pilot or a reader-comprehension study. See
the owning evaluation basis.

These additions require no automatic migration or consumer adoption. Compare the
exact source you use with this release through the existing
change-inspection route.
Select only applicable changes under your project's authority. Root's grants,
acceptance and release do not transfer to App, SWBPIPE or another consumer.
Historical sources remain recoverable through Git, earlier releases and the
recovery guide. Publication does not establish downstream notification delivery or adoption.

Verification

Independent Astra review found no integration blockers on preparation head
d1e1e0d4982ef1f8931c5858fb87df7cadad58eb; Repository checks and harness passed
on that exact head. The integration tree matches it. The final archive's 1,083
paths, blob bytes and executable/symlink modes were verified against the source
commit, including its Git archive identity.

All 30 evaluation tests passed from extracted source on Python 3.13, and the
evaluation workflow resolved from the extracted resources. Native dependency
structure had no errors and retained five external-input unknowns. Scope format,
workflow metadata, local file-link targets, conflict and credential checks passed.
The local private-term set was unavailable; the hosted required-secret check
passed separately. Earlier applicable implementation evidence was reused.

Preparation and independent review: PR #1800 ·
Changes from 1.0.2

Chirality library 1.0.2

Chirality library 1.0.2

Source: 59433388627773f008f550481c4159514f43c7e5
Tag: library-v1.0.2
Archive: chirality-library-1.0.2-source.tar (1,056 files)
SHA-256: 669e358f7b4a9a17a877fe44593af1a24b7e9cc2e66893a842d652c21935be97

The owner authorized this release: “Publish new version 1.0.2”.
The attached archive matches the identified Git source and executable modes.
SHA256SUMS supplies its checksum; tracked resources and notices are retained.

What changed from 1.0.1

Chirality in Practice now presents its purpose and arguments independently of
previous Project Management Manuals. Predecessor framing, editorial-lineage
commentary and incidental manual-history passages have been removed. Development
positions and constructed examples are explained directly. The thesis and actual
case sources still ground the account, including the documented connection from
project experience to shared guidance.

The README and publication index present the book independently. Historical manual
sources and existing anchors remain available outside its narrative. Root's
reflective scope now calls for a source-basis note rather than a lineage note;
its current authoring need and required comparison with v9 have been removed.
The optional reflect-on-work reference selects the revised book source.

This is an editorial and source-relationship update. It changes no executable
tool, host permission or product behavior, and introduces no new reading duty.
Existing releases, selected consumer sources and historical manuals are unchanged.

Read and use

Read the book's Markdown
or extract the source archive and open
docs/alignment-manual/Chirality_in_Practice_Edition_1.html for its reading edition.
Keep the source tree together to preserve local references and resources.
The rendered book identifies its exact Markdown source at 360a2d5050302e27c143e6c76bd367f2d94b0072.

The consumer entry
explains version selection, resources, release subscriptions and update inspection.
Each consumer decides whether and when to adopt this edition.

Verification and limits

Required Repository checks and harness passed on exact PR head
fa87b8368ce1b8705540b9283731ba3f8a67778d; the integration tree matches it.
The maintained renderer reproduces the HTML from its committed Markdown.
Local checks covered 156 links/fragments, scope format, workflow-index freshness
and native dependency structure (7 deliverables, 63 needs, no errors and two
existing unknown observations). The archive's 1,056 files match Git bytes/modes.
Credential and local private-term screening found no issues using 3
available local patterns; hosted coverage is separate.

Earlier scoped behavioral evidence remains applicable to unchanged implementation.
No new product execution, reader-comprehension test or consumer adoption is claimed.

Change and verification: PR #1794 ·
Source comparison

Chirality library 1.0.1

Chirality library 1.0.1

Source: 73912ca8b46d8e13b4978904f2e02110b35bb33c
Tag: library-v1.0.1
Archive: chirality-library-1.0.1-source.tar (1,056 files)
SHA-256: 95090580fe6a7a018f201c5b46ec194e693a4a40e7872c99747e5ea8c2e9683a

The owner approved the complete book and connected library changes and authorized
this release: “Approved. This will increment the published library to v1.0.1”.
The attached source archive matches this revision's Git blobs and executable modes.
SHA256SUMS identifies the archive. All tracked resources and license notices are retained.

What changed from 1.0.0

• Chirality in Practice, first edition: Reflections on Purposeful Work by People and Agents.
  The book develops the thesis through practice, documented cases and reflection,
  including work after completion. It describes cross-project learning as a direction
  being developed through occasional owner-mediated experience, not an established system.
  Clearer wording applies STE-100 principles without claiming formal compliance.
• Clearer consumer entry. The README explains choosing material and a version,
  subscribing to GitHub releases or the Atom feed, and inspecting updates before adoption.
  Practical roles and methods remain separate from the book's reflective purpose.
• A bounded reflective connection. Root's reflective deliverable explicitly includes
  the book. The reflect-on-work method adds one optional link to its exact Markdown source.
  No mandatory reading, recurring project report or new host permission is introduced.

The approved book's source commit is b31e06213ba7c8d2b16d0d87284dac7f25d6307e.
Its rendered HTML contains the corresponding source hash. Approval and release annotations
are later repository changes; they do not alter the reviewed book bytes.

Read and use

Read the book's Markdown
or download and extract the source archive, then open
docs/alignment-manual/Chirality_in_Practice_Edition_1.html for the self-contained reading edition.
Keep the extracted tree together to retain the book's local source links and resources.
The publication index
distinguishes the reflective book from the retained agent-addressed Project Management Manual v9.

Use the consumer guide
to select materials and inspect updates. Existing v9 uses remain valid at their chosen basis.
Library 1.0.0 retains its original tag and archive. Each project decides whether to adopt 1.0.1;
copying the library transfers neither Root authority nor product permissions.

Evidence and limits

The manuscript received repeated Claude Opus 5.5/high consultation, parallel source-grounding
research and comparison, a Claude wording proposal, and Agent 0's full meaning assessment.
Actual documentary episodes remain distinct from constructed examples. This is not new
App/SWBPIPE product qualification, a controlled productivity study or a reader-comprehension test.

The deterministic renderer, source bindings, local links/fragments, workflow metadata/index,
scopes and native structure were checked. Existing catalog-test evidence applies to unchanged
selection behavior. Required hosted checks passed on the integrated PR head, and its tree
matches the release integration tree. Archive screening found no credential or local private-term
findings using 3 available local patterns; hosted coverage is separate.

No executable tool or product behavior changed. Tool dependencies and the selected-use limits
from 1.0.0 remain applicable. The book is material for understanding and questioning practice,
not a replacement for a project's actual commitments and selected instructions.

Full source comparison ·
Consumer-entry change #1792 ·
Book and reflective-scope change #1793

Chirality library 1.0.0

Chirality library 1.0.0

Source: fc73de583d25bf792d5c3abb3bf1ac8e0c38f7d6
Tag: library-v1.0.0
Archive: chirality-library-1.0.0-source.tar (1,054 files)
SHA-256: e75ce1396e8bb92d4e2f144ba13336ee93a7ad7579494b2a6d21117857733567

The owner approved acceptance and public release of this exact source edition.
The attached archive matches its Git blobs and executable modes; its checksum
is also supplied in SHA256SUMS. Required hosted checks passed on the integrated
PR head; the merge tree matches it. Credential and three available local
private-term patterns found no issues in the archive. Hosted coverage is separate.

What this edition provides

Chirality is a source library of principles and publications, agent roles,
workflows, executable tools and their usage instructions, shared references, and
its own maintenance execution material. It supports people and agents locating,
maintaining, examining and reusing identified holdings under their own authority.
It requires no companion application merely to read or use its instructions.

The delivery is the complete tracked source archive of the approved
publication revision. Historical and Root-only holdings retain their stated
standing; inclusion does not make every archived tool a supported current product.
The exact source commit and archive SHA-256 are identified above.
The candidate PR identifies the reviewed source and locally checked archive;
any later integration revision needs its own correspondence check before release.

Obtain, use and inspect changes

Start with the repository README.
For a published edition, obtain the source archive attached to its named release
or the repository archive of the exact published tag/commit. Preserve its source
identity, original relative paths, required resources, MIT notice
and applicable component notices. A clone is useful for Git-dependent tools;
ordinary file reading does not need Git. Selecting an unpublished commit or main remains an explicit development choice.

Read each holding's applicability and limits. Preserve a selected workflow's
complete package and its required resources.
For maintenance of Root itself, enter through AGENTS.md
and its linked loop. Consumer projects choose their own instructions and authority;
copying the library does not transfer Root's grants, project governance or hosts.

Use the change-inspection procedure
to compare the exact basis in use with this edition, read the applicable
change accounts and examine affected local uses. Inspection does not adopt an
update. Historical sources remain recoverable through Git and the
frozen-project recovery route.

Consequential changes in this development increment

This account covers the integrated library development in PRs #1779–1789, through
35273905a90ee6c1032a7f49db2236ed19371029, plus the publication preparation in
PR #1790. It is not a comparison against a previous published library version.
Each PR retains its actual preceding basis and validation; the following links
are the change accounts for the individual changes.

• Current maintenance setup and discovery. #1779,
  #1780 and
  #1781 connect current locality
  preparation, seven accepted deliverables, consumer-local needs and the entry.
  Explicit current setup preserves existing work and does not manufacture blank
  acceptance contracts. Retained legacy routes keep their compatibility standing.
• Accurate tool prerequisites. #1782
  makes the native queries' required --project argument explicit.
  #1787 documents that resolver
  --brief needs PyYAML even for JSON input; without it, normalization currently
  raises an import traceback. These are usage repairs, not new host capabilities.
• Shared reference applicability. #1783
  clarifies current Work locality and the scope of historical product contracts.
  Current ScopeOfWork format validation remains current, not legacy-only.
  Shared definitions do not appoint a runtime provider or impose Root authority
  on independent consumers. Existing adopted clauses and pins retain their basis.
• Consumer use. #1784
  supplies obtaining, resource-preservation, source-identity and update-inspection
  guidance, with a bounded named App-reader case. #1787 extends the examined
  delivery subject to a complete source archive and selected standalone operations.
• Retired Git layers and focused reflection. #1785
  removes workflows/change/ and .agents/skills/chirality-change/.
  Explicit selections of these packages and legacy CHANGE fail; there is no
  canonical successor or silent fallback. For ordinary authorized work, use the
  actual brief and applicable repository conventions. Root's concise Git rules
  remain in AGENTS, with detailed recovery guidance
  loaded when needed. Historical enum/schema identities and source pins remain
  unchanged. The distinct reflect-on-work
  method supports human–Agent 0 examination of purpose and practice; it grants no
  authority and is compatible with HELP_HUMAN, HELPS_HUMANS and WORKING_ITEMS.
  TASK can supply evidence through its caller, not select ownership of this method.
• Evidence and current standing. #1786,
  #1788 and
  #1789 reconcile bounded
  discovery evidence, adopted method/publication bindings and the owner's gate
  decisions. Those decisions do not themselves accept or publish the product.

Dependencies and qualification limits

Consult the selected tool's guide before execution. Preparation uses zsh and
Python/PyYAML with the documented helper/module resources. Native deliverable
queries need Git, a resolvable HEAD and PyYAML; an archive supports direct reading
of declarations but not computed reverse links or Git observations. ScopeOfWork
utilities retain their shared common.py and id_catalog.json. Workflow resolution
needs roles, registry, catalog, selected packages/resources and applicable legacy
maps; structured briefs additionally require PyYAML. Resolution selects context
and composes policy; it does not launch work or enforce host permissions.

The owning evidence establishes exact archive correspondence
and selected extracted-source operations on the observed platform. Broader runtime
or cross-platform qualification is not claimed. The named App reader case covers
capture, declaration and content identity at the recorded revisions; it does not
establish registration, execution, adoption or all consumers' compatibility.

The seven deliverables' 44 criteria have bounded applicable support as described
in the roadmap and owning Work. Actual maintenance repairs, the F-02 counterexample
and repair, and adopted reflection supply substantive use evidence. The fresh-reader
amendment brief was hypothetical. Eight maintenance operations were examined as
routes, not all executed separately. The labelled custody case used the same
holder and maintainer; transfer, timeout and enforced exclusion were not established.
Procedural coordination is not filesystem exclusion. No productivity improvement
was measured.

Incompatible reinterpretation of adopted shared clauses remains held until the
actual consumer basis is bound. Independent consumer adoption, frozen-product
reactivation, further archival disposition and bespoke tooling are not implied.
Local public-content screening and hosted private-term/secret-set checks have
separate coverage; the candidate's check results identify their actual subjects.

Continuing responsibility and release standing

Root maintains the shared source and change explanations. Consumers retain their
selected source, local adaptations, product operations, acceptance and adoption.
Interrupted Root work follows the existing maintenance recovery instructions;
elapsed time alone grants no right to discard retained work.

The owner approved final acceptance of this identified library result and its
public release as library-v1.0.0: “I approve both decisions.” Consumer adoption
and reliance remain independent. The source archive retains the pre-release
standing recorded before that decision; this release records the subsequent
acceptance and publication without changing the approved source bytes.