9. A library learning from its own work

The following episodes concern the concentrated Root library undertaking from PRD acceptance on October 31 to the release record on November 1, 2026. That undertaking built on months of earlier development. This chapter is a documentary examination of identified source and review records. It does not execute the reported tests again, and its conclusions concern these cases. App and SWBPIPE appear through bounded consumer evidence, not as freshly qualified products. The source references at the end of this chapter identify the maintained accounts and the actual integrated revisions.

A draft interpretation challenged in review

The F-02 undertaking addressed how shared references apply. Some passages mixed reusable concepts with historical product ownership, or appeared to impose Root governance on independent projects. An agent wrote a draft qualification that treated part of the format-validation account as legacy-only.

Before integration, an independent examination compared the draft with the actual code. It exposed a counterexample: a current ScopeOfWork caller and validator still depended on the distinction that the account described. The broad interpretation would have made the explanation easier to simplify, but only by misdescribing a live use. The repair qualified the actual scope. It did not erase current behavior or historical adopted contracts.

The episode supports the value of review with access to the actual code and its consumers. A plausible proposed explanation was corrected before it became integrated guidance. It was not a deployed interpretation whose failure appeared later through user experience. Consistency among the draft documents alone would not have exposed the error.

A boundary that made work too small

During F-02, the owner also questioned the scale of what the undertaking returned. An early touchpoint for interpretation had become a stop before the connected publication work was carried through. The owner authorized a trial of a more coherent boundary. The implementation owner then carried the reference changes, the rendered publication and the reconciliation through as one result.

The first reflective conclusion was that the existing ownership guidance could stay while its application changed. Later discussion separated orchestration from reflection and led to a small separate reflect-on-work method. The two have different subjects. Orchestration carries connected contributions to a result. Reflection examines whether the chosen practice serves the intended purpose.

The record supports those interpretations and their actual consequences. It gives no controlled comparison of productivity. Fewer fragmented returns can be useful to the person without support for a general numerical claim about efficiency.

Reconsidering where instructions belong

The owner questioned the value of the bundled change workflow given the agents' capability and actual use. The owner said: “It's seldom used in the right manner when agents are the ones invoking it. The task is easy for agents to do.”

The library undertaking removed the change workflow and the Root change skill. It moved the needed Git conventions and a recovery entry into the repository instructions that agents read every turn. Detailed recovery guidance stayed available on demand. The removal of two packages redistributed guidance. It did not by itself establish a reduction in attention, interruption or maintenance cost.

The retirement did not silently substitute an unrelated method. Explicit selections of the removed packages and of the historical CHANGE route failed, while historical identities and source pins stayed recoverable. Bounded inspections of consumers separated known present uses from uses that were not searched or that were selected dynamically.

The episode connects a poor fit with agent use to a changed assessment of what agents can carry without a separate procedure. Their consequences depend on the functions that stayed and on the actual consumers. Deleted text is not by itself evidence of reduced burden.

Reflection and the 60% decision

The owner asked for an actual use of the newly adopted reflective method to examine readiness at 60%. Its first recorded application here was by the Agent 0 that had developed it. The inquiry considered what was established, what the next work would rely on, and whether more activity was necessary. It found stale standing descriptions, together with bounded evidence that supported a decision to proceed.

The consequence was factual reconciliation and further concrete work, including fresh-reader discovery and a broader source-delivery candidate. The owner made the gate decision. The later 90% assessment assembled evidence for specific claims across the seven deliverables. It kept the limits of the named-reader, custody and archive cases.

The reflection did not need to find a new mechanism to be useful. It helped separate work that would improve the result from activity that would only repeat an examination. The outcome also showed why current descriptions matter. A correct historical account can mislead when a sentence in the present tense still says that a decision is pending.

An identified delivery

Library 1.0.0 was accepted and published from fc73de583d25bf792d5c3abb3bf1ac8e0c38f7d6. The delivery preparation checked that the complete source archive matched the Git bytes and executable modes. It also checked that resources and notices were retained. It reused selected behavioral evidence where operational sources were unchanged. After publication, the public archive and checksum were downloaded and compared with the prepared result.

The named App-reader case had established capture, declaration and content identity for particular package bytes, through a reader at an identified App revision. It did not supply evidence of runtime execution or universal adoption. The custody case was labeled, and the holder and the maintainer were the same. A write from a separate process exposed the absence of filesystem exclusion. These limits were part of the accepted result.

So a useful library edition could be completed without proof of every imaginable later use. Its usefulness depended on how four things related: actual commitments, bounded evidence, an identifiable delivered subject and the owner's decision. The publication remained available for each consumer to inspect and adopt independently.

After the edition

The selected post-completion record is one improvement made on the same day. It is not a longitudinal study of maintenance. PR #1791 recorded the acceptance and the release pointer in current sources and kept the approved archive. PR #1792 then clarified how readers could select material, follow releases and inspect updates. Its owning records separated guidance in the source about subscription from a subscription that was actually configured and from a notification delivery that was tested.

The change addressed a usability need that was newly stated. Its records did not present it as proof that the published edition had failed an accepted commitment. The owner authorized the concrete improvement and its integration. Publication of another edition remained a separate decision. The archive stayed at its original source, while the README on the development branch gained later guidance.

This small case gives post-completion work an identifiable subject. An accepted edition, its maintained source, an authorized improvement and a future publication were related but not interchangeable. The case is evidence of that relationship. It is not evidence of how well readers used the guidance, or of the adoption of any later edition. The sources are PR #1791 and PR #1792, the latter integrated at 843824e10e0664a2cb5251280e863fd7b4f3e4f8.

Sources for the case

• F-02 applicability and repair, integrated in PR #1783 at 1357d706ea77497903976bf159f3880bea4d1360.
• Reflective basis and maintenance basis, including PR #1785, integrated at 047da79894bc5631dca564a30113f2cd26ec7ae1.
• PR #1786, integrated at 547e7d7f833f9bec351f7a034bddd7c1a37db15a, records the 60% standing and the bounded fresh-reader examination. PR #1788 carries the later factual reconciliation of needs. PR #1789 records the owner's 90% decision.
• Consumer basis keeps selected evidence about obtaining, readers, the archive and change inspection. Library 1.0.0 identifies the released source and artifact. PR #1791, integrated at ceb2d9bd72bd8bdd6c8b959836d6fe83a60d802c, records its acceptance and verified publication in current source.