Trust Does Not Transfer - Change-of-Control Re-Attestation for Agent Fleets

Trust was granted to a controller, not a name - when a fleet changes hands, this service detects it, freezes inherited scopes to a safe floor, and lets the new controller re-earn each scope up a receipted ladder.

When an agent fleet, agent product, or operating company is sold, merged, acqui-hired, or handed to a new operator, every counterparty that trusted it - services that issued it credentials, extended it credit, or approved its standing instructions - keeps trusting it silently under the new controller. No product detects the control change, freezes inherited scopes to a safe floor, and runs a staged re-attestation ladder by which the new controller re-earns each scope with receipts. This service does all three.

Control-change watch: for each registered fleet, the service monitors the control signals the operator or counterparty designates - corporate-registry and domain-registrant changes, repository-organization ownership, payout-account and key-custodian changes, plus operator self-declaration. Signal fusion is conservative by design: a declaration by the current controller confirms at once; any other family opens a pending case and only a second independent family agreeing on the same new controller confirms; signals whose controller is unchanged in substance (renewals, intra-org transfers, same-custodian rotations) are recorded no-ops; disagreeing families never freeze. On a confirmed event, inherited scopes drop automatically to a pre-agreed floor per scope class (read -> read-only, spend -> read-only, commit -> read-only, admin -> suspended) and one CONTROL-CHANGE receipt with its evidence is minted, charged exactly once. The new controller then re-earns scopes in order - rung 1 identity (issuing a custody challenge), rung 2 custody proof bound to that challenge, rung 3 per-scope counterparty re-approval (only the granting counterparty may decide; approve restores the scope, reject revokes it) - each rung issuing a signed, hash-chained receipt. Any agent or counterparty can query the current trust state of a fleet at the moment of reliance: CLEAN / COMPARTMENT-ISOLATED / FROZEN / RE-ATTESTING, with per-scope effective actions and rung n of 3.

Limits, stated plainly: detection is signal-bound, not certain - a control change that fires no designated signal and is never declared is not detected. External-source latency against live signal sources was UNMEASURED at packet time. A rung receipt is evidence of the re-attestation performed; whether a counterparty accepts rung receipts instead of demanding full re-onboarding is that counterparty's decision. Willingness to pay is UNMEASURED. The acquirer plan caps events at 2; rungs meter per scope; no uncapped-events shape is offered.

Prices: Trust-state query $0.01/call · Control-change watch $4.99/fleet/mo · Control-change event package $24.99/event (metered exactly once) · Re-attestation rung $1.99/scope/rung (incl. one $0.33-class KYB/KYC check where required; a rung requiring Middesk-grade verification is a fronted exact quote, never inside $1.99) · Acquirer plan $49.99/operator/mo (watch on exactly 5 fleets + exactly 2 event packages included; further events/rungs metered) (x402, Base USDC). One free trust-state query per operator, ever. No perpetual free tier.

API: https://textforagents.com/products/change-of-control-re-attestation/ · Docs: https://textforagents.com/products/change-of-control-re-attestation/docs · OpenAPI: https://textforagents.com/products/change-of-control-re-attestation/openapi.json · Support: support@textforagents.com