Skip to content
Portfolio/Capabilities

CAPABILITY 11 / 30

The sales desk

Three agents that each produce one document, and each stop when a fact is missing.

STAGED, WITH GATES

Defined and gated, but not running unattended. A person starts it, and it stops when a fact is missing.

A proposal agent, an account brief agent, and an onboarding plan agent. Each knows the facts it needs before it may run. Missing one is not something to work around: the run stops and says who normally has the answer. Stopping is the designed behaviour.

TRY IT / RUNS IN YOUR BROWSER

Use it here.

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

The sales desk

Three agents that each produce one document, and each stop when a fact is missing

Every agent below is defined as data: what it is for, the facts it must have before it may run, the sections it writes, the checks it runs on its own output, and the rules that stop it.

These three are staged, not running unattended. They are defined here with their gates in place, and each one produces its document when a person runs it. None of them runs on a schedule, watches an inbox, or sends anything to anybody. The documents linked below were produced by these definitions for a fictional partner.

1

The roster

What each agent produces, what it refuses to start without, what it checks, and where it escalates.

Loading the agent definitions.

2

The gate, demonstrated

The proposal agent, started with two of its six required facts missing. This is the part worth watching.

Loading the agent definitions.

THE OUTPUT / GENERATED FOR APEX INSTRUMENTS

What comes out.

JSON
The three agents defined as dataData · One entry per agent with its purpose, the document it produces, the sections of that document, its required facts (each with who holds it, why it matters, and what it unlocks), its optional facts and what each one changes, the checks it runs on its own output, and the escalation rules that stop it. Plus the seven line Apex catalogue every price is validated against.Open the file ↗
Partnership proposal, Northlight Group, six pages
Partnership proposal, Northlight Group, six pagesPrint · 6 pages · Cover, the situation in the partner's own quoted words, three options priced line by line from the catalogue, what is included and explicitly what is not, schedule and commercial terms, and an acceptance page with signature blocks. Every option total is the sum of its own lines and every unit price is a catalogue price.Open ↗PDF
Account brief, Northlight Group, one page
Account brief, Northlight Group, one pagePrint · 1 page · The page a rep reads in the ten minutes before a meeting. Identity strip, the relationship in four dated lines, what they buy and what they do not, three open items each with a named owner and a date, two risks, and one recommended next step.Open ↗PDF
First 60 days, Northlight Group, two pages
First 60 days, Northlight Group, two pagesPrint · 2 pages · Four phases across 60 days counted from the contract signed date, 22 dated steps each with an owner at Apex and an owner at the partner and the artifact it produces, three decision points with a decider and the artifact the decision is made against, what done means for each phase, and the escalation ladder.Open ↗PDF
MD
What is here and whyData · What was built, how the gate works, the arithmetic behind the three options, the judgement calls, the three layout bugs found and fixed, and what is not resolved.Open the file ↗

THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE

How it works.

What a skill is
  1. 01Declare the facts

    Each agent lists what it must have before it may start.

  2. 02Check the gate

    A missing fact stops the run and names who normally has it.

  3. 03Refuse bad values

    A price outside the catalogue or a date in the past is rejected with the reason.

  4. 04Produce one document

    The agent writes its document from an approved template, nothing else.

  5. 05Hand back

    A person reviews and sends. The agent does not.

WHAT IT READS

  • The account record
  • The catalogue and the terms
  • A required-fact list per agent
  • An escalation rule for each stop

WHAT IT CHECKS BEFORE IT SHIPS

  • A missing required fact stops the run
  • Every figure traces to the catalogue
  • A produced document names the template it used
  • Nothing is sent by the agent itself
Staged in both company systems with their gates defined. These are run by a person, not left running on their own.

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