Engineering
Agent tooling
Graphify and Cognee — how engineers and agents navigate E-FACTS code
Agent tooling
E-FACTS uses durable graphs and memory so humans and coding agents share context.
Graphify
Cross-project code graph: ~/.graphify/global-graph.json
Indexed tags include: efacts_inc_2026, efacts_v1, efacts_backend, efacts_iosapp, efacts_website, and this docs site when indexed.
graphify query "EFACTS shopper auth receipts" --graph ~/.graphify/global-graph.json
graphify path "RootTabView" "ShopperAPIClient" --graph ~/.graphify/global-graph.json
graphify explain "wallet bind" --graph ~/.graphify/global-graph.jsonAfter meaningful code changes in an indexed repo:
graphify update <project-dir>
graphify global add <project-dir>/graphify-out/graph.json --as <tag>Do not index node_modules, .next, .git, venvs, or binaries.
Cognee
Durable project memory across Coding Projects.
| Dataset | Scope |
|---|---|
efacts_inc_2026 | Current portal / 2026 work |
efacts_v1 | V.1 backend + iOS |
efacts_website | Marketing site |
efacts_backend | Backend services |
Recall before deep debugging or architecture questions. Remember after decisions, root causes, and session outcomes.
Cursor rules
Example: .cursor/rules/performance.mdc — Server Components first, lazy hero visuals, reduced-motion, image/font discipline.