Roadmap
Shipped, in progress, and planned next.
Read live from the same board the team works from, acceptance criteria included. See Open Source for the code behind it.
422 items across 5 stages.
In review · 32
Verification submitted for review
Keep Gmail follow-ups actionable through reviewed drafts
Turn grounded follow-up work into an editable Gmail draft, then keep the linked commitment visible until it is sent and resolved.
Bring retained source tools onto shared admin and canonical read contracts
The existing Modernize and canonically integrate every additional admin tool card combines several independently reviewable outcomes. This slice owns only the acceptance below.
Generate useful boards, views, workflows and Coworker recommendations from a Blueprint
Prove the Architect can produce an immediately useful operating workspace from business context using semantic configuration over existing primitives, including custom Kanban lifecycles where appropriate.
Preserve every source row before contact import approval
Make the first business-data import trustworthy: users see every input row or an actionable refusal, never a silently incomplete review.
Preserve fork branding, pages, plugins and configuration across core upgrades
Owners can customize the complete product and receive upstream features without losing their website, business records or deployment identity. Saved Site Studio documents and workspace configuration already live outside core source, but fork guidance still recommends editing tenant source and tracked hosting configuration. Safe customization ownership and upgrade preservation are not proven end to end.
Preserve keyboard focus when invoice commands open Stripe setup
Remove an observed release-blocking invoice setup keyboard failure. Agent-generated applications can reuse a dependable command palette, dialog and navigation runtime instead of repairing focus per screen.
Change collection policies through reviewed AI and MCP proposals
Change collection holds, promises, ownership and next actions conversationally with exact human approval and current invoice evidence.
Observe fresh homepage entrances before CI sampling delays
The turnkey fork candidate PR220 passed installation and preservation checks, but CI run 37388338530 failed because homepage QA sampled the first word at currentTime 1820/endTime 1820 after its entrance finished. Trace the fresh prefetched navigation and capture its real animation state in the browser before process delays. Preserve all existing motion assertions and prove absent/immediate/history entrances are refused.
Prove workspace recovery and upgrades preserve business truth
Prove workspace recovery and upgrades preserve business truth. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Verify receivables, sales follow-up and onboarding as complete release exemplars
Verify receivables, sales follow-up and onboarding as complete release exemplars
Keep AI Readiness keyboard focus and progress accessible
Browser review found that advancing between assessment questions leaves focus on the document body, and the assessment progress bar has no accessible name.
Complete reviewed content-calendar creation, deletion and reordering
A self-hosted business can manage its editorial calendar from the admin or approved AI/MCP commands without losing fields, overwriting concurrent edits, or mistaking a calendar status for publication.
Give AI readiness a branded, animated experience
Redesign the AI readiness assessment so it feels like a crafted Accelerate diagnostic, with a distinctive animated visual system and fluid, sequenced transitions from introduction through questions and results.
Make contributor pickup reject unusable repository addresses before claiming
Make turnkey contributor pickup reliable: readiness and claim validation must reject unsupported repository addresses, report the exact affected card safely, and preserve claims and retained work. Repair the observed legacy repository address through a reviewed revision-checked edit.
Polish the core Command Center theme collection
Refine the eight existing non-Capy Command Center appearances as a coherent professional collection. Preserve each theme's identity while improving hierarchy, contrast, control states, surface depth, and responsive consistency through the existing shared theme token system.
Add a Capy-inspired Command Center appearance
Add a distinct, polished appearance for the full admin Command Center, guided by Capy AI's visual style and implemented through the existing validated theme system. Keep it coherent across shared admin routes and the fictional demo workspace.
Explain missing or mismatched contributor bases before claiming
Contributor pickup must identify the exact card and distinguish a missing approved commit, a commit outside the approved branch, and Git fetch failure. Preserve the approved repository contract, retained source and immutable claim history.
Forced synthesis at the agent step budget
The tool-calling loop stops at a fixed turn count and the run is marked partial with a message; nothing forces the model to actually answer. Near the limit the agent can spend its remaining budget launching another lookup and finish with no answer and no artifact. Warn the model as the budget runs low, remove tool access on the final step so it must synthesize from what it already gathered, and record the budget-exhausted outcome as a first-class traced event.
Triage gate and silent exit for the operator queue
Every proposal reaches action_queue as pending; only an exact dedupe_key suppresses a repeat. A thin or low-confidence finding therefore becomes a row the founder must dismiss, and a background job has no documented "nothing worth surfacing" exit. Score a proposal before it queues, route it to answer, investigate, or pass, and let an investigation that finds nothing actionable conclude silently with a recorded reason instead of a queue row.
Keep founder command approvals and traces private from tenant agents
Prepare founder administrative work without exposing other businesses or giving tenant agents platform authority; reuse the existing approval and trace runtime.
Public marketing pages load and navigate fast
Every public marketing route rendered on each request and shipped the whole operations stylesheet, so a first visit waited on a server render and downloaded admin CSS it never used. Marketing pages now prerender behind a short revalidation window that a publish invalidates immediately, admin theme and component sheets load only behind the admin chrome, the chat panel and site search load on first open, the below-fold product slider stops preloading its image, and the route focus handoff only re-runs when its destination was actually replaced.
Verify and repair row security for learning proposals
Read-only database advisor baseline during recovery reported public.learning_proposals with RLS disabled. This is a recorded finding, not yet proof of cross-tenant disclosure: verify current role grants, owning service and migration history before proposing a minimal corrective migration.
Remove excess client privileges from Learning Inbox proposals
Reduce avoidable database access and schema discovery while preserving the Learning Inbox. Agents get a tested portable migration instead of manual dashboard security changes. Read-only 7 October audit of Accelerate Agency confirms learning_proposals RLS enabled, but anon and authenticated retain all table privileges including TRUNCATE, REFERENCES, TRIGGER and MAINTAIN. Anonymous SELECT causes GraphQL schema discoverability. No unauthorized proposal content was returned in four read-only negative contexts.
Add reusable workflow layouts and saved work views
Let operators organize the same canonical work in suitable list, board, and calendar views across supported admin workflow pages. Make due dates, owners, status, priority, filtering, and saved layout preferences easy to scan and use, while keeping the existing work records and domain services authoritative.
Complete approved AI task reopening and description edits
Deliver the bounded task adapter gap found during the CRM parity audit. Preserve the broader CRM requirements and active import owner.
Add approved AI operation parity: Branding, plugin controls and workspace settings
Allow requests such as changing logo/colors, disabling a plugin or changing sync settings without manually hunting through settings pages.
Make Revenue contract totals and recovery accurate
Revenue subtracts currently churned contracts at their start dates, includes onboarding value in its chart, groups dates in the host timezone, and ignores client/proposal read errors. The demo reports inconsistent hardcoded values.
Make homepage motion verification reliable across delayed observations
Remove the homepage motion verification blocker by proving whether delayed observation or runtime behavior causes the failures, then fixing the responsible owner without weakening visual acceptance. Reliable CI lets agents deliver permissions and contributor improvements without repeated manual reruns.
Make the first agent-built extension follow the current plugin contract
Repair the documented extension entry path and give a business owner a complete brief for Codex or Claude Code. Agents should reuse working runtime services and current validators rather than discover missing manifest fields, guides and incorrect source paths by trial and error.
Publish versioned releases and fork upgrade compatibility metadata
Fork owners can identify the installed core release and find a supported stable update without treating every main-branch commit as a production release. Published main has Git-derived deployment identity, package version 0.1.0 and a checksummed migration ledger. The release listing is empty; there is no coherent stable-release discovery and compatibility contract for fork owners.
Make workspace password recovery usable and prove native reset emails
Continue the founder-authorized turnkey work. Expired recovery links currently return to a sign-in screen that hides reset guidance. Password-update failures can leave the form disabled. The connected-fork journey has no real password-reset proof. Fix the existing account-recovery owners and extend the isolated native Auth journey.
Planned · 8
Committed; readiness checked at claim
Add real roles, record ownership, and per-object agent permissions
tenant_memberships.role currently permits exactly one value, admin, so every member of a workspace can do everything and the AI can reach everything that member can. A second person in the business, or a client given limited visibility, is not expressible today. This is also the one place a competitor's AI governance is genuinely ahead: theirs scopes agent access per object by role.
Implement v2 Command Center operator and product education redesign
Today, Inbox and plugin surfaces use overlapping work vocabulary and extensive navigation. Docs explain implementation shapes before business problems; supplied v2 briefs define the target.
Decision Memory: record why, supersede cleanly, surface implications
Businesses forget why they decided. A decision object records what was decided, why, by whom, when, what evidence supported it, what it superseded, and what it implies. Approving a decision surfaces conflicts with existing policies, documents and workers and offers explicit updates; nothing propagates automatically.
Add approved AI operation parity: Content and generated business material
Create, revise, publish and archive the content and generated material actually available in admin, using an inspectable approval workflow.
Generate the plugin manifest from validators and fail on drift
Plugin Platform phase 2 of 6. A hand-maintained manifest goes stale the moment someone edits a schema, which is exactly what happened to setupChecks in the current module contract, where all four declared ids drifted away from the real checks. The proven answer is to generate the description from the live validators so it cannot drift, the same principle behind a generated schema description that can never disagree with reality. For Tier 2 and above the manifest is derived from source; for Tier 0 and 1 it stays hand-written because there is no source to derive from.
Prepare safe fork update branches with verification and recovery guidance
An owner can prepare and verify an upstream update without changing the running website or risking uncommitted work and tenant data. Fork updates currently rely on manual upstream guidance. Migration ledger and deployment guards exist, but no integrated command prepares a reviewed update branch. Broader backup/restore proof already belongs to release-restore-upgrade-proof.
Add an owner-guided update center to Command Center setup
Installation owners can understand what an update changes, what prevents it, and the next safe action from the existing Command Center. Setup Center reports installation capabilities and schema status but has no fork release discovery, compatibility summary or guided update handoff.
Ground AI retrieval in Drive provenance and citations
Retrieve only relevant approved document excerpts for research, briefs, audits, and proposal drafts and return source links.
Blocked · 16
Waiting on a dependency
Bring existing business data into Accelerate without identity drift
Bring existing business data into Accelerate without identity drift. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Connect Google OAuth and complete the first Workspace sync
Configure the founder-only Google connection with the minimum Gmail, Calendar, and selected-Drive scopes, then produce successful source receipts.
Finish one auditable communication sender
Unify Gmail personal replies and Resend campaign/transactional sends behind validated services that record provider IDs and terminal results.
Import Gmail incrementally with cursor recovery
Persist Gmail history cursors, process oldest unseen work first, report deferred backlog, and safely recover expired cursors.
Connect live business signals so Accelerate can see and remember
The system sees only what arrives through its own forms. Gmail and Calendar sync exist in code but Google has never been connected, and there is nowhere for the founder's own notes to enter at all. A brain whose only sensory input is a contact form cannot be a second one. Connect Workspace, land threads and events as canonical activity through the existing resolver, and add a plain capture surface for notes.
Restore Email Studio, sent history, and live template publishing
Give the founder one discoverable workspace to view, edit, preview, test, publish, restore, compose from, and audit transactional and sequence email without another provider account.
Synchronize Calendar events and associate revenue records
Import upcoming and recent Google Calendar events idempotently and link attendees to contacts and opportunities.
Add approved AI operation parity: Proposals, invoices and Collections
Prepare and maintain commercial documents, invoice pages and collection policies through AI with the same reviewed business facts as admin.
Rank today’s best opportunities with evidence
Explain which opportunities deserve attention using the deterministic priority policy plus bounded qualitative evidence.
Prepare the technical self-hoster production launch
Implement the founder-approved September 21 launch plan: core CRM/tasks, grounded AI, reviewed learning and plugins, using free-tier isolated validation. Preserve cold-start PR 122 and existing tenant boundaries. Complete production readiness with evidence, never label fixture proof as hosted or human proof.
Fully edit and publish the installation website from admin, with portable fork ownership
Founder explicitly prioritizes fully editing the Accelerate site in admin and equivalent ownership for independent forks before domain hosting or broader Architect work.
Add approved AI operation parity: Founder-only platform administration
Give the founder conversational access to platform work planning and supported tenant administration without extending tenant agent authority.
Review, edit and simulate the proposed workspace inside Architect chat
Let the owner inspect the evolving Blueprint through rich chat cards and a lightweight inspector, conversationally revise it, and simulate representative business events before applying real configuration.
Add approved AI operation parity: CRM records, tasks and identity
Update customer ownership, canonical contact/company/opportunity fields, next actions and tasks conversationally, without revisiting separate forms.
Backlog · 168
Captured, not yet committed
Add safe behavioral tests and recovery actions to Setup Center
Give each provider and subsystem a bounded test that proves the intended capability and changes status on failure and recovery.
Ship newsletter, event invitation and reactivation campaign recipes
Provide three editable business starting points that lead from audience selection to reviewed, scheduled and receipted campaigns. Implementation steps: 1. Define newsletter and event-invitation templates over the existing campaign document/step schema. 2. Route customer reactivation through the existing Recovery eligibility and staging service. 3. Add bounded AI drafting with approved facts, explicit apply-draft, protected manual work and no fabricated assets/prices/deadlines. 4. Provide coherent recipes in all five fictional workspaces; date-sensitive examples derive from demo scenario time.
Build grounded company research and revenue-leak analysis
Research a company from approved sources, separate evidence from inference, and identify likely operational revenue leaks relevant to outreach or calls.
Workspace Architect: guide an owner from business context to a useful workspace
Guide an owner from empty workspace to a useful business outcome. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Create a shared outcome and evaluation framework for AI work
Give Skills, Coworkers, model routing and refinement one shared way to define task success, golden cases, deterministic checks, human review signals and business outcomes. Use external eval tooling as a runner where useful, never as authoritative business state.
Opportunity Radar discovery worker on Crawlee
Give Opportunity Radar its documented-missing discovery worker: Crawlee (Apache-2.0, npm) crawls an operator-approved list of public sources with queues and retries, extracts candidate opportunities, dedupes against the CRM, and stages scored candidates into the existing Radar review. Closes the gap stated in docs/plugins/OPPORTUNITY-RADAR.md.
Finish the founder Proposal workspace
Support grounded draft, preview, versioning, send, view activity, accept/decline, expiry, and follow-up from the linked opportunity.
Wire notification preferences into actual dispatch
Ensure urgency, channel, quiet hours, and disabled preferences govern real notification creation and delivery rather than settings display only.
Standardize loading, errors, retry, and preserved route state
Make every core route retain useful context through refreshes and show actionable loading, empty, degraded, and error states.
Governed Browser Worker on Stagehand for API-less portals
Let coworkers do real work in portals with no API: Stagehand (MIT, local Playwright) runs under narrow business tools only (bid-portal checks, vendor invoice retrieval, listing updates, prospect research). No generic browser tool is ever exposed; every run is budgeted, receipted, and approval-gated.
Version and harden the existing provider integration adapter contract
Define one typed provider adapter boundary for scoped connection state, incremental reads, external actions, cursors, rate limits, receipts, reconciliation, health, and canonical service mapping before adding another provider.
Run authenticated production admin QA on desktop and mobile
Exercise Today, Pipeline, Conversations, Campaigns, Proposals, Analytics, Setup Center, Settings, and Feature Board on the deployed founder account.
Automatic call intelligence on faster-whisper sidecar
Make every sales and support call usable data: a self-hosted faster-whisper sidecar transcribes uploaded audio, Accelerate extracts commitments, objections, decision makers and next steps, then updates CRM records and drafts follow-ups through the existing Meeting Commitments path after review.
Add Gmail Pub/Sub watch renewal with scheduled fallback
Use push notifications when configured, renew watches before expiry, and retain protected scheduled incremental sync as fallback.
Add assignment, snooze and a durable needs-reply conversation queue
An operator can reliably find unanswered customers, assign ownership, snooze work and reply without losing obligations when a thread is opened. Implementation steps: 1. Extend the canonical conversation contract with member assignment and snooze deadlines using additive tenant-scoped migrations. 2. Derive needs-reply from recorded inbound/outbound events, independently of unread styling. 3. Add templates, bulk triage, deep links, keyboard list/detail navigation and stable filters to the existing conversation surface. 4. Use the same predicate for Today, navigation counts and AI reads; wake expired snoozes through durable work.
Action Network on Activepieces pieces as MCP tools
Accelerate keeps triggers, WorkItems, approvals, receipts. Selected Activepieces pieces (MIT, npm) are consumed as MCP tool servers and mapped into capability-gated tools. No Activepieces builder or server is embedded.
Site Studio: AI-editable versioned public site runtime
Build a first-class optional site/CMS module that lets a business manage pages, posts, collections, navigation and brand/style through validated semantic React-shaped documents, visual editing and AI patch commands. Public rendering remains independent of the editor and trusted interactive functionality stays source-controlled.
Proposal intelligence via Papermark view tracking
Self-hosted Papermark receives view webhooks, enriches recordProposalView (proposals.ts:179-187) with page-level engagement and viewer identity, and triggers NOTICE alerts for the Sales Coworker on buying signals (repeat views, pricing time, multi-viewer).
Add a Context Provider Registry and Context Compiler
Generalize the existing bounded grounding infrastructure into explicit context providers and a compiler that selects the smallest authorized evidence pack needed for a task. Preserve the existing grounding contract, memory categories and tool evidence rather than creating a new generic memory store.
Finish the Campaigns planning and control workspace
Give the founder one place to define audience, sequence, policy, dry run, activation, enrollment, performance, pause, and exceptions.
Rebuild the public site around capacity liberation and editorial visuals
Reframe Accelerate as the operator that absorbs routine work so teams can do the work only they can do, then rebuild the public homepage and supporting marketing surfaces so they are visually led, short, and free of dollar-ROI theater.
E-signature from accepted proposal to closed won via Documenso
Self-hosted Documenso CE: generate agreement from accepted proposal, send for signature, on signed webhook transition opportunity to CLOSED WON, create onboarding WorkItem, prepare invoice, notify team. All through canonical services.
Paid SaaS Beta: make Accelerate chargeable and operable as a hosted product
Define and prove the minimum commercial release where a new business can receive a workspace, connect business context, invite teammates, use governed AI, understand failures, and pay Accelerate. This is the release-level productization gate, not a replacement for existing runtime, tenancy, integrations, or customer invoicing services.
Add Google token health, scope drift, and reconnect recovery
Detect revoked credentials, missing scopes, refresh failures, and account changes, and guide the founder through safe reconnection.
Lead nurture and lifecycle campaigns on self-hosted listmonk
Self-hosted listmonk (AGPL, CVE-clean pinned version, egress-restricted) delivers Accelerate segments (lost 6-12mo timing, silent customers 90d, etc.) after AI drafts content and approval. Bounces/suppressions flow back to canonical records.
Universal approved AI interface for every admin operation
Operate every authorized admin business workflow conversationally through exact approvals and shared domain services.
Customer support + website conversations on Chatwoot
Self-hosted Chatwoot (MIT): website chats flow through identity resolution to Contact/Company/Opportunity, AI triages, Sales/Support Coworker queue. At-risk language escalates to Today.
Revenue attribution and referral tracking on Dub
Self-hosted Dub CE (AGPL): auto-created tracked links per campaign/post, conversion webhooks link→form→lead→opportunity→revenue chain. Business Pulse reports pipeline per source, not clicks. Unattributed traffic stays unattributed.
Finish reply, local archive, and follow-up actions in Conversations
Let the founder reply in-thread, link/create records, set next action, create a task, archive locally, and enroll permitted follow-up from one conversation.
Business document intake on Docling sidecar
Self-hosted Docling (MIT, docling-serve): RFP/invoice/PO/contract upload → structured extraction → canonical records + WorkItems (bid deadline, payable, proposal tasks) after review. Replaces manual admin labor.
Opportunity Radar: repeatable installation and two-business demo acceptance
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Opportunity Radar: verified recognition and learning
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Rebuild Feature Board drag, details, and mobile interaction
Make the managed backlog feel like a professional delivery tool with stable drag ownership, cross-column previews, reliable persistence, accessible movement, and a portal-based responsive detail editor.
Complete keyboard, accessibility, reduced-motion, and mobile parity
Verify every critical founder workflow without a mouse and at mobile breakpoints, including dialogs, drawers, tables, Kanban, command palette, and toasts.
Add authenticated API contract and failure tests
Exercise authentication, founder authorization, payload validation, idempotency, transition rejection, provider failure, and truthful errors for every material API.
Build business-specific record screens from supported view contracts
Build business-specific record screens from supported view contracts. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Add canonical saved audiences and explainable campaign eligibility
Operators save named lists and nested AND/OR segments, inspect exact sendable counts and exclusion reasons, and use the same audience from UI or AI. Implementation steps: 1. Add tenant-owned saved lists/members and segment definitions with versioning and canonical contact references; use additive migrations and RLS. 2. Expose a typed allowlist of filter fields/operators; reject unknown fields, invalid types, empty rules and excessive nesting. 3. Implement one bounded, deterministic audience/eligibility service with stable pagination and database-side filtering. 4. Add read-only preview and saved-audience selection; AI can read previews and propose edits through registered tools.
Make the governed business runtime installable, extensible and recoverable
Make the governed business runtime installable, extensible and recoverable
Add scoped Google sync controls to admin integrations
Expose safe source-scoped Google workspace sync actions in the Integrations admin surface and preserve truthful busy/error behavior.
Opportunity Radar: bounded discovery and source health
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Extend the shared email document and branded layout library
One editable, branded email document powers Campaigns and Email Studio with images, lists, quotes, columns, undo/redo and responsive previews. Implementation steps: 1. Extend the existing versioned document contract and migrate/read old five-block documents without losing IDs or formatting. 2. Adapt pure block-to-Maily compilation and layouts; use tenant branding and approved asset references with explicit unresolved image slots. 3. Extend the existing shared composer with undo/redo, accessible ordering and desktop/mobile preview. 4. Make preview, controlled test and final send consume exactly the same validated document renderer, including plain text and unsubscribe footer.
SaaS customer lifecycle, recovery, export and deletion
Complete the boring but required customer lifecycle around trial/activation, payment degradation, cancellation, export, deletion and recovery while preserving business truth and explicit release boundaries.
Finish proposal PDF, expiry, superseding, and follow-up
Generate matching PDFs, expire old versions predictably, and create deduplicated founder follow-up when proposal state changes or stalls.
SaaS billing and plan entitlements
Charge Accelerate customers for hosted workspaces and enforce plan capabilities through explicit entitlements. Keep platform subscription billing separate from customer-facing invoices and collections inside a tenant.
Enforce campaign policy envelopes and version reapproval
Persist the approved audience, sender, copy, steps, timing, stop conditions, and daily limit as an immutable executable version.
Add approved AI operation parity: Boards, recovery, notes and AI workspace controls
Use AI to organize work, change workspace layout and operate recovery controls while keeping the conversation and resulting work inspectable.
Build campaign dry-run, exclusion, and sample personalization review
Show the exact eligible recipients, exclusions, reasons, step timing, limit impact, and representative personalized messages before activation.
Opportunity Radar: evidence-based assets and reviewed distribution
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Opportunity Radar: configurable earned-growth business plugin
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Workspace invitations, members and role administration
Give workspace owners a complete customer-facing member administration flow using the existing tenant membership and record/action permission model.
Tenant usage economics, AI cost accounting and plan limits
Measure the real marginal cost of each workspace and enforce explicit plan/fair-use limits using existing model call, budget, work and integration receipts.
Recover and integrate all started work; restore trustworthy backlog
Founder-approved 2026-09-12 plan: reconcile all 353 cards and 60 retained worktrees, finish and independently review all recoverable started work, integrate into main, organize untouched backlog. Automatic safe takeover. Preserve source; production deployment separate.
Complete campaign enrollment and bounded personalization
Enroll canonical contacts once with auditable eligibility and generate only approved, fact-grounded personalization fields.
Deliver the first lead-to-delivery-and-invoice journey
Deliver the first lead-to-delivery-and-invoice journey. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Add durable operating goals with scorecards and generated work
Let the founder set versioned period goals for recorded revenue, qualified inquiries, response time, meetings, proposals, wins, and delivery commitments, then compare them with canonical actuals and named data gaps.
Modernize and canonically integrate every additional admin tool
Bring Leads, Contacts, Inbox, Bookings, Clients, Chat Inquiries, Subscribers, Content, Resources, Partners, and Website Grades onto the shared responsive shell and connect revenue-bearing records to canonical contacts, companies, opportunities, activities, tasks, attribution, and Today.
Add explicit platform-sponsored AI budgets per tenant
Extend tenant-owned OpenRouter BYOK with a founder-controlled sponsorship mode for exceptional workspaces, without turning the platform key into an implicit global fallback.
Accelerate operator console for hosted customer support
Give Accelerate a platform-level support surface for customers, workspaces, subscriptions, usage, integrations, agent failures and audited support access without routine direct database access.
Client document and access readiness plugin
Unblock onboarding and delivery by tracking exactly which client documents, information and access grants are missing, who owns the request and whether the submitted material is actually usable.
Enforce Learning Inbox lifecycle, audit and tenant-owned links in the database
Keep reviewed business guidance and its audit history accurate even when an agent calls the database directly. Tenant records and approval receipts must not be linked across workspaces. The 7 October read-only audit found learning_proposals authenticated ALL policy checks membership but not admin role, no non-internal lifecycle trigger, and single-ID FKs to action_queue/learned_policies. The service validates dispositions and records audit separately, but direct same-tenant table mutations bypass that service validation and audit. Current approved activation RPC is transactional and must be reused, not replaced.
Make the integration adapter registry the real resolution point
Plugin Platform phase 0 of 6. INTEGRATION_ADAPTERS at src/lib/revenue-os/integration-adapters.ts:460 documents itself as the registry every provider-scoped write resolves through, so that a new adapter is one entry rather than hardcoded imports scattered across routes. It has zero call sites. src/app/api/admin/tenant/providers/route.ts:12 imports whatsAppAdapter and hubSpotAdapter directly and calls them from an if/else chain at lines 257 and 301, which is exactly the pattern the comment claims to prevent. This is a prerequisite for plugin-supplied adapters, not cleanup: a plugin can only register into that map once the map is what provider operations actually traverse.
Deliver an optional Support plugin for triage, reply drafting and escalation
An optional Support coworker classifies incoming questions, prepares evidence-backed replies and escalates unresolved or overdue work to a human. Implementation steps: 1. Declare required conversation, knowledge, task and draft/send capabilities using the existing manifest/module runtime. 2. Register bounded work kinds for triage, draft reply and escalation with event dedupe, leases and budgets. 3. Reuse canonical context and tool registry; AI proposes replies and task actions through the normal approval queue. 4. Expose role, capabilities, pending work, drafts, escalation reasons and terminal receipts in the existing conversation and AI surfaces.
Add grounded AI drafting, intent classification, and next-action suggestions
Use bounded thread and revenue context to draft replies, classify intent, summarize history, and propose follow-up without taking external action automatically.
Turn flagged answers into reviewed knowledge corrections and regression cases
Operators inspect why an answer failed, propose a sourced correction, approve it and prove the corrected behavior without teaching the model unreviewed feedback. Implementation steps: 1. Attach bounded tool/evidence/validator traces to exact answer IDs with explicit missing-history state. 2. Build flagged-answer review with proposed source correction and duplicate-safe linkage to the original run. 3. Require approval and source access validation before publishing knowledge/exemplars; preserve old source/run history. 4. Turn approved corrections into deterministic regression prompts with expected evidence or escalation outcomes.
Verify Support end to end across all five shared admin demos
Prove useful Support outcomes in every fictional business using actual admin components and the shared session-local demo engine. Implementation steps: 1. Add distinct inbound questions, handoffs, reply templates, assignments, snoozes, failed drafts and reviewed corrections for all five scenarios. 2. Extend the shared demo transport and schema validation; never add replacement demo-only pages. 3. Automate triage to draft to approve to simulated reply, then customer follow-up, escalation and correction. 4. Verify reset, persistence, tenant/scenario isolation, plugin toggles and authenticated-founder request isolation; document the runnable journey.
Generate grounded pre-call briefs
Assemble company research, qualification, pipeline history, conversation, proposal state, documents, and stated objectives into an actionable meeting brief.
Build post-meeting notes and commitment extraction
Prompt after meetings for notes, then extract commitments, tasks, follow-ups, stage suggestions, and proposal inputs for founder review.
Extend Proposal Studio with branded options, specifications and attachments
Operators assemble professional customer proposals with several priced options, specifications and protected files, then publish a version that records exactly what the customer accepted. Implementation steps: 1. Extend the current proposal document model with optional comparison options, specifications, timeline and approved asset references. 2. Reuse shared branding and document presentation primitives without changing authoritative prices. 3. Use existing proposal lifecycle services for preview, publication, revocation and customer acceptance against an immutable version. 4. Connect accepted terms to existing opportunity/onboarding/invoicing services through explicit governed actions.
Build an optional inventory plugin with audited stock movements
A business tracks materials, stock movements, reorder thresholds and consumption with inspectable receipts rather than a read-only inventory report. Implementation steps: 1. Add tenant-owned material identities and append-only stock movements through a dedicated domain service and additive migrations. 2. Expose grid/detail views with units, thresholds and provenance; compute stock deterministically from reconciled movement state. 3. Register narrow receive/adjust/reserve/release actions with approval policy, concurrency protection and idempotency. 4. Create deduplicated low-stock work and a fictional inventory demo; retain movements on plugin disable.
Send proposals through the auditable communication service
Preview and confirm the exact recipient, version, public link, subject, and body before sending, then connect the provider receipt.
Add confirmation-gated Calendar create, reschedule, and cancel
Allow UI and AI to propose exact event mutations while requiring founder confirmation of calendar, attendees, time, timezone, and action.
Add supplier purchasing with approved orders and partial receiving
An operator turns a reorder need into a reviewed supplier purchase order, sends it through the governed sender and records partial deliveries against inventory. Implementation steps: 1. Model supplier links, purchase-order revisions/lines and per-line receipts with canonical IDs and tenant constraints. 2. Create a draft from low-stock work with operator-entered price/lead-time facts. 3. Approve the exact order version before external send; use recorded communications and immutable document snapshots. 4. Post partial receipts through stock movements with deterministic receipt keys; expose remaining quantities, cancellation and exceptions.
Add production jobs with sample approval and quality gates
A production business converts accepted specifications into assigned jobs, material commitments, sample approval and inspectable quality checks. Implementation steps: 1. Define a bounded job lifecycle linked to the accepted specification/version, assigned members and required materials. 2. Add sample approval and quality checklist gates that block production/completion when unmet. 3. Record progress and material consumption through canonical services with replay protection. 4. Surface blockers/capacity summaries in plugin views and Today using deterministic facts; AI may summarize or propose tasks.
Expose the existing coworker runtime through a governed WhatsApp operator channel
An authorized operator can ask for business status and review governed work from WhatsApp using the same agent and permissions as the browser. Implementation steps: 1. Extend the existing connector where supported; document exact supported provider capabilities before enabling the channel. 2. Bind verified sender identity to an active tenant member and validate signed inbound events with durable replay claims. 3. Adapt channel formatting/chunking and deterministic help/status commands around the existing coworker runtime. 4. Bind any approval response to the exact actor, action, version and expiry; expose receipts in browser and channel history.
Finish the just-in-time internal campaign executor
Claim due campaign steps internally, re-check policy and stop conditions at send time, enforce daily limits, and record terminal receipts.
Enforce every campaign stop condition immediately
Stop future steps on reply, hard bounce, complaint, unsubscribe, manual pause, opportunity conversion, meeting booking, or policy invalidation.
Draft personalized first-touch and reply messages safely
Generate editable outreach and reply drafts from approved facts, templates, campaign policy, and conversation context.
Summarize meetings and extract reviewable commitments
Turn notes and permitted conversation context into summaries, commitments, follow-ups, risks, and stage suggestions for founder review.
Draft audits and proposals from approved evidence
Create structured audit and proposal drafts from notes, company research, selected documents, approved offers, and pricing inputs.
Explain pipeline health, campaign results, forecast risk, and setup
Let the founder ask grounded questions about live metrics, failures, setup documentation, and recommended recovery actions.
Complete campaign unsubscribe handling
Provide one-click public unsubscribe, standards-compliant headers, durable suppression, and operator-visible receipts.
Build the AI policy, exemplar, ambiguity, and quality control plane
Give each AI surface versioned instructions, source rules, review requirements, curated examples, ambiguity handling, kill switches, and measurable quality outcomes.
Expose campaign performance, exceptions, and recovery
Report enrollment, sends, delivery, replies, stops, meetings, proposals, wins, failures, backlog, and recovery actions by approved version.
Add Playwright journeys for proposals and Setup recovery
Verify proposal send/view/accept/decline and demonstrate that provider failure and recovery change Setup Center truthfully.
Vendor subscriptions and obligation management plugin
Prevent forgotten renewals, unused service spend and missed vendor commitments by turning confirmed vendor terms into accountable review and cancellation work.
Add accessibility, reduced-motion, and visual regression coverage
Automate critical accessibility assertions and preserve desktop/mobile screenshots for the founder workflow surfaces.
Create one guarded Revenue OS ship command
Require typecheck, lint, unit/API/browser tests, build, migration dry run, deployment, and authenticated production smoke evidence in a deliberate release workflow.
Complete a 14-day automation health burn-in
Monitor campaign and Workspace jobs, provider receipts, retries, queue freshness, alert delivery, and audit history before increasing automation volume.
Deliver proactive operator briefs and leading indicators
Turn canonical changes into a concise, evidence-backed operating brief that tells the founder what changed, what is likely to matter next, why, and the safest next action before a deadline, revenue risk, or system failure becomes urgent.
Build the canonical Tasks workspace
Give the founder one complete commitments workspace for open, overdue, snoozed, completed, and record-linked tasks while keeping tasks.ts as the only writer and repairing every existing Tasks destination.
Add Revenue OS service-level unit coverage
Unit-test identity resolution, pipeline rules, task dedupe, priority selection, campaign eligibility/stops, AI impact tiers, and canonical metrics.
Build the data-quality repair center
Turn missing attribution, missing owners or next actions, orphan links, impossible stage history, duplicate candidates, and failed reconciliation into exact inspectable records with safe service-owned repair paths.
Define a plugin/module contract for optional business capabilities
Split the always-on core (contacts, companies, auth, tenancy, permissions, activity, AI context) from optional modules (proposals, campaigns, bookings, analytics) behind a declared contract, so a self-hoster or template author can enable or omit a capability without forking core logic. This is the prerequisite for business templates and a template directory; do not start those before this contract exists, or every template reinvents its own ad-hoc module boundary.
Build the incident, receipt, and recovery console
Give the founder one evidence graph from a health alert or failed action to its job, source, webhook, message, action, audit, and provider receipts, with only bounded and explicitly safe recovery operations.
Add versioned forecast scenario planning
Add base, upside, and downside planning scenarios whose versioned assumptions operate on canonical open-pipeline facts while remaining visibly separate from recorded forecast and won revenue.
Add Playwright journeys for Gmail linking, reply, campaign approval, pause, and stops
Prove conversation association and reply controls plus campaign dry-run, activation, due execution, pause, and stop behavior.
Expense intake, approval and reimbursement tracking plugin
Give small teams a complete expense workflow from evidence to approval and reimbursement status, with project attribution and duplicate prevention. Make cash commitments visible without pretending to be the accounting system.
Build the client-success lifecycle workspace
Extend the command center beyond the sale with one canonical workspace for onboarding progress, delivery commitments, client communication, risks, outcomes, renewal timing, expansion evidence, and referral follow-up.
Add governed bulk operator actions
Support carefully bounded multi-record task, ownership, stage, suppression, and campaign operations through exact previews, version-bound confirmation, per-record claims, receipts, partial failure, and safe retry.
Generalize approved automation policies
Replace bespoke autonomous modules with one versioned registry for bounded triggers, envelopes, eligibility, stop rules, templates, models, eval fixtures, approvals, kill switches, decisions, and execution receipts. Reuse boundary: src/lib/revenue-os/autonomy-policy.ts already exists. Verify its current behavior and implement only the remaining per-action, plugin or operator acceptance; do not build another runtime.
Prove client-instance export and restore portability
Give each instance a bounded secret-free export and a scratch-instance restore proof covering canonical records, immutable provenance, approved configuration, templates, and schema version without copying Accelerate or another client's data.
Add optional Microsoft 365 workspace parity
Map Outlook mail, Outlook Calendar, and selected OneDrive or SharePoint content through Microsoft Graph into the same canonical communication, scheduling, identity, knowledge, run, and receipt services used by Google.
Add optional Stripe revenue reconciliation
Link Stripe customers, invoices, subscriptions, payments, refunds, and disputes to canonical companies and opportunities so recorded payment truth can reconcile with pipeline and delivery without making Stripe the CRM.
Add optional Slack notification and approval delivery
Deliver selected briefs, operational alerts, and expiring approval links to founder-approved Slack destinations while keeping the Command Center as the durable notification, decision, and action ledger.
Add optional Notion knowledge ingestion
Index only founder-approved Notion pages and databases into the shared knowledge substrate with provider provenance, edit and permission propagation, citations, recency, and explicit deletion or inaccessible states.
Ship 2-3 vertical business templates (roofing, law firm, agency)
Package pre-configured tenant-config seams (branding placeholders, default pipeline stages, default AI system prompt framing, seeded demo data matching an industry) for 2-3 verticals already represented in this site's own case studies and demo scenarios, so a visitor can deploy something that already looks built for their business rather than a blank instance. Depends on the module contract so a template can declare which modules it enables.
Publish an integration adapter SDK for third-party connections
Extract the pattern already used for Google/Gmail/Calendar/OpenRouter connections (src/lib/revenue-os/integrations.ts, integration-registry) into a documented adapter contract a third party can implement for a new provider (Stripe, QuickBooks, Slack, Twilio) without touching core connection/credential storage.
Ship a create-accelerate scaffolding CLI
npx create-accelerate as a second on-ramp alongside the Deploy button, for developers who want a local clone pre-wired to a chosen template and modules rather than a hosted instance. Only makes sense once the module contract and templates exist; building this first would just hand-roll the same choices the contract should express declaratively.
Hiring pipeline and interview coordination plugin
Help a growing service business fill real delivery gaps through an accountable hiring workflow, reusing identity, conversations, calendar, work and approvals without mixing candidates into sales opportunities.
Let businesses extend records without creating another backend
Let businesses extend records without creating another backend. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Move saved views server-side and make record pages configurable
Saved views are localStorage only (src/lib/admin/pipelineViews.ts, leadsViews.ts), so they are per-device, unshareable, and lost when a browser is cleared, while being presented as a feature. Move them to tenant-scoped storage, shared or private per user, and extend the same mechanism to record page layout and sidebar arrangement.
Add user-defined dashboards and metrics
Analytics is a fixed set of canonical formulas on one page (src/lib/revenue-os/analytics.ts). A workspace cannot define its own metric, cohort, or dashboard. Build on the existing attribution model, which already surfaces unknown attribution honestly rather than reporting it as zero, so a user-defined metric inherits that truthfulness instead of inventing a cleaner-looking number.
Build a visual trigger, condition, and action workflow designer
Automation exists but is hardcoded across campaigns.ts, inbound.ts, and auto-responder.ts, so changing when something fires means changing code. A visual designer over the same primitives lets an operator express a rule, while every action it can take stays inside the approval and receipt model rather than becoming a second, looser execution path.
Publish a public REST API for canonical records
The only external programmatic surfaces today are MCP and write-only tenant ingest keys. There is no way to read records out, or to integrate a tool that does not speak MCP. A documented REST surface over the canonical services, authenticated per tenant and scoped by role, is what makes the open and flexible claim hold for someone who is not using an AI client.
Add foreign-key-safe generic record merge with supersession
Plugin Platform phase 1 of 6, primitive 1 of 7: Records. Duplicates are inevitable once ingestion is AI-driven, and most integrations either never clean them up or delete and orphan the dependents. A merge driven by the entity registry's foreign key catalog walks every dependent in one transaction, preserves the loser's identity as an alias on the winner so future inbound matches still resolve, and supersedes live dependent rows rather than deleting them. That combination is what makes merge safe to run repeatedly.
Resolve identity in batches before any write that could create a person
Plugin Platform phase 1 of 6. resolveOrCreateIdentity exists in src/lib/revenue-os/identity.ts and resolves one record at a time. Every capability that extracts people from unstructured input has the same failure mode: silent duplicate creation from name variants and transcription drift. Resolve identity for a whole batch first, once, and classify each candidate as matched, ambiguous, near miss, or new. Ambiguous and near miss are queued for a human and never silently created. This becomes mandatory middleware on any write that could create a person or a company rather than a helper a caller may forget.
Add a durable, replayable event bus with at-least-once delivery
Plugin Platform phase 1 of 6, primitive 4 of 7: Events. Nothing in the tree provides typed business events, durable delivery, replay, or delivery deduplication. Without them, capabilities can only be wired by direct calls, which creates a dependency graph nobody can upgrade and is the failure mode this platform exists to avoid. Events are also the only sanctioned way capabilities communicate with each other.
Require declared evidence on every write, enforced at the executor
Plugin Platform phase 1 of 6. The repository is further ahead here than the specification assumes: grounded answer validation already rejects an answer that does not cite receipts from tools that actually executed in that run, and execution re-reads record state and expires a proposal if reality moved. What is missing is applying the same discipline to writes. A commitment extracted from a transcript, or a stage advanced on inferred intent, is exactly where a hallucination causes damage. Evidence requirements belong in the validator, because a prompt instruction is a suggestion to a model while a validator is a guarantee.
Hold plugin credentials in a broker the isolate can never read
Plugin Platform phase 2 of 6, primitive 7 of 7: Connections. integration_connections already stores per-tenant credentials with AAD-bound envelope encryption, which is the hard half. What is missing is the broker shape: a plugin calls a fetch against a named connection and the broker attaches the token, so a compromised or malicious plugin cannot exfiltrate a refresh token because it never holds one. This is the single property that makes third-party plugins safe to connect to a customer's Google or payment account.
Make plugin activation, upgrade and removal predictable
Make plugin activation, upgrade and removal predictable. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Meter plugin usage and enforce a spend budget that halts cleanly
Plugin Platform phase 2 of 6. A plugin that calls a paid external service needs a per-install budget, and hitting the cap must disable that capability and notify rather than fail silently in the middle of a batch. Nothing meters plugin cost today because there are no plugins, but the shape should match the existing per-tenant AI budget work rather than inventing a second accounting system.
Add a per-action trust ladder with a permanent irreversible floor
Plugin Platform phase 3 of 6. Trust is held per install and per action, never per plugin and never globally, because the unit a human can reason about is one narrow capability. Four levels: always propose; auto-execute with notification and a 24-hour undo; auto-execute within a declared budget, dropping to always-propose when the budget is exceeded; and autonomous with digest reporting only. The hard invariant is that an irreversible action never auto-executes at any level, for any publisher, with no configuration flag, and the validator rewrites any manifest that attempts otherwise. Reuse boundary: src/lib/revenue-os/autonomy-policy.ts already exists. Verify its current behavior and implement only the remaining per-action, plugin or operator acceptance; do not build another runtime.
Propose trust promotion on evidence and demote automatically on failure
Plugin Platform phase 3 of 6. This is the loop that makes the product feel like it is learning without ever making the operator feel it is escaping. Promotion is proposed by the system and approved by a human, never taken. Demotion is automatic, immediate and unilateral. The asymmetry is the point: earning trust requires a human decision, losing it does not. Reuse boundary: src/lib/revenue-os/trust-graduation.ts already exists. Verify its current behavior and implement only the remaining per-action, plugin or operator acceptance; do not build another runtime.
Give every auto-executed reversible action a working 24-hour undo
Plugin Platform phase 3 of 6. An undo offer is only honest if the compensator has actually been executed against real state. A compensator that merely exists is a promise; one verified by executing and then undoing against seeded data is a guarantee. Undo is what makes the second trust level acceptable at all, so it is a precondition for graduation rather than a convenience.
Make approvals inline and capture reviewed edits as explicit feedback
Plugin Platform phase 3 of 6. An approval queue that requires navigating to a dedicated page is an approval queue people stop using. Approve from the digest, from chat, and from a dashboard card. Batch related proposals with per-item expansion. Treat edit-then-approve as first class, and record what the human changed as structured feedback rather than discarding it, because that edit is the highest-signal training data the system will ever get and it also feeds the graduation calculation. Reuse boundary: src/lib/revenue-os/action-executor.ts already exists. Verify its current behavior and implement only the remaining per-action, plugin or operator acceptance; do not build another runtime.
Make server-computed report recipes a registrable primitive
Plugin Platform phase 4 of 6, primitive 2 of 7: Views. Analytics today is a fixed set of canonical formulas on one page, and saved views are localStorage only, so they are lost on a device change while being presented as a feature. A recipe is one server-side computation with a typed output schema that answers a whole question in a single call. The alternative, letting a model assemble an answer from five separate queries at request time, is more expensive, inconsistent, uncacheable, and can silently omit a metric because the model forgot a call.
Render dashboard cards from JSON so the Tier 0 floor stays at twenty lines
Plugin Platform phase 4 of 6. This is the single most important number in the platform: if adding a chart takes more than roughly twenty-five lines of JSON and zero build tooling, the ecosystem does not happen. A declarative card is validated against a schema and rendered by core, which means no build step, no bundle, no cross-site scripting surface, and automatic theming. Because core owns the pixels, the admin design token contract and the navigation runtime contract hold for plugin UI for free.
Add UI slots and sandboxed panels that cannot escape their frame
Plugin Platform phase 4 of 6. Declarative cards cover most needs; the remainder need real UI. A sandboxed frame with a message bridge to the same capability-checked data API, and host-provided design tokens so plugin UI matches the product without sharing a stylesheet. Named slots let a plugin place a card, a record tab, a sidebar section, a bulk action, a command palette entry, a settings section, a digest section, or a custom approval card. Slot contention is resolved by the operator's saved layout, never by install order.
Give developers a working first business plugin with init, build and check
Give developers a working first business plugin with init, build and check. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Prove a plugin completes a safe business workflow before release
Prove a plugin completes a safe business workflow before release. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Exemplar Tier 0: a dashboard chart that is pure JSON
Plugin Platform phase 5 of 6. The floor test. A complete, installable plugin that adds a pipeline-by-stage chart with no code, no build step, and no permission beyond a single entity read. If this file grows past roughly twenty-five lines, the platform has failed its floor test and that is a release blocker rather than a note.
Document a version-matched extension and MCP developer journey
The existing Write the 49-page documentation spine in link-dependency order card combines several independently reviewable outcomes. This slice owns only the acceptance below.
Exemplar Tier 1: Business Pulse as one recipe, not five stitched queries
Plugin Platform phase 5 of 6, and the launch demo. A daily briefing covering open pipeline, overdue invoices, unanswered inquiries bucketed by age, proposals awaiting follow-up, calendar deltas, and anomalies such as channel volume diverging from close rate. Built as one server-side recipe, because five ad-hoc queries stitched at request time drift the moment a data source is added and can silently omit a metric. The demo arc is connect, understand, find problems, propose work, approve, work happens, and the last step is honest only because it traverses the same executor as manual work.
Exemplar Tier 2: Meeting Intelligence, the integration test for every primitive
Plugin Platform phase 5 of 6. This is deliberately built third, before any further connectors, because it is the only exemplar that exercises identity resolution, provenance gating, the full trust ladder and the event bus at the same time. If the primitives are wrong, this is where it surfaces, and finding that out here is far cheaper than finding it out after three more connectors assume the primitives are correct.
Exemplar Tier 3: external enrichment with a budget and a fill-empty-only policy
Plugin Platform phase 5 of 6. The exemplar for third-party data, and the one most likely to be copied badly, which is why it must demonstrate the discipline rather than only the capability. The write policy is the crux: enrichment never overwrites a non-empty field and never touches human-curated fields such as type, stage or owner. That single rule is the difference between enrichment as an asset and enrichment as data corruption.
Publish one version-matched developer journey and business exemplar guide
Publish one version-matched developer journey and business exemplar guide. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Publish a signed plugin registry with trust tiers that gate defaults
Plugin Platform phase 6 of 6. A public directory with installation from the registry or from a git URL. The listing requirement that matters most is that the plain-language capability summary is generated from the manifest rather than written by the publisher, because publisher-authored summaries are exactly where honesty degrades. Trust tier gates behavior rather than only badges: a community plugin installs at always-propose across every action regardless of what its manifest requested.
Ship verticals as signed bundles of plugins, settings and layout
Plugin Platform phase 6 of 6. This is where the scale actually comes from. Most businesses will install a vertical rather than assembling ten plugins, so a distribution is a signed bundle of plugins plus settings plus seed segments plus a dashboard layout, versioned and installable in one action. The existing five fictional demo workspaces are already the shape of this, which makes them useful evidence rather than only a demo.
Version the public extension contracts before inviting external plugins
Version the public extension contracts before inviting external plugins. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Complete task-oriented product and developer documentation
Document the shipped product in independently reviewable operator and developer journeys. Reconcile the actual four-section manifest and existing pages before expanding it; page counts are not a proxy for usable documentation.
Receivables and dispute resolution plugin
Turn overdue invoices into a controlled collection workflow with a clear next action, fewer duplicate reminders, and a defensible record of promises and disputes. Finance observations become work tied to actual invoice balances, not guesses based on won opportunities.
Retainer entitlements and client renewals plugin
Protect recurring revenue and service commitments by linking agreement terms, actual delivery usage, renewal decisions and invoices. Give the owner time to resolve overages or renewal risk before the next billing period.
Scope change and commercial approval plugin
Prevent unpriced work and lost margin by making a client request traceable to a reviewed impact, approved commercial change and delivery update. Keep teams from treating an informal chat message as permission to expand scope.
Client deliverable review and approval room plugin
Replace scattered approval threads with a single customer-facing review workflow that identifies exactly which deliverable version was approved and what the team must change next.
Delivery capacity and assignment planning plugin
Give the business a realistic delivery promise by connecting committed work, availability and skills. Turn overload or missed coverage into explicit scheduling decisions before a customer deadline is missed.
Project time, billable usage and margin control plugin
Make project economics actionable by turning approved time and costs into billable usage, invoice preparation and margin exceptions. Distinguish estimates, earned/billable value, invoiced value and received cash.
Establish honest scale limits for the business runtime
Establish honest scale limits for the business runtime. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Document Pipeline, Conversations and Proposal operator journeys
The existing Write the 49-page documentation spine in link-dependency order card combines several independently reviewable outcomes. This slice owns only the acceptance below.
Document Campaign, Email Studio and Support workflows that are available
The existing Write the 49-page documentation spine in link-dependency order card combines several independently reviewable outcomes. This slice owns only the acceptance below.
Verify north star Phase C through a complete business outcome
Existing shipped component cards do not establish the complete phase outcome. This card collects missing end-to-end proof without rebuilding those primitives.
Verify north star Phase D through a complete business outcome
Existing shipped component cards do not establish the complete phase outcome. This card collects missing end-to-end proof without rebuilding those primitives.
Verify north star Phase E through a complete business outcome
Existing shipped component cards do not establish the complete phase outcome. This card collects missing end-to-end proof without rebuilding those primitives.
Verify north star Phase A through a complete business outcome
Existing shipped component cards do not establish the complete phase outcome. This card collects missing end-to-end proof without rebuilding those primitives.
Add approved AI operation parity: Conversations, email and campaign management
Let users organize conversations, edit drafts and campaigns, manage membership, and approve sending or pausing from one conversation.
Extract SD Command into shared runtime capabilities and optional business plugins
Recover reusable SD Command engineering and business value through existing Accelerate services and optional plugins, with evidence-backed acceptance and no duplicate roadmap.
Model owed work and waiting states in the shared priority selector
Make fresh commitments visible while separating stale backlog and work blocked on someone else.
Unify scoped feedback and business outcomes without automatic policy promotion
Connect operator edits and recipient outcomes to subsequent work while preserving explicit human authority over durable policy.
Ship an optional relationship follow-up and commitment keeper plugin
Help businesses follow through on commitments using relationship-aware cadence and explicit stopping rules.
Ship optional explainable scoring over registered business records
Let businesses define transparent qualification and readiness scores without delegating arithmetic or truth to a model.
Ship optional evidence-backed participant and resource matching
Match people and resources to business needs with explicit eligibility and missing-evidence explanations.
Prove the extracted plugins with SuperDebate and a second business distribution
Demonstrate reusable operating workflows with a lean installation and no business-specific changes to the runtime.
Deliver proactive operator intelligence and quiet-day briefs
Every code path runs because a request arrived or a daily cron fired. Nothing notices a deal gone quiet, a promise unkept, three inquiries from one company, or a reliable client who has gone silent. Add a background loop producing a written synthesis: what changed, what it means, what is at risk, what needs the founder. Prose worth reading, not a digest of row counts.
Generalize approved automation policies into a shared policy registry
The inbound responder proved the pattern of a versioned founder-signed policy with an envelope, guardrails, a kill switch, and a recorded decision either way. But it is one module written by hand. Generalise it so adding a policy is declaring config and fixtures rather than writing another module and another test suite. Prove it with two more: a stalled-deal nudge and a commitment keeper.
Create a Business Outcome Ledger linking actions to measured results
agent_learning records one bit per run, misattributed across every tool that run touched. Nothing links an action to what happened next: did the reply produce a booking, did the proposed task get done, did the stage move stick or get reverted. Without that link the system accumulates history and never improves, and calling it learning is decoration. Add outcome windows, per-tool attribution, and an eval set per policy.
Build an accountable AI activity narrative over receipts and runs
Audit rows exist for everything and there is nowhere that says, in sentences, what the system did today, why, and what it decided not to do. Trust is the real bottleneck on autonomy rather than capability, and nobody widens the scope of a system whose reasoning they cannot inspect. Build the narrative surface on the audit ledger and agent_runs, both of which already record enough.
Harden task-focused tool bundles and on-demand activation
Plugin Platform phase 4 of 6, primitive 5 of 7: Tools. PACK_TOOL_NAMES is a fixed three-entry map, not a bundle activation mechanism, and it currently fails closed in a way that silently hides any tool nobody remembered to add. Replace it with manifest-declared bundles, a small always-loaded core, and an intent lookup that activates the matching bundle for a conversation. The rule that keeps this honest: a tool needing five calls to answer a common question is a missing recipe, and that is enforced in review rather than left to the model to stitch together.
Introduce versioned reusable Skills without granting capabilities
Plugin Platform phase 4 of 6, primitive 6 of 7: Skills. A skill is markdown shipped with a plugin describing when a capability applies, what good output looks like, and what never to do. Skills load when their bundle activates. The invariant that makes them safe is that a skill may reference tools but can never grant one: a skill instructing the model to send an email, against a plugin that never declared a send capability, simply has no function to call. That is enforcement by absence applied to instructions.
Verified · 198
Verification accepted; merge and deployment tracked separately
Operate the Feature Board as the delivery source of truth
Maintain one durable roadmap with exact ordering, structured details, archival history, and agent-ready handoffs.
Generalise tasks and scheduling into a durable Work Engine
Introduce a WorkItem abstraction that represents durable, lease-based, retryable, schedulable, and explainable units of work. Every autonomous action — follow-ups, research, invoice reviews, report generation — becomes a WorkItem that survives browser closure, deployment, process restart, model failure, and agent failure. This replaces ad-hoc cron-then-prompt patterns with a transactional claim model (FOR UPDATE SKIP LOCKED or equivalent), bounded retries, and mandatory reason fields on every scheduled future action.
Build one canonical Capability Graph for workspace capabilities
Create a single machine-readable Capability Graph that exposes every available workspace capability (crm.read, gmail.send, calendar.write, etc.) together with its policy (available, approval_required, unavailable). Coworkers and plugins query this graph before beginning work so they discover their capabilities up front rather than by repeatedly failing calls. This extends the existing integration capability platform into a first-class runtime primitive.
Detect reusable corrections from work diffs and propose learnings
Notice when a human correction is probably reusable and turn it into a Learning Inbox proposal with a guessed type, scope and confidence. Detection covers explicit user-marked corrections and diff-derived candidates from edited drafts; every candidate still waits for human review and nothing reaches shared knowledge automatically.
Verify isolated self-hosted Postiz service and LinkedIn company-page readiness
Automate Accelerate social content and establish a customer-facing optional plugin reusable across tenants.
Expose task-focused tool discovery through the existing MCP registry
Reduce routine agent context while preserving explicit discovery and independent authorization.
Create the shared operator-priority selector
Rank overdue commitments, unread replies, imminent meetings, proposal follow-up, campaign exceptions, and system warnings with one explainable policy.
Unify agent permissions into one Autonomy Policy Engine
Create one coherent system governing all agent actions, unifying AI confirmations, automation permissions, standing approvals, coworker permissions, safety floors, and audit provenance. Implement the five-level autonomy ladder: Level 0 (Prohibited), Level 1 (Always ask), Level 2 (Ask until trusted), Level 3 (Standing permission with constraints), Level 4 (Autonomous read/reason). Hard safety floors — destructive deletion, credential changes, financial transfers, full database exports — must exist in code and be irremovable by prompt instructions or repeated approvals.
Extract the business model and ask prioritized clarification questions
Turn messy business context into a structured intermediate model of entities, relationships, lifecycles, responsibilities, exceptions and unresolved questions. Ask only high-value follow-ups that materially affect workspace architecture.
Create a versioned Workspace Blueprint contract
Define the machine-readable, reviewable Workspace Blueprint that represents proposed navigation, entities, relationships, work types, boards, views, workflows, Coworkers, Skills, attention rules, integrations, permissions and unresolved questions before anything is applied.
Implement deterministic contact and company identity resolution
Create one identity resolver for UI, forms, syncs, webhooks, campaigns, and AI that handles alternate emails and refuses ambiguous matches.
Restore verified Site Studio writes and reconcile applied migration history
Recovery prerequisite discovered in PR83: authenticated RPC grants bypass installation-owner service checks and accept caller-supplied audit identity. Preserve the applied migration byte-for-byte, restore service-only writes with verified request context, and stage revocation after compatible application release.
Consolidate analytics on canonical source-to-revenue data
Make every admin metric derive from the same canonical contacts, opportunities, stage events, campaigns, meetings, proposals, and won revenue.
Compile approved Workspace Blueprints through existing Accelerate primitives
Build the deterministic compiler/preflight layer that maps approved Blueprint declarations onto existing entity, board, view, workflow, Coworker, Skill, integration and policy services. The model proposes architecture; the compiler decides what Accelerate can actually represent.
Build the provider capability platform and integration catalog
Create the stable integration contract that lets the Command Center add, replace, degrade, and retire providers without leaking provider-specific assumptions into admin, AI, or domain workflows. Ship a truthful founder-facing catalog for live and planned capabilities before adding another provider.
Reconcile Revenue and Activity with canonical records and receipts
The existing Modernize and canonically integrate every additional admin tool card combines several independently reviewable outcomes. This slice owns only the acceptance below.
Back legacy admin reads with canonical adapters
Temporarily preserve legacy response shapes while sourcing data from canonical services until parity checks and UI conversion pass.
Build the canonical task generator with deduplication
Create tasks from humans, meetings, campaign exceptions, proposals, and AI without producing duplicate open commitments.
Memory architecture: five distinct memory categories with unified query
Implements northstar §23: memory should not be treated as a single vector database. Five distinct categories are kept separate: canonical (business records), activity (what happened), knowledge (documents and indexed sources), agent (prior work, research, questions with time-decay horizons), and learned policy (explicit rules from human decisions with supersession). A unified queryMemory interface routes across all five without collapsing them.
Finish the canonical pipeline transition service
Route every opportunity stage change through one validated service with immutable history, reasons, and terminal-state rules.
Maintain agent-ready architecture and recovery runbooks
Document operating contracts, data ownership, dependencies, setup, failure recovery, testing, and safe change boundaries so another agent can resume without rediscovery.
Add an open entity registry and a polymorphic link graph
Plugin Platform phase 1 of 6, primitive 1 of 7: Records. There is no entity_links table, no entity_types registry, and no generic merge anywhere in src or migrations. Without a generic link table every pair of capabilities that needs to relate records requires a bespoke join table and its own migration, which is the cost that stops an ecosystem before it starts. A meeting capability needs to link a transcript to a contact to an opportunity to a follow-up task; today that is four schema changes. Entity types become rows rather than an enum so that links, merge and audit work on a newly registered type the day it appears, with no code change.
Harden encrypted secret and token storage
Keep provider secrets in environment configuration and encrypt refresh/access credentials server-side with rotation and redacted diagnostics.
Verify founder-only admin access and service-only data policies
Prove that only the configured founder can enter admin routes and APIs and that browser clients cannot use service-role capabilities.
Finance Coworker: revenue tracking, overdue detection, and reconciliation
A dedicated Finance Coworker that tracks revenue, monitors payment patterns, alerts on overdue payments, and reconciles financial records. Three work kinds: weekly_revenue_reconciliation (compares won deals week-over-week, weighted pipeline), detect_overdue_payments (flags won deals with no recent activity), revenue_stage_audit (identifies high-stage deals at risk of stalling). Bootstrap registers crm.read + crm.write capabilities and autonomy policies.
Opportunity Radar: durable discoveries, evidence and opportunity lifecycle
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Decide the scheduling substrate
Phases C through F need something to run when nobody is asking. Vercel Hobby gives exactly two cron slots at daily granularity and both are used by revenue-campaigns and google-workspace-sync. This is an architectural ceiling rather than a backlog item, and it blocks continuous cognition entirely. Three options: Vercel Pro, Supabase pg_cron with edge functions, or an external worker.
Make task pickup and resume compact, durable and CLI-first
Reduce repeated context loading and setup while preserving the full live work contract and canonical claims.
Enforce selected-folder Drive access boundaries
Let the founder save a small allowlist of Drive folders and prove synchronization cannot traverse unrelated content.
Ship an isolated, persistent Command Center demo mode
Provide a shareable full-screen Command Center sandbox that demonstrates realistic operator workflows with fictional data, coherent session state, and an explicit safety boundary before any account or provider is connected.
Build contextual contact, company, and opportunity details
Create responsive record details showing identity, qualification, value, timeline, conversations, meetings, proposals, tasks, research, attribution, and next action.
Add Playwright journey for inbound capture and pipeline progression
Prove a real inbound form creates one canonical identity and opportunity, preserves attribution, appears in Today/Pipeline, and progresses through validated stages.
Preserve Gmail threading and message idempotency
Normalize Gmail threads and messages while retaining RFC message IDs, references, provider IDs, participants, and reply headers.
Ship three complete full-admin demo scenarios
Populate the shared full-admin demo with three coherent fictional businesses whose emails, records, workflows, AI context, receipts, metrics, integrations, and guided stories reconcile across every enabled workspace.
Add schema-version and drift verification
Make the deployed schema version and expected columns, constraints, functions, policies, and indexes reproducibly verifiable before shipping.
Work scheduler: auto-create recurring daily and weekly coworker work items
The work scheduler closes the gap between 'coworkers exist' and 'coworkers have work to do'. Before each work engine execution cycle, the scheduler creates daily work items (daily digest, stale deals, bottleneck check, health check, overdue scan) and weekly items (revenue reconciliation on Mondays). Date-based deduplication keys prevent duplicate work items.
Phase B: a knowledge substrate with provenance
The system knows rows, not things. Ask what was agreed with a client last month or why a deal stalled and there is nowhere to look. Add a chunked, embedded, retrievable knowledge store where every chunk carries its source, its date, and its confidence. This is the single largest gap and the one that makes the phrase second brain mean anything.
Build the isolated full-admin demo runtime
Render the real admin route tree through one safe live-or-demo runtime so shareable fictional workspaces reuse every production component without weakening founder authorization or reaching protected systems.
Finish the shared AI confirmation system
Require explicit in-turn approval for individual sends, stage changes, event mutations, proposal sends, and destructive operations.
Build the persistent streamed AI command runtime
Turn the one-shot Revenue Copilot into one founder-only runtime with durable conversations, page context, streamed run events, cancellation, bounded history, and the existing registered-tool and action-queue boundaries.
Verify the production Revenue OS schema
Confirm the canonical Revenue OS and Feature Board schemas are present in production and record the verification baseline.
Prove a fresh fork reaches its first usable business workspace
Prove a fresh fork reaches its first usable business workspace. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Make completed build process-group cleanup reliable without weakening resource limits
Final Collections build completed compile/types/page generation, then the resource wrapper reported kill EPERM. Verify whether an owned process group still exists before final cleanup; always release the lock after errors and retain failed receipts.
Normalize the cross-channel activity ledger
Represent form submissions, messages, meetings, notes, proposal events, stage changes, tasks, and AI actions in one chronological activity contract.
Collections Action Desk: deliver the operator workspace and business proof
Collections Action Desk: deliver the operator workspace and business proof. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Collections Action Desk: persist cases, disputes and payment promises
Collections Action Desk: persist cases, disputes and payment promises. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Expose the governed tool registry through MCP
Use the same versioned tool definitions for approved MCP clients and future external MCP sources so the Command Center can expand without creating parallel business logic.
Prepare the repository for a safe public launch
Turn the production-derived private repository into a credible open-source project with a reproducible newcomer path, explicit licensing and asset boundaries, public-safe operations, automated security hygiene, and a reviewed GitHub community surface.
Make clean installation and upgrades use a verified migration ledger
Make clean installation and upgrades use a verified migration ledger. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Keep every public route inside the standard site shell
Make public campaign, demo-selection, and marketing routes feel like one Accelerate site by applying the standard header, navigation, footer, chat, route progress, and responsive shell everywhere except authenticated or entered full-admin workspaces.
Enforce module enablement on routes, not only navigation
Plugin Platform phase 0 of 6. Three shipped documents state that a disabled module's routes fail closed: src/lib/revenue-os/modules.ts:12, extensions/README.md:32, and docs/contributing/EXTENDING.md:17. Nothing enforces it. isModuleEnabled has zero callers in src/app and src/middleware.ts, so disabling a module hides its sidebar link while the page still renders on direct navigation and its API routes still answer. Close the gap at two points and describe each one accurately.
Add Resend delivery webhooks and suppression receipts
Verify and process delivered, bounced, complained, opened, and clicked events idempotently and connect hard failures to suppression.
Build the governed agent learning feedback loop
Capture founder feedback and real action outcomes as reviewable signals that improve future AI guidance without creating self-modifying behavior or ingesting unsafe instructions.
Ship a one-click Vercel deploy button
Add a real Deploy to Vercel button and template configuration so a visitor can go from the README to a running, empty, unconfigured instance without cloning the repo or touching a terminal. This is the single highest-leverage change for adoption: every extra manual step between 'I found this on GitHub' and 'I have a working workspace' loses non-technical operators and the agencies serving them.
Ship tenant workspaces, switching, and founder provisioning
Give the founder a platform tenant directory and invitation lifecycle, give client admins the complete tenant-scoped operator workspace, and make tenant identity visible and stable across navigation, cache, branding, setup, and recovery.
Complete AI tool registry and impact tiers
Register bounded tools dynamically and classify reads, internal writes, external actions, and destructive actions with explicit schemas and permissions.
Build the Evidence and Claim Ledger for AI-derived facts
Create an evidence-backed fact system that prevents models from inventing confidence scores and treating them as truth. Every AI-derived fact becomes a Claim with supporting Evidence entries carrying sourceType, sourceId, observation, timestamp, provenance, and strength. Deterministic business rules — not the model — decide whether evidence is strong enough to update authoritative state. This implements the human truth protection hierarchy: human-confirmed > human-entered > verified external > probable external > model inference.
Close the module contract gaps that let unreachable code ship
Plugin Platform phase 0 of 6. Four defects let broken module wiring pass CI today. setupChecks is read by nothing and all four declared ids at modules.ts:152 and :194 are drifted, resolving to no real Setup Center check. availabilityFor marks any tool outside PACK_TOOL_NAMES unavailable while ai-agent.ts always passes a pack, so a registered tool can pass every gate and be permanently unreachable. isNavLinkEnabled and isAiToolModuleEnabled both fail open on an unknown id, so deleting a manifest without deleting its code pins that code on forever. And verify-module-contract.mjs parses TypeScript with regular expressions, which is how a gate script eventually starts lying about what it checked.
Opportunity Radar: source-backed people and warm introduction paths
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Ship one operator-grade AI workspace everywhere
Use the shared command runtime from a dedicated AI workspace, a global command panel, and contextual record launchers with one conversation state and one approval boundary.
Make first PWA update activation reload-safe
The PWA update handler waits for controllerchange when an active controller exists, but a first activation with no controller reloads before sending SKIP_WAITING.
Complete before/after audit coverage for material changes
Record the actor, origin, target, before/after summary, and timestamp for every material founder, AI, automation, integration, and public action.
Tenant-isolate providers, public intake, webhooks, and jobs
Resolve public capture, OAuth, provider credentials, sends, syncs, webhooks, cron, health, tokens, and idempotency through the owning tenant so no external effect or provider fact crosses a workspace.
Expose governed Collections reads and reminder proposals to AI and MCP
An operator can ask an AI assistant to inspect overdue cases and prepare verified reminders for review, without duplicating billing rules or granting the agent sending authority.
Lock the full-service AI positioning and reset public marketing copy
Rewrite the public marketing site around Accelerate's actual offer: understand each business, identify where AI and automation can free time or increase revenue, then advise, build, integrate, execute, train, and improve the custom solution. Keep the Command Center as one integrated solution rather than the company definition, and make the positioning durable for future agents.
Integrate completed agent work and deploy the verified production release
Completed UI integration, PWA, agent workflow and interaction branches need one reviewed production release. Founder explicitly authorized integrating completed agent work and deploying the live site on 2026-09-21.
Establish universal approved AI access to admin operations
Users should operate every authorized admin business workflow conversationally with exact human approval, using the same domain services as UI and plugins.
Resume interrupted agents with durable checkpoints and fenced claims
Implement approved automatic safe takeover and durable handoffs in the canonical work board.
Finish the preserved services redesign and verify its public journey
An unfinished services redesign exists only in an old worktree. Its five files are now preserved at c5edb9360136051fd9d573323848dd25b643cdc0. It has not passed current-main content, navigation or visual verification.
Answer every inbound inquiry inside an approved response policy
Acknowledge a first-touch inbound inquiry within seconds, grounded strictly in what the prospect wrote and the canonical record, executing inside a founder-approved response policy version rather than a per-message approval. The engineering contract permits an external action without per-instance confirmation only from inside an approved policy version, so the responder is not a trusted agent: it is a signed policy carrying the trigger, envelope, guardrails, template, and model, and any material edit bumps the version and suspends sending until re-approval, exactly as activateCampaign already behaves.
Close plugin data grant and tenant-boundary bypasses
Northstar foundation follow-up: make the existing capability data API enforce host tenant identity, entity grants, readable fields, bounded queries, and namespaced storage consistently before plugin hosts build on it.
Prove the plugin runtime with four switchable business reports
Founder-directed northstar proof: ship useful read-only pipeline risk, overdue commitment and upcoming meeting reports through the existing module registry, capability data boundary and QuickJS isolate. One host and one workspace activation contract serve UI and AI.
Finish Today as the prioritized operator inbox
Make Today the founder’s single queue for overdue work, replies, meetings, proposals, campaign exceptions, approvals, and system warnings.
Overhaul core admin clarity, guidance, visual hierarchy and navigation
Implement the founder-approved full cohesive admin overhaul: canonical language, contextual support, shared shell polish and coordinated motion; reconcile submitted contact-review/demo, theme and naming changes.
Deliver actionable invoicing, onboarding and meeting workflow plugins
Founder correction: report-only examples do not prove a business command center. Build substantive optional plugins that prepare concrete business actions, accept editable inputs, obtain approval through the shared queue, execute through existing domain services and preserve durable results. Start with Stripe invoicing, then won-deal onboarding and meeting commitments.
Adopt instance-per-client cloning as the Command Center product shape
Preserve the evidence and consequences of the former instance-per-client decision. This historical card was explicitly superseded on 2026-08-30 by shared-database-multi-tenancy-contract and no longer governs new schema or authorization work.
Add actionable health alerts and recovery runbooks
Notify the founder when syncs, jobs, delivery, webhooks, tokens, or queue freshness breach defined thresholds and link to recovery steps.
Polish the coherent admin core and distinguish all seven themes
Founder follow-up explicitly asks to polish the completed core and themes to a professional standard. Build directly on its submitted implementation without altering the frozen prior submission.
Reduce avoidable agent workflow friction
Make ordinary agent pickup, long verification and handoff work predictable without weakening claims, leases, checkpoints, review or evidence.
Fix the cold-clone onboarding and fork deployment gaps
Founder requested all findings from the September 21 cold-start evaluation fixed: placeholder login mismatch, Hobby-incompatible cron defaults, inherited disabled Git deployment, overloaded/conflicting setup docs, and weak first-real-result acceptance. Make the complete product easy to explore and provide one truthful path to a connected workspace.
Rebuild dashboard with compact hierarchy and actionable content
Founder requests a researched dashboard redesign: remove redundant heading lines, wasted top-right space, divider/button collision, incoherent first-card gradient and redundant list icons.
Complete AI run traces, tool evidence, errors, and usage
Persist bounded run metadata, tools, inputs/results summaries, model usage, failures, and affected records for debugging and cost control.
Run plugin code in an isolate with no ambient authority
Plugin Platform phase 2 of 6. There is no sandbox of any kind in the tree today: no isolated-vm, no worker, no node:vm. The current seam avoids the problem by executing nothing from extensions, which is a correct invariant for a manifest but caps the platform at declarative capabilities forever. An isolate moves the boundary: plugin code runs with no database handle, no filesystem, no environment, and a default-deny egress allowlist, receiving only host bindings pre-scoped to what its manifest declared. Cold start under 50ms is a requirement rather than a goal, because event handlers fire constantly and a slow cold start makes the whole product feel dead.
Resource budgets for autonomous workers with explicit spending caps
Implements northstar §24: autonomous workers require explicit resource constraints. Six budget kinds: model_spend, vendor_api_calls, emails_sent, research_depth, retry_count, runtime_seconds. Limits can be per-coworker or global, with daily/weekly/monthly periods. The work executor checks budgets before executing work and records usage after. Running out of budget is a normal state — work is skipped with a clear reason, not failed.
Repair admin overlays, entry motion, tokens, and collapsible navigation
Replace route-local overlays and undefined visual tokens with one portal-based interaction system, intentional page entry motion, a responsive shell, and a persisted collapsible desktop sidebar.
Extract every business fact into one tenant configuration
Create one typed configuration module that is the only place the brand, founder identity, offerings, industry playbooks, pipeline labels, AI persona, capability switches, and external project links appear, so a second installation is a config file rather than a search and replace across the codebase.
Make generic policy registration and reapproval deterministic
upsert_autonomy_policy uses ordinary nullable unique conflict target, so NULL generic registrations create multiple rows. grant_standing_permission UPDATE RETURNING can fail on those duplicates. Current strict reads preserve older restrictive rules.
Demonstrate business plugins and branding across the five fictional workspaces
Founder-directed follow-up: make invoicing, client onboarding, meeting commitments, plugin activation and branding explorable in the actual admin demos using coherent fictional business data and useful simulated outcomes.
Reconcile historical completion claims with their current prerequisite evidence
Fourteen historical shipped cards currently name unverified prerequisites; this is an evidence discrepancy, not proof that their implementations are absent.
Prove multi-tenant isolation and activate the first client
Run the complete database, API, browser, public, provider, and recovery matrix with controlled tenants, then activate client access only after every cross-tenant attempt fails closed and Accelerate behavior remains intact.
Remove work-volume blocking and resume named expired claims without repeated approval
Explicit founder work requests must proceed without arbitrary board capacity or expired-claim approval loops.
Build the identity review workbench
Turn ambiguous and unmatched Gmail, Calendar, import, form, and compatibility identities into a bounded founder review queue with evidence-backed link, create, no-match, and defer decisions.
Make Command Center installable and mobile-ready as a scoped PWA
Give authenticated tenant workspaces a professional installed experience on macOS, iOS, iPadOS and Android while preserving tenant routing, auth boundaries and marketing-site behavior. Add a dedicated app origin, stable manifest, install UX, strict service-worker cache policy, safe offline summaries, non-sensitive drafts, mobile Today priorities and privacy-safe telemetry. Keep consequential actions online and defer native wrappers and push notifications.
Finish the canonical Pipeline workspace
Provide one industry-agnostic opportunity workspace with stage control, qualification, value, next actions, and consistent contact/company context.
Import and clean ad hoc contacts with AI review and approval
Give the founder one importer for pasted notes, copied lists, CSV/TSV, and JSON. Deterministic parsing runs first; OpenRouter proposes normalized contacts and company links; the founder edits, includes/excludes, and approves an immutable reviewed snapshot before canonical writes execute with row-level receipts.
Make record and action permissions consistent for UI, agents and plugins
Make record and action permissions consistent for UI, agents and plugins. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Keep first-run demo rewrites internal on the CI loopback server
CI binds Next to 127.0.0.1 while NextURL canonicalizes loopback destinations to localhost. The router compares different origins and proxies an intended internal demo rewrite over HTTP. CI run 34007270461 captured an ECONNRESET and a literal Internal Server Error page. Align the test server origin and prove routing remains internal.
Build the selected work portfolio
Create Accelerate's six-project public Selected Work system, with Northern Trust preserved as an unlisted archive, as a proof layer for the operating, product, software, automation, growth, and emerging-technology experience behind the firm.
Enforce atomic claims and idempotency for jobs and actions
Ensure campaigns, approvals, sync jobs, sends, and webhook processing claim work atomically before side effects.
Rebuild core admin around one expressive, coherent design system
Founder approved plan on September 12: core design first across all admin; keep the system simple, expressive and tactile. Shared tokens, components and five page compositions before further skin differentiation.
Refine admin spacing, navigation and motion across all themes
Founder follow-up explicitly asks to polish the completed core and themes to a professional standard. Build directly on its submitted implementation without altering the frozen prior submission.
Build the tenant control plane and backfill Accelerate
Add tenant, membership, ingest-key, and platform-audit tables; give every operational row explicit tenant ownership; and backfill the existing database into the Accelerate tenant without deleting or duplicating records.
Collections Action Desk: send one approved and freshly validated reminder
Collections Action Desk: send one approved and freshly validated reminder. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Make the backlog an executable guide to north star business outcomes
Founder-approved plan: improve the full live backlog and existing universal work board so independent agents can safely deliver useful business journeys across parallel north star phases.
Today: composable business workspace with sourced intelligence and contextual actions
Founder-approved implementation plan: run the business through saved composable views, a sourced brief, contextual work and approvals, coworker progress and existing App contributions. Stable user-controlled layout with live content. Must look polished with zero, one, sparse or abundant records.
Operations Coworker: system health, integration monitoring, and data quality
The meta-coworker that watches the platform itself. Three work kinds: daily_health_check (failed jobs, stale work claims, expired actions), integration_status_audit (source_runs for failures and unconfigured sources), data_quality_scan (contacts without email, opportunities without company name or next action). Bootstrap registers crm.read capability and ops autonomy policies.
Reconcile legacy records with the canonical model
Prove row-count and field-level parity between legacy capture tables and canonical contacts, companies, opportunities, activities, and attribution.
Generate bundled workflow contracts from the business validators
Bounded implementation slice of plugin-manifest-generator. Eliminate duplicated input schemas and action selections for onboarding, meeting commitments and Stripe draft workflows before adding the broader tier/evidence/event/read-write grant model.
Give the founder's own knowledge a way in
Every input the system has arrives from someone else: a form, a mailbox, a calendar. What the founder himself knows, a constraint a client mentioned, why a deal actually stalled, what was decided and rejected, has nowhere to go. That is the difference between a record of what happened to the business and a second brain. Add a plain capture surface: a note, optionally attached to a contact, company, or opportunity, stored with a date and retrievable later.
Finish Setup Center as the operational control plane
Group Core, Email, Google, AI, Campaigns, Proposals, Analytics, optional Booking, and Operations into actionable live capability checks.
Make the Feature Board an authoritative human and agent work system
Founder-directed implementation: make live work definitions authoritative; unify transitions, structured dependencies, fenced claims, review evidence, scoped agent API/MCP/CLI, and operator organization. After implementation, add ten distinct business-value plugin specifications.
Route every write through one executor with reversibility and compensators
Plugin Platform phase 1 of 6, primitive 3 of 7: Actions. This is a refactor of something real rather than a greenfield build. action_queue already carries the status lifecycle, a pending dedupe index and expiry, and the AI tool registry already asserts at runtime that a mutating tool staged a proposal. What is missing is the reversibility axis, which is orthogonal to the existing impact tiers: impact says how far an effect reaches, reversibility says whether core can restore the prior state. Add the class, add compensators, add an evidence column, and make one executor the only write path so that a user clicking Save and a plugin proposing a change traverse identical code. That single property is what makes the approval queue real rather than cosmetic and the audit log complete rather than best-effort. Reuse boundary: src/lib/revenue-os/action-executor.ts already exists. Verify its current behavior and implement only the remaining per-action, plugin or operator acceptance; do not build another runtime.
Implement strict documentation coverage checks and actionable gap reports
The current documentation manifest contains four sections while the older card assumes a finished 49-page spine. Implement the coverage checker independently; content slices fill its reported gaps, and final CI enforcement belongs to docs-extension-developer-guide.
Finish Conversations as the unified communication inbox
Combine synchronized Gmail, inbound forms/messages, Resend activity, and manual communication into one founder inbox with record context and reply tools.
Require truthful coworker completion and durable Sales drafts
Replace outcome-string-only execution with explicit dispositions so skipped, deferred, partial, and failed work cannot be marked completed. Verify Sales drafts against durable approval proposals and preserve retryable handoffs.
Create the won-to-delivery handoff
Turn one canonically won opportunity into one inspectable client engagement with onboarding milestones, commitments, source context, and a receipted handoff without creating a second identity or sales pipeline.
Modernize demo marketing and clarify contact review copy
Replace the confusing Identity Review screen shown by the founder with plain business language and truthful states. Audit shared setup messages used by adjacent admin pages. Redesign /demo/command-center as a modern persuasive marketing launcher with dynamic product visuals, as explicitly requested by the founder.
Repair public-site motion and static delivery
Make every public route immediately visible from prerendered HTML, remove hydration-gated route blanks, and give the full public site a coherent, mobile-safe entrance-motion system with especially complete coverage across Selected Work.
Build the documentation site infrastructure at /docs
Documentation track, step 1 of 4. Land the whole navigable spine with only three pages of prose, so the system is proven before any content volume is written. The MDX pipeline already exists and is production-proven for the learning hub: createMDX with the gfm, slug and autolink plugins, compileMDX from next-mdx-remote, a filesystem loader, and thirteen components. Three gaps: the loader is a flat directory read with no recursion, there is no persistent sidebar, and there is no docs search. Structure is an explicit manifest rather than a filesystem walk, because a walk can only ever be self-consistent: it can tell you what exists but never catch a page that was supposed to exist.
Add cancellation-aware work deadlines and bounded provider circuit recovery
Prevent a slow provider or timed-out operation from losing the tail of a batch or producing late duplicate effects.
Expose one capability-checked data API with no raw database handle
Plugin Platform phase 1 of 6. Reads must go through a single capability-checked interface and writes must go through the executor, because that is what makes row-level security, cost accounting and audit complete rather than best-effort. The pattern is already proven in this repository: bindTenantDatabase is a proxy that forces tenant filtering because the service role bypasses row-level security. Generalize it into a data API with three shapes, a filtered entity query, a server-computed recipe, and a capability's own namespaced storage, and deliberately provide no direct write to core entities.
Keep appearance choices from reverting across open demo and admin tabs
Founder reports that changing appearance on /admin/conversations immediately reverts. Reproduce shared theme ownership across live/public and demo tabs, then correct the shared lifecycle.
Execute approved AI branding changes through the shared admin service
Let an operator ask AI to change workspace logo, colors and business identity, inspect an exact change preview, then approve the actual shared branding save.
Give every portfolio case distinct art direction and restrained motion
Refine the public Work index and six public cases into a more alive, editorial proof layer with project-specific visual worlds, stronger media composition, and restrained motion that remains fast, accessible, and recognizably Accelerate.
Consolidate Settings and connection ownership
Give every integration, AI rule, notification preference, template, pipeline option, and audit view one authoritative admin surface.
Support explicitly authorized local operator ticket execution
Allow an authorized local operator to use the canonical work service when scoped HTTP access is not configured, without weakening remote authentication or ticket lifecycle.
Reconcile analytics with canonical stage history
Make funnel progression, furthest stage reached, time in stage, regressions, stale movement, and forecast inputs derive from canonical stage_events while current-stage reporting remains explicitly current state.
Extract and index approved Drive documents
Fetch supported document text and metadata, hash content, skip unchanged files, and retain folder and provider provenance.
Harden webhook, cron, replay, validation, and rate-limit defenses
Apply provider signatures, OAuth state, replay IDs, cron secrets, strict payload validation, and bounded rate limits to every external entry point.
Document installation and the first useful business journey
The existing Write the 49-page documentation spine in link-dependency order card combines several independently reviewable outcomes. This slice owns only the acceptance below.
Collections Action Desk: decide the next safe action per account
Collections Action Desk: decide the next safe action per account. Deliver an observable business or developer outcome, not a decorative report or a second infrastructure stack.
Execute approved AI plugin toggles and module settings
Let an operator enable or disable installed plugins and edit their declared public settings conversationally, with exact approval and the same admin service.
Deliver five complete targeted business demo workspaces
Turn the full-admin demo into a five-business sales suite for home services, law firms, professional services, real estate, and nonprofits, with separately authored operating data, intentional default appearances, and a light/dark launcher that helps a visitor choose the right example.
Standardize every AI workflow on the OpenRouter gateway
Replace route-local model clients with one server-only OpenRouter gateway that owns authentication, model selection, structured outputs, timeouts, safe errors, attribution headers, and usage receipts for every Accelerate AI workflow.
Provide a neutral fork distribution without inherited agency assets or deployment assumptions
Provide a neutral fork distribution without inherited agency assets or deployment assumptions
Govern machine-wide agent resources without terminating session context
Prevent cross-project RAM exhaustion with one local supervisor, bounded heavy-job admission, durable session recovery, and explicit pause versus cancellation controls.
Make commits fast while preserving reliable review and release verification
Replace the untracked full-build/live-database commit hook with versioned, staged-content checks. Remove duplicate TypeScript work and parallelize CI without weakening its required result.
Rebuild Analytics around decisions and data quality
Present source-to-revenue funnel, campaign outcomes, forecast, response rates, meetings, proposals, wins, and data-quality warnings from one metric service.
Associate Gmail threads with canonical revenue records
Link participants and conversation context to contacts, companies, opportunities, campaigns, and proposals with review for ambiguity.
Workspace Architect chat session, attachments and source context
Make chat the primary Workspace Architect interface with durable sessions, file attachments, connected context and explicit source provenance. The conversation remains the control plane while supporting visual cards and inspectors.
Add useful Pipeline saved views and ownership filters
Support repeatable views for new inquiries, no next action, overdue follow-up, upcoming meetings, proposals, at-risk deals, wins, and nurture.
Build the system-health report and freshness thresholds
Summarize sync freshness, job receipts, queue backlog, delivery failures, webhook failures, connection degradation, and alert deliverability.
Prevent growth of silent error swallowing in runtime services
Make newly swallowed runtime errors fail CI, and require the recorded exception budget to shrink when existing silent catches are removed.
Complete the shared professional admin system
Complete the founder-approved coherent admin polish, responsive reliable Kanban, and modular user/AI theme creation.
Explain platform value across product pages, demos, docs and industry recipes
Implement the founder-approved plan: equal emphasis for business users and builders, refine the current brand, two actionable recipes on all ten industry pages, and a full public documentation clarity pass.
Audit recent architecture drift and consolidate runtime contracts
Founder-directed August 29 through September 4 architecture audit and incremental consolidation. Preserve feature development while making shared runtime governance, work receipts, and domain ownership enforceable across entrypoints.
Institutional Learning Inbox: propose, approve and record reusable corrections
Turn reusable human corrections into approved shared intelligence instead of letting them disappear into conversations. A Learning proposal carries type, scope, confidence, conflicting references, affected workers, supersedes links and source; ignore and this-conversation dispositions leave no shared residue; approval routes through the existing action/autonomy path and persists via the extended learned-policy record with authority tier and provenance.
Duplicate campaigns into new drafts with versioned copies
Operators duplicate a campaign into a fresh draft that copies audience selection, document revision, sender, schedule, limits and stop policy without copying membership state, receipts or approvals. Implementation steps: 1. Add a tenant-scoped duplicate domain service that deep-copies the source campaign row, steps and approved document reference into status draft with version 1 and no approved_version. 2. Never copy campaign_members, messages, receipts, approvals or audit history; the clone starts with zero members and requires fresh enrollment and approval. 3. Expose duplicate through the existing Campaigns workspace row action and the governed admin/AI path with the same authorization as campaign creation. 4. Record an audit receipt linking the new draft to its source campaign and version for provenance.
Make public proposal views and decisions idempotent
Record public views safely and allow accept or decline without login or payment while preventing duplicate outcomes.
Add bulk tag, list, and enrollment operations to Contacts
Operators select lead rows and apply reviewed bulk actions against the linked canonical contacts: add/remove tags, suppress from campaign email, or stage enrollment into a draft campaign, with per-record results and full receipts. Saved-list membership stays on card:campaign-saved-audiences, which owns those tables. Implementation steps: 1. Extend the existing Leads table selection (the only multi-select contact surface) with a bulk bar; leads without a linked canonical contact are named and skipped, never guessed. 2. Implement tenant-scoped bulk domain services for validated set-semantics tag mutation, canonical suppression, and campaign enrollment staging through the shared member-staging service; each returns per-record applied/skipped/failed outcomes and caps oversized selections instead of silently truncating. 3. Require an exact confirmation showing the affected count and action before any write; writes reuse canonical contact IDs, idempotency keys and audit receipts, one summary receipt per run. 4. Surface partial failures with per-record reasons and safe retry that never duplicates an already applied change.
Enforce Feature Board dependency integrity
Make the managed Feature Board safe for lower-context workers by validating dependency direction, delivery-circuit ordering, roll-up ownership, milestone notes, and documentation references before a card can be claimed.
Reconcile retained admin routes with their canonical owners
The existing Modernize and canonically integrate every additional admin tool card combines several independently reviewable outcomes. This slice owns only the acceptance below.
Fix shared Kanban spacing and unwanted scroll movement
Fix shared Kanban spacing and unwanted scroll movement. Treat the reported UX regression as urgent shared product work.
Discover and activate admin tools across pages within a bounded AI run
Let the command agent discover any registered authorized module and activate its schemas without being trapped in the initial page tool pack.
Harden recent plugins and deliver authenticated ChatGPT Site Studio control
Implement John's approved September 19 launch-readiness plan: repair audited Form Builder, Site Studio defaults and neutral starter defects; unify existing styling; provide full scoped editor MCP control with OAuth delegation and truthful authorization receipts. Preserve unfinished work and keep deployment separate.
Document workspace setup, permissions and operational recovery
The existing Write the 49-page documentation spine in link-dependency order card combines several independently reviewable outcomes. This slice owns only the acceptance below.
Expand small-business industries and Chicago SEO
Implement the approved ten-industry, twenty-recipe expansion and Chicago/suburbs hub, using the founder-confirmed Ferris headquarters address. Continue from the verified public-platform follow-up without merging or deploying it.
Repair fresh-fork release checks and polish credential-free entry journeys
John requests a further professional-quality implementation pass. Repair confirmed PR116 CI failures, diagnose the neutral browser 500, and improve first-run error handling and verification without altering submitted work.
Connect the command palette to real Revenue OS actions
Make search and commands navigate records, create tasks/opportunities, compose messages, open setup actions, and invoke safe AI reads.
Require real agent-loop regressions in CI
Require real agent-loop regressions in CI
Verify north star Phase B through a complete business outcome
Existing shipped component cards do not establish the complete phase outcome. This card collects missing end-to-end proof without rebuilding those primitives.
Connect login and recovery labels to their inputs
Fix the visible but unassociated labels found during the founder-authorized production release smoke check. Preserve all authentication and reset behavior.
Enforce bounded AI context and grounding rules
Build prompts from relevant live records, approved templates, business rules, and cited documents rather than uncontrolled database dumps.
Ship the full product neutral by default with an editable connected homepage
Implement John's approved plan: preserve the full repository and opt-in agency installation; default new forks to an editable public Command Center homepage, isolate disabled agency routes/assets, connect published forms through existing intake, and fix launch candidate CI. Local implementation and controlled proof are separate from hosted release verification.
Polish industry and Chicago pages for release
Founder-requested follow-up: make the existing industry and Chicago pages useful, elegant, conversion-ready and technically sound for SEO. Preserve the submitted expansion and prepare a separate verified handoff.
Turn the roofing ingestion path into a configurable playbook
Replace the vertical-specific inbound capture function with one generic qualification path that takes an industry playbook as data, so roofing becomes one configuration entry instead of an exported code path that every future installation inherits.
Plugin documentation contract and Radar reconciliation
Keep the flagship plugin buildable on current main and make every plugin understandable, reproducible and supportable.
Verify settled plugin toggles persist across demo reloads
Require real agent-loop regressions in CI
Guide connected installation and repair missing bootstrap owner membership
Guide connected installation and repair missing bootstrap owner membership
Reconcile booking activation and health truth
Make public booking, Calendly attribution, tenant configuration, Setup Center, and admin guidance agree on one optional activation model with truthful behavioral health and a complete manual fallback.
Repair copy and formatting drift found by integration CI
Require real agent-loop regressions in CI
Reconcile the reusable business-plugin baseline before Workshelter adoption
Establish one verified integration baseline containing the completed plugin, branding and five-business demo work before another agent expands Campaigns or Support. Implementation steps: 1. Read root/app contracts and inspect worktrees without changing their working files. 2. Create an isolated integration branch from the current integration target and reconcile completed commits a743947, e150dd2, 72f2102, 2d8d7c3 and c7da31b, including required ancestors; skip patches already present. Preserve unrelated in-progress branches. 3. Resolve conflicts using current tenancy/action-executor contracts, not by choosing an entire side. Verify extension generated output matches manifests. 4. Record the exact resulting commit and available canonical services in card evidence; descendants start from that commit.
Give first plugin evaluation reliable headroom under the cold-start budget
The accepted isolate host measured 48.0 ms on CI34007680976, but the unchanged host failed its first-evaluation 50 ms budget at 50.375514 ms on CI34008739864 job101420679988. This is an unresolved performance headroom issue, not a workflow-schema regression. Preserve the failed receipt and establish a reproducible performance fix.
Opportunity Radar: useful outreach with approval and relationship checks
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Opportunity Radar: business opportunity development and daily selection
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Polish Tasks and Pipeline desktop controls
Founder screenshot shows full-width stacked desktop filters and sparse rows. Fix responsive layout in the existing page and shared styles, preserving all mutation and authorization behavior.
Opportunity Radar: Today and intelligence packet workspace
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Explain the open-source AI Command Center through clear guides and product visuals
Rewrite the public documentation entry journey around ownership, connected business context, AI actions and extensibility, with real fictional-demo screenshots and concrete examples.
Restore tenant-scoped conversation and message upserts
Restore approved email sends and conversation/message synchronization without weakening tenant identity or replay protection.
Make developer onboarding and backlog pickup work from a fresh checkout
Developers can establish readiness, pick a bounded ticket and submit verifiable work without undocumented local state.
Connect learning, shared knowledge, plugins and first-use outcomes
Implement the founder-approved researched plan for a useful out-of-the-box learning loop. Preserve existing source-authority review and all unrelated retained work.
Keep invoice demo usable when an operation result lacks currency
The fictional Northline invoicing route throws RangeError/TypeError in money(result.amountRemaining,result.currency) when a demo operation result contains invoiceId without currency.
Opportunity Radar: reusable profile and governed AI setup
User-authorized Opportunity Radar program: Discover → Understand → Develop → Review → Act → Measure → Learn. Optimize verified earned business recognition and useful relationships, not output volume.
Complete the proposal lifecycle and version rules
Control draft, sent, viewed, accepted, declined, expired, and superseded states with linked contact, company, and opportunity.
Centralize themed controls and repair workspace polish gaps
The live Studio-theme Setup Center readiness card uses hardcoded white text on the pale sidebar-toned surface. Reuse the matching surface foreground tokens and verify all supported themes.
Wire docs into search, sitemap, navigation and a generated llms index
Documentation track, step 2 of 4, still with only three pages of prose so the wiring is proven before the content exists. Search costs almost nothing: one deploy-time index already serves the whole site and the client filters locally, so adding docs is a loop plus two typed entries, and because those are a keyed record and a typed array, forgetting either breaks the typecheck. Two corrections to earlier assumptions are load-bearing here. src/content/navigation.ts is dead and imported by nothing, so links go in the header and footer components directly. And a static file in public shadows any route handler at the same path, so the machine-readable index must be a build script with a check mode rather than a route.
Generate workflow policies and invalidate stale plugin approvals
Derive enforced policy grants for the three isolated business workflows, preserving service identity and retry behavior. A bounded child of the full manifest generator; not general SDK completion.
Introduce Coworkers as first-class runtime identities with manifests
Introduce Coworkers as first-class configuration objects over the shared Accelerate runtime. A Coworker is not a separate LLM instance or chatbot — it is an identity with a role, objectives, skills, tools, triggers, permissions, autonomy policies, memory scope, allowed entities, budgets, schedules, and escalation rules. Coworkers are described through machine-readable manifests (YAML/JSON) that are explicit, inspectable, portable, and eventually shareable. The Sales Coworker is the reference implementation that proves the entire architecture end-to-end.
Add Agent Activity surfaces on every major business record
Every major business record (contact, company, opportunity, proposal, invoice) should have a consistent AI/Agent Activity surface that makes autonomous work understandable to a normal operator. This is not a raw audit-log dump — it is a readable timeline showing what the agent looked at, what it concluded, why, what it did, and what happens next. The Command Center evolves into the operator interface into the business runtime, with sections for 'Needs you' (only things requiring human judgment), 'Coworkers' (status of each worker), 'What changed' (business-level intelligence), and 'Activity' (unified human + agent timeline).
Generate plugin tool grants from the runtime registration
Unify tool names, input validators and safety metadata for isolated workflows and existing Stripe adapters. A bounded child of the full manifest generator; not general SDK completion.
Opportunity Radar: enforced low-cost models and provider options
User explicitly requires inexpensive operation, prefers OpenRouter and wants multiple options. Cost must be enforced before requests, not only displayed in settings.
Route every AI job through an audited model registry
Choose OpenRouter models by typed workload requirements instead of scattered IDs, with current capability and cost metadata, explicit activation, eval gates, and rollback.
Polish Command Center PWA state and dialog UX
Harden the submitted Command Center PWA around fresh offline state, service-worker updates and accessible install/draft dialogs.
Integrate shared UI polish and repair release checks
Founder asked to do what is best after the two completed UI handoffs. Consolidate PR125 and PR126, repair their concrete CI failures, verify once and merge through required checks.
Got an idea?
Suggest a feature. A founder reviews every submission before it appears here.