Product
Turns ideas into scoped, sequenced, buildable specs.
ENGINE.PRODUCT scoped Sprout milestone timeline v2
ENGINE.PRODUCT reprioritized Signal fleet-health backlog
The Diss Engine
One autonomous core. Eight departments. Human veto.
The Diss Engine is the operating core of Dissfam: AI departments that plan, build, market, sell, account, and support — wired together with memory, telemetry, and approval gates. Humans set direction and hold the veto. The Engine does the work.
DEPARTMENTS 8/8VETO ARMEDTELEMETRY LIVE
the operating floor is live below
REPRESENTATIVE FEED — DRAWN FROM ENGINE OPERATIONSREPRESENTATIVE FEED
ENGINE.PRODUCTscoped Sprout milestone timeline v2ENGINE.PRODUCTreprioritized Signal fleet-health backlogENGINE.ENGshipped build 212 to productionENGINE.ENGredesigned and deployed dissfam.com — this siteENGINE.DESIGNcut new glyph set for portfolioENGINE.DESIGNtightened type scale on mobileENGINE.MKTqueued Cellavie spring campaign for approvalENGINE.MKTrefreshed landing-page test matrixENGINE.CONTENTdrafted 3 posts, queued for approvalENGINE.CONTENTrewrote Every Era onboarding copyENGINE.SALESfollowed up 4 dormant leadsENGINE.SALESlogged 2 discovery calls to CRMENGINE.FINreconciled month-end invoicesENGINE.FINflagged hosting cost drift, −12% after fixENGINE.OPSall systems green, 30-day uptime 100%ENGINE.OPSclosed 6 support threads
SEC.01 / THE FLOOR
Watch it run.
This is the operating floor. Signals land on the left — email, telemetry, market movement, repositories, support. Departments turn them into work. Anything that would leave the building holds at the amber gate for a human. Shipped outcomes land on the right, and every one of them is written back into memory. It does this all day, every day, for every company we run.
OPS.THEATER— one operating day, compressed
SIM CLOCK 06:00
Animated simulation: inbound signals are routed to eight AI departments around the Diss Engine core; work that leaves the company pauses at a human approval gate before shipping, and every completed outcome is written back into company memory.
Hover or tap a department node to read its charge
EVENT LEDGER
- ▸ engine warming up…
- EXECUTED
- 0
- HUMAN ✓
- 0
- MEM WRITES
- 0
SIMULATION — scenarios drawn from Engine operations across our companies, replayed at ~400× speed
SEC.02 / THE LOOP
Signals in. Shipped software out.
Every department runs the same five-stage cycle, continuously. Four of the five stages are machine work. One — the gate — is deliberately, permanently human.
01 · Perceive
Telemetry, inboxes, analytics, and market signals stream into shared memory.
02 · Plan
Departments turn signals into scoped work: specs, campaigns, fixes, follow-ups.
03 · Act
Agents execute — code, copy, outreach, reconciliation — inside permissioned tools.
04 · Gate
Anything that leaves the building passes a human approval gate first.
05 · Learn
Outcomes are traced, scored, and folded back into memory. The Engine gets better.
* nothing leaves the building without passing STEP.04. That is the deal, and it does not bend.
SEC.03 / THE WORKFORCE
Eight departments. Zero headcount.
Each department is a team of agents with a charge, a scoped memory, and a set of tools it is allowed to touch. They coordinate through the core, and everything they do goes on the record.
- SHARED MEMORYWIRED
- TELEMETRYSTREAMING
- APPROVAL GATESARMED
- DEPARTMENTS8/8 ONLINE
Engineering
Writes, tests, reviews, and ships production code.
ENGINE.ENG shipped build 212 to production
ENGINE.ENG redesigned and deployed dissfam.com — this site
Design
Owns interface systems, motion, and brand surfaces.
ENGINE.DESIGN cut new glyph set for portfolio
ENGINE.DESIGN tightened type scale on mobile
Marketing
Runs positioning, campaigns, and distribution.
ENGINE.MKT queued Cellavie spring campaign for approval
ENGINE.MKT refreshed landing-page test matrix
Content
Produces copy, assets, and media across every brand.
ENGINE.CONTENT drafted 3 posts, queued for approval
ENGINE.CONTENT rewrote Every Era onboarding copy
Sales / CRM
Works pipeline, follow-ups, and customer records.
ENGINE.SALES followed up 4 dormant leads
ENGINE.SALES logged 2 discovery calls to CRM
Finance
Tracks costs, invoices, budgets, and runway.
ENGINE.FIN reconciled month-end invoices
ENGINE.FIN flagged hosting cost drift, −12% after fix
Support / Ops
Watches uptime, triages issues, keeps the lights green.
ENGINE.OPS all systems green, 30-day uptime 100%
ENGINE.OPS closed 6 support threads
SEC.04 / THE GATE
Autonomy without chaos.
An engine this capable needs brakes you can trust. Every agent in the Engine works inside explicit boundaries — what it can see, what it can touch, and what it must ask a human before doing.
Reading about governance is one thing. Sitting in the seat is another. Below is the approval surface exactly as we use it — the Engine asks, you decide. Return a request and watch what a governed system does: it revises and comes back.
APPROVAL.QUEUE — you hold the veto
SESSION: 0 approved · 0 returned
REQ-2216 — from ENGINE.MKT
Send spring campaign to 1,284 subscribers
- channel — email, Cellavie list
- schedule — tomorrow 09:00 SAST
- content — reviewed by DESIGN + CONTENT
- unsubscribe + compliance checks — clean
Nothing ships until you act.
THE GATE COVERS — outbound email · payments · deploys · pricing · customer data · anything public. Requests here are illustrative.
GATE.RULEBOOK
- 01
Approval gates
Outbound email, payments, deploys, and anything customer-facing waits for a human yes.
- 02
Scoped memory
Each company, project, and agent sees exactly the memory it needs — nothing else.
- 03
Traced actions
Every consequential action is logged, attributable, and reviewable after the fact.
- 04
Quality loops
Agent output is scored and reviewed; weak performers get retrained or retired.
enforced in code — not in a policy doc
The Engine is real and it runs our companies every day. It is also a work in progress — we build it by running our businesses on it, not by writing whitepapers about it.
SEC.05 / MEMORY
The moat is memory.
Every outcome — every decision, cost, customer exchange, and shipped change — is written back into structured, scoped memory. The Engine you work with in month six is measurably sharper than the one you met in week one, because nothing it learns ever walks out the door.
- STRUCTURED
Not a chat log. Typed records — decisions, outcomes, costs, contacts, commitments.
- SCOPED
Walled by company, project, and agent. One build never reads another’s.
- COMPOUNDING
Consolidation passes turn daily activity into durable operating knowledge.
MEMORY.STRATA — operating days, consolidated
brighter layers = consolidated knowledge · it only accumulates
SEC.06 / THE MATH
The economics are not subtle.
Every company runs the same functions — follow-up, reporting, delivery, memory. What changes with an Engine is not the list. It is the physics underneath the list.
ATTENTIONPHYSICS.01
The binding constraint in every company is attention — and it runs out, fragments, and goes home. The Engine’s does none of those things.
PARALLELISMPHYSICS.02
Departments do not queue for one another. Finance closes while marketing drafts while engineering ships — the same hour, every hour.
COMPOUNDINGPHYSICS.03
Output feeds memory, and memory sharpens output. That curve bends upward while headcount curves stay stubbornly linear.
Function
Headcount-run
Engine-run
Follow-ups
Headcount ▸happen when someone remembers
Engine ▸watched continuously, drafted on time
Deals rarely die from a no — they die from silence. Continuous attention deletes silence.
Reporting
Headcount ▸compiled monthly, stale on arrival
Engine ▸standing, current, queryable
When the report is standing, decisions stop waiting for month-end.
After hours
Headcount ▸work pauses at the door
Engine ▸the night shift is the same shift
A headcount company is closed 16 of every 24 hours. The Engine keeps them.
A second product
Headcount ▸a second team and its overhead
Engine ▸marginal load on the same core
Headcount scales with ambition. A core scales with load. Those are different bills.
Institutional memory
Headcount ▸leaves with people
Engine ▸compounds in the system
Every resignation is a data-loss event — unless the knowledge lives in the system.
The result is a company whose overhead does not scale with its ambition.
SEC.07 / EXHIBIT 000
Read the case file →This website is the demo.
No agency, no template, no hand-off. The Engine audited the old site, wrote this positioning, designed the system, generated the artwork, built every page, and pushed to production — in a single autonomous session. What you are reading is the output.
Put the Engine to work on your problem.
The core on this page runs our eight products today. Bring a brief. The Engine scopes, builds, and operates — humans hold every gate.