"Everyone's here, except Apricot?", Orange frowns. "He should be in office today. Anyone seen him?"

"Not today, he missed lunch. But it's still five minutes until the scheduled meeting. He's never actually late."

And about fifteen seconds later, Apricot stumbles out of a storage room of cleaning supplies. There are more and less subtle signs that he has just woken up.

"Good morning everyone!" he proclaims. "Orange, how did the call with the" - yaaaaawn - blinking - "eeehm, bank API provider go?"

"Afternoon. Quite well, I'd say. We'll still need to negotiate an actual contract, but we're getting access to the sandbox environment today, so you can start integrating it immediately."

He flips open his laptop, navigating to the kanban board tracking high-level tasks. The section marked "backlog" has been expanding in a worrying pace. He nervously reorders some of the items on the bottom, before turning eyes to the "in progress" section. "Ok, lets go through the updates. Vanilla, you first?"

Vanilla also has her laptop open.

"Morning! And yeah that works. Just a second." 

Keyboard noises. Vanilla quickly browses through the assigned tickets and checks what was marked completed last week.

"The new interface prototype is progressing. Completed navigable prototypes for three different approaches but we're not quite sure which approach to commit iterating on and for building the more complex features with."

"The next steps for the interface development are otherwise clear for this week but I'm unsure how last weeks plans compare to the new backlog items, might need to address that, and additionally choose one of the three approaches today."

"We should probably have a meeting after the weekly to discuss the approaches, then. You and Raspberry, at least."

Orange proceeds on without waiting for any acknowledgement.

"Blueberry, you're next. How's the status page shaping up? The internal one, I mean."

"Grafana configuration is now mostly done. I just got the http endpoint error and timing graphs to show on our custom status page as well."

Blueberry smiles briefly before checking the assigned ticket.

"I'm supposed to work on outage alarms next, but we haven't specified that at all. Do we actually want PagerDuty-style phone calls when something goes wrong? Seems a bit early for that, but it would be good to have the integration ready for when we'll have actual uptime targets. Not a priority right now, I'd say."

"Agreed on prioritization. We need a way to notice if something's broken though. Maybe we should still send emails for those? Or we could have a status screen in the lobby?"

Apricot thinks that the CEO looks a bit too eager to have a status screen.

"A Slack bot would probably be the best way to do this.", he interjects.

Nod. "Let's do that."

Orange waits until Blueberry nods too, and the proceeds onto the next person.

"Raspberry? You we're looking at the interface, too?"

The person in the room whose laptop contains the most stickers turns their gaze towards Orange.

"Yup definitely.

I think the multiple-prototype approach has already provided some info. I'd say it doesn't look reasonable to keep building on anything besides the chat-based solutions. We just can't fit the desired amount of breadth into a clean visual interface.

I'm kind of lost on what to fiddle with next. Could look into feature-specific interfacing?"

"Fwiw I agree that the non-chat solutions probably aren't worth the hassle and even if we had a big UI team might still be worse than the chat-based ones. So I'd also vote for the chat based ones if we were counting. Dunno on what's most important to do next but you could maybe think through how interactive vs. noninteractive we want the chatting to be for multi-step operations. Maybe check out the recent advances in programming agents and think how that generalizes for our potential userbase?"

"That sounds urgent enough to me. Orange, you agree with the chat / text-based UI direction?"

"Ehh sure. We can go forward with that. By the way, I saw a cool computer use demo from a competitor last week, they had a... eeemm" *pause* "this thing in it. Sort of like a window that floated around and explained what it was doing. We should have that kind of thing as well."

Orange creates a new ticket. "I'm assigning it to you, Raspberry. Take a look at it when you have time to spare."

"Ok Apricot you next."

Apricot opens up the real issue tracker. The one Orange doesn't know about. A keyboard shortcut brings up an automatically generated summary of all his ongoing work.

"Last week, we finished the remaining subtasks on cross-device authentication. We got QR-code, email magic link, passkey, SSO and plain old username-password with 2FA all working now. The login UI is still a bit ugly but fully functional and UX by itself is as good as it gets. Session revocation is also implemented, and also has bare-bones UI with just a list of devices and revoke buttons."

He reads the notes further.

"The email magic links are sent from a temporary address and sometimes go to junk mail. 2FA recovery code and password reset flows still need a bit of work. I need to think about the threat model for account recovery a bit more before I'm confident on actually implementing any of that."

mentally taps himself on the back That's a great excuse to take Wednesday off.

frown (a practiced one, and perhaps pretended too, he doesn't know anymore)

"Now that we have multidevice setup working, we need consider syncing between devices too. Ideally the user could control their PC from their phone, for instance."

A small pause, to see if anyone comments on that.

No one does.

"Ok that's all from me. Prune, you next?"

Prune nods.

"The publish CD pipelines for are fully set up, except iOS. I'll set up that next. We'll need a notification on the web frontend whenever there's an update available, too."

Tap tap tap the table. A good way to remember things.

"The cloud-provided speech recognition is quite expensive. I'm going to experiment a bit with on-device support."

A quick glance at Apricot.

"The backend support for paying with a linked credit card is almost done. Just needs sensible limits on when it should confirm with the user. 'cot, could you handle that?"

"Yep. We should probably make it dynamic using the bank account APIs, but for now I think we just make the default to be..." pause "maybe we should just ask this directly, when the user links the card?" frown "We still need a default, let's go with fifty. I'll handle that."

"Thanks. That's all from me."

"Ok thanks everyone. I gotta make some calls now, but I'd be quite interested to see the interface demo later today."

He looks expectantly at Vanilla.