Use the team’s earlier decisions
The developer asks dev-ui@factory to use a backend approach chosen last month. The decision is part of the project’s saved knowledge; it does not have to be present in the agent’s immediate conversation.
What happens
Find the route to the answer
The agent reads RESEARCH-ROUTES.md. That project file points to the integration decision at factory-project/DECISIONS.md#shared-client.
Retrieve the relevant section
rig context get returns the named section. It includes both the choice—use the shared client—and the reason: existing integrations depend on its reconnect behavior.
Carry the reason into the implementation
dev-ui@factory chooses the shared client for the new feature. Knowing the reason helps it preserve behavior that a fresh implementation might otherwise overlook.
What OpenRig does
OpenRig retrieves addressable context from a configured project context pack. Here the agent asks for a specific file section, rather than loading every project document into its conversation.
What Claude or Codex does
The agent follows the research route, requests the section and uses what it reads. The route and decision are authored project material. The retrieval shown here is an explicit tool call; it is not automatic discovery or a transfer of another agent’s private reasoning.
When this helps
Months of project knowledge can stay available without every agent carrying all of it at once. Useful routes let an agent find the relevant decision when its current work needs it.