Skip to content

Graphify maintenance

Purpose and boundary

Graphify maps the technical repository: source files, headings, code symbols and their structural connections. The publication step enriches that extraction with Wiki document links, registered-source references, Zensical navigation, filesystem hierarchy and explicit file references.

This is operational metadata. It is not the case–mechanism/evidence map, does not add a source to the reviewed corpus and cannot support a coronial or Defence claim. Preserve the canonical authority chain:

primary source → report → claim → mechanism → candidate requirement → assurance test

Shared-data contract

npm run graph:update produces four runtime assets under the generated boundary:

Asset Role
assets/generated/graph.json One complete enriched node/relationship dataset used by both views
assets/generated/graph.html Graphify's searchable and filterable 2D view
assets/generated/graph-3d.html Force-directed 3D view of the same dataset
assets/generated/summary.json Counts, named layers and generation metadata used by checks and text summaries

The page component embeds the appropriate renderer and links to the shared JSON and summary. It must not cap the graph to a convenient subset or fabricate depth from a 2D drawing.

Enrichment semantics

  • links to follows an internal Markdown link.
  • defines source joins the source register page to a registered SRC- reference node.
  • cites source records that a repository document mentions a registered source ID. It is not a finding that the source supports every statement on that page.
  • nav contains follows the production Zensical navigation hierarchy.
  • filesystem contains records repository path hierarchy.
  • references file records an explicit repository-file reference in text.

These technical relations do not replace the source register, screening log, included-case dataset or claims register.

Update and verification

  1. Run npm run kb:update after canonical content or workflow changes.
  2. Run npm run check:graph to verify asset presence, same-data parity, enrichment layers, counts, provenance and freshness metadata.
  3. Run npm run verify for all content, profile and strict-build checks.
  4. Inspect both rendered routes at desktop and narrow widths before publication.

Never edit graphify-out/ or docs/assets/generated/ by hand. The updater deletes old generated assets before raw extraction so Graphify cannot ingest its own prior publication.