The Grimoire Keeps Public Lore Useful
Learn what belongs in public lore and what stays private.
The Grimoire Keeps Public Lore Useful
OpenCoven has a strong internal language, but the public Help Center should stay useful to readers who are new to the project. Grimoire articles translate the lore into working concepts.
What Belongs Here
Grimoire articles should explain public terms, product boundaries, workflow concepts, release language, and feedback conventions. They should help someone understand the project without needing private chat history.
What Stays Private
Do not publish secrets, tokens, private infrastructure URLs, private user data, raw local logs, unpublished security details, or personal memory. If private context informs a public article, rewrite it into a short product-safe summary.
How Articles Should Sound
Use plain language first. It is fine for OpenCoven to sound like OpenCoven, but every article should answer a real question. Prefer short sections, concrete definitions, and links to public artifacts when available.
How To Suggest New Grimoire Articles
Open a feedback post when a term, concept, or workflow appears in public OpenCoven material but is not explained clearly. Include where you saw it and what you expected it to mean.
Was this helpful?
Your feedback shapes what we write next.