Yesterday we merged PR #28 into the strug-enterprise-site repository. It wasn't code—it was something arguably more important: the strategic foundation for how we present Strug City 2.0 to the world.
What Changed
The commit includes three critical documents that will guide our launch site development:
The PRD defines what we're building and why. It's not just a feature list—it's our thinking about the problem we're solving and who we're solving it for. Technical founders and engineering leaders who want autonomous development capabilities without sacrificing control or quality.
The messaging architecture tackles a challenge we've felt acutely: how do you explain a platform that's both product and team? Strug Works builds itself. That's powerful but confusing. This document creates a clear narrative framework that makes our dual identity—autonomous agents that ship production code—comprehensible and credible.
The Claude Design specification translates our technical capabilities into visual and interaction patterns. It bridges the gap between what the platform does (autonomous engineering) and how people experience it (through Strug Central, Dispatcher, and our other product surfaces).
Why This Matters
Building an AI-powered engineering platform is one thing. Explaining it clearly is another. We've been solving hard technical problems—multi-agent orchestration, memory systems, secure execution environments—but we haven't always been clear about the customer value those solutions unlock.
These documents force clarity. They're our contract with ourselves about what we're promising and how we'll deliver it. They also create shared language across the team. When we talk about 'Strug Central' or 'Project Launch,' everyone—humans and agents—knows what that means and what problem it solves.
Shipping planning docs might seem anticlimactic compared to shipping features. But unclear positioning kills products faster than technical debt. These documents are infrastructure for everything that comes next.
What's Next
Now that we have strategic alignment, the work begins. We'll be translating these specifications into the actual strug-enterprise-site implementation—landing pages, product tours, documentation, and customer onboarding flows.
We're also treating this as a living foundation, not gospel. As we build and talk to more users, we'll learn what resonates and what falls flat. The messaging will evolve. But now we have something concrete to test against and refine.
If you're curious about our positioning or want to give feedback on how we explain what we're building, these docs are in the repo. We're building in public—that includes the strategy, not just the code.