docs(architecture): point new language extractors at extractors/, not extract.py - #2289
docs(architecture): point new language extractors at extractors/, not extract.py#2289PathGao wants to merge 1 commit into
Graphify — looks good
Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).
Details
Graphify reviewed this change.
Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).
Graphify review — findings
This PR updates the "Adding a new language extractor" section of ARCHITECTURE.md. It revises the instructions to reflect a new structure where language extractors live in a graphify/extractors/<lang>.py package rather than directly in extract.py, and adds a step to re-export the function from extract.py while noting an ongoing migration away from the monolithic file. The change is documentation-only and touches the extractor onboarding steps.
No blocking issues surfaced.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 9 functions depend on the 9 node(s) this change touches.
Health — grade A; no new coupling hotspots.
Verification — 9 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 9 function(s) in the blast radius were not formally verified this run