Shared business records

The five steps in How it works — and the five areas of the workspace that serve them — are different views of one business. What makes them one business rather than five apps is a shared set of records that every area reads and links to. This page defines that vocabulary. It is a conceptual model: a claim about how the records relate, not a claim that every record already has a complete database table and screen.

flowchart LR
  P[Product] --> O[Offer]
  O --> CA[Campaign]
  CA --> TK[Task]
  TK --> RN[Run]
  RN --> AV[Artifact version]
  AV --> PB[Publication]
  PB --> RS[Results]
  CU[Customer / account] -. activity .-> RS
  G[Goal] --> TK
  CL[Calendar entry] -. refers to .-> TK
  CL -. refers to .-> PB

The records

Record	What it means	How it connects
Product	What the business creates or sells	A book, course, film, or downloadable resource links to its tasks, files, offers, and results
Offer	How a product or service is packaged for a buyer	Price, bundle, terms, positioning, and landing pages can change without redefining the product
Customer / account	A person or organisation with a business relationship	Contacts, leads, opportunities, customer activity, service history. The relationship continues after the sale
Campaign	A coordinated effort aimed at an outcome	Connects audience, offer, tasks, channel placements, deliverables, spend, and observed results
Funnel stages & events	The intended progression, and the activity actually observed	A view, inquiry, signup, or purchase has a source and a definition. A stage is not proof of a causal conversion
Goals, tasks & runs	Intent, planned work, and actual execution	A task can involve multiple runs and deliverables. Chat messages reference tasks without becoming their storage
Artifacts & versions	The results people inspect, use, or publish	Stable references connect deliverables to source work and explicit versions; names and locations can change independently
Calendar entries	When work, events, or publishing should happen	A scheduling view that links to authoritative tasks, posts, appointments, and automation rather than duplicating them

Two meanings of “account”

Customer account here means a business relationship — someone the brand sells to or serves. The account or organisation that owns a WilsonOS brand is a separate access-and-billing concept, governed by the identity foundation.

Why the vocabulary matters

One post, several views. When Prime schedules a Pinterest post for a RiseBlox book, the product identifies what it promotes; the task tracks its creation; the calendar schedules it; the connection publishes it and records the external post identifier; business performance measures it; learning proposes improvements. Six areas, one record chain, no copies.

Feedback lands on the right thing. A comment attaches to an artifact version, so “make the cover warmer” refers to the version it was said about, and the next version does not erase the note. A rating attaches to the run, so the skill that produced it can be evaluated later.

Attribution stays honest. Because a funnel event carries its source and definition, a dashboard can show “twelve signups this week from the campaign’s landing page” without implying that a Pinterest impression caused a purchase. The record model preserves the links where the underlying systems provide evidence, and says so where they do not.

Renaming does not break anything. Artifacts and tasks are identified by stable references, not by file names or folder paths. A deliverable can be retitled, moved, or reorganised, and every link to it — from a chat message, a calendar entry, a campaign — still resolves.

What a record is not

• A chat message is not a task. It can create or reference one.
• A calendar entry is not a post. It points at the post’s task and its publication.
• A file on disk is not an artifact’s identity. It is the current bytes of one version, under one label.
• A funnel stage is not a conversion. It is a definition that observed events are matched against.

direction The vocabulary is the agreed model and is used consistently across the architecture contracts. Products, tasks, runs, artifacts, versions, and calendar entries have database-backed records today; customer accounts, campaigns, and funnel events are at varying maturity — the docs explain their relationships now without commissioning a new CRM or analytics engine.

Related

How it works in 5 stepsThe journey these records connect.

FoundationsData governance: one canon and one writer per record class.

Example: market an existing bookThe record chain followed through a real campaign.

GlossaryAll terms in one place.