Coordinated

Fictional example · Atlas. These product cards illustrate the manually delivered pilot workflow, not the Lantern simulator results.

In the pilot today

Use cases / Northgate · Atlas launch

Six moments when the record has to move before the work does.

Memory can recover what people said. These cards show what each person was asked to accept, the source sentence behind it, and what stayed on record after the answer.

← Back to the homepage

Fictional example · Atlas

01 · A date slips

“Staging slipped to Saturday. Who needs to know before Sarah's spend locks Tuesday at 5?”

Sarah is asked: her announcement needs ten calendar days after staging and Sat Oct 10 leaves five. Marco is informed: his Acme condition still holds by one business day. Nadia decides; the forecast is on record either way.

CoordinatedAPP

Staging may slip: Thu Oct 1 → Sat Oct 10

Maya's forecast, not yet a change. Nadia decides.

Your announcement (Thu Oct 15) needs ten calendar days after staging; Sat Oct 10 leaves five.

Your campaign spend locks Tue Oct 6, 5:00 PM.

  • Launch plan ¶7 · ten days after staging
  • Delivery notes, line 11 · Acme rollout Thu Oct 15
  • Spend lock · Tue Oct 6, 5:00 PM

Decided Tue Oct 6, 9:05 AM · 1 asked, answered · 1 informed · 0 pending · terms v2

What stays on record: the forecast, Nadia's decision, Sarah's answer, Marco's unchanged condition, and the source lines that connected them.

Fictional example · Atlas

02 · A scope changes

“Nadia removed self-serve import on Wed Oct 7. Which promises now need an answer?”

Sarah is asked because the launch announcement names the import. Marco is asked because the Acme rollout includes it. Dana is informed because the support guide no longer needs the import path.

CoordinatedAPP

Atlas scope changed: self-serve import removed

Nadia decided. Your Thu Oct 15 announcement currently names the import.

Marco's Acme rollout also includes it. Dana's Mon Oct 12 support guide no longer needs it.

  • Launch plan ¶4 · self-serve import in scope
  • Acme notes, line 8 · import workflow Thu Oct 15
  • Support brief ¶3 · guide due Mon Oct 12

Decided Thu Oct 8, 11:20 AM · 2 asked, answered · 1 informed · 0 pending · scope v2

What stays on record: the removed scope, both affected promises, each answer, and the support artifact no longer required.

Fictional example · Atlas

03 · An owner leaves

“Maya is out through Fri Oct 16. Who owns the staging decision due Thu Oct 8?”

Nadia is asked to name temporary authority. Josh is informed because the launch cannot move without that decision. No replacement is inferred; ownership stays unseen until a person accepts it.

CoordinatedAPP

Staging authority needs an owner by Thu Oct 8, 2:00 PM

Maya is unavailable through Fri Oct 16. Coordinated cannot see a named replacement.

Nadia is asked to name authority. Josh is informed.

  • Review notes ¶6 · Maya owns staging readiness
  • Atlas terms v2 · decision due Thu Oct 8, 2:00 PM
  • Team update · Maya unavailable through Fri Oct 16

Recorded Wed Oct 7, 4:40 PM · Josh accepted interim authority · 0 pending · ownership v2

What stays on record: the unavailable owner, the authority gap, who named the temporary owner, and when Josh accepted.

Fictional example · Atlas

04 · A promise is made to a customer

“Marco promised Acme a Thu Oct 15 rollout. Does the current plan support it?”

Marco is asked to confirm the condition. Nadia decides whether it becomes part of the Atlas terms. Sarah is informed because her announcement uses the same rollout date.

CoordinatedAPP

Acme promise proposed: rollout Thu Oct 15

Marco posted the date. Nadia decides whether it enters the Atlas terms.

Sarah is informed because the announcement uses Thu Oct 15.

  • Acme thread · rollout Thu Oct 15
  • Launch plan ¶7 · staging Sat Oct 10
  • Announcement brief · publication Thu Oct 15, 8:00 AM

Accepted Mon Oct 5, 2:10 PM · customer term recorded · Marco owns the update · terms v2

What stays on record: Marco's promise, Nadia's acceptance, the condition that qualifies it, and Sarah's linked announcement.

Fictional example · Atlas

05 · An assumption comes due

“The rollout assumes legal approval by Mon Oct 12. What happens if it is not in?”

Nadia is asked to decide before the approval window closes. Sarah and Marco are informed because their Thu Oct 15 work depends on the answer. The record labels legal approval unseen until someone posts it.

CoordinatedAPP

Approval assumption comes due Mon Oct 12

Legal approval is not visible in the record. Nadia decides what happens if it is not posted.

Sarah and Marco are informed; their Thu Oct 15 work depends on the answer.

  • Atlas assumptions ¶2 · legal approval Mon Oct 12
  • Campaign brief · spend starts Tue Oct 13, 9:00 AM
  • Acme notes · rollout Thu Oct 15

Answered Fri Oct 9, 3:30 PM · condition added · review Mon Oct 12, 9:00 AM · 0 pending

What stays on record: the assumption, its due date, what was not visible, Nadia's condition, and each affected owner.

Fictional example · Atlas

06 · A review starts

“What is already settled before the Tue Oct 13 review?”

The staging forecast is decided, the import is out of scope, Marco's customer condition is recorded, and every affected owner has answered. The brief opens with the remaining decision, not a reconstruction.

CoordinatedAPP

Atlas review brief: 3 changes settled

Staging is Sat Oct 10. Self-serve import is out. Acme's Thu Oct 15 condition remains accepted.

One legal approval condition is due for review at Tue Oct 13, 9:00 AM.

  • Atlas terms v2 · accepted Thu Oct 8, 11:20 AM
  • Owner responses · through Mon Oct 12, 4:15 PM
  • Review brief · generated Tue Oct 13, 8:00 AM

Review opened Tue Oct 13, 9:00 AM · 3 changes settled · 0 decisions reconstructed

What stays on record: the accepted terms, the source for every change, all answers, and the one condition still requiring a decision.