Discussions

The project's public forum is GitHub Discussions. It is the right place to ask questions, raise objections, propose alternative readings, suggest sources, coordinate translation work, or otherwise engage the corpus in public.

The author reads and responds. Responses are not always immediate — the project is conducted on the margins of a demanding professional life — but every substantive thread gets a real answer.

What it's for

Questions

Anything the FAQ doesn't already cover, or where the FAQ answer raises a follow-up. The FAQ itself grows from Discussions threads: a good question that recurs may end up answered there.

Objections and alternative readings

The project's stance is that the framework is a working hypothesis to be tried, not a doctrine to be defended. Disagreement is welcomed. If you read the source material differently than the corpus does, or you think the scholarly consensus is being misrepresented somewhere, or you find a specific interpretive move unconvincing, the Discussions are the right place to say so.

The author would rather hear an honest objection than an insincere agreement. Substantive challenge is one of the things that improves the corpus.

Source suggestions

If you know of a source the project should engage — a primary text, a scholarly study, a critical reading, a parallel from a tradition the corpus hasn't yet treated well — Discussions is the place to flag it. Include a citation, a paragraph on why the source matters, and ideally a specific page or passage in the corpus where it would be relevant.

Translation coordination

The site is published in nine languages, and additional translations are welcome. Translation work is coordinated through Discussions: scope, glossary, style questions, review.

Introductions

If you are new to the project and want to say hello, the Discussions support an introductions category. There is no expectation that participants introduce themselves; the project is happy to have readers who only ever lurk.

What it's not for

• Factual corrections to a specific page — those go on the issue tracker, not Discussions.
• Code or infrastructure work — pull requests and issues on the relevant repository, not Discussions.
• Private messages to the author — the Discussions are public by design. If something genuinely needs to be private, the project's Code of Conduct describes the appropriate channels.

On register

The Discussions are a public space and follow the project's Code of Conduct. Substantive disagreement is welcomed; personal attacks, harassment, and targeted hostility are not. Read the Code of Conduct before posting if you have not already.

The project's scholarly register applies in Discussions too, though more loosely than in the corpus itself. The author writes there in the same voice they write the corpus in — direct, source-aware, careful about claims — and that is the register that gets the most useful responses.