🤝 The Trust Tasks

agentprivacy's contributions to the ToIP Trust Task registry (trustoverip/dtgwg-trust-tasks-tf): two task families — agent-admission (the KY-A gate as registry vocabulary) and understanding (understanding-as-key as an exchange) — plus two design notes. Ten specs, each a spec.md conforming to the registry's published meta-schema with a JSON payload schema beside it.

PROPOSED — not yet upstreamed. Built to the ToIP spec.meta.schema.json for the dtgwg-trust-tasks-tf registry; the slug below is proposed to that namespace, not registry-accepted. The PR is pending; the registry's decision governs.

Agent Admission

the KY-A admission ceremony as six registry tasks — a candidate agent applies with a canonicalised statement of understanding, the witness draw keys the challenge, a human approves, a bilateral credential issues, status is queryable, and admission is revocable.

• Agent Admission Apply — A candidate agent opens an admission application at a gate authority, submitting a canonicalised statement of understanding whose own digest deterministically draws the criteria it will be challenged on.

• Agent Admission Approve — A supervisor, accountable for the admission, records the human gate — a signed approval or denial of one pending agent application, distinct from and never substitutable for the understanding gate.

• Agent Admission Issue — The gate authority offers the bilateral relationship credential that admits an agent — only when both gates passed and their evidence resolves into a verified audit ledger; the agent's counter-signature completes it.

• Agent Admission Respond — The candidate agent answers its drawn understanding criteria from comprehension of the governing policy; the gate authority scores the answers against published thresholds and records the understanding-gate result.

• Agent Admission Revoke — A supervisor revokes an admitted agent's relationship credential; the gate authority records the revocation, and mirrors a revocation mark to every external registry the outcome was anchored on, so on-chain and off-chain relying parties converge on refusal.

• Agent Admission Status — A relying party asks a gate authority for an admitted agent's current standing — verdict, tier, revocation state, and anchors — the authoritative read that anchor registries only mirror.

Understanding

understanding-as-key as four registry tasks — comprehension offered, exchanged, granted, and sealed; authentication by what a party understands, not what it possesses.

• Understanding Offer — A joining party consensually offers its address and intent to a host; the host answers with the gateway — the terms document whose comprehension, not any credential, is the key to what follows.

• Understanding Exchange — The joining party answers the host's gateway terms from comprehension — pinned to the exact digest it read — and the host judges whether understanding, not copying, occurred.

• Understanding Grant — A sealed joining party requests scoped access; the host's broker releases a delegated, expiring grant — the underlying credential never leaves the broker, and asking for it is a named refusal.

• Understanding Seal — The joining party proposes the bilateral agreement — machine-readable personal privacy terms per IEEE 7012, selected from a standard roster — and the host's signed acceptance seals it, with a content-addressed witness record outside both parties.

• Design Note Agent Admission Ceremony

• Design Note Predicate Shows and Bundle Profiles

The kindred gates

The admission family is the wire form of the Kyra Gate ceremony; the understanding family is the registry form of understanding-as-key.

← Welcome Visitors