Getting Support
Where to go for each kind of question or report.
Start with the tools and the docs
If you are wondering why a block did or did not parallelize, ask the tool
first. lucen explain yourfile.py reports statically what Lucen decided for
every marked block and why; lucen profile yourscript.py reports what actually
ran.
- README.md covers install,
lucen run, activation, reading the reports, and the clause surface. Start there. - LIMITATIONS.md is the inventory of what Lucen does not do and where its guarantee's boundary lies. If a block is refused or behaves unexpectedly, the answer is usually here.
- BENCHMARK.md has measured performance across interpreters, for calibrating expectations.
- The technical specification is the authority on every semantic, and the engineering guide maps the codebase.
Where to take each kind of thing
| You have | Go to |
|---|---|
| A usage question ("how do I...", "why does this block run sequentially?") | GitHub Discussions (or a question issue if Discussions is not enabled) |
| A reproducible bug, including any parallel result that differs from sequential outside the documented trust contract | A GitHub issue with a minimal reproduction |
| A suspected security issue, especially a silent wrong result reachable from ordinary code | The private channel in SECURITY.md, not a public issue |
| A feature idea or a limitation you want closed | A GitHub issue; check ROADMAP.md first to see if it is already planned |
| A change you want to contribute | CONTRIBUTING.md |
Writing a good bug report
The most useful report is one that makes a divergence concrete. When you can, include:
- A minimal marked source file that triggers the behavior.
- The interpreter and platform (for example, CPython 3.12 on Windows, GIL build). Routing and the native core differ across these, so this often localizes the issue immediately.
- For a wrong or unexpected result, both outputs: the file run with Lucen activated, and the same file with the pragmas treated as comments (Lucen not activated). That difference is the bug.
- Whether the native core or the pure-Python fallback was in use.
LUCEN_DISABLE_NATIVE=1forces the fallback; a divergence on only one path tells the maintainers exactly where to look.
What this project does not provide
There is no paid support tier and no private support commitment. Lucen is a community open-source project; help is provided on a best-effort basis through the public channels above. Security reports are the exception and are handled privately and promptly per SECURITY.md.