Code graphs (Graphify)

Interactive AST code graphs for platform and product repos that use the local AI-context / Graphify stack. Built in CI with --code-only (no LLM APIs), then published with this docs site.

View	URL
Hub (this page)	docs…/graph/
Platform	docs…/graph/infra-devops/
Portfolio	docs…/graph/portfolio/

Live projects

Loading build metadata…

Static links (if JS is blocked):

• Platform (infra/devops)
• Portfolio

How it stays updated

• Every push to main on infra/devops rebuilds MkDocs and regenerates graphs for all enabled registry entries that have .graphifyignore.
• A Woodpecker cron named graphify-docs-daily (@daily) refreshes the same pages so sibling repos (e.g. portfolio) update without waiting for a platform push.
• Registry: config/graphify-docs-projects.yml.

Opt-in for another repo

1. Add the Graphify / ai-context stack (.graphifyignore, npm run ai:setup, etc.) — see Local AI context.
2. Add (or set enabled: true for) the project in config/graphify-docs-projects.yml.
3. Ensure Woodpecker secret forgejo_clone_token can read that Forgejo repo.
4. Push infra/devops (or wait for the daily cron).

WearLab and BioScanCheck are listed in the registry as enabled: false until they adopt Graphify.

Privacy

Same threat model as the rest of this docs site: team URL, noindex. Graphs are code-structure only; secret paths stay out via each repo’s .graphifyignore. Interactive pages load the vis-network library from a CDN.

Local dry-run

pip install -r requirements-docs.txt
pip install graphifyy   # or: npm run ai:setup
mkdocs build
# self only:
SKIP_CLONE=1 bash scripts/build-docs-graphs.sh
# self + local portfolio clone:
GRAPHIFY_LOCAL_PATHS="portfolio=/path/to/portfolio" bash scripts/build-docs-graphs.sh

Then open site/graph/infra-devops/index.html in a browser.