Skip to content

Releases

Chirality Library 3.4.0

Choose a tag to compare

@sgttomas sgttomas released this 12 Nov 03:29
1bba3d1

Chirality Library 3.4.0

A scope of work now leads and a deliverable is two files; every project's AGENTS.md can carry the same two passages on how work and agents are organised, with the project-entry template as their source. The entry layer and the way agents are organised changed in this edition: it is not a guidance-only revision, and a project on the three-file entry layout must change that layout to adopt it.

Source: 1bba3d170e7a25bc2a04e0a4dfe77b624ea440ca
Tag: library-v3.4.0
Archive: chirality-library-3.4.0-source.tar (779 tracked files)
SHA-256: b4f0ec20b5e9a26125a16002e95895e5171ebeb6d4e44664e400f18dfe9eb7b5

Changes since 3.3.0

Compare editions. The changes are in pull requests #31 to #41 and #43; each describes its own change.

Scopes of work and deliverable localities

  • The scope leads. workflows/scope-of-work/WORKFLOW.md opens with a new section, "What a scope says": what each of a scope's six parts holds, that code is measured against the scope, and that a decision appears only as the current statement it settles. "Requirements and their grounds" and "Changing a statement" replace the earlier list of where an expected result comes from; decision labels, dates and quoted approvals no longer belong in a scope. The revise step no longer writes an amendment record into the scope. A new "Verification entries" section has each entry written or changed from now on state its kind: an executable check, a comparison with a named reference, or a judgment by a named role. An unchanged entry without a kind fails in no mode. The method also adds an independent reading: a reviewer who did not write a scope, and does not see the writer's reasoning, reads it against the PRD and decomposition, the code it represents and neighbouring scopes.
  • The scope validator no longer requires a revision pin. In 3.3.0, tools/scope_of_work rejected a scope whose decomposition_basis did not bind a path and a revision with @. That check is removed. A scope with a pin still validates. A scope written without one fails the 3.3.0 validator and passes this one, so a project whose scopes follow the changed method needs this edition's tools.
  • A deliverable locality is ScopeOfWork.md and deliverable.yaml; there is no Work/ folder. Scaffolding (tools/scaffolding) no longer creates or requires Work/; an existing Work/ folder in a consumer's locality is tolerated and left untouched. The deliverables guide, bounded-reconciliation, dependency-extract, define-work, construct-local-work-graph, the audit and estimate workflows and the preparation skill no longer read or write it. scope-change-packet returns its result instead of writing a run record. docs/PRD.md R08 defines the locality the same way.
  • Needs. bounded-reconciliation and the entry passages have a contributor correct a need the work showed to be wrong, missing or no longer applicable, in the same pull request. dependency-extract states that a need is not removed for being met, and adds when where the source states when the need applies. A need's condition is now written as what the neighbour observably provides, in the provider's product terms, and tested by asking which acceptance criterion in the provider's scope makes it true; where none does, the need creates no obligation on the provider and the gap is returned. The workflow and the deliverables guide no longer document the optional evidence field of a need; the tools were not changed to reject it, so existing declarations that carry one need no edit.
  • How work will be known to be done. software-decomp gains a section 9, "Examination and Integrated Path" (each deliverable's expected examination, each objective's check, the thin end-to-end path, any coupled core), for decompositions begun under this text, and now states its conformance rules in the package: where ambiguity remains, the package's stated purpose governs interpretation, in place of the rationale of a standard held outside the Library. software-test-planning returns a check of stated kind for each claim in a criterion and says how a miss would fail it. coordinated-knowledge-work carries the criteria and the check in the brief and establishes the combined check first. In current project setup and package activation, where the project's own standing instructions call for independent scrutiny of a class of change, someone who did not write a verification entry asks whether it could pass while its criterion is unmet, before dependent implementation relies on it. That follows the project's existing scrutiny rules and is not a setup gate.

Entry instructions and how agents are organised

  • Two-file entry layer. A project's entry is a root init-prompt.md and AGENTS.md (with CLAUDE.md containing @AGENTS.md). There is no init/ folder and no loop/LOOP_INIT.md; what the loop entry held is in AGENTS.md. The Library's own entry documents follow this layout.
  • The project-entry template is the source of two common passages. workflows/project-setup/resources/project-entry.md holds "How the work is organised" (packages, deliverables, scopes of work, needs, code paths, the two queries, and when a scope, a need or a criterion is corrected or taken to the owner) and "How agents are organised" (Agent 0, Type 1 and Type 2; assignments and returns; independent review; the INTERLOCUTOR; which role text each relationship loads). A project copies them word for word and fills two named slots: its list of deliverables, and what <query> is there. The template's shared text no longer carries the role table, the working cycle or the criterion paragraph, which the passages replace.
  • What the passages change in meaning. A Type 1 agent is started in a new thread of its own, at the same level as Agent 0's, and the owner may work with it directly; a Type 2 agent is delegated as a child and starts no other agent. "Delegate" is kept for a Type 2. A Type 1 may start another Type 1; any agent may message any other, with assignments and returns usually following the line of assignment. Each independent review is a fresh reviewer. Models and effort come from the owner's steering for a session and are named in no file.
  • Section order, postures, rules and grants. The template gives an order of sections for AGENTS.md; two postures a project may select for a phase ("finishing toward a target" and "pruning and honing"); and a rule that a rule in AGENTS.md stands on its own, with the owner's words kept only where they are a grant and define its extent or conditions.
  • What the finishing posture requires of a project that selects it. The posture is reusable and the grant is not: a project selects it only where its owner has delegated the decisions it describes, and inserts that grant itself, in the owner's words. Everything in it applies within the extent, conditions and reservations of that grant, including any limit on passing those decisions on. A Type 1 agent decides how the work within the locality of its assignment is done and takes a changed commitment, criterion or hold to Agent 0. A decision's record names the agent that decided, never the owner; and a criterion that requires the owner as actor is corrected in its scope, with its review, before it is relied on. The posture changes no verification, required check or independent review.
  • Entry-prompt check. init-prompt.md confirms that the checkout's AGENTS.md is the one on the repository's default branch and reports a difference before relying on it. A project working toward a release target also asks the first report for the path to that target and what it needs from the owner.
  • Root relationship. The template's shared text states what Root may do in a project: read session telemetry read-only and segregated by repository; change the project's files within work the owner has authorised, through a pull request there under the project's own instructions, checks and Git grant; and open an issue for an approved finding. In 3.3.0 the template said Root changes no files in a project.
  • INTERLOCUTOR. agents/AGENT_INTERLOCUTOR.md describes a Type 2 child that Agent 0 starts within its own session and continues by message, replaced only if it is lost or the owner asks; in 3.3.0 it described a separate paired session. In each review round it examines the findings and the proposed response against the undertaking's purpose and the earlier rounds before the response is settled, including rounds a Type 1 runs.
  • HELP_HUMAN. One sentence is removed from agents/AGENT_HELP_HUMAN.md: "Keep a replaceable recovery note only when needed."
  • Packaged product instructions. The template tells an application that bundles agent instructions to keep canonical runtime assets in the product's source locations and list the maintained and shipped paths in deliverable.yaml; it no longer asks for a master copy in Work/.

The retained setup route

  • project-setup-retained is a new workflow package. It holds the retained DOMAIN and legacy phase and control-file contract and method that 3.3.0 kept in project-setup. It is selected explicitly with Workflow: project-setup-retained; existing files alone do not select it. Its DOMAIN and semantic phases are restored against today's pac...
Read more

Chirality Library 3.3.0

Choose a tag to compare

@sgttomas sgttomas released this 08 Nov 19:24
ec3ee2d

Chirality Library 3.3.0

Projects can identify the Library source and published edition their adapted documents were last reconciled against, and use a small workflow to compare and discuss differences. Project-entry is the single source of shared entry wording; Library AGENTS is an adaptation of it too.

Source: ec3ee2d1b398eba1fb3227ccf93e2569df95bacd
Tag: library-v3.3.0
Archive: chirality-library-3.3.0-source.tar (788 tracked files)
SHA-256: e3db320a1d6b7b69dcb2e71d171849904189da1ce7666aa522ae91d6b98c3b20

Changes since 3.2.1

Compare editions. All changes are in PR #30.

  • Optional derivation metadata: metadata.upstream contains source and edition. The edition identifies the published Library basis last reconciled against, not the project document's own version or its overall Library selection. Existing headers remain valid; status/date/revision exclusions remain. Field definition · Schema.
  • Compare Library derivations: one workflow maps real sources, compares old/current/target content where available, discusses consequential differences and records justified dispositions. Deliberate adaptations can remain. Workflow.
  • Canonical template: project AGENTS.md, init/init-prompt.md and loop/LOOP_INIT.md derive from the relevant project-entry sections, including Library's own entry documents. Shared wording is no longer sourced from Library AGENTS. Local grants, delegations and reservations stay local.
  • What the repository keeps: the template now states the retained-work, recovery, source-of-instructions and scratch boundaries. Library standing instructions add ephemeral session discovery and the no-memories rule. Current sessions are found through T3 thread listings.

First comparison when adopting 3.3.0

Run the comparison at Library-release adoption or when explicitly selected. Either the project's Agent 0 or the coordinator may run it under actual authority; the project's Agent 0 makes edits and integrates. Use the existing conversation, PR or Work location for results.

  1. Select the 3.3.0 Library basis through the project's adoption route and identify the adapted files to compare. Keep separately pinned product assets on their own route.

  2. Load Workflow: compare-library-derivations from that Library. The bundled identity is source=bundled, sourceRootId=chirality-root, kind=workflow, name=compare-library-derivations. The ordinary resolver can load it, for example:

    python3 "$INSTRUCTION_ROOT/tools/workflow_runtime/resolve_workflow.py" \
      --root "$INSTRUCTION_ROOT" --role HELP_HUMAN \
      --workflow compare-library-derivations
  3. Map project entry documents to the relevant workflows/project-setup/resources/project-entry.md sections. Map an adapted project workflow to its actual Library source. Read directly consumed roles and methods at the selected basis.

  4. Compare prior Library source, current adaptation and 3.3.0 source. Without a known prior reconciliation, make a fresh two-way comparison and state the historical attribution gap. Discuss each consequential difference: retain locally, change locally, propose upstream, or leave unresolved.

  5. After the whole document is reconciled and required local changes are checked, add or advance the optional field for that document. Retain its existing name, description and applicable kind/surface. For an adapted project AGENTS, the metadata fragment is:

    metadata:
      kind: instruction
      surface: standing
      upstream:
        source: workflows/project-setup/resources/project-entry.md
        edition: library-v3.3.0

A partial comparison leaves an existing field unchanged; omit it where no justified source/edition pair exists. Use source inspection and the actual comparison to justify the pair; the schema checks its shape. Adopting the edition alone does not set every document's reconciliation basis.

Verification and delivery

The merge tree equals checked head 74150aee29f3c587d0badbee5e1c0e50277d45d1. Repository checks and required harness passed on that exact head, including 546 selected tool tests and 61 routing/workflow checks. The design used HELPS_HUMANS and create-workflow and received owner content approval with option A and the comparison defaults.

All 788 archive entries match Git and extracted bytes/executable modes; full-archive credential and symlink screening passed. The extracted source passed 230 schema/role/catalog/runtime tests, metadata/index validation and resolution of the new workflow. SHA256SUMS covers the attached archive. No source changes were added for publication.

Read source files directly or run tools with their documented dependencies. Git-dependent queries require a clone with suitable history. Publication leaves consumer selections and separately pinned product assets with their owning projects.

Chirality Library 3.2.1

Choose a tag to compare

@sgttomas sgttomas released this 08 Nov 18:42
fd7015b

Chirality Library 3.2.1

Work holds the current account, revised in place; execution narration belongs in the PR. The shared paragraph is included in Library standing instructions and the project-entry template, preserving frozen and accepted evidence.

Source: fd7015bb96902c1ea4ec4714ef30972d81d92f15
Tag: library-v3.2.1
Archive: chirality-library-3.2.1-source.tar (787 tracked files)
SHA-256: 913e0d713c0fa7058b6c6b4290495d63bf6becafca17ec87480e1e74487cd560

Changes since 3.2.0

Compare editions.

  • Work and PR guidance: keep findings and reasons current, retain hashes when they bind relied-on inputs, state facts once, and keep approval/review/check narration in the PR. Both AGENTS and the project-entry resource use the owner-approved paragraph. #29
  • Coordination discovery: remove the private cross-project index pointer from Library AGENTS; existing direct Agent 0 messaging remains in place. #29
  • Selector policy: a header comment states the independent-review requirement for narrower coverage and the unknown-path full-coverage rule. This comment changes no selector behavior. #29
  • Inherited execution layout: already-integrated #28, which followed 3.2.0, moves the unchanged Rust reproduction to tools/workflow_runtime/fixtures/app_workflow_reader.rs, repoints its live consumers, adds the always-run execution-boundary guard, and routes declarative/historical inputs to structural checks. Unknown inputs still select full coverage. The guard detects recognized source-placement patterns; it does not trace arbitrary dynamic execution.

Verification and delivery

The source is #29's merge commit; its tree equals approved head 98855d012c4a7b136d036a3d0a1b2b37f9b16d19. Both hosted checks passed on that exact head, including all 1,187 tool tests. The inherited #28 coverage narrowing received independent review. No source changes were added for publication.

All 787 archived files match Git and the extracted files in bytes and executable modes; full-archive credential and symlink screening passed. The extracted source passed 62 role/workflow-runtime/catalog tests plus instruction/workflow metadata and index validation. SHA256SUMS covers the attached archive.

This publication changes no project's selected Library revision or separately pinned product assets. The shared checkout remains at 3.1.0. Read source files directly or run selected tools with their documented dependencies; Git-dependent queries require a clone and suitable history.

Chirality Library 3.2.0

Choose a tag to compare

@sgttomas sgttomas released this 08 Nov 15:18
95ad289

Chirality Library 3.2.0

All five roles now carry reporting guidance in their own files: lead with the outcome, summarize decisive evidence, offer real choices, and state material limits and the next actor once. Each role remains usable on its own.

Source: 95ad2891d5a9212e21bcd71fdd8c7475cf2e5c39
Tag: library-v3.2.0
Archive: chirality-library-3.2.0-source.tar (785 tracked files)
SHA-256: 67708ea749de5dee89e47065b820efe3bbe4ae12b2c7e541d2d302e5143adfb5

Changes since 3.1.0

Compare editions.

  • Reporting guidance: TASK, WORKING_ITEMS, HELP_HUMAN, HELPS_HUMANS and INTERLOCUTOR include the guidance inline. Short advisory replies stay short. The five copies serve self-contained role delivery and should be updated together. #26
  • Deliverable records: current accounts replace stale progress and approval/check narration, retaining historical findings, methods, source identities and limits. Protected evidence and edition outputs keep their bytes. Approved scope descriptions reflect the bounded work. #17, #18, #20–#25
  • CI: input rules follow actual consumers, distinguish guides from code and provision selected dependencies. Any unknown path selects all suites and standalone checks. Regression and tracked-path completeness checks protect the routing; the aggregate harness requires selected verification to finish successfully. #16
  • Library–Root ownership: the standing entry links the governing retained Library obligations and R18 transfer records. #25

Adoption

Compare the roles, instructions and packages your project selects against its current edition. Adopt through the project's own selected-release route, retaining source identity, required resources and license notices. Keep separately pinned product assets at their selected revisions.

The typed-header schema and role eligibility are unchanged. No additional header migration is needed. The consumer route describes obtaining and inspecting updates.

Verification and delivery

The release tree matches the checked #26 head. All five role-only resolver contexts include the guidance; 514 selected tests passed. Required hosted checks passed on every integrated PR head, and independent fidelity reviews covered the deliverables cleanup.

All archive bytes and executable modes match Git and the extracted files; the full archive passed credential and symlink screening. The extracted source passed 183 metadata/role/resolver tests and workflow/index validation. SHA256SUMS covers the attached source archive.

Read the archive directly or run selected tools in place with their documented dependencies. Git-dependent queries require a clone with the appropriate history.

Chirality Library 3.1.0

Choose a tag to compare

@sgttomas sgttomas released this 08 Nov 04:17
88ab3f4

Chirality Library 3.1.0

Agent 0 guidance now keeps the owner's question, adequate effort, actual host
capabilities and next action explicit. Deliverable Work keeps current findings
and their reasons; approval and review/check narrative lives in PRs.

Source: 88ab3f4f5f8ec7f7e030279164dbd1a4aa38b514
Tag: library-v3.1.0
Archive: chirality-library-3.1.0-source.tar (785 tracked files)
SHA-256: 6553f7cc735740233f236bc773a3a43c03163d4351a6575d320694fb271d91ad

Changes since 3.0.0

Compare source editions.

  • HELP_HUMAN. Identify the owner's question and take the cheapest sufficient
    route; inspect actual host capabilities before acquiring or building tools.
    Explain the benefit and ending of mechanisms added after corrections.
    At a turn's end, identify the next action and active carrier, or the concrete
    blocker/reserved decision. Refer to the owner-facing role as Agent 0.
  • Standing instructions and shared project entry. Lead owner updates with
    the result or decision needed; use plain prose and spaced identifiers in
    delegate messages. Keep findings and reasons in Work and approval/review/check
    narrative in the PR. Record an owner override of a standing rule in the PR
    and ask once whether the rule should change.
  • Maintained entry and records. Retain the dated old-entry redirect without
    a removal deadline. PR9/PR10 approval/run commentary is removed from the two
    owning Work sections while useful findings remain. Git and the PRs retain
    the original evidence.
  • Direct instruction prose. Replace document disclaimers with direct
    instructions in entry/role files, selected workflows and tool guides.
    Preserve applicable decision owners, evidence requirements and write targets.
    Route shared Library instruction maintenance to Library Agent 0, and routine
    repository review to the project's own standing instructions. Distinguish the
    original publication undertaking from subsequent identified editions.

These changes are approved in #14
and #15.
INTERLOCUTOR keeps its continuing-session lifetime and existing consultation cadence.

Adoption

Compare the instructions and packages your project uses with its selected
3.0.0 basis. Adopt the shared wording under your project's authority and record
the resolved revision with dependent results. Preserve actual grants,
accepted scope, required package resources and license notices. Apply findings
and record cleanup through the owning project's change process.

The YAML metadata schema, role eligibility, 76-method index and executable tool
source are unchanged from 3.0.0. Existing 3.0.0 header/parser adoption remains
applicable. Follow the
consumer route.

Verification and delivery

Both required hosted checks passed on both owner-approved PR heads. The final
merge tree equals the approved #15 tree. The core change passed 514 affected
tests; the final change passed 544. Index, path-anchor, changed ScopeOfWork,
credential/symlink and conflict-marker checks passed.

Every archive file byte and executable mode was checked against the source Git
objects and extracted files. The extracted package passed 185 metadata, role
and resolver tests and its 69-workflow/76-method validation. The source changes
require no HTML regeneration. SHA256SUMS covers the attached archive.

Use the complete source archive for reading and in-place tools. Tools require
their documented dependencies; Git-dependent queries require a clone with the
appropriate history.

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.

Chirality library 2.1.0

Choose a tag to compare

@sgttomas sgttomas released this 07 Nov 18:14
c35b7bb

Chirality library 2.1.0

Source: c35b7bbc463f81c1fed566c744ea49d168d29eee
Tag: library-v2.1.0
Archive: chirality-library-2.1.0-source.tar (779 files)
SHA-256: 03d29bbaebecfb0448d303fb1928be12b224c07d9b2312741ff954ad3eb10be7

The owner approved the official INTERLOCUTOR instruction, opt-in per session,
and authorized publication: “this also means you need to publish a new official
library package incrementing to v2.1.0”.

Changes since 2.0.0

The comparison basis is library-v2.0.0, source
2f981163d76772d3779697d9def1a9e951d978e7.

  • Opt-in INTERLOCUTOR role. A fifth official role supplies a bounded Type 2
    second opinion on Agent 0's effectiveness and direction. In sessions selecting
    it, Agent 0 supplies periodic summaries and consults it before every PR merge.
    After three rounds without convergence, Agent 0 explains its own decision and
    continues within its authority. Advice carries no sign-off or veto. Model and
    effort choices remain session steering.
  • Registration and method compatibility. All direct-entry roles can delegate
    INTERLOCUTOR; neither Type 2 role delegates. Existing method eligibility stays
    unchanged: methods without an execution companion inherit the original four
    roles. INTERLOCUTOR needs explicit compatible_roles to select a method and
    needs no method for its ordinary advisory brief. Existing resolver behavior for
    other registered roles and omitted role lists is preserved. Strings are rejected
    as malformed role lists. Explicit write targets and
    actual host permissions remain necessary for writes.
  • Restored methods and tools. PR #5
    restored workflows and supporting tools removed before 2.0.0, including
    document, domain, drawing, evaluation and research methods. The consumed index
    now contains 76 method entries, compared with 43 in 2.0.0. Inclusion preserves
    each holding's own applicability and evidence limits; it does not qualify every
    method for every project or role.
  • Library and Root identity. PR #4
    and PR #6 distinguish this
    public Library from private Root and correct current entry/discovery wording.
    Earlier records keep their identified historical meaning.
  • Root-owned evaluation holdings. PR #7
    removes tools/undertaking_evaluation/ and excludes audit-agents and
    evaluate-repository-change from current Library discovery after verified
    byte-preserving transfer to Root. Its owner-approved R18/A9 and scope amendment
    ends the corresponding continuing Library executable/workflow obligation;
    original contracts, editions and evidence remain recoverable. Current public
    Library source supplies no runnable repository-change evaluator. Private Root
    starting material is not a required dependency or replacement public service.
    evaluation-protocol, evaluation-report and tools/evaluation/ remain here.

Consumer adoption

Removed: tools/undertaking_evaluation/ shipped in 2.0.0 and is absent from
2.1.0, with no public replacement. Keep 2.0.0 or the identified pre-removal public
source if you depend on that evaluator; private Root is not an adoption route.

Consumers that enumerate exactly four roles must deliberately support the fifth
descriptor, its Type 2 nondelegation and session opt-in. The method index schema
remains chirality-method-index/v1; the discovery fixture adds the role and
compatibility cases. Existing custom-role inheritance remains as before. To use a
method with INTERLOCUTOR, give that method an explicit roles list including it.

Choose adoption under your project's authority. Preserve complete packages,
relative resources and notices, and compare the exact edition currently used.
Start from README. The attached
source archive is for in-place reading/tools; it is not a Python wheel or new
application runtime. pyproject.toml's dependency-only version is unchanged.
Python tool prerequisites remain in the selected tool guide and that manifest.

Verification and limits

The full Library tool suite passed 972 tests. Role, workflow and skill
metadata, native deliverable structure, index freshness, Ruff, conflict-marker
and changed-file credential/symlink checks passed. Independent implementation
review and the pre-merge interlocutor consultation completed; their remaining
consumer-facing concerns were resolved before integration.

Hosted Repository checks and harness passed on exact head
b662b89b0cadaa87cfefa766661acfe61f519285. The integrated source tree matches
that head. All 779 archived file bytes and Git modes were compared with that
source; the approved role's SHA-256 is unchanged. From the extracted archive,
five-role validation, 76-entry index freshness, standalone INTERLOCUTOR resolution
without write/delegation authority, preserved evaluation-protocol resolution,
and exclusion of incompatible/removed methods passed on Python 3.13 with PyYAML.
SHA256SUMS supplies the attached archive checksum.

This is a source release. Git-dependent utilities need an appropriate clone;
the source archive contains no Git database. Retained holdings preserve their
own applicability and evidence limits. These checks do not establish App v4,
SWBPIPE or Root adoption, broad host compatibility, comparative productivity
improvement or additional host enforcement. Each consumer owns its update.

Chirality library 2.0.0

Choose a tag to compare

@sgttomas sgttomas released this 05 Nov 05:10
2f98116

Chirality library 2.0.0

Source: 2f981163d76772d3779697d9def1a9e951d978e7
Tag: library-v2.0.0
Archive: chirality-library-2.0.0-source.tar (552 files)
SHA-256: 32af15c9f09ffbd489f7687660ce5d0dd8884cee2cd6d72fe80e70da28a96553

The owner authorized this release: “let's issue the first release”, selecting
version 2.0.0 because a different edition already carries the number 1.1.0.
This is the first release from sgttomas/chirality-library.
The attached archive matches the identified Git source and its executable modes.
SHA256SUMS supplies its checksum, and tracked resources and notices are retained.

Why 2.0.0

The library now lives in its own repository, with a fresh history that starts
from the Root tree at sgttomas/chirality@05d96f3e (2026-11-04). Earlier
editions, 1.0.0 to 1.1.0, were published from sgttomas/chirality, which is now
private, and remain identified there.

Compared with 1.1.0, this edition removes methods, tools and interfaces.
Consumers that depend on any of the following must adapt before adopting it.

Breaking changes from 1.1.0

  • Workflows removed (about 45). These are the dbm-*, audit-* (except
    audit-dep-closure and audit-governance), equation-*, drawing-*,
    domain-* (except domain-knowledge-intake, domain-prose-validate and
    domain-source-atomize), kty-*, pandid-*, semantic-*/lens-register,
    evaluation-*, research-orchestration, review, task-management,
    four-documents, content-digest, aggregation, equipment-* and
    evaluate-repository-change (its tools/undertaking_evaluation CLI remains). workflows/index.json now lists 43 methods.
  • Legacy aliases removed. workflows/legacy-methods.json and
    legacy-agents.json are gone, along with the legacy section of
    workflows/index.json, publicExportExclusions, and the resolver's stage
    output. Old method or role names now fail as unknown, and a brief carrying
    TaskSkill fails explicitly.
  • Tools removed (about 50k lines). These are practitioner_harness,
    publication, analysis, aggregation, drawing_extract, equation_audit,
    pipe_specs, taskmgmt, domain_extract, five corpus-specific decomp
    scripts, archive_agent_runs.py, and the domain-engine and private-term
    validators. The write-guard tests that protected tools/scaffolding/write_status.sh
    were retained and relocated.
  • Reference documents removed. These are AGENT_WORKFLOW_RUNTIME.md,
    PRODUCT_BOUNDARIES.md, COMPATIBILITY_FORMATS.md, MAINTENANCE_RECOVERY.md,
    CI_SELECTION.md, READER_STYLE.md, SOFTWARE_WORKFLOW_PROFILE.md,
    projects/FROZEN.md, docs/governance_harness/, docs/rubrics/, the v7
    management manual, _DomainEngines/ and plans/.
  • The agent-instruction validator now validates only agents/registry.json.
    The old snapshot mode is gone.

Other changes

  • Thesis. The efficacy claims now state what the method achieved in one
    undertaking, by one developer, without comparison and with partly private
    evidence. The duplicate introduction, conclusion and design-analysis files were
    merged into INTRODUCTION.md, CONCLUSION.md and Chapter 7. Chapter 2 uses a
    single citation scheme backed by references.md, and Appendix D is plain prose.
  • Packaging. A new pyproject.toml declares Python dependencies with
    extras (test, retrieval, pdf, data-app, ci, all).
  • Checks. CI adds a pyflakes-only lint gate and runs Python 3.13. The
    report-only mapping step and the private-term check are removed. The credential
    and leak scan, conflict-marker check and path-anchor check remain.
    deliverables check now reports a non-UTF-8 file as a per-file error instead
    of aborting.
  • Public-content hygiene. Client-project identifiers, a corpus
    de-anonymisation vocabulary and owner machine paths present in earlier
    editions are not included.
  • Repository identity. README, the init prompt, AGENTS.md (including the
    standing Git grant) and the PRD now name sgttomas/chirality-library.
    References to removed material point to the private archive or were removed.

Read and use

Start with the consumer entry,
then the selected holding's own guide. Keep the source tree together to preserve
local references and resources. Each consumer decides whether and when to adopt
this edition. Compare it with the source you currently use, and select only the
changes that apply under your project's authority.

Verification and limits

The required Repository checks and harness passed on exact PR head
60bf996f5, and the integration tree at the source commit matches it
(309c064f). The full tool suite ran in the .[ci] environment: 814 passed,
2 skipped (openpyxl not installed). The deliverables check reported 0 errors
and the workflow index check passed.

This edition is a source release. It changes no host permission, and it starts
no agent or automatic adoption.