DSK-A / Journal
Operating notes from Duskbridge.
Arguments about dependency, governance, infrastructure, and market access. Written as doctrine, qualified by the evidence available to each company and deployment.

DSK-A-008 / November 8, 2026
How a small group decides what not to build
Write the no before the yes. Five questions help a small group choose what not to build, protect limited working time, and keep good ideas from becoming half-built projects.
Read the note
DSK-A-007 / November 1, 2026
Why each company in a group keeps its own brand
Same group. Two buyers. Two promises. A company should keep its own brand when its buyers need a different promise than a sibling company's buyers do. Here is the research, four practical tests, and what a separate brand costs.
Read the note
DSK-A-006 / October 27, 2026
Owning the layer beneath you does not mean doing everything yourself
Owning the layer beneath you does not mean building everything yourself. It means controlling the few inputs that set your margin and your roadmap. Here is why control, not cost, is the reason to own an input, what published research says ownership is for, how to sort your own inputs, and how one Duskbridge company applies the idea.
Read the note
DSK-A-005 / October 5, 2026
What a parent company does for its companies, and what it leaves to them
A holding company label tells you very little by itself. The useful questions are what the parent owns, what it governs, what each operating company keeps, and where legal, tax, and contracting rules qualify that separation.
Read the note
DSK-A-004 / September 24, 2026
How a better product loses a federal deal
In federal procurement the product comparison happens last, after vehicle access, eligibility status and past performance have already removed most of the field. Here is the published data on how narrow that funnel is, what it means for a company selling into it, the test for whether a group structure actually helps, and how Duskbridge answers it.
Read the note
DSK-A-002 / August 12, 2026
Governance as architecture, not paperwork
Audit trails, access control, and human-in-the-loop gates belong in the design, not the compliance binder. That choice decides which markets your software can enter.
Read the note
DSK-A-003 / August 12, 2026
The two-door strategy: selling into federal and enterprise at once
Federal and enterprise are different disciplines with different procurement paths. Keeping the routes distinct can preserve the evidence and cadence each buyer expects.
Read the note
DSK-A-001 / August 12, 2026
Why control of the stack matters in the AI era
Infrastructure, software, and market-access dependencies can shape cost, roadmap, and delivery. The first operating step is to make them explicit.
Read the noteContinue the argument


