Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?
One graph for the whole story. At the bottom, the 359 changed hunks of the php2shell fix, each a line range in php-src; above them the functions and files they sit in, the parts of the fix, the two flaws; then the claims and events that talk about them and the sources those cite; then the story arcs those claims carry, the risks the arcs describe, and at the top the fifteen kinds of reader who face those risks. 895 nodes, 1230 edges. Every node opens into its own neighbourhood: walk it, from the top or from a line.
| Layer | Nodes | Where it comes from |
|---|---|---|
| Stakeholders | 16 | the fifteen readers in data/personas.json |
| Risks | 9 | authored in data/arcs.json, each resting on claims |
| Story arcs | 7 | authored in data/arcs.json, each carrying risks and resting on claims and events |
| Claims and events | 138 | data/claims.json and data/timeline.json, each with a status or a date |
| Sources | 91 | the captured, hashed sources the claims and events cite |
| The flaws | 2 | the two CVEs, from data/review.json |
| The fix | 7 | the commit and what it does, from data/review.json |
| Areas and files | 73 | php-src areas and files the fix changed, from review/code/files.json |
| Functions | 193 | the C functions the fix changed, from the diff |
| Lines | 359 | every changed hunk, with its line range in php-src |
The top three layers and the joins from a claim to a flaw or a part of the fix are written by the librarian in data/arcs.json; everything else is derived by the build from files the site already publishes. The assembled graph is data/fractal.json.
Each is the shortest path down the ladder from one reader to a changed line, computed by the build. Click any rung.
| Edge | Count |
|---|---|
| changed at | 359 |
| cites | 293 |
| changes | 193 |
| rests on | 124 |
| dated by | 67 |
| faces | 44 |
| contains | 37 |
| about | 36 |
| touches | 36 |
| told in | 18 |
| realised in | 9 |
| closed by | 8 |
| introduces | 6 |
Edges are read top down: a stakeholder faces a risk, a risk is told in an arc and rests on claims, a claim cites sources and is about a flaw or a part of the fix, a flaw is closed by the fix, which is realised in files, which change functions, which are changed at lines. The navigator walks them both ways.
The fix-only version of this graph is the fix mapped to the code; the citation graph alone is as a graph. This answers the second memo's ask for the semantic fractal graph; what it still lacks is on corrections.