Limen Brand Doctrine¶
Status: Locked.
Version: 0.2
Date: 2026-08-08
This document locks the brand identity for the Limen platform. It is the reference for all visual, verbal, and product decisions.
1. Brand summary¶
| Element | Definition |
|---|---|
| Company | Fordsworth |
| Platform | Limen |
| Tagline | Risk is just data. Run it on Limen. |
| Archetype | The quiet authority — precise, inevitable, calm. |
| Domain | Threshold, crossing, liminal space. |
| Emotional promise | You stop fighting legacy and start operating from a new foundation. |
| Functional promise | Any risk, any line, at speed, with full auditability. |
Limen is not a consumer app. It is infrastructure. It must feel serious enough for a boardroom, precise enough for an actuary, and modern enough for a software engineer.
2. The name¶
Limen is Latin for threshold. It is the boundary between one state and another. In the platform, it is the boundary between legacy insurance operations and modern, data-driven risk management.
The name is:
- Short: Two syllables, five letters.
- Unique: Not used by any major insurance or software vendor.
- Meaningful: It carries the idea of transformation without being aggressive.
- Global: Pronounceable across markets.
The name is locked. It is not AIR-OS, Fordsworth PAS, or any other variant in external communication.
3. The tagline¶
Primary tagline¶
Risk is just data. Run it on Limen.
This is the core idea. It is the one-line truth of the platform. It removes the artificial complexity of legacy insurance and positions Limen as a data infrastructure play.
Business audience tagline¶
Run insurance like a modern business.
For CEOs, COOs, and board audiences, the technical tagline can feel reductive. "Risk is just data" is true to us but may sound like we are trivializing the human stakes of insurance. The business tagline focuses on the outcome: a modern, fast, profitable operation that serves people better.
Supporting messages¶
Use these as secondary lines depending on the audience:
- For product leaders: Launch products in days, not months.
- For operations: No more month-end paralysis.
- For finance: Every transaction is traceable.
- For actuaries: Own the rules.
- For customers and brokers: Built for the people who depend on it.
Tagline rules¶
- The primary tagline is the default for the website, API docs, and technical decks.
- The business tagline is the lead message for investor decks, board presentations, and sales conversations.
- The two taglines are not competing. They are translations of the same idea for different audiences.
- Never use both in the same headline. Pick the audience and commit.
4. The logo: current evaluation¶
The current logo is a doorway frame with a serif capital I inside, rendered in gold. The concept is correct: a threshold, a figure at the crossing, a single strong accent color.
What works¶
- The doorway shape directly references the threshold concept.
- The single gold color is distinctive and ownable.
- The geometric simplicity scales well in most contexts.
- It avoids the clichés of shields, umbrellas, and checkmarks.
What needs testing¶
- Distinctiveness: At small sizes (favicon, app icon), the doorway and I can read as an abstract rectangle or a stylized building. It is not immediately recognizable as a brand mark.
- Differentiation: The threshold/doorway idea is not unique in the abstract. We need to own it through consistent use, not rely on the shape alone.
- Emotional charge: The mark is calm, but it is also slightly neutral. It does not carry the sense of precision and inevitability we want.
- The serif I: It is a clever reference to the first letter, but it may feel too academic or Roman.
Logo criteria (pass/fail)¶
Before the logo is final, it must pass these tests:
- Scales to 16px: It must be recognizable at favicon size.
- Works in one color: It must read in gold, black, and white without losing meaning.
- Distinct from competition: A side-by-side with major insurance/insurtech logos must show clear difference.
- Carries the threshold idea: A viewer who knows the name should understand the doorway concept.
- Feels engineered: It should feel like software, not a bank or a consultancy.
Recommendation¶
Keep the logo as the working mark for the next 90 days. Treat it as a candidate, not a final identity. Commission three alternatives: one that doubles down on the doorway, one that abstracts the threshold into a line or plane, and one that uses a typographic mark. Test against the criteria above before any investor deck is printed.
In the meantime, lock the usage rules below. The logo is only part of the brand. The color system, typography, voice, and product behavior do more work than the mark alone.
5. Color system¶
The palette is built on a warm-neutral grayscale with a single strong accent.
Primary colors¶
| Color | Usage | Token |
|---|---|---|
| Gold | Brand, primary actions, focus, key data | --gold |
| Ink | Primary backgrounds, body text | --background / --foreground |
| Charcoal | Surfaces, cards, secondary backgrounds | --card |
| Bone | Inverted text, light-mode surfaces | --foreground / --background |
Functional colors¶
| Color | Usage | Token |
|---|---|---|
| Success | Positive states, active coverage | --success |
| Warning | Due, pending, attention | --warning |
| Destructive | Reversal, lapse, cancellation | --destructive |
Rules¶
- Gold is the single strong accent. Do not introduce a second brand color.
- Status colors are muted. They support the interface; they do not dominate it.
- The interface defaults to dark mode. Light mode is supported, but dark is the primary expression.
- Never use gradients for brand elements. Gold is flat, precise, metallic in concept only.
6. Typography¶
| Typeface | Role | Why |
|---|---|---|
| Manrope | Headlines, body, interface | Geometric, modern, measured. Neutral authority. |
| Geist Mono | Labels, references, data, timelines | Technical cadence, wide tracking, tabular numbers. |
Usage rules¶
- All-cause uppercase labels use mono, wide tracking (
0.12emminimum), and small size (11pxor12px). - Headlines are tight-tracking, medium weight, not heavy.
- Body text is relaxed but not loose (
leading-relaxed). - Numbers are tabular. Money, dates, references, and policy numbers must not jump when digits change.
- No decorative fonts. No script. No serif body text.
7. Voice and tone¶
Voice attributes¶
| Attribute | What it means | Example |
|---|---|---|
| Precise | Every word earns its place. | "Your policy is in force." Not "Your coverage is good to go!" |
| Calm | No urgency where none is needed. | "Premium due in 7 days." Not "Act now!" |
| Confident | We state facts without hedging. | "Ledger entries are immutable." Not "We believe in strong audit trails." |
| Transparent | Explain the reasoning. | "Premium increased 5% due to CPI escalation." |
| Engineered | Speak like software people. | "DMN version 4.2 applied." Not "Our system thought about it." |
Tone by channel¶
- Investor deck: Calm, inevitable, architecture-first. Avoid hyperbole.
- Product interface: Plain, explanatory, no marketing language.
- API documentation: Precise, technical, with examples.
- Sales material: Problem-led, outcome-focused.
- Internal communication: Direct, no corporate filler.
Words to avoid¶
- "Disrupt" and "disruptive" — we are not trying to be loud.
- "Seamless" — it means nothing. Say what is actually true.
- "AI-powered" — AI is a component, not the value proposition.
- "Next-gen" — vague. Use the specific advantage.
- "Revolutionary" — we let the architecture speak.
8. Product language¶
Use the same vocabulary across the platform, the API, the docs, and the pitch.
| Concept | Preferred term | Avoid |
|---|---|---|
| The legal agreement | Contract | Policy (when the domain is generic), "book" |
| A cover item within a contract | Component | Rider, benefit, coverage, add-on |
| A person or organization in a contract | Party | Customer, client, insured, broker as separate entities |
| The relationship role | Role | Type, category, function |
| A version of a contract | Version | Snapshot, revision, iteration |
| A financial movement | Entry | Transaction (transaction is fine for user-facing), line item |
| The financial record store | Fluid-GL | Ledger (generic), sub-ledger (external) |
| The decision model | DMN rule | Algorithm, formula, calculation script |
| The deployment unit | Cell | Tenant, region, pod |
9. The experience signature¶
Limen must feel like one product across every touchpoint. The signature moments are:
- The timeline as navigation. Time is not a filter. It is the organizing principle.
- The money trail. Every amount shows where it came from and where it went.
- The rule trace. Every calculation is explainable: DMN version, inputs, outputs.
- The threshold transition. State changes feel deliberate and clear, not abrupt.
These moments must be visible in the product, the demos, and the pitch.
10. Cleanup list¶
Before the brand is considered consistent, remove or fix:
- [x] The
generator: 'v0.app'metadata in the Next.js layout. - [x] The
"name": "my-project"inpackage.json. - [x] All remaining AIR-OS references in active documents (old documents moved to
docs/archive/). - [x] The inconsistent demo data: ZAR term life vs. USD "Passage Plan" in the same prototype.
- [x] The fictional "Limen Assurance Ltd." in the contract page.
- [ ] Any decorative UI that does not serve the four signature moments.
11. Decision¶
The brand direction is locked. The logo is a candidate requiring final testing. The color, typography, voice, and vocabulary are final. All future materials must use this doctrine as the reference.