| ▲ | wewewedxfgdf 3 hours ago | |||||||
I built a system that records numbered design decisions and numbered requirements as claude works in a Postgres database organised as a graph with links/interconnection between items. It's an MCP server that Claude uses as we develop so there's a permanent record of everything and work is driven by requirements and decisions. | ||||||||
| ▲ | vecter 4 minutes ago | parent | next [-] | |||||||
Sorry, I'm not following. What does this graph of design decisions and requirements have to do with architectural design and code quality? And, how is the graph constructed (i.e. what determines what the nodes and vertices are)? | ||||||||
| ▲ | taurath 3 hours ago | parent | prev [-] | |||||||
I've seen dozens of those, Claude even suggests building them, and they are all crap after a month. Just updating all the references of decisions becomes onerous. Make one change, it cascades everywhere, eventually all turns to utter crap. The gastown project failed in part due to agents inability to continuously carry context and it kept working on the information system instead of the problems. Good luck to you. | ||||||||
| ||||||||