01
Do and verify the work
Atlas gathers evidence, completes the request and checks the real result before treating an approach as proven.
01 · Purpose
What Atlas is
Atlas is a shared digital teammate: an agent that retains operational context and can use it to help teams understand what is happening, decide what to do next and move work forward.
It connects knowledge across approved sources, keeps that understanding current and turns context into practical action. Atlas can answer questions, generate reports, analyse patterns, work across connected platforms, create artifacts and build or run reusable workflows.
Atlas is currently built around Omaze DE as its first partner context. Creative is the deepest adoption lane today, while PM, leadership reporting, Performance, Data Analytics and Data Science are the next parts of the connected operating model.
Context that can act
Atlas combines persistent team knowledge with execution. It should ground its work in evidence, state uncertainty, respect source authority, verify consequential actions and improve from useful feedback.
02 · Self-improvement
Teach Atlas once. Reuse and automate the workflow.
Atlas can turn a proven process, or a useful correction from the team, into shared context or a reusable skill instead of 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 a reusable skill.
03
Learn from team interaction
Teammates can correct stale context, explain a convention or provide a missing source. Atlas preserves durable, relevant information with provenance and uncertainty.
04
Reuse and improve it
Future sessions can use the corrected context and improved skill, so good work compounds instead of being rebuilt from scratch.
05
Automate only when approved
A skill can be used on demand or connected to a schedule or event. Creating a capability does not automatically authorise writes or enable automation.
Memory
Stable facts, preferences, access details and standing boundaries.
Context vault
Shared operational knowledge, decisions, partner context, evidence, learnings and declared gaps.
Skills
Reusable execution playbooks describing how Atlas performs a workflow safely and consistently.
Automations
Approved skills connected to schedules or events so useful workflows can run reliably.
Teach Atlas through conversation
Tell Atlas what is wrong, explain the missing context or give it a source. Atlas can preserve the durable part while distinguishing teammate-provided context from independently verified evidence.
Bring new capability needs to R&D
Describe the outcome or frustrating workflow. R&D can inspect existing Cowork skills, Atlas capabilities and automations, then evaluate the value, access, safety and architecture before building.
Exactius capabilities already available
These are built around real Exactius workflows, not generic chatbot features.
Partner-context ingestion
ActiveTurns approved meetings, decks, channels and operational sources into curated partner context, decisions and learnings.
Purpose: Preserve what the business knows, not just where the information lives.
Operational monitoring
ActiveChecks authorised work surfaces for status movement, dependencies, approvals, requests and exceptions.
Current depth: Strongest in Omaze DE Creative and expanding into wider operations.
Executive reporting
AvailableCombines partner context, recent movement, decisions, dependencies, learnings and data cuts into reviewable reports.
Boundary: Non-creative data conclusions remain qualified until the semantic layer is mature.
Brief and document workflows
AvailableCreates briefs, pre-reads, recaps and structured documents, including guarded write-back into approved templates.
Safety: Structural dry-runs and approval gates apply to consequential writes.
Workflow porting
AvailableInspects Cowork skills and n8n workflows, understands intent and dependencies, and adapts approved methods into Atlas.
Purpose: Reuse good work while preserving provenance and safeguards.
Public and secure publishing
AvailablePublishes approved reports, dashboards, onboarding guides and static artifacts as public or access-controlled pages.
Safety: Atlas confirms visibility and reviews content before publishing.
03 · Current understanding
What Atlas understands today
Atlas is not a general archive of every Exactius client or system. Its deepest context is currently Omaze DE, with deliberate expansion by partner, lane and source.
Exactius foundation
Company roles, working conventions, recurring forums, shared methods and the boundaries between Atlas, Cowork and specialist systems.
Omaze DE fundamentals
Partner structure, objectives, team relationships, recurring meetings, core work surfaces and important operational language.
Creative operations
The deepest live lane: workflows, campaigns, tasks, assets, approvals, source authority, creative performance and team feedback.
Weekly learnings
Meeting and deck evidence transformed into structured learnings, open hypotheses, confidence and next checks.
Executive context
Current priorities, material movement, relationship signals, decisions, dependencies and decision-grade open loops.
People and ownership
Who people are, what they own, which workflows they support and identity details needed to avoid mixing up similar names.
Source authority
Which system answers which question, what is evidence versus status, and how conflicts should be surfaced instead of silently resolved.
Live operational state
Recent changes, blockers, deadlines, approvals and requests from authorised sources, with links and explicit uncertainty.
Declared gaps
Missing access, incomplete semantic definitions and areas where team or specialist validation is still required.
04 · Connected systems
Access today, with the real limits
“Connected” does not mean “everything.” Atlas can only use the accounts, channels, files, projects, datasets and permissions that have been deliberately authorised.
Slack
Live nowConversational access plus authorised shared-channel history and scheduled ingestion for selected operational sources.
Boundary: Channel membership and ingestion scope are separate. Slack signals do not silently override canonical systems.
ClickUp
Read + writeReads authorised boards, tasks, comments and docs. Can create, edit, assign, move and comment when the workflow permits.
Boundary: ClickUp remains authoritative for task state. Ambiguous or consequential changes require confirmation and read-back.
Google Workspace
Live nowUses the Atlas account to read authorised Drive, Docs, Sheets, Slides, Gmail and Calendar sources.
Boundary: Access is file- and account-specific. A missing link or share remains a real gap.
Fireflies
Live nowReads available meeting transcripts and uses speaker-attributed evidence for context, actions and learnings.
Boundary: Missing transcripts stay missing. Atlas does not fabricate meeting evidence.
Figma + Frame.io
Scope variesReads authorised design/video projects, files and authored comments where the connected account has access.
Boundary: Asset and comment access varies by project. Comment language is evidence, not automatically formal approval.
BigQuery
Read-onlyCan run bounded read-only analysis against the governed creative-performance scope already connected for Omaze DE.
Gap: Broad analysis waits on Data Analytics context, semantic definitions and specialist validation.
GitHub + context vault
Live nowA Git-backed curated vault holds source summaries, context layers, decisions, learnings, evidence and system rules.
Boundary: It is curated operational context, not a raw mirror of every message or transcript.
Scheduled tasks + automations
Build + runCreates durable scheduled or event-driven workflows across authorised platforms with explicit delivery and verification.
Default: Trigger, ownership, permissions, failure behavior and approval gates should be clear before enabling.
Cowork skills + n8n
Source accessInspects existing skills and workflow definitions so approved methods can be reused instead of rebuilt.
Boundary: Preserve provenance, intent and safeguards. Atlas-specific runtime adapters stay separate where appropriate.
Shareable pages
Public + securePublishes approved reports, dashboards, diagrams, decks and onboarding artifacts as stable browser links.
Choice required: Public versus secure visibility is confirmed before publishing.
Access is not understanding. A connected API or table does not by itself provide the operational meaning, grain, attribution, freshness or exceptions needed for reliable conclusions.
05 · Practical use
What teams can ask Atlas right now
Good requests name the partner, workflow, source, audience or time window. Atlas can still help when these are missing, but should ask or label assumptions instead of guessing.
01
Find context and source material
Locate the task, document, meeting, decision, asset, thread or prior learning and return the best available evidence links.
02
Reconstruct what changed
Summarise movement over a time window across authorised sources, including conflicts, missing evidence and unresolved decisions.
03
Prepare meetings and decisions
Create a pre-read, agenda, status brief or decision memo with the relevant history, owners, dependencies and open questions.
04
Coordinate tasks and follow-ups
Check for existing work, draft tasks or updates, propose ownership and dates, and apply approved changes with verification.
05
Generate reports and artifacts
Produce executive reports, operational summaries, decks, onboarding pages, dashboards and secure shareable artifacts.
06
Analyse bounded performance questions
Use governed data scopes and definitions where available, state attribution and freshness, and separate observed associations from causal claims.
07
Build scheduled tasks and automations
Turn a recurring workflow into a skill and approved automation with clear sources, permissions, checks, failure behavior and delivery.
08
Collaborate and correct shared context
Work with Atlas in a team thread, add missing conventions, correct stale facts and preserve durable context for future conversations.
09
Reuse existing Exactius methods
Find relevant Cowork skills or n8n workflows and recommend how to use or adapt them without duplicating capability.
10
Explore future execution loops
Bring R&D a repetitive decision or workflow where context, data, action and outcome measurement could become a bounded specialist agent.
06 · Complementary tools
Atlas and Claude on your computer
Atlas does not replace Claude Cowork or Claude Code. The useful distinction is between a persistent shared teammate and a local assistant helping one person with the work in front of them.
| Area | Atlas | Claude Cowork or Code |
|---|---|---|
| Role | A persistent digital teammate serving shared workflows. | An interactive assistant working with an individual in a local session. |
| Context | Maintains governed shared context across approved sources and interactions. | Primarily uses the current conversation, project, files and connected services. |
| Continuity | Retains team knowledge and reusable capabilities across sessions. | Continuity depends on the user’s sessions, projects and setup. |
| Execution | Works across authorised platforms and can coordinate durable team workflows. | Performs powerful user-directed work with local tools and connectors. |
| Automation | Can run approved scheduled and event-driven workflows. | Usually interactive unless automation infrastructure is separately configured. |
| Skills | Uses shared skills with context, permissions, approval gates and verification. | Uses personal or project instructions suited to the current work. |
| Best fit | Shared context, continuity, cross-platform execution and recurring operations. | Exploration, drafting, coding, prototyping and personal work. |
Personal workspace meets shared teammate
Use Claude locally when you want a powerful assistant beside you. Use Atlas when the work benefits from shared context, continuity, team-visible evidence, cross-platform execution or a workflow that should keep running.
07 · Capability map
Live now, partial and future potential
| Capability | State | What that means |
|---|---|---|
| Shared context retrieval | Live now | Answers from the curated Omaze DE context base and authorised source systems with evidence. |
| Creative operational support | Live now | The deepest current lane: status, assets, approvals, tasks, meetings, requests and bounded performance analysis. |
| Meeting and deck learnings | Live now | Turns approved meeting/deck evidence into structured learnings, confidence and next checks. |
| Task and document workflows | Live now | Can draft and, where authorised, create or update work with approval and verification. |
| Executive and operational reporting | Live now | Creates Slack summaries and polished secure/public report artifacts on demand. |
| Scheduled tasks and automations | Live now | Builds and runs approved workflows with explicit ownership and delivery. |
| Skill reuse and porting | Live now | Inspects Cowork and n8n sources, preserving intent, provenance and runtime boundaries. |
| Broad Performance analysis | Partial | Some data is accessible, but deeper operational and semantic context is still being integrated. |
| Data Analytics integration | In progress | The target is a governed semantic/query layer Atlas can call for reliable analysis. |
| Data Science integration | Next | DS workflows, model context and safe handoff points still require domain engagement and design. |
| Closed execution loops | Future | Specialist agents can eventually detect, diagnose, recommend, execute, measure and learn within bounded workflows. |
| Additional partners | Future | Reuse the company and squad foundation with deliberately onboarded partner-specific context and permissions. |
08 · Help shape Atlas
What else should Atlas help with?
Atlas grows around real needs. Bring R&D a repetitive task, a report you wish existed, a source that is hard to search, a workflow that keeps breaking or a decision loop that could improve with better context.
Bring R&D a need
Describe the outcome you want. You do not need to know the technical solution.
Bring us a frustrating workflow
Show the manual steps, duplicated work or recurring handoff consuming the team’s time.
Bring us a source
Suggest a system, document set or data product that would improve context, analysis or execution.
Bring R&D an execution loop
Identify where the team repeatedly observes, decides, acts and measures. That may be a candidate for a specialist agent.
You do not need to design the solution
Start with “I wish Atlas could…” or “Our team needs help with…” R&D will explore value, access, safety and effort before building the strongest ideas into shared context, skills, reports, integrations or automations.
09 · Start here
Example prompts to try
Copy one, then add the partner, workflow, audience or time window. Atlas should answer with evidence and flag uncertainty.
“I was away for three days. Summarise what changed across my authorised work, grouped by priority, with owners, source links and unresolved questions.”
Missed context“Prepare a five-minute pre-read for tomorrow’s meeting: relevant history, movement since the last meeting, decisions needed, dependencies and open questions.”
Meeting preparation“Find the current source of truth for this workflow, explain what each system is authoritative for and flag any conflicting evidence.”
Source authority“Check whether this action already has a ClickUp task. If not, draft the task, owner, due date and evidence, then wait for approval before creating it.”
Controlled task creation“Turn this thread into a decision-ready summary: options, trade-offs, evidence, dependencies, owners and the next decision.”
Decision support“Create a concise status report for leadership using the current partner context. Separate confirmed movement, hypotheses, missing data and decisions needed.”
Executive reporting“List the Cowork skills, Atlas capabilities and n8n workflows relevant to this request. Recommend what to reuse before proposing anything new.”
Capability discovery“Design a scheduled workflow that checks this source every weekday, surfaces only material changes and drafts an update for review. Show the plan and dry-run before enabling it.”
Automation design“That context is out of date. Here is the correction and its source. Update the shared context, explain what changed and preserve the provenance.”
Correct shared context“Analyse this performance question using only the governed data scope. State the grain, attribution, freshness and missing dimensions before giving conclusions.”
Bounded data analysis“Publish this approved report as a secure Exactius page. Show the final recipient allowlist and verify there is no public origin.”
Secure artifact publishing“Our team repeatedly does this workflow manually. Help me describe the trigger, decisions, actions, outputs and measures so R&D can evaluate it as an Atlas capability.”
Capability intakeHow this guide was grounded. The content reflects the live Atlas architecture, current Omaze DE context, observed adoption, connected-system boundaries, existing Exactius skills and the current Performance/Data integration plan. Access and source freshness can change; Atlas should re-check before answering time-sensitive questions.