---
title: "Daniel Westgaard (@danielw) | Hashnode"
description: "Developer with a passion for building and development -  currently building Riftmap, https://riftmap.dev"
url: "https://hashnode.com/@danielw"
---

@danielw

# Daniel Westgaard

@danielw · Oslo, Norway · Joined April 2026

Developer with a passion for building and development - currently building Riftmap, https://riftmap.dev

[Website](https://riftmap.dev/)

## Comments

[Good question, and I think it's pointing at a real seam. Riftmap's job stops at making the graph correct and legible: here's the blast radius, here's what's downstream, here's who/what it touches. Whether that's been accepted (routed vs. actually picked up, as you put it) is a coordination state that lives one layer up from the context itself. We deliberately don't own that state machine today; the context and the acceptance-of-context feel like two different primitives, and conflating them is how you get a graph that's technically right but operationally dead. Curious how you're thinking about the owner/ack layer on your end? That split (context underneath, coordination on top) seems like where a lot of the interesting design questions are.](https://hashnode.com/posts/ai-coding-agents-need-cross-repo-context-the-teams-running-them-at-scale-are-already-building-it-themselves/6a02e5246a2561e6c739131f/comment/6a8d7d805553fb0ff59ce3ea#reply-6a8d8ed92b38e4a022d703db)

Reply · Article · Aug 25 · [AI coding agents need cross-repo context. The teams running them at scale are already building it themselves.](https://hashnode.com/posts/ai-coding-agents-need-cross-repo-context-the-teams-running-them-at-scale-are-already-building-it-themselves/6a02e5246a2561e6c739131f)