Documentation
Bobby Brand pilot documentation
A truthful description of the product, the governed workflow and what is and is not operational today.
Current pilot scope
What Bobby Brand is
Bobby Brand is being built as an AI-assisted brand-book generator, brand optimizer, brand manager and brand-governance platform. Its intended product workflow helps individuals, companies, products and teams create, organise, approve, maintain, distribute and monitor complete brand systems.
Bobby Brand is not a logo generator. A logo is one component of a system that also covers strategy, naming, tone of voice, colour, typography, imagery, social, email, covers, product UI and the governance around all of it.
The two creation pathways
Mode A — Create a New Brand: complete brand discovery, company and product information, preferred and prohibited styles, then five genuinely distinct brand directions to compare, comment on and choose from. The selected direction is refined into the complete brand book and initial asset package.
Mode B — Upgrade My Existing Brand: you provide your website URL, existing logo files where available, social profiles, company information, existing documents, known fonts and colours, what must be preserved, what may change, and your desired modernisation level. Bobby Brand then proposes five evolutionary complete directions plus two revolutionary logo concepts. A selected revolutionary concept is expanded into a complete direction before final refinement — a logo alone is never presented as a complete brand book.
Bobby Brand does not promise to reproduce an existing logo exactly from a website image, does not silently redraw an existing logo and label it the original, and does not provide trademark clearance.
The governed workflow
Planned customer flow: discovery, analysis, direction generation, owner review, refinement of the selected direction, brand-book generation, asset generation and verification.
Review supports approve, reject, request refinement, compare, comment, rank and archive. Rejected directions are preserved as historical evidence, never silently deleted.
Project status is shown from real recorded workflow states and completed milestones. Bobby Brand does not display invented progress percentages.
Brand-book versions
Every brand book carries a draft version and an approved version, with author, reviewer, approver, effective date, change summary, source files, checksums, usage rights, audit history, superseded versions, rollback and review date.
Approved versions are immutable and reproducible. Changes are proposed, reviewed, approved and only then published. Generating files never means a brand book is complete.
Assets and exports
The approved vector source is the source of truth; PNG and variant exports are derived from it with recorded lineage, checksums, version identity and approval state.
Planned packages include a complete brand kit, logo, icon, app, email, social, cover and developer token packages. Every export identifies its brand, brand-book version, source asset, format, dimensions, colour mode, background, creation time, generation method, approval state and checksum.
Customer brand assets are private by default and served only through authorised or signed delivery unless a workspace explicitly approves public distribution.
Planned API
Status: planned, not operational. The API will expose workspace-scoped access to brands, brand books, versions, sections, review and approval, publication, rollback, assets, exports, design tokens, tone-of-voice rules, approved terminology, audits and webhooks.
Granular scopes are planned, including brands, brandbooks (read, write, review, approve, publish), assets, exports, audits, autopilot, team, billing and integrations. A general write scope never implies approval, publication or paid credit spending.
Planned MCP
Status: planned, not operational. A remote MCP endpoint is planned so AI tools can retrieve approved brand context and perform authorised operations under explicit workspace consent and scoped grants, using standards-based OAuth.
The API and MCP will share the same authorisation authority and brand services. No parallel security system will be built.
Planned integrations
Status: none configured, none connected. A provider-neutral integration framework is planned with platform-managed, workspace-managed and hybrid credential modes.
Planned capability slots include Firecrawl for authorised crawling, Google split by capability (Search Console, PageSpeed Insights, Fonts metadata, OAuth), Cloudflare split by product (Browser Rendering, Images, R2) and a minimal core public-site reader.
Website analysis is available only after ownership attestation and domain verification, within strict page, depth, size, timeout and rate limits, with SSRF protections and recorded provenance. Authenticated-site crawling is out of scope.
Autopilot boundaries
Autopilot means governed monitoring and proposed maintenance: remembering the approved rules, making them retrievable by AI tools, detecting drift and preparing proposals.
Autopilot must never silently replace an approved logo, publish a brand version, change public assets, update websites, send messages, spend credits beyond configured limits or override an owner rejection.
Current pilot limitations
The platform foundation is active for P2A verification: authentication, profiles, role tables, workspace authority foundations, audit/security records, feature flags, /account, /console and /admin authorization boundaries exist.
Customer brand generation, checkout, billing, AI generation, integrations, crawling, API, MCP, file uploads and Autopilot are not operational.
Bobby Brand R1 version 1.0.0 is the canonical approved brand system. No Platform Owner database role has been provisioned, and no bootstrap authorization material exists.