# Veriom content and social playbook

## Objective

Build authority around current, trustworthy system understanding. Every piece should help someone understand a system, a change, or a decision before it asks them to evaluate Veriom.

Security is the first commercial wedge, not the master story. The same underlying model should remain useful to engineering leaders, architects, platform teams, security leaders, AI-system builders, and non-technical decision makers.

Primary paths are to inspect the demo, read the method, understand the product boundaries, and request an evaluation.

## Editorial territories

1. **System understanding:** what exists, how it fits together, what was intended, and what changed.
2. **Truth and evidence:** provenance, freshness, confidence, contradictions, coverage, and decision memory.
3. **Change and engineering:** architecture drift, code-to-runtime identity, ownership, onboarding, and safe change.
4. **Humans and AI agents:** bounded context, tools, authority, cost, replayability, and trustworthy action.
5. **Security consequence:** structural weakness, reachability, trust boundaries, blast radius, and reviewable remediation.
6. **Building with care:** reliability, benchmarks, release gates, counter-evidence, and durable product craft.

## Message order

Use the same hierarchy in articles, pages, demos, and social posts:

1. Universal truth or practical tension.
2. Plain-language explanation of what becomes understandable.
3. Technical proof: source, scope, evidence, freshness, and limits.
4. Consequence for the reader's next decision.

Do not require the reader to learn a category name before understanding the problem.

## Voice

Clear, not clever. Certain, not aggressive. Human, not “cyber.” Calm, not fear-based.

- Distinguish current capability, plan, hypothesis, and belief.
- Never invent customer quotes, performance, accuracy, adoption, ROI, certifications, or availability.
- Pair material claims with dated evidence and keep counter-evidence visible.
- Explain what is unknown or stale.
- Use sentence case, proper punctuation, and direct language.
- Do not publish “AI-powered,” “next-generation,” “revolutionary,” “single pane of glass,” or generic fear-based security copy.
- The tagline remains unlocked; no campaign phrase becomes a permanent signature by repetition.

## Repurposing contract

Each substantial article can produce a LinkedIn point of view, an educational document, a short technical thread, several observations, a diagram grounded in real product behavior, and an FAQ answer. Repurposing must preserve the evidence and qualification of the original claim.

Keep overt promotional content below ten percent. Product updates should explain the prior understanding gap, what can be understood now, the evidence behind it, and what becomes possible.

## Visual contract

- Space White and Ink are the default environment.
- Use one functional accent per composition: Yellow for action/illumination or Teal for knowing/information.
- Use Instrument Sans. Reserve IBM Plex Mono for genuine evidence.
- No decorative gradients, neon grids, glowing networks, fear imagery, locks, shields, or dark-mode-as-identity.
- Motion must explain discovery, connection, resolution, drift, or cause and effect.
- Never place the compact mark beside the wordmark.

## Publishing checklist

- Does the opening name a real outcome, tension, or question?
- Is there one useful framework, example, or decision rule?
- Are source, date, scope, and uncertainty visible where needed?
- Can someone outside cybersecurity understand it?
- Does the visual improve understanding without relying on motion?
- Does the call to action match the reader's stage?
- Would the piece still feel like Veriom if the security context disappeared?

Last updated: 5 September 2026.