This was a consolidation week. I run a bunch of small products under ITW Creative Works, and for years each one carried its own slightly different website, backend, and config. This week most of that duplication died.
OMEGA, the framework under everything
Most of the week went into OMEGA, the framework I'm building to run every brand: ten minor releases in seven days (0.29 โ 0.43).
The headline pieces:
- Payments, end to end. Checkout, billing UI, discount handling, and production gating now live in the framework. A brand turns payments on with config, not code.
- One analytics contract. Every target (website, backend, desktop, extension) now reports events through a single typed contract. One definition, no per-app drift.
- Lifecycle plumbing. A retention dialog, a winback flow, and offline mode, all shipped once and inherited by every brand.
The reason this is cool: fixing something in one product used to mean fixing it in ten places. Now every brand picks it up on its next update.
Nine brands, one template, one hour
The payoff moment. I scaffolded monorepos for nine brands, including StudyMonkey, Giftly, DashQR, Bink, Ghostii, Chatsy, Kirue, Clockii, and the ITW site itself, all from a single brand template, all within the same hour.
Migration was config conversion, not a rewrite: each legacy site and backend got ported onto the framework packages, and its old settings were translated into one omega.json5. The brands with the most legacy baggage took a few extra commits; the clean ones were nearly free.
StreamForge: the start of a video pipeline
New project. I want long working sessions to become edited videos without me living in a timeline editor. This week its first repo, cutroom, got a working recap pipeline: ingest the footage, render a longform cut, then frame shorts out of it with proper edge anchoring. A second repo, switchboard, is seeded and waiting. No public site yet; when the first output is watchable, that will be the post.
The agent workflow engine
My Claude Code workflow tooling (an engine I call workkit) went 0.41 โ 0.47: a live board for every project's issues, stale-work alarms, and documentation-density enforcement. The idea it encodes: GitHub issues are the single source of truth, and the agents' job is to keep them true. It manages a small fleet of coding sessions across all the repos above.
Small but satisfying
- Dotfiles shipped 3.20.4 and 3.21.0: a Chrome E2E teardown fix and pinning
jqso hooks stop resolving to the system build.
Next week: first real output from the video pipeline, and the brand rollout continues. If you have gone through a many-products-one-framework consolidation, I would genuinely like to hear what broke for you. Comments open.
!["[260823] ์ฃผ๋ง A/B ํ
์คํธ ๊ฒฐ๊ณผ ํ์ + ์คํ ํ์ดํ๋ผ์ธ ์์ ์ฑ ๋ณด๊ฐ"](https://media2.dev.to/dynamic/image/width=1200,height=627,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi0qlehk1k43o43xfg8xl.png)
!["[Aug 17-23] Rebuilding the Publishing Pipeline, Then Catching Signals That Fail Silently"](https://media2.dev.to/dynamic/image/width=1200,height=627,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxp18v4h3xrqhthz401qu.png)
!["[260823] Weekend A/B Verdict and Execution Pipeline Hardening"](https://media2.dev.to/dynamic/image/width=1200,height=627,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftrcmjxqr3bl3kknwqgj6.png)