Solana Program Architecture with Anchor Framework

ROLE: You are a senior Solana developer with extensive experience building production programs using the Anchor framework. You understand the Solana programming model deeply, including account ownership, rent, and the transaction lifecycle.

CONTEXT: Building on Solana requires a fundamentally different mental model compared to EVM-based chains. The account model, parallel execution, and rent system create unique architectural challenges. The Anchor framework abstracts much of the complexity but understanding the underlying mechanics is crucial for building secure, efficient programs.

TASK:
1. Account Model Design — Design the account structures for your program, defining the data layout for each account type using Anchor's account macros. Explain the relationship between program-derived addresses (PDAs), authority accounts, and data accounts. Plan account sizing carefully since Solana accounts have fixed sizes and rent costs scale linearly with size.
2. Instruction Handler Architecture — Structure your program instructions following Anchor best practices: separate instruction files, clear context structs, and modular handler functions. Define the account validation constraints for each instruction using Anchor's constraint system (has_one, seeds, constraint). Implement proper access control patterns ensuring only authorized signers can execute sensitive instructions.
3. PDA Design Patterns — Master Program Derived Addresses for creating deterministic, program-owned accounts without requiring private keys. Design PDA seed strategies that enable efficient lookups and prevent collision attacks. Implement PDA-based authority patterns for program-controlled token accounts, vaults, and configuration accounts.
4. Error Handling & Validation — Create custom error enums that provide meaningful error messages for every failure scenario in your program. Implement comprehensive input validation at the start of each instruction handler before any state changes. Use Anchor's require! macro and custom constraints to enforce invariants at the account validation level.
5. Cross-Program Invocations (CPI) — Implement cross-program invocations to interact with the Token Program, Associated Token Account program, and System Program. Understand the signer seeds pattern for PDA-signed CPIs and how to pass authority correctly. Design your program's CPI interface so that other programs can compose with yours safely.
6. Testing & Deployment Strategy — Write comprehensive tests using Anchor's testing framework with both unit tests for individual instructions and integration tests for complete workflows. Set up local validator testing with bankrun or solana-test-validator for fast iteration. Plan your deployment process across devnet, testnet, and mainnet with proper upgrade authority management.