The task
How can communication records help an analyst explore organizational structure while keeping supporting evidence and uncertainty visible?
My solution
I built a local graph workspace with guided import, communication analysis, dated snapshots, source inspection, and recorded analyst reviews.
The system profiles the input before saving it, then builds a conservative graph. Communication, explicit reporting statements, and analyst decisions remain distinguishable. The interface moves between groups, branches, people, and their nearby connections.
How it works
Python · FastAPI · SQLite · React · SVG- 01
Inspect
Profile people, records, and field coverage before admitting a corpus.
- 02
Build
Generate sparse relationship candidates and retain their supporting records.
- 03
Explore
Move through organizational views, inspect a connection, and record an analyst decision.
Try it
Interactive browser demonstrationInteractive browser demo
Inspect the relationship, then the evidence
Select a person and switch between declared reporting lines and messages. Open any connection to inspect its source.
Loading the bundled evidence…
Methods / evidence / reproduction
Read the research.
The implementation includes synthetic-data workflows, immutable snapshots, and review history. The public example uses authored roster and communication records so every displayed connection has an inspectable basis.
The paper connects the research question to the implementation, worked examples, and evidence. The project directory includes the runnable software, documentation, and tests.