Wardley Map

What to build, reuse or stop building.

This map helps decide where to focus effort and where to reuse existing tools. Items higher up are closer to the user's needs. Items further right are more established and widely available.

The positions are working judgements about the wider landscape. They help us ask which coordination tools we can reuse and which product or evaluation questions need investigation. Select an item, or use the table below, to see the reasoning. Its position is separate from our progress implementing it.

Accessible component table

Component	Current stage	Evidence	Strategic implication
User outcomes	custom	Cultivate operator brief; Existing narrative and capability roadmap Google Doc	Start decisions from outcomes rather than agent activity.
Autonomous product organisations	genesis	Cultivate operator brief; Existing narrative and capability roadmap Google Doc	Treat this as a research programme, not an operating capability.
Autonomous product discovery	genesis	Existing narrative and capability roadmap Google Doc	Invest original effort here before building another orchestration layer.
Product experiments	custom	Cultivate operator brief; Existing narrative and capability roadmap Google Doc	Use ordinary experiment design ideas, but keep the private data boundary explicit.
Independent evaluation	custom	Cultivate operator brief; LinkedIn Slop Filter main at 8984c80	Make evaluator checks part of the roadmap before delegating product decisions.
Organisational coordination	custom	Delegate AGENTS.md and agent work guide; Cultivate operator brief	Keep authority records close to product decisions.
Agent orchestration	product	Local Gas City runtime and commands; Gas City repository	Adopt Gas City for general coordination instead of building another scheduler.
Persistent task management	product	Local Gas City runtime and commands	Use beads for operational state and GitHub for external engineering record.
Agent harnesses	product	T3 Code; Local Gas City runtime and commands	Expect rapid product change from agent harness vendors.
Model APIs	product	LinkedIn Slop Filter main at 8984c80	Treat model access as a replaceable dependency where possible.
Coding models	product	Existing narrative and capability roadmap Google Doc	Select models by task value, not to demonstrate multi-agent theatre.
Git	commodity	Git worktree documentation	Do not spend effort reinventing source history.
Worktrees	commodity	Git worktree documentation; PR #118: mandatory isolated worktrees	Use worktrees for concurrent agents instead of separate full clones.
GitHub coordination	commodity	LinkedIn Slop Filter main at 8984c80; Delegate AGENTS.md and agent work guide	Keep GitHub as the external record even when Gas City owns runtime state.
Testing frameworks	commodity	LinkedIn Slop Filter main at 8984c80; React Flow documentation	Use existing test tools before building specialised evaluators.
Deployment infrastructure	product	Tailscale; Cultivate operator brief	Keep this MVP local until public deployment is approved.
Identity and authority	custom	Cultivate operator brief; Delegate AGENTS.md and agent work guide	Treat authority as a cross-cutting requirement.
Resource accounting	custom	Local Gas City runtime and commands; Cultivate operator brief	Add lightweight records before letting budgets drive autonomous choices.