pub const ASSOCIATION_TOOLS: [&str; 16];Expand description
The sixteen a memory store advertises, in the order it lists them.
A store with no repository in it used to be handed the code door’s own task
tools — map, context, impact, owners, why, sync — which answer
from a code graph there is none of, plus ingest_json. Six of the eleven
names an assistant found answered from a repository the store did not
hold. These are
the questions an entity graph can answer: what is there (query — now
with a role), why two things are associated, what is around a node, what
it is and what it is joined to, whether a link held at a commit and when it
changed, what is like it, and what was written down about it.
Listing order is ranking: a host that defers schemas shows this list in order, so the two questions this door exists for come first.
edges_at and what_if are the two the first association benchmark run
showed missing: a run asked what a node’s relationships were at a past
commit and spent twenty to sixty-seven turns replaying edge_history for
it, and had no way at all to ask what a change would do. They sit after
was_linked, which is the narrowest form of the same time question.
The code task tools stay served on a memory store, as these stay served on
a code-graph one — [tools_list] decides what is advertised, never what
is answered.