Skip to main content

Documentation Index

Fetch the complete documentation index at: https://cognis.vasanth.xyz/llms.txt

Use this file to discover all available pages before exploring further.

Cognis is a small project run by people who want to ship a tool they’re proud of. We expect contributors and maintainers to treat each other the way you’d want to be treated.

In short

  • Be kind. Disagreement is fine; condescension and trolling aren’t.
  • Assume good faith. People misread tone in text. Ask before escalating.
  • Focus on the work. Critique code, not contributors.
  • Listen to feedback. Including review comments you didn’t expect.
  • Don’t be a gatekeeper. Newcomers are welcome; their first PR is allowed to be rough.

Specific behaviors we expect

  • Use inclusive language. The whole field is rebuilt from scratch every two years anyway — no one is “supposed to know” everything.
  • Accept that we’ll change our minds. APIs evolve. Decisions get revisited. That’s not a personal failure.
  • Default to public. Most discussion belongs in issues and PRs, where future contributors can read it.
  • Keep private channels for sensitive matters. Conduct issues, security disclosures, and personal disagreements happen out of the public eye.

Behaviors we don’t tolerate

  • Personal attacks, insults, or demeaning language.
  • Sustained disruption — heckling reviewers, derailing discussions, repeating dismissed points.
  • Sexualized language or imagery; sexual attention or advances.
  • Doxxing or sharing others’ private information without consent.
  • Threats of violence, including jokes about it.

Reporting

If something happens — to you or someone else — that doesn’t fit what’s described above:
  • In a PR or issue: flag it to a maintainer with a comment or a DM.
  • Privately: email the maintainer (see the GitHub profile of @0xvasanth).
  • Anonymously: there isn’t a formal anonymous channel today. We’ll add one if the project grows to need it.
We’ll respond, listen, and act. The default response to a credible report is to address the behavior with the person involved and, where appropriate, take action — warnings, removed comments, or, in severe cases, removal from the project.

Reviewers and maintainers

The same standard applies. Reviewers don’t get to be sharper than contributors because they have merge access. We hold maintainers to the same conduct expectations as anyone else; if a maintainer crosses the line, the same reporting path applies.

Scope

This code of conduct applies in:
  • The Cognis repository (issues, PRs, discussions).
  • Cognis-related events (real-life or virtual, if we have them).
  • Direct messages between participants explicitly about Cognis.
It does not apply to participants’ behavior in unrelated contexts — but if someone’s behavior elsewhere makes the Cognis community unsafe, that’s a project decision to make.

Attribution

This document is light by intention. If the project grows, we’ll align with Contributor Covenant or a similar formal CoC. Until then, the principles above are the operating rules.

See also

Ways to contribute

Where to start.

PR guidelines

What review feedback looks like.