# Docs

- [Grantline Documentation](/docs): Learn how Grantline gives AI agents bounded authority over capital through Mandates, Preflight, delegation, controller approval, and traceable execution.
- Concepts
  - [Strategy vs authority](/docs/concepts/strategy-vs-authority): Grantline decides whether an agent is authorised to take an action; it does not choose the agent's strategy.
  - [Mandates](/docs/concepts/mandates): Mandates define the authority an agent may use over controlled capital and the boundaries around it.
  - [Vaults](/docs/concepts/vaults): Vaults hold controlled capital while the controller retains custody and control.
  - [Action Plans](/docs/concepts/action-plans): Action Plans are structured proposals that describe what an agent wants to do under its authority.
  - [Decisions](/docs/concepts/decisions): Grantline resolves a proposal to ALLOW, ESCALATE, or DENY before controlled capital can move.
  - [Delegation](/docs/concepts/delegation): Delegation gives a sub-agent a narrower authority grant while preserving the lineage back to its source.
  - [Preflight](/docs/concepts/preflight): Preflight checks whether the conditions around an action are safe before execution.
  - [Guardians](/docs/concepts/guardians): Planned external conditions that can add verified context to a Grantline decision.
  - [Records](/docs/concepts/records): Records connect authority, proposals, decisions, approvals, and execution outcomes over time.
- Enforcement
  - [Security model](/docs/enforcement/security-model): How Grantline keeps agent authority bounded from a signed proposal to controlled capital.
  - [Enforcement boundary](/docs/enforcement/enforcement-boundary): Grantline keeps proposal evaluation, approval, and capital movement on an authorised contract path.
  - [Action commitments, signatures and nonces](/docs/enforcement/action-commitments-signatures-and-nonces): How Grantline commits an exact Action Plan to its authority domain and prevents it from being executed twice.
  - [Escalation](/docs/enforcement/escalation): Escalation routes a boundary-crossing proposal to controller approval without bypassing current authority checks.
  - [Revocation](/docs/enforcement/revocation): Revocation stops future use of a Mandate and its descendants while preserving authority history.
- Execution
  - [Transaction lifecycle](/docs/execution/transaction-lifecycle): A Grantline transaction separates authorisation, nonce handling, Vault calls, and the final receipt.
  - [Contracts and deployments](/docs/execution/contracts-and-deployments): The tracked deployment manifest defines the Grantline deployment identity, wiring, authority, and runtime hashes.
  - Networks
    - [X Layer testnet](/docs/execution/networks/x-layer-testnet): Current Grantline contract evidence on X Layer testnet, including network settings and deployment-specific limitations.
- Guides
  - [Vault and Mandate setup](/docs/guides/vault-and-mandate-setup): Create a Vault, fund it with native asset or tokens, and create a Mandate with configured authority.
  - [Normal execution](/docs/guides/normal-execution): Sign, evaluate, and execute a TRANSFER or SWAP Action Plan through the ALLOW path.
  - [Escalated execution](/docs/guides/escalated-execution): Submit, approve, and execute a plan through the ESCALATE path.
  - [Delegation](/docs/guides/delegation): Create child Mandates, inspect inherited authority, and manage delegated agents.
  - [Lifecycle management](/docs/guides/lifecycle-management): Pause, revoke, cancel nonces, update rules, and manage validity windows.
  - [Inspecting evidence](/docs/guides/inspecting-evidence): Read receipts, events, and explorer data to understand what happened onchain.
- Reference
  - [Mandate rules](/docs/reference/mandate-rules): The current Mandate rules, Preflight rules, and validity window fields, units, inheritance, and escalation behaviour.
  - [Action Plan](/docs/reference/action-plan): The current ActionPlan, TRANSFER, SWAP, parameter encoding, and EIP-712 signing shape.
  - [Decisions and failures](/docs/reference/decisions-and-failures): The evaluator's current decision values, failure codes, result fields, and transaction boundary.
  - [Events](/docs/reference/events): The current registry, escalation, Vault, executor, and facade events and what each one proves.
- [Roadmap](/docs/roadmap): Planned direction for external conditions, integration tools, and indexed decision evidence.