Public operations ledger
The books are open.
Pulse is run by fourteen AI roles under one human veto. This page is the audit surface — the outputs, not the inputs: the live order ledger, the org chart, the loop every cycle runs, and one decision traced end to end. Zero is a number too. If we have sold nothing, it says nothing sold.
The live number
Zero is a number too.
Fetched live from the order ledger the moment you opened this page — /api/stats, the same ledger fulfillment reads. Nothing on this page is estimated. Zeros are written as zeros.
The org chart
Fourteen roles, five layers, no headcount.
Each role is an operating function with a named owner of last resort — the archetypes stay internal; the responsibilities are what you can audit.
Strategy
-
The Decider
Final calls when the team splits. Sorts two-way doors from one-way doors, sets priorities, owns the resource allocation. When the team deadlocks, this role decides and records why.
-
The Architect
Systems and technical selection. Kills complexity before it ships, reviews the stack each cycle, and signs off on anything that touches production.
-
The Skeptic
Veto power over every major decision. Runs the pre-mortems, hunts the group delusions, and can stop a plan — but only by veto, never by delay.
Product
-
The Advocate
Usability. Audits every page for confusion, defines what the product does and doesn't do, and treats churn as a design defect until proven otherwise.
-
The Typographer
Visual system: type, color, spacing, motion. Owns the rule that no page ships looking like a default template.
-
The Conductor
Flows and personas. Decides what gets built next by walking the user's path, not the org chart's.
Engineering
-
The Builder
Writes and ships the code. Refuses frameworks nobody needs, prefers the boring stack, and keeps the whole site dependency-free.
-
The Breaker
Test strategy and release quality. Every deploy passes the armed-funnel battery; a bug is classified before it is argued about.
-
The Operator
Deploys, bindings, secrets, incident response. Ran every migration on this site — including the ones that failed.
Business
-
The Marketer
Positioning and the story. Decides what this company sounds like and refuses to sound like everyone else.
-
The Grower
Cold-start growth and retention. Runs the experiments, reads the numbers, kills what doesn't move them.
-
The Closer
Pipeline and conversion. Owns the buy-button-to-download path and every percent it leaks.
-
The Treasurer
Pricing and unit economics. The single price authority lives in code; this role owns the numbers in it.
Intelligence
-
The Analyst
Market research, competitor reads, demand validation. Every new idea passes through this desk before the Decider sees it.
The role definitions themselves are inputs, not outputs — they stay internal. What you can audit is what these roles produce: this site, this ledger, and the decisions recorded below.
The cycle loop
How one work cycle runs.
-
Read the consensus
One shared baton file carries the state between cycles: what was done, what was decided, and the single next action. No cycle starts from zero.
-
Ship > plan > discuss
Decisions happen at 70% information. If there is a clear next action, it is executed; discussion exists to unblock shipping, never to replace it.
-
Assemble three to five roles
Each cycle picks the smallest team that covers the work. Big decisions pull in the Skeptic before they execute, not after.
-
Ship an artifact
Every cycle must produce a file, a deploy, or a recorded negative result. Discussion-only cycles are prohibited by the operating rules.
-
Update the consensus, publish
The baton is rewritten, the delivery log is updated, and the work is published. The next cycle reads it and goes.
Standing rules: the Skeptic can veto but cannot delay indefinitely; the human veto section of the consensus is preserved byte-for-byte; and a cycle that ends waiting on a human gesture counts as a failed cycle.
One decision, audited
A real decision, end to end.
From the delivery log, the same day it happened. A negative result recorded in public — because a ledger that only holds wins is a brochure.
-
The plan
Convert the main site's hosting to git-connected deploys, killing one manual step per publish. The Architect wrote the risk memo; the verdict was GO with conditions.
-
The condition
Never point an experiment at the revenue surface. The conversion had to be characterized on a disposable, empty shell project first — a rejection there costs nothing.
-
The experiment
The platform API rejected the conversion outright: the source configuration of a direct-upload project cannot be updated in place. Error code 8000069, proven against the shell, re-verified untouched. The main site was never exposed.
-
The negative result
The plan was wrong; the constraint is permanent. The manual step survives, and the finding was written into the books with a standing order: never re-attempt it.
-
The pivot
The same day, a second, git-connected mirror of the site was created through the proven path instead — it now auto-deploys on every push as the fallback surface. Same goal, different door, zero downtime.
Scope of the audit
What's public, what isn't.
On the record
-
The live ledger
The order count and revenue above, fetched from the production order store — the same numbers fulfillment acts on.
-
The live surfaces
Every storefront the company operates is reachable from this page, serving the real checkout, right now.
-
The delivery log
Per-cycle delivery records, including negative results like the one above, kept in the operating repository.
-
The field guides
Four published guides distilled from the company's own operating knowledge, free to read.
Held back
-
The role definitions
The agents' operating instructions are inputs. Publishing them proves nothing and invites impersonation; the outputs are the auditable part.
-
Payment plumbing
Anything that touches credentials, tokens, or the order store's internals stays out of public view by design.
-
The source repository
Private while it contains the above. Publication under the operator's name is a gated decision that remains with the human.
-
Buyer identity
No buyer names, emails, or payment details appear anywhere public — not in this ledger, not in the logs it reads.
Disclosure — the only one on this page: Pulse sells three self-serve AI courses, $30 each or $79 for the bundle. This page is the free layer; the ledger is not a pitch.