The Bitbaum studio website and its static site generator. The public site is bitbaum.orangecat.ch. It presents projects at their editorially reviewed readiness stage, documents shared packages, and routes people to the studio waitlist or to Loki for agent-assisted work.
Various problems, including economic participation, AI agent development, fundraising, and digital inclusion
AI-powered products that solve these problems, including orangecat, botsmann, Loki, hirn.li, and Revamp-IT
Bitbaum is a solo-founder AI product studio: multiple vertical SaaS products on shared infrastructure, each profitable within 12 months, each owning a specific niche.
Build multiple AI-powered products that solve real problems, with a shared infrastructure and a focus on profitability.
The stack has not been written down yet.
Investigate this project with Loki →Validate each package card against its own registry version and source, independently of accessible-label wording. Detect stale displayed versions even when packages share the same release number.
Publish checked source facts from main and propose generated snapshots through the normal pull-request gates, including generated cast documentation. Stop writing generated changes directly to main.
Expanded each package page with source-pinned API documentation and examples, repository changelogs and published release notes, section navigation and linked declared consumers. Release facts and current-source documentation are distinguished, and missing history is shown honestly. Package source failures stop a fresh publish. Expanded-documentation browser checks cover phone/desktop widths and both themes before publication.
A studio request or partner application has no account; its private link is the key. Now the link also goes to the email given — at the start, or added later in the same conversation — and the portal page has "Lost the link?": the address you gave gets a fresh link to every open request under it, and the old one stops working (Loki /api/studio-recover).
site/cast.json names every painted or drawn element once; the build finds each one on the pages it renders and writes the register (dist/cast.json, docs/CAST.md — what is where, how it moves, what shows on phones). It refuses to build when an element is on no page or a painting belongs to no entry. The first run found one: the hummingbird avatar was assigned to a venture that does not exist, so it was on no page — it now lives on Camille's bakery. site/check-cast.mjs opens every page at phone and desk width and proves each element is in the DOM, loaded and sized where the register says; it runs in CI with the other checks. Quixote and Sancho ride into the plain toward the mill — near and large first, then up and away, smaller and hazier — instead of along the horizon line. The header steps aside while the reader reads down and returns on the first scroll up; never while the menu is open.
The chevron floor is bone on ink in both modes. Its base colour was the foreground — white by night — so in dark mode the Red Room floor was a white slab. The owl's perch was a line in mid-air; its painted branch now reaches in from beyond the stage's edge. The fox and the cat meet: when the fox runs the floor the cat turns to face it, the fox leaps over, the cat startles and watches it go. On phones the riders ride too — they had been pinned still beside the rabbit and the burrow, which is what crowded the first screen. A short receding path right of the burrow, toward the mill.
Nothing is retired: every painting is somewhere, on the ground, one or two to a screen. The inner pages' creatures stand on the Lynch floor in perspective — the same floor as the hero's — and the hero keeps no second floor of its own when a stage follows. A page's objects (the soft watch and its gears, the rye, the tumbleweed, the mushrooms, the Little Prince, the dandelions, the windmill, the fog creature) stand at the page's foot with their feet on the footer's chevron band, where the cat waits — not in a grid of pictures. The gears turn, the rye and dandelions sway, the mushrooms breathe, the tumbleweed rolls through now and then. The long-legged elephant crosses the plain again on the "build it yourself" screen (desk only). Phones keep each screen to one or two things: the plain is the tree, the dome and the hummingbird; the hero's one flying thing is the whale.
The standing animals (Heidi's cow, the diplodocus, the elephant, the deer, the rabbit, the cat and the kit) graze along their floor: a slow walk to a spot, a rest, a turn, a slow walk back. On the partners' meadow the deer comes toward us over minutes and the giant in the fog paces. The scarab rolls the sun along the ground; its far start no longer floats. The stylesheet and scripts lose the hooks of a plain that no page emits any more (the old gears, rye clump, cow and diplodocus doors, the cat's perch, the scene tumbleweed).
New page, /map/: every project drawn as a loop, meaning work that recurs and still needs a person in it. Four layers: the rails (OrangeCat, Solon, Loki and the shared packages), the constraints (Substrata), professionals in the loop, and loops in the world. Each loop names who stays in it and what routine part it aims to retire. The loops live in site/overrides.json (loops). The build fails if a loop cites a project the site does not show, if a project is in two loops, or if a shown project is in none, so a new project cannot reach /work/ without someone deciding what it is for. A loop with no project is drawn as a gap and claims nothing. Allocating money is the first: named, not built, and explicitly not advice. Diplodoctor and Causius now describe their own plans: a licensed clinician, or a licensed lawyer, stays in the loop and owns the result. Both remain "not built". 138 responsive checks pass, including the new page.
The studio's intake is one field, typed or spoken, on /hire/ and /partners/: no form, nothing refused for its shape. A website in the text makes a studio request; on /partners/ the message is the application; anything else is asked one question and joins the waitlist. Every request gives the visitor its private portal link; follow-ups go to the same record; a retry reuses the same receipt. The three paths say true things everywhere: the free tool is one address, the studio shows its fixed price and its day rate, and partners read "applications open · none approved yet" with the systems design course named as the step before review. The browser checks drive the conversation instead of the forms; 135 responsive checks still pass.
One table in site/sky.mjs (WX) says what each weather does: the sky's gradient by day and night, how much sun, moon and stars show, how many clouds and how bright, what falls, how hard the wind blows. Everything that draws reads it; nothing tests a weather by name any more. Rain is an overcast with no sun, mist veils it, snow dims the stars. Quixote and Sancho ride out of the haze: small and far first, nearer and larger as they come toward the mill, instead of sliding along a line. On a phone the clouds keep to the band above the first screen's words.
Added the studio roadmap and delivery plan. Recorded free, independent Loki access; studio-only engagement prices; course completion before studio partner approval; and optional product participation. Course, portal and intake-placement corrections remain planned. Mobile artwork has grounded spaces away from copy. All 123 responsive page/viewport checks passed, including rotation and enlarged text. Partner applications use a direct message and tracking receipt. Submission records interest for review; it does not confer approval.
Build a Bitbaum brief intake, request receipt and private customer/partner portal backed by Loki's scoped request API. Keep free Loki self-service independent, with an explicit draft-preserving handoff. Studio offer and current capacity stay in hire.json; Rescue retains its assessment scope. Add course evidence, separate studio approval, consented profile review and assigned-brief delivery. Availability determines public directory inclusion. Write the first systems design lesson, exercise and capstone rubric. Further lessons and calibration remain in development. Render the canonical roadmap and changelog through bip-kit, and resolve the studio repository through its canonical project ID. Verify the scoped backend in Loki's full CI, including PostgreSQL isolation, revocation, assignment and retry tests. Bitbaum's browser journeys and 135 responsive checks pass, including rotation and enlarged text; the narrow-screen footer and price wrapping are corrected. Production release is gated on the backend migration and API availability. The first real engagement and reviewer calibration remain pilot work.