Skip to content

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.