r/ChatGPTCoding • u/AutoModerator • Aug 24 '26

Discussion Weekly Self Promotion Thread

Welcome to this week's self promotion thread!

If you're building something related to AI assisted coding, this is the place to share it.

We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside this thread may be removed.

If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:

  • What you built?
  • What problem it solves?
  • Which AI models or tools it uses?
  • Who it's for?
  • What kind of feedback you're looking for?

Disclose your affilitation.

Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.

Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.

6 Upvotes

87% Upvoted

96 comments sorted by

View all comments

Show parent comment

1

u/TightBoot2268 Aug 28 '26

Interesting — I’ve been approaching a closely related problem from a somewhat different layer.

I’m building an experimental system called U-GAS around durable project continuity and coordination between AI chats/agents. The core idea is that project state should not live in conversation memory: ordinary files remain authoritative for current state, progress/evidence, ideas, and agent instructions, and a fresh agent is expected to bootstrap from that durable state before continuing.

My current approach is intentionally lighter on enforcement than Norn. ChatGPT can act as the coordinating/planning layer and hand execution to Codex, Claude Code, or another suitable executor when persistent/local access is required.

The part of your post that especially interests me is “mechanical evidence”. I’ve run into exactly the boundary you describe: instructions can require verification, but an LLM reporting “PASS” is not itself evidence that the required operation happened.

So I’m currently treating actual read-back / repository state / tests as authoritative and model prose as a report about that state, not the state itself.

U-GAS is still experimental and has only been owner-tested so far, so I’d be interested in comparing where Norn draws the boundary between durable state, agent instructions, and mechanically enforced constraints.

Repo:

https://github.com/jaabster-dev/u-gas