agentic engineering scorecard→agentic engineering scorecard→practice - context right in the repo→documentation context graph

documentation context graph
documentation context graph

Backlinks

documentation context graph -- document

^ documentation context graph -- document

see in context
practice - context right in the repo

I think this mostly means having something like a documentation context graph right in the codebase alongside the code.

see in context

My context is in my main markdown graph (more specifically the documentation context graph), which is in a different repo and is copied in. The challenge is that it's about Meadow, but also links to many adjacent things about psychology, indie hacking, etc. This doesn't feel quite right, yet, and I'm struggling to find an optimal solution.

see in context
practice - grill with docs for spec creation

In blog post - OpenAI harness engineering 2026-02, in the section about documentation there is a quote about when everything is important nothing is important. It also describes how documentation skews from code is inevitable in a large document because it's impossible to do things like cross-check links, look at metadata around how recently something was updated, etc. So they suggest breaking things apart into what I call a documentation context graph. I think that's probably superior to the CONTEXT.md file being advocated by Matt.

see in context
review - Open AI harness blog post - 2026-02-22

Note: in this section they describe their documentation. I've been referring to this type of documentation as a documentation context graph

see in context
specialized agent -- code merge

One thing that can help such an agent is practice - context right in the repo, especially a documentation context graph

see in context

documentation context graphdocumentation context graph

documentation context graph
documentation context graph