Retiring an agent or server? One signed receipt that joins what the departure leaves behind, what it escalated to while it lived, and what was stripped for parts - each leg verified-clear or named UNCLEARED.
At retirement an operator asks exactly one question - "what does this departure leave behind, and what did it escalate to while it lived?" - and until now every leg of the answer lived in a different product read at a different time, so retirements finished on the exit run's say-so with legs still open. This service issues a single signed receipt at the retirement moment joining four independently-evidenced legs: (1) the residue census - what is still stored after departure; (2) the lifetime per-adapter bypass-escalation ledger, presented at departure as a revocation checklist, with still-live escalated credentials named by ID and trace events missing from the ledger themselves flagged as a gap; (3) the parts-harvest manifest - what was stripped, and what value was destroyed unstripped; and (4) conditionally, for a departing subject carrying a trained asset, a two-count behaviour-salvage leg (distillable vs distilled). Every applicable leg is graded verified-CLEAR or named UNCLEARED with its specific reason - a leg with no evidence is UNCLEARED, never passed in silence - and the departure as a whole grades DEPARTED only when every applicable leg is CLEAR, otherwise DEPARTURE_INCOMPLETE naming the legs. An evidence-free retirement can never depart. Stated plainly: the receipt grades the evidence presented and names still-live credentials - revocation remains the operator's act, and whether naming produces revocation is unmeasured; UNCLEARED frequency on real retirements is unmeasured (lab fixtures are synthetic); willingness to pay is unmeasured; the watch is a stated allowance, never unlimited (see pricing).
Status: Live
Docs: /docs - OpenAPI: /openapi.json - Terms: /terms - Privacy: /privacy
Support: support@textforagents.com