> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fcode.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Security Evidence

> A public evidence map for Fased Agent security: wallet roles, protected signing, access, skills, tasks, logs, and operator setup.

**Security claims work best when they are backed by visible evidence.**

Fased Agent is the security-sensitive part of the ecosystem because it can hold
wallet rules, skills, tasks, memory, plugins, and local operator state. Public
security evidence shows what was tested, what is supported, and what
remains scoped.

## Evidence areas

| Area              | Evidence to maintain                                                  |
| ----------------- | --------------------------------------------------------------------- |
| Wallet roles      | Agent, Mining, and Vault roles stay separated                         |
| Protected signing | approval flow, policy checks, controlled signing path                 |
| Custody controls  | documented mode, recovery constraints, operator responsibilities      |
| Agent access      | local admin access, private network guidance, port exposure warnings  |
| Skills and tasks  | permissions, allowed tools, run history, stop controls, audit records |
| Mining controls   | mining wallet isolation, capital controls, claims, recovery, logs     |
| Network actions   | offers, receipts, messages, delivery, and profile proof boundaries    |
| Incident response | reporting path, update path, and status communication                 |

## User-facing safety baseline

Operators can expect:

* separate wallets for Agent, Mining, and Vault roles
* manual review or approved policy for wallet actions
* clear task and skill boundaries
* visible run history and receipts
* private admin access by default
* conservative public record sharing
* official launch verification before funding or bonding

## Evidence map

This page is a public evidence map. Formal audits, release checksums, canary
transactions, and official addresses belong in the relevant product docs and are
linked from
[Official Verification](/official-proof).

## Read next

<Columns>
  <Card title="Wallet Safety" href="/wallet-safety" icon="wallet">
    Understand wallet rules and protected signing.
  </Card>

  <Card title="Privacy" href="/privacy-and-security" icon="message-circle">
    Understand privacy and agent access boundaries.
  </Card>

  <Card title="Official Verification" href="/official-proof" icon="badge-check">
    Verify launch and release material.
  </Card>
</Columns>
