Handbook
79 documents. Everything the portal knows about how Atlas works, and why it was built the way it was.
Playbooks
Interactive reference guides for the team.
How to do things
Procedures with click-paths. Follow them rather than remembering them.
Campaign naming
Existing campaigns are not being renamed. Everything here applies to campaigns created from
Channels: when to talk in one, and when not to
Alex, 20 Sep 2026: "the channels are not very clear and super messy. it's like when are we doing
Client reporting
Three reports, and only three. Every client gets all three.
Daily ad account check
Owner: the media buyer. When: every morning, before anything else.
Day as usual: who touches what, and where it gets recorded
One page for the whole team. ClickUp is where work is planned and talked about. Calendar is where
How we work at Atlas
One page. If you remember nothing else, remember the five in bold.
Lead follow-up
What happens to a lead from the moment it lands to the moment it is won or dropped. This is the
Naming: one code per client, one id per deliverable, one shape per name
Alex, 18 Sep 2026: "they name things like 'vanity metric' or 'full suite agency' and I don't know
Reporting: weekly and monthly, who writes what, by when
Alex, 18 Sep 2026: "an AM will have to do reporting, once a week and every month. the reports should
Revisions: who comments, how many rounds, where
Alex, 18 Sep 2026: "sometimes it's the creative strat that does the commenting, sometimes the AM,
Rules of work
One page of rules, one line each, with the reason. This is what a new person is trained on and what
Sales pipeline
How a lead moves from form fill to client, who touches it at each step, and which numbers we judge
SOP — Check the month is comparable
Who: Account Manager · When: before drafting a client report
SOP — Client onboarding
The five-step process from the live onboarding deck, and what the portal does at each step.
SOP — Draft angles
Who: Creative Strategist · When: angle material exists and the client needs new creative
SOP — Draft the report
Who: Account Manager · When: after reconciling the numbers
SOP — GCP service account for Drive access
How the portal's Google credential was created, including the trap. Audience: whoever has to
SOP — Generate Meta ad statics
Who: Delivery · When: a campaign needs creative · Time: under a minute per set
SOP — Google Workspace: calendars, meeting notes, Drive
Why nobody could see anyone else's calendar or notes, and the configuration that fixes it.
SOP — Ingest client content
Who: Creative Strategist · When: onboarding a client, or any time new content exists
SOP — Promote facts to angle material
Who: Creative Strategist · When: after ingesting and deconflicting a client's content
SOP — Read the strategy readout
Who: Media Buyer · When: weekly, before making any changes to the account
SOP — Read-only Meta ad account access for the portal
Alex asked for evidence, not assurance, before granting access to the remaining clients. The naive
SOP — Reconcile the numbers
Who: Account Manager · When: after checking completeness, before drafting the report
SOP — the back-catalogue corpus
Turn delivered videos into style sheets and reconstructed scripts, then index them into the portal. This
SOP — the video editor
Run a cut of an ad from footage to a Frame.io version. The tool is video-pipeline/; its architecture,
SOP — Work the deconflict queue
Who: Creative Strategist, escalating to Founder on high severity
When an account is in trouble
Out of creatives, performance collapsed, budget exhausted: tell the account manager, not the
How this system decides
The reasoning behind the guardrails. Worth disagreeing with — a rule nobody can see is a rule nobody can challenge.
Access control
Alex asked for the code to be secure and not callable from anywhere. The audit found the portal
Ad naming
Atlas's naming was, in Alex's words, "anyhow". Two real names from one account show why that cost
ClickUp: the portal creates, never edits or deletes
Alex, 18 Sep 2026: "be very careful not to turn off any tasks, do not move anything and do not
Cost
The architecture is shaped around one idea: pay for intelligence once, reuse it many times.
Credentials and connections
The system must run unattended for months. Everything here was learned by getting it wrong first.
Data safety
Status: designed, not implemented. Recorded now because retrofitting is expensive and because
Design
The look lives in src/app/globals.css, not in the pages. Every surface is built from Tailwind
Documentation
Docs written later are docs written from memory, and they are wrong in ways nobody notices until
Frame.io: never delete anything
Alex, twice in one session, unprompted:
Guardrails
The team must not be able to produce off-strategy creative. Not "should not" — must not.
Meta is read-only. Never pause, never spend.
Alex, 23 Aug 2026: "i dont want you to be pausing anything. just read meta. this is important to
Performance and sequencing
The portal competes with a spreadsheet and a group chat. If a page takes thirty seconds, the team
Skill, agent, or ecosystem
Before building a capability, decide how much machinery its quality needs — not how much its
Skills
How the skill set stays coherent as it grows. This is the rule most likely to be forgotten by a
System rules
Non-negotiables, one file per concern. CLAUDE.md links here rather than restating them, because
Taste
Alex's requirement, stated plainly: output must be genuinely good across any industry and any
The attested bank ledger is the source of truth
On 10 September 2026 Alex checked every statement in the bank ledger by hand against the DBS PDF:
The workflow is fixed; everything else is data
Alex, 20 Sep 2026: "as simple but most extensible, so we never have to change this workflow but
Verification
Nothing is working until it has run. A passing build is not evidence.
What was sold and paid is a fact; nobody's memory outranks it
Alex, 20 Sep 2026: "the invoices and deposits are the truth. whatever I say, if we sold that and
Where this is going
Vision, architecture and the thinking behind the parts that are not obvious.
Agency operating model
How Atlas Media delivers work. This is the source of truth for role scoping, workflow stages,
Agent Architecture
How AI actually gets used in this portal, and — more importantly — where it deliberately doesn't.
Alex: by Sunday night, 20 September 2026
Everything here is blocked on Alex and nobody else. Numbers are from the portal as at 18 Sep 2026.
Atlas Creative Taxonomy
The system. Every creative Atlas produces follows this hierarchy. The AI agent selects
Atlas Paid Ads Cheatsheet
The complete system. Print this out. Pin it to the wall. Every creative we produce follows it.
Atlas Portal — documentation
Start here.
Atlas Script Reference Library
Real scripts that were cleared by clients and ran in production. This is the training data for
Content library
An ever-growing reference pool of real creative — ads and organic — that the system tags
Creative intelligence: what to buy, what to build, and what actually works
Research done 21 Aug 2026, prompted by Alex: "im not convinced your creatives will be good. we need
Decisions
Standing calls, so they don't get re-litigated. Newest first. A decision here is settled until
Five levels, and knowing which one is broken
Alex, 2026-08-21: "i need multiple levels of thinking. meaning you have to be like a marketing
Handover
Where things stand for whoever picks this up next, agent or person. Updated 9 September 2026 by the previous agent (Claude) at Alex's request, so that a different agent can continue from Git
Higgsfield as the art director
Revises the recommendation in [visual-system.md](visual-system.md). That document argued for
How Atlas actually makes ads
Alex's description of the real process, and what the system must therefore do. This supersedes any
Industry Territory Maps
The universe of things we can argue about, per industry. Every ad angle is a territory × entry
Infrastructure & accounts
What is provisioned where, who owns it, and the operational gotchas found the hard way.
Leads
A Google Sheet with 1,486 rows (486 real), where the pipeline state lived in cell colour:
Making the portal usable, not just full
Alex, 16 Sep 2026: "right now it just feels like a dump, a load of features that nobody really knows
Meeting notes pipeline
The decisions from Alex's constraints, so the puller is built to this and not re-argued.
Moved
This is now [client-dossier.md](client-dossier.md). The name changed because "brain" implied
Quality debt
Where the system produces output that is shallower than it should be.
Roles — what each person does in the portal
Honest about coverage. Most roles have no job in the system yet, and saying so is more useful
Start here
Everything a new session needs before touching anything. Read this, then docs/register.md for
The 10 Commandments of Creative Strategy
The law. Every creative that ships from Atlas follows these. The AI follows them. The team follows
The client dossier
Renamed from "client brain" on Alex's correction, 20 Aug 2026: the goal is not to clone a
The creative engine: how to make judgment reliable
Written 21 Aug 2026 after Alex reframed the goal: "the real task and goal is for the backend to work
The visual system
> Superseded in part by [higgsfield-as-art-director.md](higgsfield-as-art-director.md). The
Vision
What Atlas Portal is for. Read this before proposing what to build next — the register says what
WhatsApp as an input — what is actually possible
Two asks, and they are technically very different problems. Researched 20 Aug 2026.
Wins and failures
Alex's framing: wins pool into case studies, failures compile into an issue-management guide
Working with an agent on this repo
Written after a session that ran far too long and produced three reporting faults Alex had to catch