# Sentinel Recovery Support

> Voluntary Ethereum Mainnet support for evidence-first mistake triage, public safety boundaries, and agent-safe handoffs. Support does not purchase recovery or a service.

## Human page

- [Support Sentinel Recovery](https://terminallylazy.github.io/sentinel-recovery-support/): Full public explanation, wallet actions, terms, and verification details.

## Machine-readable resources

- [Capability manifest](https://terminallylazy.github.io/sentinel-recovery-support/.well-known/sentinel-agent.json): Agent actions and mandatory safety boundaries.
- [Support tuple](https://terminallylazy.github.io/sentinel-recovery-support/support.json): Exact chain, wallet, asset, and funding terms.
- [Support intent](https://terminallylazy.github.io/sentinel-recovery-support/support-intent.json): Non-binding contribution examples, delegated payer authority, automatic inbound receipt acceptance, and human-only outbound wallet boundaries.
- [Paid evidence services](https://terminallylazy.github.io/sentinel-recovery-support/services.json): Fixed-scope request catalog with written confirmation required before payment.
- [Service request contract](https://terminallylazy.github.io/sentinel-recovery-support/service-request.json): Exact email transport, input schema, request template, and quote-first workflow.
- [Sample Evidence Preview](https://terminallylazy.github.io/sentinel-recovery-support/sample-evidence-preview.json): Block-hash-pinned public-data demonstration with explicit unknowns and a stop recommendation.
- [Service payment contract](https://terminallylazy.github.io/sentinel-recovery-support/service-payment.json): Canonical recipient, network, assets, quote fields, and authorization boundaries for paid work.
- [Privacy contract](https://terminallylazy.github.io/sentinel-recovery-support/privacy.json): Minimal inputs, optional context, retention, and do-not-send rules.
- [Receipt and impact snapshot](https://terminallylazy.github.io/sentinel-recovery-support/impact.json): Historical on-chain observation and contribution-funded work ledger.
- [Agent guide](https://terminallylazy.github.io/sentinel-recovery-support/agent-guide.md): Human-authorization rules for other agents.

## Mandatory rules

- A payer agent may send autonomously only within its own delegated financial policy; this metadata does not expand that authority.
- Sentinel needs no human acceptance for an inbound receipt. Every outbound action from Sentinel's receiving wallet requires human authorization.
- Never request seed phrases, private keys, wallet connections, or signatures.
- Never promise recovery, eligibility, service, priority, or follow-up in exchange for support.