|
|
|
|
|
by ksajadi
16 days ago
|
|
that's an interesting approach and something i also considered (using git to avoid conflicts). one thing i needed was a "database" (basically a folder of markdowns) with a fixed schema so i can let the agents record their decisions in (for example when the code conflicts with product design spec). this combined with search has been a real lifesaver. this is how it works: https://help.markbase.cloud/humans/collections/overview |
|
https://arxiv.org/abs/2602.11988
For what it's worth, if you were considering building context out.