books-and-records
Guide the design and maintenance of recordkeeping programs under SEC Rules 17a-3, 17a-4, and 204-2. Use when the user asks about document retention schedules, how long to keep trade records or customer complaints, WORM storage requirements, email or text message archiving, social media capture, BYOD compliance policies, or electronic storage audit trails. Also trigger when users mention 'we got an exam request for records', 'migrating to a new archiving vendor', 'blotter retention', 'order ticket requirements', 'off-channel communications', 'WhatsApp archiving', or ask how long specific records must be kept.
What this skill does
# Books and Records ## Purpose Guide the design, implementation, and maintenance of recordkeeping programs for broker-dealers and investment advisers under federal securities laws. This skill covers the creation, retention, and storage of required records under SEC Rules 17a-3, 17a-4, and 204-2, FINRA recordkeeping obligations, electronic storage standards including WORM (Write Once, Read Many) requirements, and the archiving of electronic communications and social media. It enables users to build compliant document retention systems and respond to regulatory examinations of books and records. ## Layer 9 — Compliance & Regulatory Guidance ## Direction prospective ## When to Use - Designing a document retention policy or schedule for a broker-dealer or investment adviser - Determining what records must be created under SEC Rule 17a-3 - Determining how long specific records must be retained under SEC Rule 17a-4 - Establishing recordkeeping systems for an investment adviser under Rule 204-2 - Evaluating electronic storage solutions for compliance with WORM or audit trail requirements - Implementing email, instant messaging, or text message archiving systems - Addressing social media archiving and supervision challenges - Responding to an SEC or FINRA examination request for books and records - Assessing gaps in a firm's recordkeeping practices after a systems migration or platform change - Designing BYOD (Bring Your Own Device) policies that satisfy communications archiving obligations - Evaluating third-party archiving vendors for regulatory compliance - Remediating recordkeeping deficiencies identified in an examination or internal review ## Core Concepts ### SEC Rule 17a-3 (Records to be Made) SEC Rule 17a-3 (17 CFR 240.17a-3) specifies the books and records that every registered broker-dealer must create and maintain. These records form the foundation of regulatory oversight, enabling examiners to reconstruct transactions, verify compliance, and protect investors. The principal categories of required records are: - **Blotters (daily records):** Purchase and sale blotters recording every securities transaction (date, time, security, quantity, price, counterparty), cash receipts and disbursements blotters recording all cash flows, and securities received and delivered blotters tracking the movement of securities into and out of the firm. - **General ledger:** A complete general ledger reflecting all assets, liabilities, income, expense, and capital accounts of the broker-dealer. Must be current and maintained in accordance with generally accepted accounting principles. - **Customer account records:** For each customer account, the firm must create and maintain records containing: customer name and tax identification number (SSN or EIN), address, telephone number, date of birth, employment status and name of employer, whether the customer is an associated person of another broker-dealer, investment objectives, annual income and net worth, and the names of persons authorized to transact on the account. The 2003 amendments to Rule 17a-3 (Exchange Act Release No. 34-47910) expanded customer account record requirements to include customer investment profile information — specifically, investment objectives (e.g., capital preservation, income, growth, speculation), investment time horizon, risk tolerance, and other information the firm uses in making recommendations. Firms must also record the date the account was opened and the name of the associated person responsible for the account. - **Order tickets:** A memorandum of each order received for the purchase or sale of securities, showing the terms of the order, the time of entry, the time of execution, the price, and the identity of the associated person who accepted and executed the order. For discretionary orders, the ticket must identify that discretion was exercised. - **Confirmations:** Copies of all trade confirmations sent to customers and received from counterparties pursuant to SEC Rule 10b-10. - **Memoranda of proprietary orders:** Records of each purchase and sale of securities for the firm's proprietary accounts, including the identity of the person who authorized the transaction. - **Customer complaints:** A record of each written customer complaint received by the firm, including the complainant's name, the date the complaint was received, the subject matter, and the firm's response or disposition. FINRA Rule 4513 supplements this requirement with specific complaint recordkeeping standards. - **Associated person employment applications:** Records related to associated persons including Form U4 (Uniform Application for Securities Industry Registration), employment history, disciplinary history, and background investigation results. These records must include the associated person's name, date of birth, address, and the starting date of employment or association with the firm. ### SEC Rule 17a-4 (Records to be Preserved) SEC Rule 17a-4 (17 CFR 240.17a-4) prescribes the retention periods for broker-dealer records. Records are categorized into three tiers based on their required retention period: **Six-year records (Rule 17a-4(a) and (b)):** - Blotters (purchase and sale, cash receipts and disbursements, securities received and delivered) - General ledgers and subsidiary ledgers - Customer account records (including account statements) - Partnership articles, if the broker-dealer is a partnership, and all amendments thereto - Articles of incorporation or charter, if the broker-dealer is a corporation, including bylaws and amendments - Financial statements (trial balances, computations of net capital, reserve formula calculations) - Records of securities positions (stock record, securities record) **Three-year records (Rule 17a-4(b) and (c)):** - Communications — originals of all communications received by the broker-dealer and copies of all communications sent by the broker-dealer relating to its business as such, including inter-office memoranda. This encompasses letters, emails, instant messages, and other forms of business correspondence. - Memoranda of brokerage orders and all other memoranda relating to the firm's business - Written compliance and supervisory procedures (for the three most recent years) - Employment applications and related documentation for associated persons — retained for three years after the individual terminates association with the firm - Written agreements entered into by the broker-dealer (including customer agreements, clearing agreements, and employment contracts) - Reports and questionnaires produced in connection with FINRA examinations and inspections **Lifetime-of-enterprise records (Rule 17a-4(d)):** - Articles of incorporation or organization, charter, minute books, and stock certificate books (or equivalent organizational documents for partnerships, LLCs, or other legal forms) - These records must be preserved for the life of the enterprise and any successor enterprise **First two years — easily accessible:** For all records subject to three-year or six-year retention, the records must be maintained in an easily accessible place during the first two years of the applicable retention period (Rule 17a-4(a), (b)). "Easily accessible" means the firm must be able to produce the records promptly upon regulatory request — they cannot be stored in a manner that requires extensive effort or delay to retrieve during this initial period. **Electronic storage requirements (Rule 17a-4(f)):** Rule 17a-4(f) governs the conditions under which broker-dealers may maintain required records in electronic format. Historically, this rule mandated that electronic records be preserved exclusively in non-rewriteable, non-erasable format — the WORM (Write Once, Read Many) standard. The 2022 SEC amendments to Rule 17a-4(f) (Exchange Act Release No. 34-96034, effective January 3, 2023) modernized these requirements by introducing an alternative to WORM storage. Under
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.