Architecture and naming

Release 0.3.0-draft.1 · Development standards

Woblar is the master brand. Services, tools and agents should help people find their way without making the organisation look like a collection of unrelated companies.

One master brand, clear descriptors

Woblar
├── Services
│   ├── AI Readiness Roadmap
│   ├── AI Workflow Starter
│   ├── Workflow Care
│   └── Search visibility capability
├── Tools / capabilities
│   ├── Business Pulse Check
│   └── Decision Engine — confirm public context before reuse
├── Agents — role labels under Woblar
└── Campaigns — temporary messages within this identity

Preserve these service names while they remain current; the diagram describes communication architecture, not legal entities or technical ownership. A campaign may have a headline, but does not acquire an independent logo or palette.

Use “Woblar [descriptive capability]” on first mention where context needs it. Use “Woblar SEO agent” for a role, followed by what it can help with and who reviews its output. Do not invent human job biographies. Existing tool names need their current product owner and flow checked before inclusion in a new offer.

Partner relationships

Separate Woblar and partner artwork with whitespace or a thin neutral divider. Use supplied artwork at comparable optical prominence, never by equal canvas width alone. Maintain each logo's required clear space. Use at least H between visible marks, where H is Woblar’s visible wordmark height, and increase the gap whenever the partner’s required exclusion zone is larger. With a divider, preserve each mark’s own clear space on its side. Woblar leads on Woblar-owned material; client-led work follows the agreed commissioning relationship. Never infer rank from file order. Put an accurate relationship label above or below: “Prepared by Woblar for [client]” or “Created with [partner]” only when true and authorised. A technology vendor's logo does not prove endorsement, certification or a partnership.

In URLs and filenames use readable lowercase hyphenated words. In visible copy use sentence case, preserving proper names. Do not silently rename live URLs to match this draft.

See the co-branding specimen.

Operating rules

ARCH-001 — Keep the master brand clear

• Do: Present services, tools and agents under Woblar with descriptive roles.
• When: Naming and new offers
• Variation: A temporary campaign title or descriptive capability label.
• Avoid: New sub-brand logos, palettes or fictional staff identities.
• Check: Identify the master brand without explanation.

ARCH-002 — Preserve current offer names

• Do: Use AI Readiness Roadmap, AI Workflow Starter and Workflow Care accurately.
• When: Service descriptions and sales material
• Variation: Short contextual references after the full first mention.
• Avoid: Inventing prices, inclusions or guarantees from the names.
• Check: Compare names and scope with the current offer source.

ARCH-003 — Describe real relationships

• Do: Use partner artwork and relationship wording only with permission and evidence.
• When: Co-branding and client work
• Variation: Optical balancing within both brands’ clear-space requirements.
• Avoid: Implied endorsement or a merged unofficial logo.
• Check: Check permissions, relationship text and proof at intended size.

Handbook contents · AI rules