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
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
}The problem
Structure, interface and rules describe the same work from different angles. Without their connections, moving one date looks like permission to move every date.
The idea
Keep the levels connected and the responsibilities distinct. A source date can feed a working view without touching what the audience has already been told.
How it is built
The source feeds the working and curated dates. Publication is a review boundary, not another update edge.
Read the diagram as text
A manual source dated 26 June feeds the working dates and a curated view, which can inherit that date or keep its own. Reaching the audience copy means passing a review step, and that step has not been taken: the existing copy still reads 19 June.
Diamonds are decisions. Indigo marks the path that matters. Scroll across to see all of it.
Scope
Atlas maps a selected design foundation rather than shipped product behaviour. People and dates are fictional fixtures, and the date change here is a local rehearsal: no audience update is published and the supplier payment is untouched.