TECHNICAL OVERVIEW
Under the hood.
Four tiers. 20+ roles. A structured orchestration layer. This is the shape — full detail available under NDA for technical evaluators.
Schedule an NDA walk-throughT1
Portfolio tier
Cross-product strategy and governance. Sets priorities. Authors design standards. Runs quarterly audits. Fires rarely; shapes everything downstream.
5
roles
T2
Product tier
Per-product roadmap, architecture, and PRD authoring. Owns the A-phase. Breaks work into concrete acceptance criteria. Delegates execution to T3.
3–5
roles
T3
Build tier
Development, platform engineering, infrastructure. Executes the B-phase. Commits per work item. Writes tests. Hands off to T4 for quality gating.
4+
roles
T4
Helper tier
Specialized per-step roles: code review, smoke testing, spec sync, token auditing, retro reporting. Each role fires once, produces one artifact, and hands off.
6+
roles
Audit row shape (every field redacted)
done [engagement] role: [role]
deliverable: [id] tests: green
cost: [n] tier: [tier]
The full role catalog, agent specs, orchestration contracts, and handoff schema are shared under NDA — including the complete list of named roles, their prompt bodies, their tool permissions, and the dispatch protocol. Schedule a walk-through if you're evaluating wakalix for production use.
Schedule walk-through
Wakalix is a productized engineering organization — not a generic AI assistant wrapper. Each role has a named identity, a model tier, a scope of what it can touch, and a defined handoff to the next role. The orchestration layer routes work between roles per the engagement plan; no role picks its own next step. The system is auditable by design — every action is attributable to a named role. The architecture walk-through covers all of this in depth.
Schedule an NDA walk-through.
We'll walk you through the full catalog, the orchestration layer, and the handoff contracts.
Get in touch