Atlas
See the whole. Understand the change.
A connected map of Signal Studio: from the suite, to a project, to the process behind a feature.
All four filmsThe familiar problem.
Suite structure, project wireframes and process rules can describe the same work from different angles. Without their connections, a simple date change can be mistaken for permission to update a client-facing timeline or a separate payment milestone.
A different approach.
Keep the levels connected and the responsibilities distinct. A canonical Project gives the work a home; a Timeline gives it a view; the process explains which source each view uses and when a reviewed audience update is required.
A view of the structure. A reason for the change.
Atlas connects architecture to a recognizable project. The suite map leads to a wedding Project, the wireframe leads to its Timeline process, and a Ceremony date change shows why internal working dates and an audience-facing commitment cannot be treated as the same thing.
Find the right level
Move from the suite to a project and into the process behind its Timeline.
Read the relationship
Connect the interface to the Mermaid source that explains its working and audience views.
Keep commitments clear
Show what changes internally and what still needs review before the audience copy changes.
Under the surface.
This focused Mermaid process comes from the selected F2 architecture and its Timeline publication rules. The manual source feeds working dates and a curated timeline; the audience copy needs a deliberate reviewed publication action. The diagram shows the supplied 26 June source and 19 June audience copy. The film separately rehearses changing the source to 28 June, leaving the audience copy unchanged.
Read the diagram source
flowchart LR
S["Manual source<br/>26 June"] --> W["Working dates<br/>Projection"]
S --> C["Curated view<br/>Inherit / override"]
C --> R{"Review"}
R -. "Review required" .-> P["Existing copy<br/>19 June"]
classDef source fill:#F4F6FC,stroke:#5146D9,color:#171B2D,stroke-width:2px
classDef ordinary fill:#FFFFFF,stroke:#B8C0D6,color:#171B2D,stroke-width:1.5px
classDef gate fill:#5146D9,stroke:#5146D9,color:#FFFFFF,stroke-width:2px
class S,P source
class W,C ordinary
class R gateExplore the system responsibilities
- Suite foundation
- The selected F2 foundation maps Home, Projects, Notes, Tasks and Timeline. Atlas sits outside that customer navigation as an internal architecture tool; navigation lines do not imply inherited permissions.
- Canonical Project
- W1, Mara and Finn’s wedding, is the concrete project context. The source wireframe opens in Tasks and the film drills into its Timeline.
- Working dates
- Authorized source records supply this working projection. A source-date change updates its corresponding working date.
- Curated timeline
- A curated item may inherit its source date, use an explicit display-date override, or intentionally have no date. Curated display does not rewrite the source.
- Current audience copy
- The published Timeline item is separate copied content. The current Ceremony date stays 19 June until a deliberate reviewed publication action replaces it.
- Mermaid and scenario
- The readable diagram derives from canonical architecture sections 3 and 6. The film rehearses 26 to 28 June in the source; its inherited internal view follows, the audience copy and supplier payment stay fixed, and publication remains pending review.
Read the film, without motion
Where does a feature belong, what does it depend on, and what changes with it? Start with Signal Studio’s selected design foundation, inspect a Project and Timeline wireframe, then follow the Mermaid process into a date-change scenario. A one-minute internal architecture showcase; the audience update remains pending review.
A small change. Who else is affected?
A small change. Who else is affected? See the consequences.
Connected work
Every change touches people, processes and decisions.
Find the consequences
One small request can have more than one consequence.
Suite, project and process
Atlas connects the suite, project and process so we can follow the effect of a change.
From the suite to a Project and Timeline
Start with Signal Studio’s selected design foundation. Drill into a canonical Project and its Timeline.
Inspect the project wireframe
Inspect the project wireframe. Working dates, curated timelines and the current audience copy have different jobs.
Read the actual process
Follow the Mermaid process. Source dates inform internal views; an audience copy requires a separate reviewed update.
Rehearse a source-date change
Rehearse changing the internal source from 26 to 28 June. The audience copy stays 19 June and payment stays 1 June. An audience update still needs review.
Three levels. One connected view.
Clear structure, ownership and consequences. Three levels, one connected view.
See the whole. Understand the change.
Atlas. See the whole. Understand the change. An internal Signal Studio project.
The thinking behind it.
Personal project · Product direction, architecture mapping, process modelling, engineering and motion design.
An architecture map should explain both where a feature belongs and what changing it would affect.
Why this approach
A diagram becomes more useful when it leads to the interface and the rule behind the interface. Connecting the selected foundation, wireframe and process makes ownership and dependencies discussable, while preserving the distinction between an internal working change and a reviewed external commitment.
How it works
Follow Mara and Finn’s wedding project into its Timeline, inspect the wireframe and Mermaid process, then rehearse a date change. Working dates, curated timelines and the current audience copy keep their separate jobs.
Atlas connects Signal Studio’s selected F2 design foundation, dated 12 September 2026, to an illustrated read-only wireframe for the canonical Project W1, Mara and Finn’s wedding. The film moves from the suite into the Project and its Timeline, then follows a Mermaid process derived from the foundation’s architecture and publication rules. In the declared scenario, the manual Ceremony source moves from 26 to 28 June 2027. Working dates and an inherited curated date follow that source; the current audience copy stays 19 June and the supplier payment stays 1 June. A reviewed audience update remains pending.
Why it matters
See where work belongs, which information a view depends on, and where a change needs a separate review before anyone builds or publishes it.
Scope, boundaries and trade-offs
The boundary
F2 is the selected design foundation, not implemented product behaviour, customer validation or a claim that the current app has been migrated. People and dates are fictional fixtures. The wireframe is an illustrated read-only source view, and the date edit is a declared scenario. It does not publish an audience update or change the payment milestone. The separate copied-Timeline publication rule must not be generalized to live Task shares or live published Projects.
The trade-off
The curated map makes a selected contract easier to inspect, but its references need maintenance as the design changes. Inherit, explicit override and intentionally undated are different states. A source record and a published Timeline copy must keep their separate identities. Missing links still need investigation, and a passing local scenario is not proof of production authorization or concurrency behaviour.
An internal date changes
Make the source change visible in the working context. Keep the current audience copy intact and show that its proposed update still needs review.
A curated date has an explicit override
Retain the override rather than replacing it with the new source date. An intentionally undated item should also stay undated; neither state means that the source field is missing.
A payment milestone sits near the changed date
Keep its identity and responsibility separate. Visual proximity does not make a payment milestone depend on a working source date.
The selected foundation differs from the current app
Label the foundation as a selected design and the interface as a read-only wireframe. The map helps discuss implementation; it does not certify that migration has happened.
A relevant relationship is missing
Review the source references and add the missing relationship explicitly. The scenario describes its declared scope, not an automatic audit of the whole system.
What this demonstrates. Selected F2 foundation, 12 September 2026 · source Project W1 wireframe with fictional fixtures · Mermaid diagram derived from canonical architecture sections 3 and 6 · declared date-change scenario · audience review pending, no publication applied · no current-app migration claimed.