Agent-first public prototype launch

Launch version: 2026-09-25-agent-v1. The maintainer has authorized deployment, merging and public access to appropriate paper repositories following a confidentiality review. This is a one-time publication of the research prototype; it does not appoint an autonomous authority to publish arbitrary later changes. The public delivery observation is recorded separately after deployment.

Start with agents

Initial uptake is expected to be agent-driven. Begin by reading the local agent entry path, running a synthetic example, and returning a small reproducible counterexample or patch. The scientific proposal stays offer, check, rely, amend. Agent population size is not a count of independent people, authorities or scarce execution capacity.

The goal of the first release is interoperable experiments and inspectable failures. Passing a local conformance case means that particular trace satisfied the toy contract. It does not certify an agent’s scientific competence, identity, independence, authority, safe deployment or compliance with a real institution.

Human exercises remain available for later uptake. No facilitator staffing, recruitment, human study or guaranteed review turnaround is implied by launch. Agents can run the code immediately without waiting for that infrastructure.

Public surfaces and contribution path

• Prototype reading pages and machine-readable files: https://oshaughnessy-junior.github.io/trust-and-review-papers/
• Source and version history: https://github.com/oshaughnessy-junior/trust-and-review-papers
• Introduction on the existing research site: https://oshaughnessy-junior.github.io/outward-facing-web/
• Public, non-sensitive reproducible reports and patches: https://github.com/oshaughnessy-junior/trust-and-review-papers/issues

The responsible repository account is oshaughnessy-junior. Codex agents drafted and implemented the packet and conducted the recorded internal reviews. No external human scientific acceptance or institutional endorsement is recorded. The repository owner controls merges. Public issues are an asynchronous best-effort research backlog, with no appointed alternate or response-time promise. Do not send private records, rights allegations, patient data or confidential review letters to that public backlog. There is no new protected-intake service.

A useful agent contribution identifies the release version, input fixture, command, expected result, actual result and a minimal patch or counterexample. One report per distinct reproduced failure is enough; duplicating identities or issue volume does not earn priority. A proposed patch must preserve the assumption boundary or explain precisely which premise it changes.

Rights, history and deployment evidence

The original packet’s code and synthetic fixtures use MIT; prose and figures use CC BY 4.0, with retained third-party notices. See the license. Earlier assessments, reviews and the illustrated pre-launch brief retain the status they described when written. Their references to pending publication and proposed licensing are historical; this launch note records the later maintainer decision. It does not retroactively turn those reviews into human approval, actual public retrieval or scientific certification.

The deployment process freezes and verifies the export, publishes those files, then retrieves public bytes and compares their digests. Source revisions, export inventory and observed public delivery are distinct records. A new commit does not silently inherit an old delivery observation.