01
Do and verify the work
Atlas gathers evidence, completes the request, and checks the real result before treating the approach as proven.
01 · Purpose
What Atlas is
Atlas is a deeply informed digital teammate: an agent that retains rich operational context and can use it to help the team understand what is happening, decide what to do next, and move work forward.
It connects knowledge across approved shared sources, keeps that understanding current, and turns context into practical action. Atlas can answer questions, generate reports, analyse patterns, execute tasks across platforms, build automations and workflows, and create or run reusable skills.
Atlas is not limited to the Creative lane as a product vision. Omaze DE Creative is its current proving ground, while the longer-term goal is to support people and workflows across the wider team.
Context that can act
Atlas combines persistent team knowledge with execution. It should ground its work in evidence, show what it used, verify consequential actions, and continuously improve how it works.
02 · Self-improvement
Teach Atlas once. Reuse and automate the workflow.
Atlas is powered by the Hermes self-improvement loop. It can turn a proven process, or a correction from the team, into a reusable skill rather than relearning the same workflow in every conversation.
02
Capture the reusable method
It records the procedure, required sources, permissions, approval gates, verification steps and known pitfalls in an Atlas skill.
03
Learn from team interaction
If Atlas gets something wrong, a teammate can correct it. If someone has useful context that Atlas does not yet know, they can share it directly in the conversation. Atlas can store durable, relevant context so it is available to the team in future interactions.
04
Reuse and improve it
Future sessions can use the updated context and load the improved skill. Atlas preserves the useful correction or new information instead of forcing the team to explain it again.
05
Automate only when approved
A skill can be run on demand or connected to a scheduled task or event-driven automation. Creating the skill does not automatically schedule it or grant permission to write to external systems.
Memory
Stable facts, preferences, access details and standing boundaries.
Context vault
Shared operational knowledge, decisions, source maps, campaign context and evidence. Authorised teammates can add or correct durable context through normal conversation.
Skills
Reusable execution playbooks describing how Atlas performs a specific workflow safely and consistently.
Automations
Approved skills connected to schedules or events so useful workflows can run reliably for the team.
Teach Atlas through conversation
You do not need to edit a database or write a special document. Tell Atlas what it got wrong, explain a missing piece of context, or give it a source to ingest. Atlas can preserve durable information for future use while distinguishing a teammate’s contribution from independently verified source evidence.
You can create skills with Atlas
Describe the workflow in normal language. Atlas can inspect related Cowork skills, n8n workflows and existing Atlas capabilities, propose a safe design, build it, dry-run it, and separately ask before enabling automation or consequential writes.
Custom Exactius skills already available
These are team-specific capabilities built around real Exactius workflows, not generic chatbot features.
Creative operations ingestion
ActivePulls Creative activity from approved operational sources, updates house hubs, links evidence, detects action candidates and produces status updates.
Purpose: Keep the Omaze DE Creative operating picture current without manually assembling every source.
Omaze learnings ingestion
ActiveTurns weekly decks and meeting transcripts into structured learnings, a learning agenda and a testable roadmap with evidence requirements.
Purpose: Preserve what the team is learning, not just what happened.
CRM brief write-back
AvailableCopies approved final copy from a working Google Doc into the original CRM strategy brief while preserving its tabs, tables and wireframes.
Safety: Runs a structural dry-run and requires approval before writing.
Creative and business performance
AvailableAnswers detailed Creative questions and wider Omaze DE performance questions using current data and the business context needed to interpret it properly.
Useful for: Creative rankings, house and phase comparisons, fatigue checks, channel movement and commercial performance reviews.
Workflow porting
AvailableReads existing n8n workflows and Cowork skills, understands their intent and dependencies, and adapts approved workflows into Atlas skills and automations.
Purpose: Reuse good work instead of rebuilding the process from scratch.
Reports, dashboards and pitch decks
AvailableCombines analysis, operational context, source material and narrative into polished reports, presentations, dashboards and shareable pages.
Strength: Atlas can research and reconcile the material before it designs the final output.
03 · Current understanding
What Atlas understands today
The current context is specific to Omaze DE Creative—not a general archive of every Exactius or Omaze project.
Creative workflow
Request → triage → brief → production → internal review → partner approval → export/delivery → performance feedback.
Campaign structure
Launch, BV/bonus phases, Early Close, Close, Big Swings and ongoing/evergreen work, linked by house.
Creative outputs
Static, video, copy and concept work across Meta and secondary channels, with documented naming conventions.
Live house hubs
Current operational hubs for H5, H6 and H7 with linked tasks, assets, stages, pending approvals, deadlines and recent mentions.
Source authority
Which source answers which question—for example, ClickUp for task stage and Figma comments for static-review evidence.
Campaign memory
Stable workflow facts, source documents, meeting operations, action-item candidates and curated learnings with supporting data.
People and roles
Who team members are, their responsibilities, the workstreams they support and identity details needed to avoid mixing up similarly named people.
Meeting purpose
What each recurring meeting is for, which topics belong there, who participates and how decisions or actions should flow into the wider operation.
Team language and naming
Creative naming conventions, house and phase codes, workflow terminology and the source documents that define how work should be classified.
04 · Connected systems
Access today, with the real limits
“Connected” does not mean “everything in the system.” Atlas can only use the accounts, channels, files, projects and write permissions that are authorised and shared with it.
ClickUp
Read + writeHas normal-user access as Atlas. It can read, create, edit, assign, move and close tasks, and add comments across the authorised workspace.
Boundary: ClickUp remains authoritative. Atlas should confirm consequential or ambiguous changes before writing, then read the task back to verify the result.
Slack
Live nowScheduled ingestion reads four approved shared/project channels, applies a DE filter and surfaces operational requests with message evidence.
Boundary: Slack messages are signals, not canonical task status. DMs are excluded from shared-context ingestion.
Figma
PartialReads shared Omaze DE house-file comments with author, time and node context. H7 pages/comments are available; H6 comments are available.
Gap: H6 full-file export is blocked, and performance-file keys for earlier houses have not been supplied.
Frame.io
Live nowRead access to the Omaze DE project, including folders, files and authored comments. Asset paths can be linked to tasks and house hubs.
Boundary: Read-only. Comment language is evidence; formal approval logic is not assumed where the source does not prove it.
Google Workspace
Live nowAuthenticated access to the shared Creative source set, including the source map, H6/H7 narratives, H6 Big Swing deck and H6/H7 messaging matrices.
Verified: Shared Drive discovery, metadata and export now work correctly. A separate copy-working document still needs a canonical link, and the Gemini Creative-call notes remain unshared.
Fireflies
Live nowReads meeting transcripts and filters them against the documented Creative meeting guide to capture asks, commitments and asset mentions.
Boundary: Only available transcripts and matching meetings can be used. Atlas separates operational actions from learnings.
Omaze DE performance data
Live analysisAnswers questions across Creative assets, spend, revenue, conversions, CAC, ROAS, houses, events, channels, CRM, cohorts and LTV.
Strength: Atlas uses current data together with house-cycle, attribution and operational context so the answer is useful, not just numerically correct.
GitHub + context vault
Live nowA Git-backed, curated context vault holds source summaries, house hubs, action candidates, meeting operations and learnings with evidence links.
Boundary: It is a curated layer, not a raw mirror of every message, comment or transcript.
Scheduled tasks + automations
Build + runCan design, build and maintain scheduled tasks, event-driven automations and reusable workflows that operate across authorised platforms.
Default: Atlas should define the trigger, permissions, approval gates, verification and delivery clearly before enabling a workflow.
n8n
Source accessCan read Exactius n8n workflow definitions and execution history to understand existing triggers, node logic, mappings and platform dependencies.
Boundary: n8n is source material for porting. Atlas rebuilds approved workflows as scheduled tasks and automations rather than treating n8n as the default runtime.
Cowork plugins repo
Source accessCan read the private Exactius/cowork-plugins repo and use its user-created skills as source material for new Atlas capabilities and automations.
Boundary: Preserve the skill’s intent, safety rules and judgment. Port it into Atlas/Hermes rather than silently changing behavior.
Shareable pages
Public + secureCan publish approved reports, dashboards and static artifacts as either public links or secure Exactius pages protected by email one-time PIN access.
Choice required: Atlas confirms public versus secure before publishing. Secure pages use an approved email/domain allowlist and have no public origin bypass.
Source hierarchy matters. If Slack says “approved” but ClickUp still says “in partner approval,” Atlas should flag the conflict—not silently overwrite the ClickUp status.
05 · Practical use
What the Creative team can ask right now
Start with the question you need answered. Atlas can locate the relevant work, query the current data, compare the right periods and explain what the evidence means.
01
Find the work and reconstruct the story
Locate the relevant ClickUp tasks, Figma frames, Frame.io assets, documents, meetings and team discussions, then explain what changed and what remains unresolved.
02
Choose Creative worth repeating
Compare videos, static assets, messages and treatments using delivery scale, spend, FTBs, CAC, ROAS and LTV. Separate high-volume winners from efficient small samples and include preview links.
03
Compare houses and campaign phases fairly
Compare the current house or BV with equivalent stages from previous campaigns, accounting for duration, spend, house-cycle position and other differences that would make a simple calendar comparison misleading.
04
Investigate Creative fatigue
Check whether performance movement looks like fatigue, weak delivery, audience or channel mix, campaign timing, attribution restatement or an early sample that needs more time.
05
Understand themes, formats and messaging
Analyse visual treatment, prize composition, urgency, layout, copy combinations, influencer content and video type, with the paired evidence needed to support each pattern.
06
Review house-wraps and Creative decks
Check a deck against current data, reconcile the arithmetic, add missing context and turn unsupported conclusions into clearer findings and testable next steps.
07
Create comprehensive reports and pitch decks
Combine live performance, historical context, assets, team learnings, tasks and decisions into a polished Creative review, campaign retrospective, client presentation or pitch deck.
08
Prepare meetings and decisions
Create a pre-read or decision brief showing what changed, what the data says, the strongest examples, open questions, dependencies and the decisions required from the room.
09
Connect analysis to the work
Turn an approved recommendation into a ClickUp update, task draft, team handoff or follow-up report, then verify the saved result instead of leaving the insight stranded in a chat.
10
Keep useful workflows running
Turn a repeatable review, status check or reporting process into a shared skill or scheduled workflow so the team receives the same quality of analysis consistently.
06 · Complementary tools
Atlas and Claude on your computer
Claude is a powerful personal collaborator. Atlas is a context-rich team collaborator that can research, analyse, create and deliver from information already connected to it.
| Area | Atlas | Claude on your computer |
|---|---|---|
| Starting point | Begins with the team’s shared context, connected sources and current work. | Begins with the conversation, files, project and services available in that person’s session. |
| Data questions | Can retrieve the relevant business meaning, query current data, check the result and explain the commercial decision it supports. | Can analyse powerfully when the user supplies or connects the right data and explains the needed context. |
| Creative context | Already connects assets, tasks, campaigns, meetings, approvals, performance and prior learnings across the team. | The user normally gathers and introduces the relevant material for that piece of work. |
| Reports and decks | Can research, reconcile and analyse the material before producing a comprehensive report, dashboard or pitch deck. | Excellent for drafting and design from the material available in the local session. |
| Collaboration | Multiple teammates can use and improve the same shared understanding and reusable capabilities. | Primarily supports the individual operating the local session. |
| Continuity | Retains useful team context, corrections and workflows across sessions. | Continuity depends on that user’s projects, sessions and setup. |
| Moving work forward | Can connect the result to shared tasks, reports, follow-ups and recurring workflows. | Best suited to interactive personal work unless the user separately shares or operationalises the result. |
Personal workspace, shared teammate
Use Claude locally for exploration, drafting, coding and focused personal work. Use Atlas when the answer should draw on team context and current data, become a shared report or deck, or continue moving through the team’s workflow after one person closes their computer.
07 · Capability map
What Atlas can do for Creative today
| Capability | State | What that means |
|---|---|---|
| Creative operational context | Live now | Connects tasks, assets, reviews, approvals, deadlines, meetings and team requests with source links. |
| Creative performance analysis | Live now | Compares Meta ads and banners by asset, format, theme, house and campaign phase using delivery, conversion, CAC, ROAS and LTV evidence. |
| Broader Omaze DE analysis | Live now | Answers wider questions across spend, revenue, channels, platforms, houses, events, CRM, cohorts, subscriptions, cross-sell and attribution. |
| Creative fatigue and repeat analysis | Live now | Separates scale from efficiency, checks sample strength and investigates competing explanations before recommending what to repeat or test. |
| House-wrap and deck review | Live now | Reconciles presentation claims with current data, source material, attribution and campaign-stage context. |
| Comprehensive reports and pitch decks | Live now | Creates polished Creative reviews, retrospectives, pre-reads, dashboards and shareable presentations from context plus current data. |
| ClickUp work management | Read + write | Can find, draft, create and update work with confirmation and saved-result verification where needed. |
| Figma review evidence | Scope varies | Reads authorised files and authored comments where the connected account has access. |
| Frame.io asset and comment retrieval | Live now | Finds authorised video assets, folders and authored comments and connects them to the wider workflow. |
| Meeting and deck learnings | Live now | Turns approved meeting and deck evidence into structured learnings, hypotheses and next checks. |
| Scheduled reviews and reporting | Live now | Can run approved recurring checks and reports with clear delivery and verification. |
| Broader team and partner coverage | Expanding | The same approach can extend as additional partner context, sources and team workflows are deliberately onboarded. |
08 · Help shape Atlas
What else should Atlas help with?
Atlas grows around real team needs. If you have a repetitive task, a report you wish existed, a source that is hard to search, a workflow that keeps breaking, or an idea for how the team could work better, bring it to the R&D team. We can explore it with you and build the right capability into Atlas.
Bring R&D a need
Describe the outcome you want. You do not need to know what the technical solution should be.
Bring us a frustrating workflow
Show the R&D team the manual steps, duplicated work or recurring handoff that consumes your time.
Bring us a source
Suggest a system, document set or data product that would make Atlas’s context, analysis or execution more useful.
Bring R&D an idea
We can explore the value, access, safety and effort with you before deciding how to build it into Atlas.
You do not need to design the solution
Start with “I wish Atlas could…” or “Our team needs help with…” and bring that need to R&D. We will work with you to understand the workflow, investigate what is possible and build the strongest ideas into Atlas as new context sources, skills, reports, dashboards or automations.
09 · Start here
Example prompts to try
Ask the real question. Add the house, BV, comparison period or intended audience when you know it, and Atlas can establish the rest from the connected context and data.
“Which H7 BV videos are worth repeating? Compare scale, FTBs, CAC and LTV, include preview links, and separate strong evidence from small samples.”
Repeat decision“Compare H7 static Creative with the previous three houses at equivalent campaign stages. Explain which themes and treatments performed differently and what we should test next.”
House comparison“Investigate whether these assets are showing Creative fatigue. Check delivery, frequency, audience and channel mix, campaign stage, recent performance and sample strength before concluding.”
Fatigue investigation“Review this house-wrap deck against the current data. Correct the arithmetic, attribution and unsupported conclusions, then suggest clearer findings and next tests.”
Deck review“Create a comprehensive Creative performance report for the last complete house cycle. Combine live data, assets, team learnings, operational movement and the decisions needed next.”
Creative report“Build a client-ready pitch deck showing the strongest Creative learnings, current performance evidence, representative assets and the next opportunities.”
Pitch deck“Prepare a five-minute pre-read for tomorrow’s Creative meeting: what changed, what the data says, the strongest asset examples, open questions and decisions required.”
Meeting pre-read“Find the source tasks, Figma frames and Frame.io assets for H7 BV3, then connect each item to its current status and available performance evidence.”
Asset and status map“Analyse which visual, messaging and format themes separate the strongest and weakest H7 static assets. Keep the paired spend, FTB and CAC evidence with each finding.”
Theme analysis“Turn the approved recommendations from this analysis into proposed ClickUp follow-ups with evidence, ownership and next checks. Show me the drafts before creating anything.”
Analysis to action“I was away for three days. Summarise what changed in Omaze DE Creative, grouped by house and phase, and include any performance movement that changes the priority.”
Missed context“Create a recurring weekly Creative review that combines status, new learnings and material performance movement, and only surfaces items that need the team’s attention.”
Recurring reviewCurrent capability. Atlas combines authorised Creative sources, shared operational context and current Omaze DE performance data. For time-sensitive questions it re-checks the relevant sources before answering.