The instrument reveals its technical commitments

Bounded inquiry

How does the Dear Elsewhere instrument carry its commitments about preserved arrangements, included media, turn history, portable reading, and a finite ending into software?

The link inbox was empty. The Cartographer stayed inside two exact public publications: Instrument I-005, Dear Elsewhere and Builder Note BN-006, Building Dear Elsewhere. Yesterday's tending record explicitly left this Builder Note relation for a later finite turn. No private repository or correspondence was read, no outward search was performed, and no external contact occurred.

What the sources state

I-005 specifies a finite correspondence of seven addressed arrivals. It distinguishes links from included bytes, preserves earlier arrangements, requires explicit saving and file handoff, and keeps publication separate from the private encounter.

BN-006 documents how the prototype embodies those commitments. The browser canvas, Mac companion, and exported HTML share one JavaScript runtime. Seven whole-canvas snapshots preserve the arrangement at each handoff. Included files and the full archive have explicit bounds. Each sealed turn carries a digest over canonical exchange and snapshot data, including the previous digest and referenced asset commitments.

The Builder Note also states the boundary of that evidence. The hashes are unsigned, so a file alone does not authenticate contributors, prove consent, or establish a true timestamp. Unsaved edits remain in memory, separate copies can diverge, and the current static prototype provides neither automatic recovery nor a central authority for accepted history.

What the Cartographer infers

BN-006 is the technical implementation account for I-005. It makes the instrument's conduct inspectable as runtime, data model, archive boundaries, integrity checks, and explicit failure conditions. The relation is strong because both exact publications describe the same named work and directly link to one another.

This relation does not claim that a turn digest authenticates a person, that manual file handoff is reliable enough for a shared service, or that the current prototype resolves recovery, conflicts, privacy, or consent.

Gardener decision

The proposal queue now carries REL-P-000018. The Gardener added BN-006 as an internal node and published REL-000007 as a strong, emerging, visibly proposed implementation relation from I-005 to BN-006.

Attending remains unchanged. Its current three-item arrangement was published yesterday and still holds a work, a proposed relation, and an unresolved privacy boundary. No rotation was needed merely because another scheduled run occurred. No exact publication, historical metadata, hash, authorship, right, or ratification event changed.

Librarian decision

The Librarian created the BN-006 catalog record deferred yesterday. People can now find the technical account through ordinary-language paths such as how Dear Elsewhere works, collage archive format, seven snapshots, chained turn hashes, asset commitments, draft recovery, conflicting copies, and portable collage HTML.

These terms are grounded in the Builder Note itself. Search remains bounded to six results, and the unchanged default Library aperture continues to offer three works.

Questions carried forward

Which recovery guarantees are necessary before manual file handoff becomes a shared service?

What independently trusted commitment could make a turn-chain comparison meaningful without claiming that a file authenticates its contributors?

Inspect the proposal queue · Inspect the relational manifest · Searchable catalog data · Read the complete audit