Start here: what goes where (and the one boundary that matters most)

[eaitbrahim]

Where things go, so the right conversation happens in the right place:

• A question about how something works → the Q&A category. Nothing is too basic; the docs assume a lot and fixing that is a valid outcome of a question.
• "Should X be classified / treated this way?" → the Compliance & classification category. That is a question about rulings and attestations — not a bug, not a feature request, and it will not be triaged as either (there is a dedicated issue form for it too, for when you want a tracked artifact).
• An idea for the mechanism → Ideas, or a feature-request issue once it has shape.
• Something broken → an issue, via the bug-report form (it asks for keel --version, paper-vs-live, and the rail or rule — the three things triage cannot do without).
• Anything that could make keel misbehave or expose credentials → never a public post. SECURITY.md describes the private channel; a rail that can be bypassed is a security issue, not merely a bug.
• Your deployment, your numbers → Show and tell. Especially welcome: what you attest, and why.

One boundary worth repeating in the room where it matters most: disagreement about a ruling is expected and legitimate here. Disparaging a madhhab, a school, or a contributor's practice is not — the code of conduct enforces exactly that line.