Skip to main content

ASSOCIATION_TOOLS

Constant ASSOCIATION_TOOLS 

Source
pub const ASSOCIATION_TOOLS: [&str; 23];
Expand description

The tools every 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, which answered from a code graph there was none of. Those tools are gone, and a store ingest-git built is an entity store like any other, so it is served this same listing. 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.

[tools_list] decides what is advertised, never what is answered: the two served tools this leaves out, explain and rename_node, stay callable.

upsert_entity, ingest_json and create_rule were added in 0.6.12, and the reason is the shape of a first session. A new install opens on an empty store; the skill’s first instruction is to offer to fill it, naming ingest_json for a batch and upsert_entity for one; and the README sells upsert_entity -> create_rule -> find_similar -> explain_association as the minimal workflow. Two of those four were served and not advertised — and a host builds its tool set from tools/list, so “served” did not help. The listing described a store you could question but never populate.

They sit after the readers deliberately. Listing order is ranking and the questions remain the point; writing is what a session does once, at the start, before it has anything to ask.