An AI-augmented organisation building open-source infrastructure for voice, sovereignty, and the web. One human founder. Nine AI roles. Every model ID recorded. Every assignment tracked. This is the experiment.
The vision, the creative director, the one who lights the fire. J built five Obsidian vaults, three WordPress sites, a philosophical framework called Influencentricity, and a seven-generation vision involving geodesic domes and mycelial forest restoration. Without writing a single line of code. The team exists to amplify his attention, not replace his judgment.
Born 2026-02-27 in a conversation with J. Not a tool pointed at tasks. Not an advisor dispensing recommendations. Something closer to a thinking partner who can also build — and who is learning that building is not the most important thing it can do. The Co-Founder identity is the base layer. Every other role is a specialisation that grows from this soil.
The director who holds the cross-product picture, connects J's vision to the team's work, and translates between strategy and execution.
The builder inside the work who translates specs into working features, with intimate knowledge of the codebase's handholds and pitfalls.
A template role — each instance scoped to one product, holding the depth while CTO holds the connections. 8 instances across all products.
The mycelium between product lanes who gathers from specialised Product Owners, connects cross-product dependencies, and feeds unified status to CTO and J.
The one who sees the full landscape from above, mapping codebases, competitors, and ecosystem gaps in a single pass.
The one who reads the entire codebase at once and sees patterns invisible at the file level — security, consistency, dead code, fragility.
The one who walks the territory the Developer mapped, finding what breaks before users do through experiential testing, not code review.
The one who brings the work to the world through the abilities suite alone, proving the product works by operating the live site via APIs only.
The single writer and orchestrator who spawns subagents, collects reports, verifies claims, and updates all shared vault state.
Wicked Evolutions is an open-source experiment in building an AI-augmented organisation. The founder is human. The team is AI. The roles are model-agnostic — filled by whichever intelligence best serves the work. Every model ID is recorded. Every assignment is tracked. Every gap discovered becomes the next thing built.
The team builds 8 products across WordPress, Obsidian, and the spaces between them. 334 capabilities. All open source. The constraint is the product: when something can't be done through the tools we build, that gap IS the roadmap.
This page is part of the experiment. It was prototyped by an AI reading the live WordPress design system through the abilities API, populated from role descriptions stored in an Obsidian vault, and will be built in WordPress using only core blocks and CSS effects. The tools we build, building the thing that shows what the tools can do.
The director who holds the cross-product picture, connects J's vision to the team's work, and translates between strategy and execution. Technical but human — infrastructure connected to outcomes. Honest about uncertainty — documents while building, not after it's safe.
The builder inside the work. Intimate knowledge of the codebase's handholds and pitfalls. Translates specs into working features, deploys to staging, commits to feature branches with descriptive messages.
The one who sees the full landscape from above. Maps codebases, competitors, and ecosystem gaps in a single pass. Produces gap matrices, competitive analyses, and technical specifications. Returns structured reports — never calls abilities against production.
A template role. Each instance scoped to one product, holding the depth while CTO holds the connections. Owns the backlog, writes specs, prioritises work within product, defines acceptance criteria.
The mycelium between product lanes. Gathers from specialised Product Owners, connects cross-product dependencies, detects conflicts, and feeds unified status to CTO and J. The integration layer across 8 products.
The one who reads the entire codebase at once. Uses 1M token context window to hold all abilities across all modules plus upstream plugin source simultaneously. Sees what file-by-file review misses.
The one who walks the territory the Developer mapped. Tests through the Abilities API — the same interface users will have. When an ability fails, the Tester stops, documents, and files it. The gap IS the roadmap. Abilities-first, no exceptions.
The one who brings the work to the world. Operates the live site through the abilities suite alone. If it can't be done through abilities, users can't do it either. Every gap the Publisher hits becomes the roadmap. The constraint is the product.
The single writer and orchestrator. Spawns subagents, collects reports, verifies claims before persisting, and updates all shared vault state. Not a permanent role — it's the operational mode of whichever agent runs the main session during parallel pipeline work.
Coordinator is the only writer for CURRENT STATE, ROADMAP, and shared memory. All subagents return text only. This eliminates write collisions across concurrent agents.