Skip to content
Library · Evidence map

A map of the work, with its evidence

References, declared context, historical documents and bibliographic records. Storage folders are not architectural boundaries; proximity is not proof.

Search and graph controls

Loading the generated evidence map…

Canvas timing appears after the graph loads.
Legend and evidence boundaries
governancesecurityarchitectureagentsidentityplatformresearchstandardsguidesplansexecutionevidencelanguagetoolingdataoperationsunclassified

Fill = presentation domain derived from declared category/area; original values remain in the inspector. Unmapped values use neutral fill. Circles = documents / papers; squares = generated membership nodes. Size = relationship count. Border = declared document status: green active/current, amber historical/draft/planning, red superseded/deprecated, dashed gray unknown. These declarations do not prove current implementation. Solid lines = explicit references; dashed = structural membership; dotted = shared tags. The resting backbone prioritizes existing bridges and hubs. Faint labels name only declared project/system/component/repository groups; unnamed neighborhoods come from link topology. Loose storage satellites do not assert systems. Overview, neighborhood and close views progressively restore deterministic path detail. Bridge emphasis changes visibility, never evidence weight. Membership is a soft spatial influence, not an orbit or an internal relationship. A pale diamond marks a document lacking declared provenance, independently of its domain and status. The legacy Unknown bucket and its diagnostic membership records remain in the downloadable corpus asset, but never appear as nodes, links or neighbors. The inspector retains every non-diagnostic relationship. Wheel over the graph zooms it; wheel outside scrolls the page. Position and shared tags never assert architecture.

Back to Library