I recently built our knowledge management system based (loosely) on the Karpathy LLM-Wiki model. I'm not sure I understand why it is so important to be multi-a

I recently built our knowledge management system based (loosely) on the Karpathy LLM-Wiki model. I'm not sure I understand why it is so important to be multi-agent, or for each agent to define who they are and what changes they made. Our process uses git for tracking, so much of these details are captured natively in the merge. Our process is Drop a change, or something to document in an "inbox". Agent makes a branch, processes the inbox materials, updates the documents that need to be updated, updates timelines, makes a note of others on the team that may need to be notified of changes. Creator reviews the PR and ensures the changes match how they want the document to be updated. Anyone that needs to be updated is now a reviewer on the PR. I've just started rolling this out to the rest of the team, thankfully we are an engineering heavy organization so everyone is comfortable in Git. The system keeps a running audit log, input is never deleted, it's stored, documents are updated, people are notified, etc. etc. I'm just not sure what the service is offering, and how being multi-agent is solving a problem, but maybe I just haven't hit that problem yet.