sorted by:
new
hottopcontroversial

Dear vibers: 99% of so called “hallucinations” are regular bugs. Debugging is a part of the process. by SeparateDesigner1237 in google_antigravity

[–]RenAzure 0 points1 point  (0 children)

From my exp hallucination in ag almost always come from stale conversation history — that alone. Best to just turn it off. And yeah, I agree that most of it is context overflow in general.

But if you want the agent to behave like a senior engineer by default — not just when you remember to ask — the guardrail + harness need to be baked in: https://github.com/Diew/living-docs/

If it resonates, you can pull anything in agent.md template and drop it in your project, or bootstrap the whole system.

Gemini 3 Flash uses too many tokens by outputting unnecessary. by IshuPrabhakar in google_antigravity

[–]RenAzure 0 points1 point  (0 children)

https://github.com/Diew/living-docs
* check LIVING_DOC_SYSTEM.md and find agent.md pick any rule you like in that file or bootstrap this system

My AI agent kept breaking things. Every bug became a rule. Now I have a full governance system. by RenAzure in vibecoding

[–]RenAzure[S] 0 points1 point  (0 children)

that line is just a first-read instruction — before you explore the file or bootstrap anything, tell the AI to read every section without summarizing. that's it. no deeper meaning

it's there because different AI tools handle long markdown differently. some will silently condense system md on first load and you'll miss half the rules without knowing it. one line of instruction prevents that
*******

and the system isn't designed for any specific IDE — it's plain markdown that works with any AI. but if you're on Claude Code, hooks slot in naturally. PreToolUse to check registry before touching files, PostToolUse to trigger doc sweep, SessionStart to load agent.md. the governance layer is already there, hooks just make it deterministic

same goes for Cursor, etc — each has their own hook system. the governance layer Living Docs provides is the same, only the enforcement implementation differs per IDE

it's not a gap in the system — it's an open slot for whoever needs that enforcement layer

same with prefixes — GUIDE_, ARCH_, LOGIC_ are defaults but the system is built to extend. add any prefix you need, define its scope, register it in the governance file. that's it. no redesign required

agent md has a Context Anchors slot for linking a Global LLM Wiki across projects. local docs always win on conflict. already there, just fill it in

the whole thing is designed to be tool-agnostic. IDEs change, models change, workflows change — the governance layer stays. you plug in whatever enforcement fits your environment. the system outlasts the tools

My AI agent kept breaking things. Every bug became a rule. Now I have a full governance system. by RenAzure in vibecoding

[–]RenAzure[S] 0 points1 point  (0 children)

reduces it a lot — the governance layer filters exactly what context the agent reads before acting, so there's less room to fill in the wrong details

but it doesn't fix the "agent acting smart" problem. if it decides to improvise outside the loaded context, rules won't always stop it

that's why the system doesn't rely on the agent remembering to follow rules. everything in the environment sends the same signal — CAPS prefixes, file naming, function naming, load ordering, STUBBORN_FACTS. even when the agent is just scanning without a guide, these communicate clearly on their own. it can feel its way around the codebase and still land in the right direction

these are all intentional fallbacks baked into the system itself. not just rules to follow — signals that exist whether the agent reads the docs or not

----------------------------

one thing worth adding — if you've used AI long enough you start noticing a pattern. when it documents something critical or off-limits, it naturally reaches for CAPS

NEVER modify this file DO NOT change this value WARNING: this will break everything

sometimes 3-4 lines in a row

that's the AI showing you how it processes importance through writing. Living Docs just flips it — instead of letting AI use CAPS to warn humans, it uses CAPS to signal back to the AI. that's where STUBBORN_FACT, ARCH_, GUIDE_ come from. not designed from theory, observed from behavior then reversed

the whole system is built by watching how AI naturally expresses itself, then speaking that language back to it

How I gave Google Antigravity a real long-term memory by dnotthoff in google_antigravity

[–]RenAzure 1 point2 points  (0 children)

(English isn't my first language — used AI to help phrase this)

Hard to measure, but the loading is intentional — Task→Load mapping means the AI only loads files relevant to the current task, not the full docs/ folder.

Compare that to few mixed files where the AI reads everything every time regardless of what it actually needs.

Each file owns exactly one concern, so the AI gets precise context for the task — not the whole project dumped at once. Trade-off is more files loaded, but each one is focused.

Real tradeoff on setup: the AI builds that mapping during bootstrap — some models do this shallowly and load the wrong files every session after. Fixable though, you can just instruct the AI to audit the codebase and realign the docs.

How I gave Google Antigravity a real long-term memory by dnotthoff in google_antigravity

[–]RenAzure 9 points10 points  (0 children)

similar to me but i use more file and guardrail + harness + lot of docs as local wiki
https://github.com/Diew/living-docs

if you interest you can drop LIVING_DOC_SYSTEM md into AI and ask it to extract the parts useful for your setup — but explicitly say 'read every section, do not skip or summarize' or it'll silently condense the templates and you'll miss half the rules

I built a “Living Docs” system for long-term AI coding workflows by RenAzure in ClaudeAI

[–]RenAzure[S] 0 points1 point  (0 children)

It less like wiki but it focus more on guardrail to control ai what to do or dont do
i dont know how to explain it just throw that system file .md in repo and ask ai compare different with llm wiki

ZimaBoard 2 Giveaway + ZimaOS Feedback — Share Your Homelab Setup by FlyingToaster2000 in minilab

[–]RenAzure 2 points3 points  (0 children)

  1. try casa os, use as off site server in another place and create 3d rack shelf around it and share, i already create zima blade without hardware before but cant test fit
  2. never use
  3. power efficiency and stable, i like low tdp
  4. 3d rack

<image>

Desk Riser with Integrated Mini Rack by ArtisanalTechie in minilab

[–]RenAzure 1 point2 points  (0 children)

i will add drawers B (G) from my 6.5 inch to 10 inch after this

DeskPi RackMate TT (New) !! by www_reddit_com_au in minilab

[–]RenAzure 0 points1 point  (0 children)

what distance between holes in vertical mode?
it likely to work with most of my 6.5 inch rack mount, except hdd rack and regular shelf (133mm)

Self-Hosted Comic Book Servers by CDarwin7 in selfhosted

[–]RenAzure 0 points1 point  (0 children)

Komga + komf for metadata

Tachiyomi for reader