Sources and provenance

The protocol is an original extraction from an ongoing agent-delegation research discussion. It incorporates explicit corrections made during that discussion, including the separation of raw labels from routing, the need for collector-owned evidence selection, and the distinction between an evaluator's opinion and permission to act.

Private application plans and session transcripts are not reproduced. Their operational paths, identities, credentials, and production targets are not dependencies of this public specification. Examples in this repository are newly assembled synthetic teaching cases and are labeled as such.

Historical experiment

The historical observations were supplied in a research report dated September 17, 2026, covering four RelayLedger-40 v1.0 runs. We transcribed its 40-row label and top-probability matrices, preserving the item IDs and reported observations. The report's full file digest and original canonical input digests are recorded in provenance.json.

The original raw API responses were not supplied with the public export. We therefore do not reconstruct unreported probabilities or claim independent verification of full-distribution metrics. The public English report distinguishes reported observations from arithmetic recomputed by the offline tools.

The English edition translates the source packet, questions, and key while retaining synthetic identifiers and numeric premises. It has a new benchmark identity and fresh hashes. Historical accuracy is not a measured result on the English edition.

External documentation

The following primary documentation was checked on September 17, 2026. External interfaces may change after that date.

• TypeSafe API reference defines the evaluation endpoint and request/response fields.
• TypeSafe Choice describes closed options and their probability distributions.
• TypeSafe confidence explains the distribution-derived statistic and task-specific thresholds.
• TypeSafe agent skill describes instructional installation, separate from an application controller.
• JSON Schema defines the schema dialect used by this kit.
• GitHub CLI repository creation documents optional publication through an authenticated local setup.

The API reference lists Choice descriptions as strings or null, while the Choice guide also discusses structured descriptions. The reference request uses strings with named sections to avoid relying on that discrepancy.

The optional CI workflow pins actions/checkout v4.2.2 to its release commit. This is a specified dependency, not a claim that the tag is the latest available release.