docs(readme): lead with the problem Spacedock solves#213
Open
ijac13 wants to merge 1 commit into
Open
Conversation
The previous opening described what Spacedock does ("runs agent work through
defined stages..."). This rewrite leads with the problem the reader is living:
agents that drift on multi-step jobs, reviewers that rubber-stamp, work that
dies at the context limit, routines spread across too many tools.
Changes:
- New opening hook frames the pain in concrete user-language (cluster-5 alpha
pattern: "agents cannot follow full pipelines without scoping").
- Mechanism paragraph names how Spacedock answers it: stages, gates, structured
reports, reviewers that push back, state outside the agent.
- Origin sentence is first-person plural — we lived this loop, the tool is the
way we wished agent work had been organized.
- "You want Spacedock if" restructured from two bullets on the "human / agent"
axis to three bullets on three distinct axes:
1. shape (repeatable, multi-step pipelines on many inputs)
2. trust (single-agent output you can't verify on its face)
3. time horizon (work that spans days or weeks)
Source: messaging anchored in the alpha-interview synthesis at
recce-gtm/knowledge/customer-insight/interview-plans/alpha-interview-synthesis/alpha-problems.md
(7 universal problem clusters across the 9-alpha corpus).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
ijac13
commented
May 14, 2026
| # Spacedock | ||
|
|
||
| Spacedock runs agent work through defined stages, so you can delegate in batches and make only the calls that need your judgment. | ||
| Hand an agent a multi-step job and it drifts, skips steps, or invents its own path. Hand it a workflow and it follows the workflow. |
Contributor
Author
There was a problem hiding this comment.
not sure if this is a desire state or problem state
ijac13
commented
May 14, 2026
| The first officer coordinates the flow: it dispatches workers to advance each work item and surfaces approval-worthy decisions to you, the captain, so batches move forward without pulling you into every session. | ||
| Spacedock runs agent work through stages you define. Each stage gets a fresh context, an explicit gate, and a structured report. Reviewers are allowed to push back. State lives outside the agent, so work survives the context limit and picks up the next session where it left off. | ||
|
|
||
| We built Spacedock because we were there. We lived the pipelines that didn't finish, the reviewers that rubber-stamped, the work that died at the context limit, and the routines spread across too many tools. The tool is the way we wished agent work had been organized from the start. |
Contributor
Author
There was a problem hiding this comment.
don't need to mention "we're there"
Contributor
Author
There was a problem hiding this comment.
▎ We built Spacedock because we lived this. Pipelines that didn't finish. Reviewers that rubber-stamped each other's output. Work that died at the
▎ context limit. Routines spread across too many tools. Spacedock is what we needed years ago, built from inside the problem.
Contributor
Author
There was a problem hiding this comment.
▎Problem: "Hand an agent a multi-step job and it drifts, skips steps, or invents its own path. Hand it a workflow and it follows the workflow."
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rewrites the README opening so a reader instantly knows whether Spacedock is for them. The previous opening described what Spacedock does; this one leads with the pain it solves, names the mechanism that answers it, and gives three reader-state matches on distinct axes (shape / trust / time horizon).
What changes
The rest of the README ("What's Different," "Quick Start," everything below) is untouched.
Why now
The messaging is anchored in the alpha-interview synthesis at
recce-gtm/knowledge/customer-insight/interview-plans/alpha-interview-synthesis/alpha-problems.md(7 universal problem clusters from the 9-alpha corpus). The clusters that drive each piece of the new copy:Test plan
🤖 Generated with Claude Code