ATLAS · INSTRUCTIONS Published · v2
A clear answer.
In the right context.
Section 04 / Escalation guidance
If a case is unclear, flag it for review before continuing.
Knowledge Companion by mindsparx
Clear instructions.
Aligned teams.
Keep every project working from the same instructions. One place to find current guidance, resolve questions and see exactly what changed.
For agencies, data operations teams and their clients.
A clear answer.
CLIENT CLARIFICATION · LINKED TO SECTION 04
“Yes, flag the case first. We’ll confirm the next step in this thread.”
Fictional example · no customer information
Built around the work, not another chat feed.
- Current instructions
- Questions in context
- Reviewed changes
One project. A clear next step.
Less searching.
More knowing what to do.
Switch roles in the example below. Everyone shares the same workspace, with actions matched to their responsibilities.
Example projectAtlas — Search Relevance
Your next step
Operator · Read, ask and acknowledge.
Review the updated escalation rule
Section 04 changed in v2. Read the update before acknowledging it.
Your question has a reply
“When should I flag an unclear case?” · Section 04
Interactive illustration · fictional data · nothing is savedOperator = freelancer. No project or user administration.
Operator example: home. Fictional data only.
A shared way of working
From a document
to a team that understands it.
Keep the instruction, the question and the decision connected.
01
Bring guidance together.
The project manager uploads approved instruction files. The team reads the published release and searches within the project.
02
Resolve the uncertainty.
Ask about a specific section. Route questions to the right reviewer and keep the clarification alongside its context.
03
Make the change visible.
Review and publish an updated release. Show people what changed, what they need to do, and what they have acknowledged.
Clear boundaries, not blanket access
The right context.
For the right people.
Instructions belong to a project. Access belongs to a role. Publishing a change remains a deliberate human decision.
Open your workspaceProject-scoped permissions
Admins manage project roles. PMs can invite Clients and Operators to projects they manage. Clients and Operators do not manage other people’s access.
Private source files
Original documents stay in private storage. The workspace serves authorized readers a protected view, rather than a public source-file link.
A record of what changed
Versioned releases, acknowledgements and audit events help keep approved guidance separate from drafts and proposals.
Who can create and manage a project?
Admins, eligible project managers and assigned client reviewers can create projects within their organization. A client remains a client reviewer in a new project. Only Admins assign or change existing project roles; PMs may invite Clients and Operators to projects they manage.
Does it already provide AI answers?
Not in the current pilot. AI assistance with source citations is planned, but live model calls remain disabled. Today’s workflow centers on finding instructions, asking contextual questions and recording human-reviewed changes.
Can protected instructions still be copied?
Reader controls reduce casual copying and avoid exposing a public original-file link. They cannot guarantee that an authorized reader will never take a screenshot or reproduce visible information. Access controls and team agreements remain important.
Can we connect email or Slack?
Email invitations and share-link controls are implemented; live email delivery and acceptance still need verification. Automatic Slack notifications and an inbound Slack agent are later-phase features, not part of the current pilot.
Start with one project
Turn “where was that?”
into “here’s the next step.”
Explore a controlled pilot with synthetic or PM-authored instructions. Production source files and freelancer outputs are outside v1’s scope.
Discuss a pilot Opens your email app. No form tracking.