ntwrk/Brand book v1.0 · 13 Oct 2026

System / Diagrams and illustration

Diagrams and illustration

NTWRK does not illustrate. It diagrams: a figure shows a structure, a sequence or a comparison that the words describe. Every figure follows the same seven rules.

Approved: codifies liveOwner: Wes FischerUpdated 13 Oct 2026

01Rules

  1. HTML text, always. No words inside SVG <text> or images. SVG draws connectors only, marked aria-hidden.
  2. 14px minimum on a phone, 13px on desktop, measured. Below that, re-lay out the figure (stack, rail, 2×2); never scale it down.
  3. Evidence over adjectives. A figure shows a real structure from the copy beside it. If the words are not on the page, the figure cannot say them.
  4. No unsupported claims. No axes without data, no curves that imply magnitude, no invented file names or numbers. A qualitative figure says so (“Not a forecast.”).
  5. Owned is solid, rented is dashed. Forest marks the owned or decision element; --mute dashes mark the rented or external one.
  6. Every figure has a caption in mono 14px, with the source and date when it carries facts.
  7. Tokens only, so the figure works in dark theme unchanged.

02The figure family

OwnRent · logic-first comparison

What you own

Decision logicThe rules or model behind each decision, tested and versioned, with each decision recorded.
Data recordThe customer or site data each decision uses, with its sources and definitions written down.
WorkflowThe steps that carry each decision into the tools your team already uses.
DocumentationRunbooks and training, so your team can run the system and change it as the business changes.

Runs inYour environment · Your cloud · Hosted by NTWRK if needed

Rights and dependencies documented

Renting the part that decides

Platforms that keep your decision logic

AI seats that leave nothing behind

Pilots that stop before production

Consultants who leave decks

What a production build hands over, as named in its scope. A 30-day proof hands over a smaller, documented set. Cloud and model costs continue after handover, and the scope lists them. (Live Home caption, PR #138. Rented side: the four faces of the Story enemy line.)
Flow · sequence
DAY 0DAY 30
01

The decision

02

The proof

03

The record

04

The recommendation

The first 30 days: four outputs. Copy from the deck starters.
Two purchases · contrast
Breadth

Open-ended work, changing questions, wide knowledge. Rent it.

The decision

The same judgment, thousands of times. Consider controlling it.

From Build to Keep No. 05. The owned/decision side carries the Forest edge.
Record · list as figure
Decision record
  1. The data used
  2. The model and configuration
  3. The evaluation results
  4. The deployment date
  5. The people accountable for exceptions
The record a controlled decision system can keep. Build to Keep No. 05.

03Mobile behaviour

FigureAt ≤560px
ComparisonPanels stack; items go 2×2
FlowVertical left rail, dot per step, Forest on the last
HubCentre node first, then a list on a rail
TimelineColumns stack on a rail; axis strip hidden

04What a figure must not do

✕ Retired

Capability curve

An unlabelled y-axis implying owned capability climbs after 2026. No data existed. Replaced by a qualitative timeline.

✕ Retired

File-label cards

“customer_record.schema” and similar invented file names. Removed in the 23 Sep audit.