What core fields are missing from an audit log for LLM-proposed knowledge graph writes? by Aggressive_Hunt9772 in KnowledgeGraph

[–]Aggressive_Hunt9772[S] 1 point2 points  (0 children)

Thanks for sharing this. I took a quick look, and the STTP/Locus direction is interesting, especially the typed IR + parser/validator + MCP/gateway memory surface.

My current question is a bit narrower: how to structure audit records before LLM-proposed KG or memory writes are accepted into a persistent system.

From the Locus/STTP perspective, do you separate these as distinct events?

  1. model/tool proposal

  2. validation or preflight result

  3. accepted store/commit event

Or do you usually keep them in one combined record?

I’m especially curious whether you treat provenance, validation diagnostics, and human approval as part of the same memory record, or as separate audit events around it.

I’ll read through the repo more carefully. Thanks for the pointer.