Skip to content
Portfolio/Capabilities

CAPABILITY 14 / 30

Audience, tone, and channel

Pick who you are writing to, in what tone, on what channel, and see the rules that decide the words.

IN PRODUCTION

This runs in client systems today. The sample below was regenerated for a fictional company.

House style is not one rule set, it is layers. Base rules always apply, the audience adds some, the channel adds limits, the tone adds a register, and a few combinations have their own rules. This shows the layers resolving, including where they disagree and which one wins.

TRY IT / RUNS IN YOUR BROWSER

Use it here.

The mechanism is the production one. The company, the catalogue, and every figure are fictional.

Loading the rule matrix.

THE OUTPUT / GENERATED FOR APEX INSTRUMENTS

What comes out.

JSON
The Apex message rule matrixData · Five audiences, four tones, six channels, five house rules, and seven combination rule sets, with the precedence order and its reasoning published alongside. Rules that carry a key take part in resolution, so a length limit, an approval step, or a shorthand allowance can be overridden by a narrower layer. Five conflicts are declared with the rule that wins, the rules that lose, the cells they fire in, and a demonstration cell. Thirty example lines carry one underlying message written for every audience and channel pair.Open the file ↗

THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE

How it works.

What a skill is
  1. 01Start from the house

    Base rules apply to everything, whoever is reading.

  2. 02Add the audience

    Who is reading changes what may be assumed and what has to be spelled out.

  3. 03Add the channel

    Each channel brings a length limit, required elements, and things it forbids.

  4. 04Add the tone

    Register changes the words, not the facts.

  5. 05Resolve the conflict

    When two layers disagree, the stricter one wins and the picker says so.

WHAT IT READS

  • The base house rules
  • Rules per audience, per channel, and per tone
  • Combination rules for specific pairs
  • An example line for every cell

WHAT IT CHECKS BEFORE IT SHIPS

  • Every rule is tagged with the layer it came from
  • A conflict is shown and resolved, never hidden
  • Every combination has a worked example
  • Length limits are enforced, not suggested
In production: an audience, tone, and channel rule matrix in both company systems.

The mechanism runs inside client systems. Everything on this page was regenerated for Apex Instruments, a company that does not exist. Client names, source files, and internal wording stay private.

What it producesWhat is being built next