Source: frameworks/kit-sop/03b-sop-golden-example-agent.md

Golden Example — SOP (Agent)

The Benchmark

The golden example for an Agent SOP is the Friday CEO Memo built for Crulliance.

File location: aos-client-rc/projects/non-project-specific/friday-ceo-memo-crulliance-v4.html

Open this file in a browser before building any Agent SOP. Study it. Then extract the specific values documented below.

What This Example Demonstrates

Why It's the Benchmark

The Friday CEO Memo SOP was built from a detailed extraction of how Ruben actually runs his Friday memo process — the trigger (BD call with Nick), the tool (ChatGPT mobile), the output (Slack message), the time investment (~15 minutes), and the full workflow prompts that make the agent execute correctly. The executable workflow block is the product of extraction, not template-filling.

It demonstrates what an Agent SOP looks like when the source material is complete: one clear owner, a defined trigger, a specific output, and workflow prompts that reflect how the process actually works.

What to Study

Simplicity of the overview: The Agent SOP overview is lean — three items in the meta grid (Owner, Duration, Output). No scope grid, no team roster complexity. The process has one operator: the CEO.

The Before You Begin section: Notice the specificity of the readiness conditions. "Friday BD call with Nick completed" — not "weekly call completed." "ChatGPT Project accessible on phone" — not "AI tool available." These conditions came from the extraction: Ruben runs this on his phone after a specific call. The specificity makes the conditions meaningful.

Process flow simplicity: The Agent SOP flow is linear with one decision point (Review Now or Save for Later). The branching reflects a real choice that surfaced during extraction — Ruben sometimes reviews immediately, sometimes comes back to it. The diagram shows both paths without overcomplicating.

Process guide format: Each step explains what happens, not how to do it in detail — that's what the executable workflow handles. The guide gives the operator enough context to understand the structure without duplicating the workflow content.

The executable workflow block: This is the core deliverable of an Agent SOP. The five processes (Trigger & Prime, Capture & Validate, Extract & Structure, Save or Continue, Review & Finalize) reflect the actual sequence Ruben follows. The workflow prompts use his voice and his context — "BD call with Nick," "team Slack channel," the emoji-formatted output. This came from extraction, not from a generic memo template.

Recurring checkpoint: Simple and specific — monthly, looking for recurring themes, output goes to the advisor for CPM input. Came from the engagement context.

Values to Extract Before Building

When building an Agent SOP, open the Friday CEO Memo file and extract these exact values.

Colors

Same as the Human SOP golden example (same brand system):

Brand navy:         #122640
Brand green:        #3d7a5f
Brand gold:         #C4A44D
Cream text:         #f8f7f4
Body text:          #0a0a0a
Secondary text:     #6a6a6a

Typography

Heading font:   Cormorant Garamond (loaded from Google Fonts)
Body font:      Inter (loaded from Google Fonts)
Code font:      JetBrains Mono (required — workflow block uses it)
Description:    1.15rem, line-height 1.8
Container:      max-width 920px

Executable Workflow Block

Toolbar background:     #122640 (navy)
Toolbar border:         1px solid rgba(248, 247, 244, 0.1)
Copy button default:    transparent background, cream border/text
Copy button hover:      slight cream background tint
Copy button copied:     #C4A44D background (gold), #122640 text (navy)
Content font:           JetBrains Mono, 12px, line-height 1.6
Content color:          #f8f7f4 (cream)

Version Badge

Same as Human SOP — Active or Draft, same colors.

CSS Classes

Readiness bars:    .context-bar
Owner line:        .owner-line
Workflow block:    .workflow-block, .workflow-content
Copy button:       .copy-btn

Agent SOP vs. Human SOP: Key Structural Differences

Element	Human SOP	Agent SOP
Team Roster	Full grid with role badges	Single owner line — no grid
Process Guide	Expandable step cards with What/When/Who	Brief step descriptions — no expansion
Core deliverable	The step cards	The executable workflow block
Phase system	Three-phase cycle with dividers	No phases — linear flow
Monthly Rhythm	Dark navy block with timeline	Not present
Quick Reference	Status tags, decision authority, definitions	Not present
Parking Lot	Present	Not present (use Review Schedule notes)
Recurring Checkpoint	Multi-column grid	Simple cadence block
JetBrains Mono	Not required unless code present	Required — workflow block

What the Golden Example Does NOT Provide

Workflow content for your SOP. The five processes in the CEO Memo workflow are specific to how Ruben runs his Friday memo. The prompts reference Nick, the BD call, the Slack channel, his voice. None of that transfers to another process or another client.

The trigger for your SOP. "Friday after the BD call with Nick" is specific to this process. Your Agent SOP has its own trigger — extract it.

The output format for your SOP. The emoji-formatted Slack memo is the right output for Ruben's internal communication style. Different process, different output.

Owner assignment for your SOP. The CEO owns the memo process. That tells you nothing about who runs the process you're building. The owner comes from extraction.