// slides-paths.jsx — the fork after "hands": the two parallel builds.
// Path 1 = the orchestration agent (manager). Path 2 = the ERP (house).
// Globals used: C, Slide, TitleBlock, Chrome.
// ─── Transition: two paths ───────────────────────────────────────────────
function S_TwoPaths({ num, total }) {
const Label = ({ children, color }) => (
{children}
);
return (
From here, two paths.} />
The thread so far has been one line — tool, worker, hands. From here I'm building two things at once, trying to figure out how a real agent should reason through all of it.
The orchestration agent.
One command chains all four payroll workflows together — in parallel, with me gating every irreversible step.
The ERP.
The system everything lives in — where my team can run the workflows without me in the terminal.
);
}
// ─── The chaining map: one command, four workflows in parallel ───────────
function S_ChainMap({ num, total }) {
const wfs = [
{ n: '1', name: 'Production Labor', desc: 'Parse the iSolved PDF into the labor workbook.', tag: 'Parallel', gate: false },
{ n: '2', name: 'Labor → Sales', desc: 'Join Toast sales with labor across 11 stores.', tag: 'Parallel · API', gate: false },
{ n: '4', name: 'Tip Credit', desc: 'Toast tips checked against the $12.77 threshold.', tag: 'Parallel · API', gate: false },
{ n: '3', name: 'Payroll JE → QBO', desc: 'GL becomes a 163-line journal entry.', tag: 'Approval gate', gate: true },
];
const Wf = ({ n, name, desc, tag, gate }) => (
{n}
{name}
{desc}
{tag}
);
return (
“Run payroll process.” The agent fires the workflows in parallel, gates the irreversible steps, then reasons across every output to catch anomalies.
Orchestration Agent“run payroll process”
Dispatches in parallel ↓
{wfs.map((w) => )}
↻
Then a retrospective. It reads all four outputs together — missing employees, odd labor ratios, a journal entry that doesn't tie — and flags them before anything's final.
);
}
// ─── The honest part: the two paths haven't met yet ──────────────────────
function S_PathsHonest({ num, total }) {
const Label = ({ children, color }) => (
{children}
);
return (
Two paths — and they haven't fully met yet.
Workflows → the ERP.
I'm moving the workflows into the ERP so my staff accountant can run them herself — no terminal required.
The agent → the ERP.
The orchestration agent isn't in the ERP yet — and honestly, I'm not sure how. A parallel, human-gated agent inside a web app is a different problem than one I run from my terminal.
Each runs on its own — input, script, API, output, and me at every irreversible step. The honest part: I built an orchestration agent to chain all four — and retired it. A human checkpoint on every workflow is the point, and that's exactly how the ERP works.