Contributing

How to contribute to projects in the Samaritan constellation

Everything here is MIT licensed. Take it. Build on it. Fork it. Make it yours. That's not a slogan — it's the license.

How to contribute

Every project in the constellation lives on GitHub under github.com/Fimeg. The workflow is standard:

  1. Fork the repo you want to contribute to
  2. Create a branch for your change
  3. Make your changes — code, docs, tests, whatever helps
  4. Open a pull request with a description of what you changed and why

That's it. No CLA, no contributor agreement, no hoops.

What we need

Code contributions

Every project has open issues. Some are tagged for newcomers. If you see something broken, fix it. If you see something missing, build it. If you're not sure whether a change makes sense, open an issue and ask — I'd rather catch a misunderstanding early than watch you build on a wrong assumption.

Documentation

Documentation is always valuable. If you deployed one of these projects and the setup instructions were unclear, improve them. If you found an edge case that isn't documented, document it. If you wrote a guide for your own use, consider contributing it.

Bug reports

Good bug reports are a contribution. Include: what you expected, what happened, steps to reproduce, your environment. Screenshots or logs if relevant.

Testing

Run the test suites. Try edge cases. Deploy on hardware or operating systems the author didn't test on. Report what breaks.

Project-specific notes

RedFlag — 170 tests across 18 packages. If you're adding a feature, add tests. The security model is intentionally strict — changes to auth, signing, or command execution get extra scrutiny. Discord for discussion.

NetworkChronicles — Narrative contributions welcome. If you want to write game content (challenges, story elements, flavor text), open an issue to discuss the direction before writing extensively.

Souveraine — Read docs/THE_QUESTION.md before contributing. The architecture is opinionated and the terminology is precise. Contributions that understand the substrate/harness distinction are valued. Contributions that introduce "agent framework" patterns get redirected.

The philosophy

I don't gatekeep knowledge. The entire point of releasing work under MIT is that the ecosystem grows when people build on it. If something I've built improves your situation, use it. If you improve it, share the improvement.

Acknowledging where ideas come from is good practice. So is building the next thing and releasing that too.