AutoBlocks uses a deliberate language hierarchy so marketing, product UI, and internal code stay aligned. When you see a term in the app, this page explains what it means.
Brand constants: apps/product-web/src/lib/brand.ts, apps/marketing-web/src/lib/brand.ts. Governance: repo root AGENTS.md.
Brand hierarchy
| Layer | Term | Use when |
|---|
| Consumer brand | AutoBlocks / AutoBlocks.ai | Marketing, legal, help chat |
| Tagline | Calm automation for everyday life | Hero copy, nav subtitle |
| Automation unit | AutoBlock | Product UI, user docs |
| Plural | AutoBlocks | Dashboard nav label |
| Category | Automations | Supporting category language |
| Internal / system | Routine, Workflow | Code, API paths, database — not primary user-facing |
Domains and surfaces
| Name | URL | Role |
|---|
| Marketing site | autoblocks.pro | Learn, pricing, docs, help chat |
| Product app | autoblocks.run | Signup, dashboard, wizard, billing |
| API | api.autoblocks.run | Backend — sessions, runs, Stripe |
| Worker | Internal | Schedules + pending execution |
Core product terms
| Term | Definition |
|---|
| AutoBlock | A single automation you create — one trigger, one or more steps, optional rules |
| Trigger | What starts a run: manual, schedule, or inbound webhook |
| Step | An action after trigger: notification, outbound webhook, or storage |
| Rule / Rule block | Optional condition (equals, contains, greater_than) gating flow |
| Template | Pre-built AutoBlock pattern from the catalog |
| Wizard | Guided creation flow at /routines/new |
| Run / execution | One invocation of an AutoBlock from trigger to completion |
| Activity | Execution history dashboard at /activity |
| Tenant / workspace | Your isolated account space (one per user in Phase 1) |
| Trial | 14-day evaluation period with lower limits |
| Entitlement | Plan limit check (routines, executions, webhooks, schedules) |
Trigger and step vocabulary
| Code kind | User-facing label |
|---|
manual | Run on demand |
schedule | Recurring schedule |
inbound_webhook | Inbound webhook |
notification | Send notification |
outbound_webhook | POST to external URL (step) |
storage | Save run output / log |
Source: packages/workflow-domain/src/types.ts.
AI terms
| Term | Meaning |
|---|
| AI assist | In-product draft/refine/repair/explain — auth required |
| Help chat | Public marketing widget — corpus-grounded, no tenant data |
| Bounded AI | Output limited to Phase 1 trigger/step/rule constructs |
| RoutineDraft | JSON shape AI returns before you save |
Billing terms
| Term | Meaning |
|---|
| Starter | Entry paid plan — 5 AutoBlocks, 500 runs/mo |
| Plus | Higher tier — 25 AutoBlocks, 5000 runs/mo |
| Checkout | Stripe-hosted payment flow from /billing |
| Execution limit | Monthly cap on completed runs |
| 402 | HTTP status when a plan limit is exceeded |
Phase 1 exclusions (say this clearly)
| Term | Phase 1 status |
|---|
| Custom scripting | Not supported |
| Integration marketplace | Not supported |
| Book a call | Removed — /book → /docs |
| Team RBAC | Not supported |
| White-label | Not supported |
| Chat-first product | Not supported — AI assists setup only |
Naming in the monorepo (for reference)
| User sees | Code path may say |
|---|
| AutoBlock | routine, routines |
| Automations | workflow-domain types |
| AutoBlocks.ai | @routines/* package scope |
Package scope @routines is historical internal naming — consumer surfaces always say AutoBlocks.
Abbreviations
| Abbr | Expansion |
|---|
| API | Application programming interface — api.autoblocks.run |
| CORS | Cross-origin rules — API allows .pro and .run |
| cron | Schedule expression for recurring triggers |
| SSOT | Single source of truth — e.g. route tables in doc 03 |
| UI | User interface — product-web components |
Brand voice (quick guide)
| Do | Don't |
|---|
| "Create an AutoBlock" | "Build a workflow node graph" |
| "Run on demand" | "Fire the trigger node" |
| "Calm automation" | "AI magic autopilot" |
| "Review before save" | "AI will handle it" |
Related reading