Editorial guidelines

Everything published on castforge.ai is written by the people who build Castforge, starting with its founder, Julien Abenhaim. These are the rules we hold ourselves to.

What we publish

• The docs describe the current build. When a feature changes, the doc changes in the same release.
• The changelog lists every user-facing change, grouped by what is new, what was fixed, and what got faster.
• The roadmap says where we are going. It is a working list, not a promise with dates.

How we write

• Plain language over marketing language. A feature is described by what it does for you.
• We say what a feature cannot do yet. A skipped check is never shown as a silent pass, and the docs follow the same rule.
• Comparisons with other tools come from their published documentation, are dated, and are corrected when we are told they are stale.
• No claims about model providers beyond their own published terms.

Corrections

If a page is wrong, tell us at admin@castforge.ai or in the Discord. We fix factual errors in the docs as soon as they are confirmed and note material changes in the changelog.

Privacy of examples

Screenshots and examples come from our own projects or from testers who agreed to be shown. We do not publish anyone else's code, prompts or logs.