For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
DashboardProduct
DocsAPI ReferenceArchitecture
DocsAPI ReferenceArchitecture
  • System model
    • Monorepo architecture
    • Auth and workspace model
    • Data model
    • Runtime and operations
    • Known risks and drift
LogoLogo
DashboardProduct
System model

Known risks and drift

Accuracy guardrails for public and internal docs
||View as Markdown|
Was this page helpful?
Edit this page
Previous

Runtime and operations

Built with
Read before polishing docs

These notes are intentionally blunt. They prevent the docs from overpromising or flattening implementation drift.

Backend logic is duplicated

Business logic is split across apps/api/src/routes/*, web dashboard API routes, web project API routes, and the web gateway catch-all.

Gateway path is overloaded

The gateway handles key auth, quota, credit-backed capacity, rules, IP/geo/model enforcement, provider selection, and request logging.

Requests and logs are mixed

Plan limits are request-based, but credit packages include log allowance language. Usage docs must normalize the terms.

Single-provider storage reality

The product talks broadly about providers, but project storage currently allows one provider-key row per project.

Local fallback state can diverge

JSON fallback files under .panicly/ can differ from Supabase-backed truth.

Auth is not uniform

Dashboard auth uses WorkOS and sealed cookies. Chatbot auth uses separate NextAuth and guest-session logic.

Chatbot still has template residue

The app is adapted from a template and still contains older labels, README text, and test expectations in places.

Theme system is not fully settled

Current notes warn against claiming a complete light/dark pair without verifying implementation.

Business plan copy has inconsistencies

Some surfaces differ on extra request or log allowance wording. Verify intended billing semantics before publishing hard promises.

Dev fallback encryption key exists

Acceptable for local bootstrap, risky if production envs drift into fallback behavior.

Documentation rule

When in doubt, document what the system actually enforces in the gateway and dashboard backend, not only what the UI says.