Atlas
Follow the question.
A connected map of the organisation, its tools and the processes behind the work.
- Role
- Designed and built, start to finish
- Status
- Internal project
- Area
- Architecture and process
The problem
A reminder that never arrives looks like a bug. Finding out means knowing who owns that behaviour, where it is built and which rule made the decision. Those answers usually live in three different places.
The idea
Map the people, tools and processes as one connected system. Start from a question and follow it down through each layer until you reach the rule that answers it.
How it is built
Atlas connects eighteen AI roles, sixty-nine tools and 345 process records. Each process keeps its owner, its tools and its source together, so a rule can be read as a map and as the Mermaid source it comes from.
Read the diagram as text
A person asks for a nudge. Atlas resolves the context and checks access. The next decision asks whether the reminder is for someone else. When sender and recipient are the same person, the process stops deliberately and no notification is saved. For someone else, it checks the request is new and saves one notification.
Diamonds are decisions. Indigo marks the path that matters. Scroll across to see all of it.
An earlier Atlas study
Move a date.
See what follows.
Try the ceremony date. The working view follows the source. What about the timeline your guests already have?
Working and inherited dates are 26 June. The audience copy is 19 June; payment is 1 June.
Inspect the state and rules
Publication is a review boundary, not another update edge.
{
"sourceId": "manual:wedding-main:ceremony-example",
"source": "2027-06-26",
"working": "2027-06-26",
"curated": "2027-06-26",
"audience": "2027-06-19",
"payment": "2027-06-01",
"affected": [
"source",
"working",
"curated"
],
"held": [
"audience",
"payment"
],
"review": "not requested",
"revision": 0
}Scope
Atlas is an internal Signal Studio project. The film and diagram use its authored demonstration model, not deployed workflow claims. The self-nudge and parent-task guards were established from source; access, duplicate and inbox rules are proposed. The date study below is an earlier Atlas rehearsal with fictional fixtures.