Skip to main content

Marketing Documentation — Governance & Guardrails

Purpose of This Folder​

This folder contains market-facing doctrine, not system truth.

Its role is to define how Evalium is framed, positioned, and explained to the outside world — without weakening, contradicting, or reshaping the architectural and product invariants defined elsewhere in the repository.

These documents exist to support:

  • strategic clarity
  • consistent positioning
  • disciplined decision-making

They do not define how the system works.

What Lives Here​

Documents in this folder may describe:

  • Why Evalium exists (founder intent and purpose)
  • Which markets we deliberately target — and which we avoid
  • How Evalium is categorised (e.g. Assurance Infrastructure)
  • How we explain Evalium to investors, partners, and advisors
  • How we articulate value without exposing implementation detail

Language in this folder may be:

  • conceptual
  • strategic
  • declarative

This is intentional.

What Does Not Live Here​

This folder must never be used for:

  • architectural definitions
  • system invariants
  • data model or schema truth
  • API behaviour
  • UI copy or microcopy
  • implementation mechanics

If a statement here conflicts with:

  • docs/architecture/*
  • docs/product/*
  • docs/security/*

then this folder is wrong, not the system.

Relationship to Language & Tone Guidelines​

The documents in this folder operate at a different communication tier than user-facing copy.

  • UI, emails, and normal use are governed by language-and-tone-guidelines.md
  • Explain views and audit contexts prioritise outcome-focused precision
  • Marketing & strategy documents prioritise conceptual clarity and category definition

This means:

  • internal terms may appear here when defining the category or moat
  • stronger declarative language is acceptable
  • UI-level aliasing is not required

However, the spirit of Evalium’s language still applies:

  • calm
  • confident
  • non-alarmist
  • outcome-focused

Authority & Precedence​

When making decisions:

  1. Architecture and invariants always win
  2. Product doctrine and domain models are next
  3. Market framing must align with both

Marketing documents may simplify reality. They must never contradict it.

How These Docs Should Be Used​

Use this folder to:

  • sanity-check new features against target markets
  • explain Evalium succinctly to external stakeholders
  • prevent category and pricing drift
  • maintain strategic consistency over time

Do not use this folder to justify:

  • weakening invariants
  • chasing low-liability markets
  • introducing per-user or per-attempt pricing
  • reframing Evalium as an LMS, AMS, or generic workflow tool

pre-launch Framing Workspace​

For pre-launch execution work, use:

  • docs/marketing/pre-launch/README.md
  • docs/marketing/pre-launch/messaging-canonical.md
  • docs/marketing/pre-launch/proof-asset-pipeline.md
  • docs/marketing/pre-launch/side-support-operating-rhythm.md
  • docs/marketing/pre-launch/investor-readiness-checklist.md

This subfolder is the canonical operating area for:

  • messaging consistency
  • proof-asset production
  • founder + side-support collaboration cadence

If pre-launch docs drift from strategy docs in this folder, update the pre-launch docs first and escalate unresolved contradictions.

Guiding Principle​

Evalium is built for truth under scrutiny.

Marketing exists to explain that truth — not to dilute it.