The Mapping Problem: Visualizing the Energy X Ninety-Two Network

Four Days to Print

[serious] We are exactly four days out from the deadline for the Årebladet scoop. On the disk, twenty-seven parquet tables are beautifully organized, capturing every permit, corporate filing, and environmental overlap across Region Jämtland Härjedalen. The architecture is settled, the database is performing flawlessly, and the automated fact pack verifier is standing guard. But as you look at the terminal, a fundamental question emerges. How do we take a complex web of extraction permits, corporate renames, and interlocking international jurisdictions and turn it into a visual narrative that a human being can instantly grasp?

The core of this investigation isn't just a list of mining coordinates. It is a story about hidden relationships and tight operational sequences. We are dealing with an intricate corporate chain that spans four separate jurisdictions, tracking an unlisted entity through messy boardroom transitions and unexpected extraordinary general meetings. To crack this open for the editors, and eventually for the public, we need to map the connections between people and companies alongside the strict arrow of time. Let's look at the immediate options for standing up these visualizations without breaking our existing codebase or disturbing the parquet schemas.

The Web of Nodes

When you are looking at corporate networks, you are dealing with a classic graph problem. You have entities like Energy X ninety-two AB and its various foreign parent companies, and you have edges representing ownership shares, director seats, and witness signatures. Because your user interface is explicitly built with zero javascript build tools, relying on fast-a-p-i, jinja templates, and h-t-m-x, you want something that drops in with a simple script tag. The cleanest path for your internal research dashboard is a tool called py-vis.

Py-vis is a python library that wraps around a popular interactive browser layout engine. What makes it incredibly elegant for your current situation is that it allows you to build the entire network graph directly in your python backend. You query your current views in duck-d-b, iterate through the corporate pairs, add nodes and edges using pure python syntax, and let the library generate a self-contained block of interactive visual data. You can pipe this directly into a jinja template using a basic frame element, or lazy-load it with an h-t-m-x trigger only when you click on a company dossier.

The beauty of this approach is absolute isolation. You do not have to configure complex bundlers, handle heavy node modules, or write tricky front-end state management. Python handles all the heavy data lifting behind the scenes, and the browser simply renders a beautiful, draggable, physics-driven canvas without any compilation friction.

This gives you an immediate internal tool to spot hidden patterns across the entire region. When you load the data for the background companies, you can visually audit whether the same individual is popping up as a witness or a director across seemingly unrelated mining entities. It takes the cognitive load off your brain and puts it onto the screen, all while respecting the strict, read-only architectural boundaries you settled on earlier this week.

The Print Dimension

Internal research tools are excellent for discovering a scoop, but print newspapers operate under completely different constraints. An interactive, draggable browser canvas does not help an illustrator designing a static layout for a physical page in Årebladet. For the final print publication, your best asset is a dedicated desktop data application called gephi.

Instead of rendering html inside your user interface, you can write a tiny export utility inside your python tools folder that dumps your data into a standard graph exchange format file. When you import this file into gephi on your laptop, you gain total aesthetic control over the corporate web. You can scale the size of the text and nodes based on how many connections they have, instantly highlighting major hubs of mining activity. You can color-code the companies based on their country of registration, instantly separating the local Swedish operations from parent entities operating out of foreign jurisdictions like Australia.

Most importantly, gephi allows you to export high-resolution vector graphics like s-v-g or vector p-d-f files. When you hand these vector files over to the graphics team at the newspaper, they can adjust fonts, match the publication style guide, and ensure the final diagram looks perfect next to the text. It bridges the gap between your automated data spine and the traditional layout needs of a physical newsroom.

The Arrow of Time

[calm] Network graphs excel at showing who is connected to whom, but they are notoriously bad at showing when things happened. For an investigative piece like the Energy X ninety-two scoop, the timing of events is everything. You are tracking a highly specific chronological sequence: corporate renames, permit applications, sudden regulatory freezes, and specific board decisions. To make sense of this quick progression, we need a dedicated timeline view.

For your internal dashboard, a heavy third-party javascript timeline library is completely unnecessary. A clean, vertical sequence built with pure style sheets inside your jinja templates will serve you best. You can select the event date, the event type, and the description directly from your current timeline view in duck-d-b, sorting them in descending order. By wrapping this in an h-t-m-x infinite scroll container, you can smoothly scroll through the entire historical diarium without ever leaving your main research interface.

However, if the newspaper eventually wants an interactive digital timeline for their website, the gold standard is timeline jay-es, built by the knight lab. It is open-source, designed specifically for journalists, and beautiful right out of the box. You configure a single endpoint in fast-a-p-i that transforms your database timeline rows into the standard structure required by their framework. Their code handles the animations, the scaling of the time axis, and even native embeds for source documents, giving the public a rich way to explore your findings step by step.

With four days left on the clock, the goal is clarity without distraction. Building a quick python script to generate a standard frame network canvas or a clean vertical timeline will give you the visual validation you need to close out the remaining article gaps. It transforms your twenty-seven parquet tables from an abstract database on disk into a vivid, undeniable map of corporate maneuvering.