Runtime workflows versus workflow kits
The runtime suite and the kit catalog solve different problems. Do not confuse the two:- Runtime workflows (this page) are live, executable workflows that the Agent Lab runtime orchestrates. They run on triggers such as cron schedules and webhooks, and they operate the agency itself.
- Workflow kits (the catalog) are packaged, versioned deliverables described by a
kit/1.0manifest. Operators and buyers pick them up, run them, and adapt them.
MKT-06, the same workflow the Founder Signal System packages for clients.
Automatic seeding
The runtime seeds the canonical 10 into any workspace that has no workflows yet. The first time the workspace’s workflow list loads, Agent Lab inserts all 10 workflows withactive status, along with their ordered steps. You do not create them by hand.
Each workflow is a sequence of steps. A step is one of two types:
agent: an autonomous step a swarm agent executes without intervention.guardrail: a checkpoint step. The workflow does not proceed past a guardrail until the check passes. Some guardrails require an operator to approve in person.
The canonical 10
Reference these workflows by theirXXX-NN ID in commit messages, change control entries, and cross-workflow handoffs, the same convention the kit catalog uses.
SAL-01: Inbound Lead Enrichment & Verification
Enriches founder leads from Bootstrapper events and qualifies them for CRM triage. The workflow parses the inbound payload for name, company domain, and event notes, then enriches firmographics through Hunter.io and Clearbit. A guardrail step checks the lead against ICP criteria. The workflow upserts qualified leads into HubSpot and logs them in the M365 master lead sheet.FIN-01: M365 Daily Financial Reconciliation
Reconciles Stripe and Mercury transactions against the M365 Finance Control sheet every day at 18:00 UTC. The workflow fetches all net settlements, fees, and payouts for the trailing 24 hours, matches transaction IDs against operating expense budget categories, and generates a daily financial summary. It alerts when a variance exceeds $50.DEV-01: Automated CI/CD Test & Refactor Suite
Runs on every GitHub push and pull request. The workflow compiles TypeScript, runs the Vitest suites, audits the AST for circular dependencies and type leaks, and scans dependencies for vulnerabilities. It publishes a CI/CD health report with test coverage metrics and build certification status to Slack and GitHub.MKT-06: Founder Signal Content Dissemination
Runs Monday, Wednesday, and Friday at 09:00. The workflow extracts high-impact takeaways from recent operational briefs and case studies, then drafts 5 LinkedIn and X posts in the URC brand voice. A human-in-the-loop guardrail pauses the run for operator review of hooks, tone, and asset links. The workflow stages approved drafts in the content queue with scheduled publish dates.CRM-01: HubSpot Deal Stage & Pipeline Sync
Queries all active HubSpot pipeline deals hourly, including stages, amounts, and last activity dates. The workflow scores deal health, flags deals with no touchpoints in more than 5 days as stalled, and creates follow-up tasks directly in the HubSpot pipeline.MKT-09: Bootstrapper Founder Roundtable Intake
Ingests founder event registrations from Luma or Meetup webhooks. The workflow parses the attendee’s founder stage, revenue band, and primary bottleneck. It then computes a baseline 4-Engine diagnostic scorecard across the Profit, People, Value, and Financial engines, and sends a personalized pre-session brief with relevant case study references.OPS-01: Compliance Audit & Change Ledger Verification
Scans the repository against the Canonical Registry every day at midnight. The workflow runs the change control scanner across the operational catalog and confirms that every modified kit carries an activeCC-* entry in the change control register. It saves a timestamped, signed audit log in the compliance audits directory.
FUL-01: Client Onboarding & Journey Kit Provisioning
Runs manually or on a contract-signed event. The workflow initializes an isolated client workspace partition with the client’s brand tokens and credentials, then deploys the standard MKT, SAL, and OPS Journey Kits into the client directory. It verifies API connectivity with a self-test and generates the client’s Owner’s Manual quickstart as a welcome packet.Purchase ingestion endpoint
FUL-01 also accepts customer purchase events directly through the runtime API. Send a purchase event toPOST /fulfillment/onboarding/ingest when a payment lands from Stripe, PayPal, Gumroad, or a manual sale. The endpoint provisions entitlements and generates an onboarding and retention blueprint in the Results Vault. It tags the contact in HubSpot with customer_onboarded, the tier, and the source. It then schedules a 3-touch post-purchase retention sequence with milestones on days 1, 3, and 7.
The request body requires customerName, customerEmail, and productPurchased. If any of the three is missing, the endpoint returns 400.
currency to USD, source to stripe, and tier to standard. source accepts stripe, paypal, gumroad, or manual. tier accepts standard, pro, sprint, or custom. On success the endpoint returns 200 with an onboardingId, the transaction ID, a SHA-256 checksum of the generated blueprint, and status provisioned_and_enrolled. Every ingestion also writes an audit log entry with policy check results.