Show HN: Gnosis, a knowledge base for what the code can't tell you(github.com)
6 pointsby stavros5 hours ago3 comments
  • michelhabib2 hours ago
    Im currently using mintlify, with a section for design decisions, and why i picked evey one. usually i start by discussing the design, comparing options, picking a suitable one with a certain criteria, document it all in an md, and add it to that section. what is the workflow in your case?
    • stavros2 hours ago
      Basically, it's an instruction for the agent to search for existing knowledge before implementing, record decisions as they happen, and review what should be captured after finishing.
  • sebakubisz4 hours ago
    Rejections are usually conditional on the world at the time: a constraint, a dependency, a workaround that exists today. When those conditions change the rejection is stale but the log still reads "we tried this and it failed." How do you think about surfacing stale entries for revisit? Is it on the agent to spot them on its own or is there a manual deprecation step?
    • stavros4 hours ago
      There isn't a manual deprecation step, because the agent has no context outside what the human gives it. Deprecation happens when conflicting information is given ("you want to do this but this note says you tried it before and it failed, what do you want to do?").

      At that point, either the human decides to go for it and the new decision is noted, and the old decision is superseded/removed, or the human says "wow I'm sure glad I'm using gnosis" and everything is left as-is.

  • neowalteran hour ago
    [dead]