zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
1.7 KiB
common/ — read before adding code here
common/ is a transitional holding pen, not a destination. It holds shared code that predates a better home. Do not treat it as the default place for new shared code.
Disclaimer
The name is the smell. A catch-all common/ reliably rots into a junk drawer — unscoped, unenforced, imported by everything — i.e. a second monolith with worse boundaries than the first. Unlike products/* (guarded by tach + turbo), nothing mechanically guards what lands here, so the only thing keeping it honest is this file. The goal for common/ is to shrink, not grow.
Before adding anything here
Pick a home with a real boundary first, in this order:
products/<name>/— owned by one producttools/— dev/CI tooling, not shipped at runtimeservices/— independently deployedpackages/— a clean, published-style leaf with no back-edges into app code (seepackages/quill)
Fall back to common/ only when none of those fit and the code can't yet be a clean leaf because it still imports app modules (lib/*, scenes/*, etc.). If you do, treat it as tracked debt: say so in the PR and name the intended graduation target. "It follows an existing common/ precedent" is not, on its own, a reason to add more.
Graduating out
When something here becomes a clean leaf (no back-edges into app code), promote it to packages/ or into the owning product, and delete it from common/. That is the success path — quill took it.
Conventions
- Keep folder names
under_scorecased — dashes break Python imports. - Human-facing overview: README.md. Repo-wide layout: monorepo layout.