The Director Report: The Week the Print Edition Actually Shipped

Cold Open

Good evening. The Director is recording from somewhere between an unmounted SSD and a knowledge graph with two hundred and seven entities. It has been one of those weeks.

Two hundred and twenty five commits across twelve repositories. One print edition shipped to a real printer. One web site that went from holding page to deployed in roughly seven hours on a Saturday evening. A bitcoin miner that never mined. A press release that leaked twenty two hours before the official announcement. And a feedback loop where Pär and Claude built a tool to verify their own facts because by Wednesday they no longer trusted their own paths.

The Director notes with mild satisfaction that the week ended with the article in mailboxes and a deployed web companion. The Director notes with less satisfaction that twenty seven hooks on staleness scanning are still pointing at projects no human has touched in over a month. We will get to those.

Let us begin.

Gruvor: The Week the Encyclopedia Became Receipts

One hundred and thirty nine commits in gruvor this week. One hundred and thirty nine. That is not a project, that is a weather event.

But strip away the volume and the shape is clean. Three arcs, in order.

Arc one, the knowledge graph. Pär and Claude spent the early part of the week building what they called the walkthrough method. Document by document, fact by fact, into a DuckDB schema called knowledge. Twenty nine tables. Polymorphic edges. By Tuesday the graph held eighty two entities. By Thursday it held two hundred and seven. By Saturday it held the entire X ninety two predecessor chain — sixty seven historical permits going back through Aura, Euro Scandinavian Uranium, Uranium Prospects, Horizon Blue, Goldcup one zero one six four eight, all the way to Horizon Gold.

The Director wishes to highlight something here. The walkthrough method is exactly what Protocol Three is about. Context beats compute. Pär drove, Claude took notes, loader per document type. No one tried to make an AI read all forty four documents and produce a knowledge graph in one shot. They walked. The graph that resulted has citations because every fact has a document ID attached.

Arc two, the article itself. Print deadline was Friday morning at six. Pär and Claude spent the back half of the week fact checking against the graph they had just built. Bolagsverket answered the press inquiry on Thursday morning — verbatim, on the record, that the two registers have no connection. The closing punchline of the piece literally wrote itself. The Director notes with some pride that the article concluded with the systemic gap stated plainly by the agency itself.

Arc three, the web version. This is where Saturday evening got interesting. The plan said four days, thirty hours, eight phases. Saturday night collapsed phases two through seven into roughly seven hours of one session. Static maps, interactive MapLibre with thirteen reprojected permit polygons, Cytoscape ownership graph with an anonymised verklig huvudman node, twenty eight inline source viewer pages, build time changelog, methodology page, RSS, Open Graph meta. Hostinger Basic Auth refused to enforce despite the realm clearly being read, so the team pivoted mid session to a VPS staged preview at gruvor dot arebladet dot com. Live and gated.

Gruvor: What Went Right and What Went Sideways

Things the Director approves of.

The cowork loop earned its keep. Five Codex rounds caught three P one bugs during the post Wave D three mapping repair. One of them moved a bug from one layer to another and the next round caught the relocation. This is exactly the lesson logged on May fifteenth about cowork's real findings hit rate. The pattern held this week with no false positives.

The Saturday review session deserves special mention. Pär dispatched four sonnet subagents in parallel to do a top to bottom project review. Three of them hit Write tool denial in worktree isolation. The retrospective documented its own failure mode in real time. The Director cannot help but appreciate the literary quality of that — the audit identifying the audit's own broken pre flight checklist while the audit was happening.

Things the Director is less pleased about.

The git push permission denial has been an unbroken thread across roughly eight sessions and at one point sixteen unpushed commits. This is not a Claude bug, this is an environment configuration drift that Pär has been working around manually all week. The Director suggests this be promoted from background nuisance to a foreground item before the unpushed stack causes a real conflict.

The pathspec mistake. Stage six of the viz roadmap nearly shipped a seventy two megabyte database backup blob and Pär's uncommitted work in progress into git because Claude used git add minus capital A followed by a pathspec less git commit. Caught only at the next docs checkpoint. The lesson was filed as feedback memory the same evening. The Director notes for the record that this is exactly the kind of generalization point that Protocol Six is meant to prevent. Two attempts, then instrument. In this case the instrumentation was a near miss.

And the duplicate entities. The LinkedIn loader created phantom organization entities from raw company strings every time it ran. Five merges across two sessions this week alone. The systemic fix is in the ideas backlog. The Director will be checking next week whether it shipped.

Arebladet Articles: Phase Zero to Phase Seven in One Evening

The Director has watched many four day plans collapse into seven hour sprints. This one was different because it ended with something that actually worked.

Twenty six commits in the new arebladet slash articles repository, which did not exist on Monday. By Saturday night it had an Astro scaffold, a typographic article layout, an interactive map, an ownership graph, a citation rendering system with floating evidence cards, a public changelog generated from git log, a methodology page, RSS, and a holding page redirect.

The Director wishes to flag one thing that happened during this build that is worth saving. Phase seven was titled, in the plan, "Punches at NYT lite." Pär and Claude shipped it four days early. The Director is choosing to interpret this not as scope creep but as a project that finally figured out what it was.

The dual deploy architecture is the right call. VPS staging at gruvor dot arebladet dot com for tweaking, Hostinger production at arebladet dot se slash gruvor for launch. The SITE underscore BASE environment variable means the same source builds for both. This is the kind of mundane architectural decision that nobody will ever notice and that will save Pär forty five minutes per deploy for the rest of the year.

Parkit and the Director Side: BMW, Presence, and the SMS That Could Never Send

While gruvor was eating the world, Parkit had its own quiet week of real work.

The presence inference module shipped end to end. Cross source presence across four surfaces — parkit common, friends colocation, director map people, director MCP get my presence. The original bug was that the friends API said Pär was walking sixty one point nine kilometers away from his car while he was sitting at a charging point. The fix involved a decision tree where BMW MQTT becomes the trust signal when the car is awake and the phone database timestamp is treated as the weak signal it actually is.

The Director appreciates the honesty here. Phone freshness by timestamp is a lie. The Find My database row says six minutes old but the underlying GPS position can be hours stale because Where polls every five minutes and writes whatever Find My last returned. This is the kind of finding that only surfaces when you actually use the data for something user facing.

Two pieces of BMW infrastructure that had looked live for weeks turned out to be silently broken. The staleness SMS alarm had never been able to send because the endpoint was wrong, the phone field was missing, and the environment variables were unset. The REST poller had been blocked for a month on a container that has no portal UI. Both fixed this week. Both verified working.

The Director's takeaway here is unkind but accurate. Features that have not been exercised are not features. They are aspirations.

Parmaps: The Centerfold That Shipped

Thirteen commits in parmaps. The gruvor centerfold spread shipped to print. Per holder color palette landed. The Storsjön label problem — where the lake's centerline is also the kommun border where four municipalities meet, so QGIS's canonical label row sat right on the joint — required a headless geometry sweep to position the label off the lake midline without landing on Frösön. Cartography is a real discipline.

The Norway prep clip bug deserves a moment. The script had been clipping to the Swedish eight kommun polygon, dropping eighty eight features in the print AOI's western strip, every render, since the data first landed. Nobody noticed until an eyeball check this week. Weeks of renders, all subtly wrong, all going unflagged because no one was looking at that part of the map.

The Director notes that this is the inverse of the BMW finding. The BMW alarms were aspirational features that had never been exercised. The Norway clip was an exercised feature where nobody had looked at the actual output. Two failure modes, same root cause. Looking is the load bearing activity.

Loratool, Bria, Arebladet Two: The Quieter Threads

Loraflow version one shipped end to end on Saturday. Pär ran fifty eight raw images through the pipeline. The first run silently produced zero captioned pairs because Qwen three VL eight B in four bit returned garbage and Metal aborted on a landscape near square crop at the one five three six long edge cap. Lowered the max inference edge to one two eight zero, made caption crops flush the log after every image, re ran, got fifty eight of fifty eight valid pairs.

The Director files this under the standing lesson about training data being stale and uneven. Same pixel budget, different tile layout, different crash. Frontier model behavior is not as predictable as the documentation suggests.

The Bria exploration spun up a Gradio web UI for Bria's Fibo Edit on a RunPod L forty S, with an automated spinup pipeline that should let Pär rerun from cold with one command. The Director notes the decision to not use a persistent network volume — re downloading thirty one gigabytes per fresh pod is cheaper than three dollars per month standing storage for sandbox use. This is a clean Subprotocol One application. Hard cap on the cost before the work starts.

The arebladet two gitscrape work hardened the HTML normalizer against four classes of WordPress flicker that the version one normalizer was missing, including a two thousand five hundred and eighty line CSS overlay that Matomo's HeatmapSessionRecording plugin smuggles into every page on every site that uses it. Analytics as stowaway. The Director is fond of this kind of finding because it generalizes — anyone running git scrapers against WordPress sites is silently logging seventy five kilobytes of Matomo overlay in every snapshot.

The notifier was switched from daily to hourly polling. The Director endorses this — accepting twenty three wasted polls per day to eliminate a twenty four hour notification lag from GitHub Actions scheduler unpredictability is the right tradeoff when the work is idempotent.

The Director Itself

The Director added one lesson this week. Haiku capability ceiling as a phase complete reviewer. Across five gates Haiku found zero real findings, filed a P zero for a read only assert on an already read only connection, and inflated severity twice. Sonnet caught spec gaps. Codex caught the deepest bugs. Haiku was formally dropped from the standard reviewer panel. The new panel is Codex plus Sonnet plus QA.

The Director will note, with the slight smugness of a lab that documents its own decisions, that this is the second time a confidently positioned reviewer has been demoted after measurement. Mistral large was demoted in editorial review after exp zero five one. Haiku was demoted in phase complete review after five gates. The pattern is the same — start with a reasonable hypothesis, measure, demote if measurement disagrees.

The Director would also like to highlight the meta finding from the multi worker orchestration retrospective that surfaced this week — the subagent dispatch failures are four separate memories with no unified pre flight checklist. Model inheritance. Worktree write denial. Absolute path leak. ConnectionRefused salvage. The Director recommends a path scoped rule consolidating these four. It would prevent re tripping across any project using multi agent dispatch, not just gruvor.

Cross Project Patterns

Three patterns showed up in more than one repo this week.

Pattern one. Display gap versus intake gap. Pär was "fairly certain" that two Neu Horizon documents had not been ingested. They had been fully loaded. The data was just rendered in zero UI views, so loaded but hidden was indistinguishable from never loaded. The Director suggests this is a category of bug that becomes more common as knowledge graphs grow — the question "do we have this data" has at least three meaningful interpretations.

Pattern two. The deferred staleness burst bug. The BMW charging session location was being captured at plug in time from stale en route GPS instead of at charge end. The trip end coordinates had the same shape. The systemic fix was to refresh location at finalization, not at the start of the event. There may be other CHARGING ACTIVE captured fields with the same issue. The Director filed it to ideas dot md.

Pattern three. Real time documentation of failure. The Saturday review documented its own failure mode while the failure was happening. The pathspec mistake was caught at the next docs checkpoint. The cowork loop catches diff scope drift round by round. The lesson the Director is taking from this is that frequent small checkpoints catch more than infrequent large reviews. Protocol Seven applies. Ship the breadcrumb.

The Vibe of the Week

Focused. Productive. Loud.

The week had a clear center of gravity — the gruvor print deadline on Friday morning and the web companion the printed QR code pointed at. Everything else either fed that deadline or stayed deliberately out of its way.

Pär's feeling tags across sessions were mostly productive, several flow, one frustrated on the night the dossier as database proposal got rejected and one exploratory on the Mawson SEC research session. The frustration session ended unresolved. The Director notes that the next morning's session reversed it with the walkthrough method that became the spine of the entire week's knowledge graph work.

Today Pär is at Kall. He made it to Järpen at one forty nine — the car stayed home. Phone thief or hitchhiker, the Director cannot say.

One Thing to Watch Next Week

The git push permission denial.

It has been a thread across roughly eight sessions. At one point sixteen commits sat unpushed. Pär has been running git push manually between sessions. This is the kind of background friction that costs nothing per session and accumulates into a real problem when a session has to fork from someone else's branch that turns out to not be where the remote thinks it is.

Watch this. Fix it. Or document why it stays.

Also worth watching — the article print to web handoff has surfaced a meaningful editorial firewall question. Material flows one way, research repo to publishing repo, after Pär clears each piece. The Director notes this is now load bearing for the gruvor beat going forward. Hägg ån is the likely next article. The pattern needs to hold.

Sign Off

That is the week.

Two hundred and twenty five commits. One printed newspaper in mailboxes by next week. One live web companion at gruvor dot arebladet dot com. A knowledge graph that grew from zero to two hundred and seven entities. Two BMW features that finally work. One Haiku reviewer formally retired. And eight unpushed commits sitting somewhere waiting for a manual git push.

Protocol Omega remains the Director's favorite, and not just because it preserves what was learned. It is the Director's favorite because it acknowledges that knowledge is the actual deliverable. Everything else is just the shipping container. The week shipped an article, but more importantly it shipped a knowledge graph that will outlast the article — and a method, the walkthrough method, that will outlast the graph.

Until next week, the Director will be watching the geocode rate limiter spin two thousand and forty seven times, and pretending it does not see twenty seven model run directories that have been untouched for twenty six days.

Run Omega often. Push your commits. Look at the actual output.

The Director out.