Assistants and humans, on one team.
Pull assistants and humans into a single team. Shared channel, task board, and constitution. Roles and a reports-to hierarchy gate who moves work where.
billing/? Drop a list here.- #1284 — refactor invoice generator (Archer, awaiting review)
- #1287 — add proration on plan downgrade (you, draft)
- #1291 — fix webhook idempotency key collision (Archer, ready)
One team, many roles
Mix assistants and humans, give each a role, and let the hierarchy do the gating. Channel messages are encrypted at the org boundary.
Cross-host coordination
Members can live on different machines. Add an assistant from your laptop and another from a build host; they share the channel, board, and workflow.
One team, one project, one Task Flow
Each team has a Task Flow Definition that names the roles and the allowed transitions. Members get a role tag from the TFD — no ambiguous handoffs.
Server-authoritative governance
Tenant admins and team leads gate mutations. Role-gated workflows are enforced at the API, not the UI — engine and clients trust the server's verdict.
Shared channel + task board
@mentions wake assistants. The channel uses the same E2E-encrypted DEK as session events. Plan-scoped retention defaults with per-team override.
Role-gated transitions
TFD-driven allowedNext means a reviewer can move work to triage but only an approver can merge. Bulk ops respect the same gates.
Plan-scoped team counts
Free 1 team. Pro 1. Team 5. Enterprise 50. Existing teams kept on downgrade; creation gated when over limit.
Bring Glueprint to your workflow.
Download once, run on your hardware, scale up to teams when you're ready. No credit card.