Skip to main content
Mandala’s operational boundary spans the Next.js deployment, Supabase, durable workflow checkpoints, connector providers, Context Engine, email delivery, observability, and scheduled workers.

​
Configuration groups

Use .env.example as the source list. Important groups are: Only Supabase’s browser URL and anonymous key, the public site URL, and browser observability values should use NEXT_PUBLIC_. Connector, model, service-role, provider, worker, signing, and workflow database secrets are server-only.

​
Durable workflow checkpoints

Local development uses the local Supabase Postgres database. Hosted environments must provide a direct server-only Postgres connection in MANDALA_WORKFLOW_DATABASE_URL and initialize the LangGraph checkpoint schema:
Do not pass this connection string to the browser, terminal, model, tools, traces, or work-item records.

​
Scheduled workers

Production scheduling should invoke the secret-protected internal routes for connector sync, Context Engine indexing, email/account cleanup, and related maintenance. A healthy worker pipeline has more than a successful HTTP response. Verify:
  • a recent worker heartbeat;
  • claimed and completed leases;
  • no growing stuck or retry queue;
  • provider authentication and rate-limit state;
  • source and catalog freshness;
  • reconciliation outcomes; and
  • downstream evidence or provenance on a real bounded run.

​
Connector readiness

Treat these as separate release checks:
  1. credentials are configured server-side;
  2. the workspace installation is enabled;
  3. required capabilities are granted;
  4. provider health is passing;
  5. sync is continuous, not a one-time snapshot;
  6. required datasets are fresh and complete;
  7. the workspace catalog matches the current schemas; and
  8. a Sandbox or controlled run uses the expected sources.
Provider-console success or a searchable imported row does not prove the complete path.

​
Context Engine readiness

Provider sync, indexing, retrieval, and actual use in a work item are separate states. Verify the ledger and processing queue, then inspect the work item’s operationalContext and citations. If the provider is unavailable or policy-ineligible, Mandala should record a bounded fallback reason. Do not remove freshness or policy gates to make a demo pass.

​
Observability

Sentry loads through the Next.js server and client instrumentation files. LangSmith tracing is optional and should keep inputs and outputs hidden for production unless a reviewed policy says otherwise. Operational records also exist inside Mandala: workflow audit events, lifecycle events, connector health, context indexing events, execution receipts, monitoring events, feedback, provider usage, and email delivery events.

​
Release verification

Choose checks closest to the changed surface:
For connector, Context Engine, Sandbox, or approval changes, also run the focused local end-to-end suites and a bounded real journey:
A green local suite does not waive missing production environment variables, unapplied migrations, unhealthy providers, or stale data.