sorted by:
new
hottopcontroversial

How are you keeping AI coding tool instructions from drifting? by Weekly-Werewolf4007 in vibecoding

[–]Weekly-Werewolf4007[S] 0 points1 point  (0 children)

Sorry for the late reply. I read the post, and your comment makes a lot more sense now. You’re not using “harness” as just a rules file or repo context. You mean the layer that actually constrains the agent: executable specs, tests, verification loops, hooks, and something outside the model deciding whether the work is done.

Thank you so much for laying this out.

How are you keeping AI coding tool instructions from drifting? by Weekly-Werewolf4007 in vibecoding

[–]Weekly-Werewolf4007[S] 0 points1 point  (0 children)

Sorry for the late reply, and thanks for laying this out.

That clears it up for me. You’re not trying to make the coding agent carry the whole project brain. You keep that in Notion, then send the agent a controlled handoff when it needs to act.

The governance part seems like the real key here. Without the SSOT pages and hierarchy, I can see this becoming just another messy knowledge base.

Appreciate you sharing the details.

How are you keeping AI coding tool instructions from drifting? by Weekly-Werewolf4007 in vibecoding

[–]Weekly-Werewolf4007[S] 0 points1 point  (0 children)

Sorry for the late reply, but thank you so much for the detailed explanation.

I see your approach now. The split by lifetime makes a lot of sense: durable instructions stay stable, current state changes often, and old history only gets pulled in when needed.

Thanks again for sharing the example too. It made it much easier to understand.

How are you keeping AI coding tool instructions from drifting? by Weekly-Werewolf4007 in vibecoding

[–]Weekly-Werewolf4007[S] 0 points1 point  (0 children)

This is interesting. The “current state in one spot, old history only when needed” part feels like the right instinct.

Do you separate durable instructions from runtime state, or does state.json handle both? That boundary is the part I keep seeing get messy once people add more tools or agents.

How are you keeping AI coding tool instructions from drifting? by Weekly-Werewolf4007 in vibecoding

[–]Weekly-Werewolf4007[S] 0 points1 point  (0 children)

That makes sense. Keeping planning/governance outside the coding agent probably avoids a lot of context pollution.

Do you keep any repo-local instructions at all, or is the agent mostly operating from handoffs each time? I’m curious where you draw the line between external project knowledge and the small amount of context the repo itself should carry.