A busy week still needed an honest scoreboard.

The week did not fit into one green badge

The weekly review brought together work that had been happening in different places: an architecture redesign, the public website, UBI, AgentOS, a knowledge base on the VPS, the publisher proposal and substantial audio-plugin engineering. It was a busy inventory. It was also an opportunity to use the word “complete” far too freely.

Some completions were founder-reported. Others had delivery documents or automated checks attached. Those evidence types belong beside each other, but they are not interchangeable. The review needed to show what each item could support rather than flatten the entire week into a percentage.

This is an unglamorous part of building with AI. Work can accumulate faster than a reliable account of the work. If the account falls behind, the next decision starts from the wrong picture.

The tests had a boundary too

The CHOPPA audio-plugin work included 68,717 state-integrity assertions and 188 passing VST3 host checks. Those numbers described substantial automated verification. They were not a substitute for listening, exercising a physical audio setup, endurance testing or completing release signing and notarisation.

An audio product is especially good at exposing the gap. A program can preserve its state correctly and still disappoint the person hearing it. A host can load a plugin successfully while the release process remains unfinished. The useful question is what the checks exercised and what the next user will encounter.

I wanted to keep the engineering win visible without quietly turning it into a public-release claim.

UBI received a more useful kind of test

Feedback on the website chatbot brought the discussion back to the visitor. Starter questions can make an empty conversation easier to begin. Once someone starts typing, the same prompts can become clutter. A guide also needs to answer across relevant workflows instead of repeatedly steering everything towards refunds.

Those observations are small enough to be easy to dismiss and concrete enough to be valuable. They describe what a person sees while trying to use the product. Fixing them means deciding how the interface should behave in a particular moment, then checking that moment again.

A mascot makes the corner of a website memorable. Useful conversation is what earns the space.

The commercial column stayed separate

The publisher opportunity had advanced to a meeting, supported by the proposal and questionnaire. The review still had no evidenced revenue or signed scope to record. That was not a reason to erase the week’s progress. It was a reason to choose the next task carefully.

The broader lesson was to attach the right receipt to the right claim. Delivered documents, working local components, published interfaces, accepted customer work and measured time returned all tell different stories. I need those stories to stay distinguishable if UBIKITOS is going to help me run the company rather than decorate its scoreboard.