Repository navigation
Chirality Library 3.1.0
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
- 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.