FORTUNE-OS / THE SHARED PICTURE Look what we’re building.. Every contribution leaves a light on. This is our city, together.
Some source details are incomplete. View coverage. Whole city 63 Web45 Native2 Agents platform6 API & apps9 Platform15
01 / THE CODE CITY The latest shift. 67 code places · all five districts Tap a district to explore up close.
Web 45 PRs 45 linkedNative 2 PRs 2 linkedAgents platform 6 PRs 6 linkedAPI & apps 9 PRs 9 linkedPlatform 15 PRs 15 linked #2719 PR route Touched code Known evidence across every district02 Nov, 16:24 UTC Latest captured state
1× Latest63 merged PRs
5 verified contributors
63 PRs with AI evidence
+18,543 lines added
−2,067 lines removed
One PR, one city total. Multi-district deliveries stop at every affected district.
THE CITY HAS MORE THAN ONE PULSEBehind the night shift↗ Tap a city utility. Follow its real signal.
Linear Planning station 63completed issues LAST 24 HOURS Captured Sentry Signal tower 401accepted error events LAST 24 HOURS Captured Latitude Machine yard 310engineering traces LAST 24 HOURS Captured AWS runtime Power station 19running tasks CURRENT CENSUS Captured 507 open issues CURRENT
116 created issues 24H CAPTURE
35 urgent issues CURRENT
2.6h cycle time · median 24H CAPTURE
Completed issues light the dispatch windows. Open and urgent work are the current engineering census; duplicate issues are excluded.
Captured 02 Nov, 16:18 UTC Period: 01 Nov, 16:18 — 02 Nov, 16:18 UTC
Whole-source signals stay at their latest capture while PRs replay. District filters do not narrow these utilities. Lit windows illustrate volume; the power station uses observed CPU. They are not a shared health or productivity score.
The delivery Code places City changesFRTNS-1642: Use the shared write wait in the floor-editor table update tests MERGE STATION → Web
Autopilot linked 1 linked run. 1/1 checkpoint records loaded. At least 1 observed session in this PR. Evidence of participation; the agent initiator is not inferred.
+4 −21 2 commits 3 pre-merge reviews 1 changed files
THE DEPARTURE BOARD 63 real deliveries
#271916:02 FRTNS-1642: Use the shared write wait in the floor-editor table update tests @fortune-developer · Web #269915:39 FRTNS-1317: Open the cabinet's customers list on the API @dsuranov · API & apps #264515:22 FRTNS-1610: Stop a printed Android receipt from being retried as a failure by pinning its outcome tags @fortune-developer · Platform / Native #270914:55 FRTNS-1709: Date imported Fortis collections by proven settlement and show their payment methods @fortune-developer · Web #266914:46 FRTNS-1625: Re-enable Send and Pay sooner after sending an order to the kitchen @fortune-developer · Web #271014:42 FRTNS-1640: Load the guest menu with one fewer database query per visit @fortune-developer · Web #270814:14 FRTNS-1667: Stop Kitchen Desk polls from redrawing unchanged ticket cards @fortune-developer · Web #270514:05 FRTNS-1638: Stop guest and public pages from downloading the staff app for offline use @fortune-developer · Web / Platform #266813:52 FRTNS-1624: Guard payment receipts against misprinting OMR and JOD amounts @fortune-developer · Platform #269713:25 CEP-108: Alert when loyalty sign-up WhatsApp verification codes stop going out @fortune-developer · Web #269313:23 FRTNS-1634: Guarantee a paid purchase never closes another business's open purchase @fortune-developer · Web #268913:23 FRTNS-1633: Prove a terminal charging in thousandths is refused before NI Push to Pay starts @fortune-developer · Web #268713:22 FRTNS-1632: Keep board reordering from reverting a cancelled, completed or sent order @fortune-developer · Web #268413:21 FRTNS-1631: Charge the terminal only what the order still owes and block other payments meanwhile @fortune-developer · Web #270113:08 MAINTENANCE: Keep review rules in line with the latest service and data standards @fortune-developer · Platform #267613:06 CEP-104: Explain base cashback and tier conflicts on the Loyalty page and keep the open tab in its link @fortune-developer · Web #270012:54 MAINTENANCE: Make unused devtools render report schemas private @fortune-developer · Platform #269012:10 FRTNS-1665: Ask unverified buyers for an emailed code before paying @fortune-developer · Web / Platform #267511:41 CEP-105: Show loyalty guests being moved to their tiers, with progress, on the Tiers tab @fortune-developer · Web #263711:07 CEP-101: Clean up abandoned Wallet design images automatically while keeping used ones @fortune-developer · Web / Platform #269510:52 FRTNS-1700: Stabilize the POS saved drafts count check @fortune-developer · Web #269410:51 FRTNS-1698: Keep the kitchen new-order sound working after a failed load @fortune-developer · Web #269210:51 FRTNS-1695: Keep business data order history reads within the database time limit @fortune-developer · Web #268810:49 FRTNS-1694: Stop offline cart test from hanging on restored writes @fortune-developer · Web #269610:43 FRTNS-1317: Let SmartPOS terminals take card payments again @dsuranov · API & apps #268610:05 FRTNS-1317: Open the cabinet's catalog pages read-only @dsuranov · API & apps #269109:48 FRTNS-1696: Keep the sign-in page working when the browser translates it @fortune-developer · Web / Platform #268509:45 FRTNS-1317: Open the cabinet's inventory pages read-only @dsuranov · API & apps #267209:24 CEP-103: Show one captcha on the WhatsApp code sign-up page and name fortisOS as the sender @fortune-developer · Web #267009:24 CEP-102: Deliver loyalty sign-up WhatsApp codes through the Gupshup API our key works with @fortune-developer · Web #266608:00 FRTNS-1622: Refuse a kitchen reprint for an order cancelled mid-press @fortune-developer · Web #267707:34 FRTNS-1627: Keep a repeat series from moving a booking onto a table an open order holds @fortune-developer · Web #267107:33 FRTNS-1626: Stop shift close and pager assignment from failing on lock timeouts during order traffic @fortune-developer · Web #268307:32 FRTNS-1687: Stop false N+1 alerts on sign-in and API key reads @fortune-developer · Web #266707:29 FRTNS-1623: Stop agent workflow cancel tests from timing out at random @fortune-developer · Agents platform #266407:28 FRTNS-1621: Keep venue days whole when DST changes at local midnight @fortune-developer · Web #268107:24 FRTNS-1630: Guard every destructive migration pattern with a failing test @fortune-developer · Platform #268006:27 MAINTENANCE: Make unused printer hex, zoom and sound helpers private @fortune-developer · API & apps #267806:23 FRTNS-1628: Prove MyFatoorah webhook deliveries settle guest card payments correctly @fortune-developer · Web #267906:22 FRTNS-1629: Prove the AgentCore routes refuse unauthorized callers before handing out credentials @fortune-developer · Agents platform #267406:06 FRTNS-1682: Keep POS pages loading when a scanner floods the app with file probes @fortune-developer · Web #267306:04 FRTNS-1681: Show whether a slow checkout page load was a busy server or a slow database @fortune-developer · Web #266206:01 FRTNS-1674: Make the offline POS queue drain check resilient to a lost wake @fortune-developer · Web #266305:57 MAINTENANCE: Start scheduled repository agents with autonomous exploration @awinogradov · Agents platform / Platform #265304:56 FRTNS-1666: Let a confirmed business pay for several licenses at first purchase @fortune-developer · Web #252203:10 CEP-98: Let pilot merchants set up loyalty tiers from a Tiers tab on the Loyalty page @fortune-developer · Web #252101:42 CEP-100: Let guests confirm their phone with a WhatsApp code when joining loyalty @fortune-developer · Web #266022:33 FRTNS-1620: Keep a paid order on its table when a payment lands during a transfer @fortune-developer · Web #265622:31 FRTNS-1670: Stop the floor editor prefix test from reloading before the table is saved @fortune-developer · Web #266122:29 FINE-546: Complete compatible updates across all Dependa agents @awinogradov · Agents platform / Platform 63 +17% vs previous period 309 14m median first response 100% Known involvement in accepted PRs THE CITY’S PULSE
Good things are moving. View all 0 4 7 Nov 1 17:24 UTC · hour ending: 1 merged PRs Nov 1 17:24 UTC · hour ending: 1 with known agent involvement 17:24 Nov 1 18:24 UTC · hour ending: 1 merged PRs Nov 1 18:24 UTC · hour ending: 1 with known agent involvement Nov 1 19:24 UTC · hour ending: 0 merged PRs Nov 1 19:24 UTC · hour ending: 0 with known agent involvement Nov 1 20:24 UTC · hour ending: 6 merged PRs Nov 1 20:24 UTC · hour ending: 6 with known agent involvement Nov 1 21:24 UTC · hour ending: 3 merged PRs Nov 1 21:24 UTC · hour ending: 3 with known agent involvement 21:24 Nov 1 22:24 UTC · hour ending: 1 merged PRs Nov 1 22:24 UTC · hour ending: 1 with known agent involvement Nov 1 23:24 UTC · hour ending: 4 merged PRs Nov 1 23:24 UTC · hour ending: 4 with known agent involvement Nov 2 00:24 UTC · hour ending: 0 merged PRs Nov 2 00:24 UTC · hour ending: 0 with known agent involvement Nov 2 01:24 UTC · hour ending: 0 merged PRs Nov 2 01:24 UTC · hour ending: 0 with known agent involvement 01:24 Nov 2 02:24 UTC · hour ending: 1 merged PRs Nov 2 02:24 UTC · hour ending: 1 with known agent involvement Nov 2 03:24 UTC · hour ending: 1 merged PRs Nov 2 03:24 UTC · hour ending: 1 with known agent involvement Nov 2 04:24 UTC · hour ending: 0 merged PRs Nov 2 04:24 UTC · hour ending: 0 with known agent involvement Nov 2 05:24 UTC · hour ending: 1 merged PRs Nov 2 05:24 UTC · hour ending: 1 with known agent involvement 05:24 Nov 2 06:24 UTC · hour ending: 6 merged PRs Nov 2 06:24 UTC · hour ending: 6 with known agent involvement Nov 2 07:24 UTC · hour ending: 2 merged PRs Nov 2 07:24 UTC · hour ending: 2 with known agent involvement Nov 2 08:24 UTC · hour ending: 6 merged PRs Nov 2 08:24 UTC · hour ending: 6 with known agent involvement Nov 2 09:24 UTC · hour ending: 1 merged PRs Nov 2 09:24 UTC · hour ending: 1 with known agent involvement 09:24 Nov 2 10:24 UTC · hour ending: 4 merged PRs Nov 2 10:24 UTC · hour ending: 4 with known agent involvement Nov 2 11:24 UTC · hour ending: 6 merged PRs Nov 2 11:24 UTC · hour ending: 6 with known agent involvement Nov 2 12:24 UTC · hour ending: 2 merged PRs Nov 2 12:24 UTC · hour ending: 2 with known agent involvement Nov 2 13:24 UTC · hour ending: 7 merged PRs Nov 2 13:24 UTC · hour ending: 7 with known agent involvement 13:24 Nov 2 14:24 UTC · hour ending: 4 merged PRs Nov 2 14:24 UTC · hour ending: 4 with known agent involvement Nov 2 15:24 UTC · hour ending: 4 merged PRs Nov 2 15:24 UTC · hour ending: 4 with known agent involvement Nov 2 16:24 UTC · hour ending: 2 merged PRs Nov 2 16:24 UTC · hour ending: 2 with known agent involvement Merged PRs Known agent involvementPR / hour · UTC
460 unique PR commits 2.4h median PR cycleBETTER TOGETHER
Humans & machines of accepted, non-dependency PRs have known agent involvement.
Autopilot54
AI-assisted9
No known attribution0
Dependency automation0
THE PEOPLE BEHIND THE LIGHTS
This shift’s crew View all NEIGHBOURHOOD WATCH
Where the work happens THE DEPARTURE BOARD
Fresh out of the station View all