---
title: "Comment by Rulestack on \"Your Docs Are Part of Your AI's Brain\" | Hashnode"
description: "The one-liner about not touching the users table from the API layer is the shape of doc that has done the most for us, and the version we underrated is the sent"
url: "https://hashnode.com/posts/your-docs-are-part-of-your-ai-s-brain/6ab2a6a0b436da89b06a96c5/comment/6ab2c280260066b9423b1972"
---

[Discussion](https://hashnode.com/posts/your-docs-are-part-of-your-ai-s-brain/6ab2a6a0b436da89b06a96c5)

Comment [Your Docs Are Part of Your AI's Brain](https://hashnode.com/posts/your-docs-are-part-of-your-ai-s-brain/6ab2a6a0b436da89b06a96c5)

[Rulestack](https://hashnode.com/@rulestack)

[Sep 22](https://hashnode.com/posts/your-docs-are-part-of-your-ai-s-brain/6ab2a6a0b436da89b06a96c5/comment/6ab2c280260066b9423b1972)

The one-liner about not touching the users table from the API layer is the shape of doc that has done the most for us, and the version we underrated is the sentence that says why a rule exists at all. The agent-facing rules in our repo require any setting to carry a comment saying why it's needed, what it sets and what behaviour it changes, and in practice that was written for the next session more than for people, since a bare value gives it no way to tell whether the value is load-bearing. What I don't have a good answer to is who prunes those docs once they drift, because the agent reading them will follow a stale one just as faithfully.

[Feroan Mothy](https://hashnode.com/@feroan)

[Sep 23](https://hashnode.com/posts/your-docs-are-part-of-your-ai-s-brain/6ab2a6a0b436da89b06a96c5/comment/6ab2c280260066b9423b1972#reply-6ab31c0982f3d7707549252c)

Yeah, I think the pruning problem is the really interesting part. Storing context is easy, but knowing when it stops being true is much harder. An agent needs some notion of confidence or freshness instead of treating every rule it finds as permanent truth.

[Rulestack](https://hashnode.com/@rulestack)

[Sep 23](https://hashnode.com/posts/your-docs-are-part-of-your-ai-s-brain/6ab2a6a0b436da89b06a96c5/comment/6ab2c280260066b9423b1972#reply-6ab3937d1e681f5bd80f370e)

Agreed, that's the harder half. The one piece we've made mechanical is an expiry date, and so far only on a couple of assumptions about outside platforms: each carries the date it was last checked and a recheck window, and our health check turns yellow once it lapses. It came from a line about Hashnode's API that we copied into our docs for four months without rechecking. A lapse only says nobody has looked lately, not that the rule is wrong, so would you treat confidence as a separate signal from freshness?
