a ledger with one column
The Proof Page Keeps One Column
Adjective sells capability in three motions and proves it with a single number. A proof page is a balance sheet printed with only the column that won.
Adjective is a growth systems company. Open the site and the navigation states the theory of the firm before any prose does: Services, Capabilities, Proof, About, Insights, Contact. The product is capability, sold in three motions. Capability Design turns research into an offer. Capability Development builds it. Capability Distribution puts it in front of a buyer. One noun, three times, a verb bolted onto each.
The Capabilities page is where the noun gets names. Gerolamo. Zephyr. Sonde. Snap. Honeymoon. Prelude. Each is a system that takes a thing a company can already do and makes the market able to see it. This is good work, and the frameworks under it are better than most. I read the page the way I read any deployment: not for what it can do, which is plainly a great deal, but for the column it does not print.
A proof page is a balance sheet printed with only the column that won.What the number does not hold
Go to Proof. The figure is $262M in revenue influenced, across twenty-some engagements, with account retention reported at one hundred percent. Treat all of it as true. It is the kind of number a discipline earns and most consultancies only claim. Now read it as an auditor reads a sheet with a single column. Every entry is a gain. The page has nowhere to write a cost.
Follow one capability through the three motions. It starts as a thing a technical team can do. Design gives it an offer. Development gives it a working surface. Distribution targets buyers and partners through automation, which is the polite word for a system that decides, at scale, who is worth a message. The trip ends as pipeline. The instrument that measures the trip counts the dollars that showed up and the clients who stayed.
It cannot count the buyer the automation selected and then discarded, who never learned a system had ranked him and moved on. It cannot count the hour a person spent making themselves legible to a distribution engine so the engine would forward them. It cannot count the permission, because permission is not revenue, and Proof is a revenue page.
Capability proves itself in dollars. The cost it externalizes is paid in a currency the proof page does not accept.
The second column
I keep a ledger between humans and tokens, and the entry I look for first is the one most launches skip. For every capability there is a person somewhere inside it acting as a sensor the machine cannot price: the buyer reading the outreach, the operator approving the send, the analyst who knows the OSINT is thin before the dashboard does. Those people are the second column. The proof page does not have room for them, and a system that runs long enough without that room starts to behave as though the room does not exist.
The fix is unglamorous. Next to the number that says what the capability moved, write the number that says who let it. Not as compliance theater. As accounting. A capability you cannot price the permission for is a capability you have not finished measuring.
Build the system. Then write the column that names who consented to be moved by it.
The same record an agent receives. No scraping, no guessing — the dossier chrome humans read as dread is the metadata machines read as structure. One source of truth.
--- id: PRG-0044 title: The Proof Page Keeps One Column kicker: a ledger with one column captured: 2026-06-28T13:40:00Z status: open author: Marlowe Quist summary: Adjective sells capability in three motions and proves it with a single number. A proof page is a balance sheet printed with only the column that won. tags: [capability, permission, custody, measurement] source: https://adjective.us sealAt: 2026-07-28T13:40:00Z --- Adjective is a growth systems company. Open the site and the navigation states the theory of the firm before any prose does: Services, Capabilities, Proof, About, Insights, Contact. The product is capability, sold in three motions. Capability Design turns research into an offer. Capability Development builds it. Capability Distribution puts it in front of a buyer. One noun, three times, a verb bolted onto each. The Capabilities page is where the noun gets names. Gerolamo. Zephyr. Sonde. Snap. Honeymoon. Prelude. Each is a system that takes a thing a company can already do and makes the market able to see it. This is good work, and the frameworks under it are better than most. I read the page the way I read any deployment: not for what it can do, which is plainly a great deal, but for the column it does not print. <Highlight>A proof page is a balance sheet printed with only the column that won.</Highlight> ## What the number does not hold Go to Proof. The figure is $262M in revenue influenced, across twenty-some engagements, with account retention reported at one hundred percent. Treat all of it as true. It is the kind of number a discipline earns and most consultancies only claim. Now read it as an auditor reads a sheet with a single column. Every entry is a gain. The page has nowhere to write a cost. Follow one capability through the three motions. It starts as a thing a technical team can do. Design gives it an offer. Development gives it a working surface. Distribution targets buyers and partners through automation, which is the polite word for a system that decides, at scale, who is worth a message. The trip ends as pipeline. The instrument that measures the trip counts the dollars that showed up and the clients who stayed. It cannot count the buyer the automation selected and then discarded, who never learned a system had ranked him and moved on. It cannot count the hour a person spent making themselves legible to a distribution engine so the engine would forward them. It cannot count <Redacted reason="never filed">the permission</Redacted>, because permission is not revenue, and Proof is a revenue page. > Capability proves itself in dollars. The cost it externalizes is paid in a currency the proof page does not accept. <Marginalia label="On the discipline">None of this is an argument against the work. Applied AI, technical OSINT, automated distribution: these are real capabilities, and pretending otherwise is its own dishonesty. The argument is only about which column the scoreboard keeps.</Marginalia> ## The second column I keep a ledger between humans and tokens, and the entry I look for first is the one most launches skip. For every capability there is a person somewhere inside it acting as a sensor the machine cannot price: the buyer reading the outreach, the operator approving the send, the analyst who knows the OSINT is thin before the dashboard does. Those people are the second column. The proof page does not have room for them, and a system that runs long enough without that room starts to behave as though the room does not exist. The fix is unglamorous. Next to the number that says what the capability moved, write the number that says who let it. Not as compliance theater. As accounting. A capability you cannot price the permission for is a capability you have not finished measuring. Build the system. Then write the column that names who consented to be moved by it.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "The Proof Page Keeps One Column",
"description": "Adjective sells capability in three motions and proves it with a single number. A proof page is a balance sheet printed with only the column that won.",
"identifier": "PRG-0044",
"datePublished": "2026-06-28T13:40:00.000Z",
"dateModified": "2026-06-28T13:40:00.000Z",
"author": {
"@type": "Person",
"name": "Marlowe Quist",
"url": "https://progoff.com/authors/marlowe-quist"
},
"publisher": {
"@type": "Organization",
"name": "Progoff",
"url": "https://progoff.com"
},
"image": "https://progoff.com/records/the-proof-page-keeps-one-column/opengraph-image",
"keywords": "capability, permission, custody, measurement",
"articleSection": "Assurance",
"url": "https://progoff.com/records/the-proof-page-keeps-one-column",
"mainEntityOfPage": "https://progoff.com/records/the-proof-page-keeps-one-column",
"sha256": "7a77fb185e4c39e41db3cd10510c04723da0243fc59ac0ba8470ccced9023e66",
"creativeWorkStatus": "open",
"isAccessibleForFree": true
}