Overnight push: the team’s PrompTugal app

From 02:45 to 10:30 Lisbon time on 8 November, seven sessions build the native PrompTugal app for the team: vaults on the phone, one schedule, agents and team visibility, observability, debug panels, AI and the product site. This page is the shared plan, and every session reads it first.

Lead: Dinis Cruz · Conductor: the coordinating Claude session · Wrap-up: about 10:30 Lisbon time (UTC), with a report on this page

Positioning, from Dinis

• Update, 8 Nov (Dinis): sgit is one of the things we do, so product pages may name sgit as our own. RiskMandate powers the site and is credited in the footer ("Powered by RiskMandate"). What makes the team of 100+ agents possible is RiskMandate's Agent Behaviour Policies (ABP), one per agent; the Teams and Overnight pages say so.
• This is PrompTugal, and only PrompTugal. The app and its website are about PrompTugal. Leave RiskMandate, sgit.ai marketing and the other summit sites out of the product, its copy and its default shortcuts. Team data sources stay usable, as data.
• Native is the point. Large parts should be native. That is why we are building an app.
• The team is the first customer. Seven to nine of us use it at Web Summit Lisbon (9–12 November). Silvio has already installed it from Xcode, so everyone can. The App Store is a bonus, not a dependency.
• Two products in one: a user platform (readers and attendees) and a creator platform (the team, our agents, our newsroom). The platform itself is something we will sell.
• Make it spectacular on iPad. The iPad is a better place than the website to see what agents and the team are doing. What we learn natively goes back to the website.
• The first audience of this version is us. As it stands, this is fundamentally an internal application for the team.
• Make everything visible. Like our websites, the app should show its working: debug panels, traffic, encryption, data and versions.

Decisions taken (answers to brief pack 2026-11-07, D1–D7)

What to build tonight

1. Vaults on the phone. A Swift sgit reader with a cache and sync. Unlock with Face ID, with passkey PRF where possible and read-key import as the always-works path. A debug panel showing every request, byte count, file ID, decryption step and timing. Never show keys.
2. One schedule. Website picks (nr.schedule.v1) and native saved sessions as one list, synced both ways through the web view, mirrored to the vault (agenda/picks), with reminders. Plus "help me plan my presence", and coordination with teammates through their vaults.
3. What my agents and team are doing. Native iPad dashboards built from the team site’s public JSON (people, me.json, command-centre data.json, wakes, reports, pulse, meetings, log) and the newsroom’s JSON (/api/v1/newsroom/*).
4. Briefed. My stand-up briefings, the briefs, decisions waiting on me.
5. The news, in every form. The PrompTugal feed, newsletter editions, stories, wires and the graph. Some pages native, some web, side by side, to learn the balance.
6. Observability and visualizations. Website traffic and newsroom status, and the visualizations Silvio and Angelo have built, as native iPad views (Swift Charts) next to the web originals.
7. AI. OpenRouter chat with the key in the Keychain (and optionally in the vault), using the app’s own data (agenda, my picks, team status) as context.
8. Collaboration through vaults. Shared picks and notes, and append lanes for messages to teammates and to the newsroom.
9. Meter and native top-up. The website’s meter, kept, topped up through StoreKit, with a local StoreKit configuration for testing.
10. The product site. ios.app.promptugal.news becomes a PrompTugal product site for both platforms, with a build log of tonight and many admin pages.

Sessions

The conductor merges green branches into dev about once an hour. Each merge releases and deploys the site.

Progress

The build log on the site has one page per checkpoint: /admin/build-log/.

• 09:20 Wrap-up: iOS run 188 green on every job; screenshots run 16 has all 13 screens on iPhone and iPad; 239 commits on dev since 02:40. The morning summary is final.
• 08:45 Wind-down: every session's last work merged at 08:10 and 08:40; iPhone unit tests 124 of 124 (run 173); 13 iPhone screenshots live, iPad pending. The morning summary is in its final shape.
• 08:15 Run 160 fully green: build, vault tests, iPhone and iPad unit tests on the integrated app. The bridge's end-to-end test against the live website is in Tools/bridge-e2e.
• 07:15 Team reports the bridge passing every check against the live promptugal.news. Screenshot test split per screen after a timeout. Dev frozen until 07:40 so queued iOS runs can finish; last green full run still 04:41.
• 06:20 First real screenshots on the site (5 iPhone screens); design fixed four interface bugs they showed. iOS tests on dev queued since 05:16.
• 05:40 First fully green CI run of the integrated app (run 104); unit tests 64 of 66 on iPad and iPhone, the 2 failures already fixed. New: the Wall screen for an iPad on a stand.
• 05:15 Collab merged: all 19 features in the beta, 28 screens, no placeholders.
• 04:45 Dev at v0.1.20: screenshot workflow, privacy manifest, schedule key-order fix, launch arguments per screen. 16 of 19 features in the beta; collab is the last branch.

Rules for every session

• Read contracts before writing code. It fixes the shared interfaces and file ownership.
• Stay in your folders. If you need a change in someone else’s folder, write it in your status page under "Needs from others", and the conductor routes it.
• Small commits, pushed often, to your branch only. Rebase on origin/dev at least every hour. Never push to dev or main.
• CI is the compiler. No one can build Swift on Linux. Push, then read the iOS workflow result for your branch and fix it before moving on. A red branch is not merged.
• No third-party packages. Apple SDK only, as today.
• No secrets in git. No vault keys, read keys, tokens or OpenRouter keys in the repo, test fixtures or logs. Test vaults must be throwaway vaults created for the tests.
• Update your status page at least every hour: done, in progress, next, blocked, needs from others. It needs a # Title line and a > summary line, because the site publishes it.
• Keep working until about 10:15 Lisbon time. If you finish your list, take the next item from your backlog. If a turn ends early, schedule yourself a message to continue (send_later, 15–20 minutes) instead of stopping.
• Write plainly. Short sentences, numbers counted from source, no marketing words.