Skip to content

Chirality Library 3.0.0

Choose a tag to compare

@sgttomas sgttomas released this 08 Nov 02:57
5170575

Chirality Library 3.0.0

A major edition of the shared agent and instruction model: one continuing
INTERLOCUTOR alongside Agent 0, a common project entry route, and typed documents
that distinguish instructions, explanations, examples, proposals and historical
sources across the corpus.

Source: 5170575f3f4c1fc51386fa5cd38c7ef9ac048b20
Tag: library-v3.0.0
Archive: chirality-library-3.0.0-source.tar (785 tracked files)
SHA-256: fe7e5787a1a4812b8a3d56b19bfc59a2321c5f0e48f676c2ccc80c8c118a073c

The owner authorized this major release: “Publish this library as new version
3.0.0 because we've introduced a new agent type which is a fundamental difference
and with it comes many other significant changes to how the entire corpus relates
and evolves together.”

Changes since 2.1.0

Comparison: library-v2.1.0…library-v3.0.0,
from c35b7bbc463f81c1fed566c744ea49d168d29eee.

  • A continuing INTERLOCUTOR. First published as the fifth role in 2.1.0,
    INTERLOCUTOR now stays in one child session for the life of its paired Agent 0
    session. Start it once on session opt-in and continue summaries and advisory
    consultations in that same thread. Replace it only if lost or the owner asks.
    It reads Agent 0's actual conversation and keeps its own understanding across
    consultations. It remains a nondelegating Type 2 role, with advice rather than
    a veto, a three-round disagreement limit and consultation at least before every
    PR merge. Model and effort remain session steering. (#12)
  • One route into ongoing work. init/init-prompt.md loads standing authority
    from AGENTS.md and the operating route from top-level loop/LOOP_INIT.md.
    Operating steps and queries live in the loop; AGENTS retains standing authority,
    boundaries and reconciliation principles. The old coordination entry remains
    a compatibility pointer. (#10)
  • A shared project-entry convention. project-setup/resources/project-entry.md
    connects bootstrap, standing instructions, current work, local/shared methods,
    actual owner grants, and deliberate Library source selection. Applications
    maintain packaged instruction sources in a named deliverable's Work and generate
    shipped copies; the Library publishes its documents at their source homes.
    (#11)
  • Coordination suited to the actual host. The coordination method selects
    staffing by contribution, establishes delivered/retrievable context, gives full
    assignments and retains contributor ownership through repair. Completion and
    recovery use supported host mechanisms. Historical cases remain preserved.
    (#9)
  • Typed corpus metadata. A shared YAML header supplies name, description
    and metadata.kind/metadata.surface, with optional applicability and existing
    package fields. It covers 136 maintained entry, role, tool-guide, documentation,
    workflow and skill sources. Status, date and revision stay out of headers.
    The role validator accepts typed headers before its four prose sections; the
    renderer excludes headers from prose and hashes the complete source. The 22
    refreshed HTML editions preserve their article bodies and anchors.
    (#13)

Adopting 3.0.0

  • Keep one interlocutor conversation. Update any automation that starts a fresh
    advisor for every consultation. Independent reviews are separate contributions;
    they do not replace the continuing interlocutor. Sessions opt in individually.
  • Read YAML before the body. Role files and maintained guides may begin with
    ---, not #. Use the metadata contract
    and preserve the four role sections. metadata.kind describes document use;
    the method index's top-level kind still identifies workflow or skill packages.
    Existing role eligibility and method restrictions are unchanged. Consumers
    pinned to a four-role list must support the fifth descriptor already added
    in 2.1.0.
  • Use the entry route deliberately. Update current navigation to loop/LOOP_INIT.md.
    Copy only the <init-prompt> block for session bootstrap. Preserve your own
    authority, accepted layout and actual grants when adapting the convention.
  • Choose the source you rely on. Identify an edition or tracked line and record
    the resolved revision with dependent results. A checkout path alone identifies
    neither. Product builds/tests/CI remain independent of a sibling Library checkout.
  • Carry complete packages and notices. Preserve required resources, relative
    paths, local adaptations and LICENSE/component notices. Follow the
    consumer route.

Users coming from 2.0.0 should also read the
2.1.0 removal notice:
tools/undertaking_evaluation/ and the moved audit/evaluate-repository-change
workflows have no public replacement. This edition retains evaluation-protocol,
evaluation-report and tools/evaluation.

Verification and delivery

The integrated source equals the owner-approved head b68548463ee0cbd9362952e5b057e9037fa44cb2,
where Repository checks and harness both passed. The 1,126 affected tests and
lint passed during integration. All 785 archive file bytes and executable modes
were compared with immutable source Git objects and the extracted files.

From the extracted source, 189 metadata/role/resolver tests passed, five-role and
76-method index/workflow checks passed, standalone INTERLOCUTOR resolution retained
complete source and no unassigned writes or delegation, and an ineligible method
was rejected. All 23 included Markdown/HTML reading-edition pairs reproduced
exactly. The committed-change credential/symlink scan against 2.1.0 passed on
179 changed files with zero findings. SHA256SUMS covers the attached archive.

This is a complete source release for reading and in-place tools. It is not a
Python wheel; pyproject.toml retains its dependency-only package version. Tools
need their documented dependencies; Git-dependent queries need a clone with
appropriate history. Consumers choose adoption under their own project authority.