Engineering status: product cleanup, growth, and customer readiness.

This week was about tightening the system around the product, not just adding another feature.

That means three things:

• public version and test numbers now stay aligned instead of getting hand-copied across multiple sites
• Cloud is being explained more clearly as the product around validation and shipping checks
• the public surface is getting instrumented so we can learn from real traffic instead of guessing

Consistent public numbers matter more than one flashy page

If the test count, version, diagnostics, or MCP surface drift across the site, docs, GitHub, and company pages, the product feels less real than it is.

So part of the work now is boring in the best way:

• one canonical metrics snapshot
• generated metrics flowing to the public surfaces
• fewer places where a manual copy edit can quietly go stale

That is not just an ops task. It is credibility work.

Cloud has to read like a product, not a vague beta

One thing that became obvious is that limited-access language can be ambiguous.

It makes people ask the wrong question:

"Wait, am I paying you, or are you paying me to try this?"

The better framing is a scoped team engagement.

That says it more directly:

• this is a scoped commercial engagement
• it is founder-led
• it is tied to one real Apple-native workflow
• both sides should learn something concrete by the end

The goal is not access for its own sake. The goal is a real shipping decision around one workflow that matters.

Growth work only counts if it teaches us something

We also do not want "marketing" to mean yelling louder into the void.

The useful version is:

• clean attribution between company, product, and GitHub surfaces
• better instrumentation on stars, partner applications, and Cloud actions
• publishing cadence that reflects actual progress instead of fake freshness

That is how the outside world starts answering the question for us:

is this actually resonating with real builders?

What comes next

The next layer is external signal:

• more real traffic
• more team conversations
• outside contributors
• third-party writeups and quotes

The core product is real. The job now is to make the public surface just as legible as the underlying system.