Sources and boundaries.

LedgerPilot AI uses source context to ask better workflow questions and prepare a partner review packet. It does not make final tax, legal, audit, payroll, or accounting conclusions, and it does not need client files during discovery.

Used for

Workflow discovery

Sources help LedgerPilot ask where work starts, which system is the source of truth, who approves output, and what proof metric a partner would trust.

Not used for

Final advice

Sources do not turn LedgerPilot into a tax advisor, auditor, payroll processor, bookkeeper, attorney, or firm decision-maker.

Packet output

Cited context

Generated review packets include source context when a lane matches the curated registry, plus the same human-review boundary.

Source-backed playbooks now guide the agent

LedgerPilot maps tax, payroll, bookkeeping, CAS, audit support, AP/AR, billing, front desk, and partner-visibility conversations to domain playbooks. Each playbook carries source categories, better "I don't know" redirects, reviewer controls, and proof metrics.

Domain Source context Agent behavior
Tax and notices IRS / Treasury Routes toward notice ownership, source monitoring, client FAQ review, and professional sign-off.
Payroll workflow IRS / DOL Routes toward change intake, cutoff reminders, recordkeeping, exception review, and no-submission boundaries.
Bookkeeping, CAS, AP/AR, billing QuickBooks / Xero / FASB Routes toward source-of-truth systems, reviewer ownership, approval packets, and no-posting/no-payment controls.
Audit support AICPA / PCAOB Routes toward PBC ownership, deadline visibility, and audit-judgment boundaries.

Current public source registry

The registry is deliberately metadata-first. It points discovery toward credible context while keeping client data and final professional judgment outside the public intake.

What stays human-owned

Lane LedgerPilot scopes Hard boundary
Tax workflow Research monitoring, notice routing, organizer updates, reviewer queues. No final tax conclusion, filing position, eligibility determination, or client-specific planning.
Payroll workflow Change intake, recordkeeping, cutoff reminders, exception routing. No payroll submission, employee-specific advice, payroll tax conclusion, or wage-law conclusion.
Bookkeeping and close Exception review, missing receipt follow-up, reconciliation readiness, close status. No bank-data intake during discovery, posting, journal entry release, or final accounting treatment.
AP, AR, and billing Invoice readiness, approval routing, WIP visibility, vendor follow-up queues. No payment release, vendor bank change, invoice release, or client message without approval.
Audit support PBC tracking, request ownership, evidence readiness, reviewer status. No audit opinion, assertion, conclusion, or client-file ingestion during discovery.
Front desk and admin Inbound routing, escalation paths, service-line assignment, deadline-sensitive flags. No advice, confidential-detail collection, or final client response from discovery.

Available source APIs

These endpoints and files expose the same boundary-backed source context used by the discovery agent and review packet.

GET /llms.txt
GET /mcp-actions.json
GET /api/knowledge/sources?domain=payroll_workflow
GET /api/discovery/playbooks
GET /api/reviewer/qa
POST /api/reviewer/qa/answer
POST /api/knowledge/query
GET /api/tax-research/sources
POST /api/tax-research/query