Support

Aletheia is maintained by one person alongside other work. Help is best effort: expect an answer within a few days, not hours, and a fix on the maintainer's schedule. Do not send tokens, personal data or customer documents.

Where to ask

You want to	Go to
Read how something works	The docs site: https://akhiljames.github.io/aletheia/, starting with Get started, Concepts and the tutorial
Ask a question, report a bug or propose a change	Email aletheia-dev@ajrd.net
Follow releases	The changelog and the roadmap
Report a security problem	Security: by email, never anywhere public

Before you report a bug

Say which version or image tag you run, how you run the stack (compose or Helm), the steps, what you expected and what happened, and the relevant log lines. Logs from the API and worker carry request and workflow run ids; include those lines and redact anything that identifies a person or a tenant (tokens, emails, document contents). The operations runbooks cover the five alerts a running deployment raises and are the quickest route to a diagnosis.

What to expect

• Questions are answered when the maintainer gets to them, usually within a few working days.
• Confirmed bugs that break a pilot deployment are fixed first; everything else is scheduled.
• Security reports are acknowledged within three business days (Security).
• There is no commercial support offering.