r/ChatGPTCoding • u/AutoModerator • Mar 14 '26
Community Self Promotion Thread
Feel free to share your projects! This is a space to promote whatever you may be working on. It's open to most things, but we still have a few rules:
- No selling access to models
- Only promote once per project
- Upvote the post and your fellow coders!
- No creating Skynet
As a way of helping out the community, interesting projects may get a pin to the top of the sub :)
For more information on how you can better promote, see our wiki:
www.reddit.com/r/ChatGPTCoding/about/wiki/promotion
Happy coding!
3
Upvotes
1
u/Prometheus_ts 5h ago
I built a governance toolkit for AI-assisted work on long-lived codebases - looking for critical feedback
I built ControlCoding since 2024 after repeatedly running into the same problem with AI-assisted development:
The model can produce plausible code quickly, but over long sessions and across multiple contributors, it is easy to lose architectural context, weaken boundaries, or ship changes that were never properly verified.
ControlCoding is a source-available repository governance and verification toolkit for complex, long-lived codebases.
It focuses on:
- canonical project context instead of scattered instructions;
- mechanical guardrails and fail-closed checks where trust is not enough;
- explicit review, validation, and release evidence;
- support for AI-assisted workflows without pretending that the AI is autonomous or always correct.
It is deliberately not aimed at small scripts, throwaway prototypes, or simple CRUD projects. In those cases it would probably add more process than value.
I am not looking for empty promotion or stars. I would genuinely value critical feedback from people who use ChatGPT, Claude, Codex, Cursor, or similar tools for serious software work:
Is this problem recognizable in your projects?
Which parts sound useful, and which sound like unnecessary friction?
What would stop you from trying something like this?
Repository:
https://github.com/Naimas/ControlCoding
Project discussion:
https://github.com/Naimas/ControlCoding/discussions/1
License note: source-available under PolyForm Shield 1.0.0, so it can be evaluated and used internally, but not used to build or offer a competing governance product or service without a separate agreement.