bonna61/Bonna-Moon-Studio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

VISION: record settled architecture decisions (repo home, two decoupled apps, kiln parked, assisted-search scanner)

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Bonna
2026-08-06 21:56:51 -05:00
parent 7fed279343
commit f4c1d6ca94
1 changed files with 17 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
VISION.md
View File

@@ -81,19 +81,24 @@ be the "solid organizational net" under her return: she should be able to jump
back in and trust that recipes, firings, notes, and tasks are held somewhere that back in and trust that recipes, firings, notes, and tasks are held somewhere that
isn't her head. Design for re-entry: low friction, forgiving, encouraging. isn't her head. Design for re-entry: low friction, forgiving, encouraging.
## Open architecture questions (for Tony + Bonna) ## Architecture decisions (settled with Tony, 2026-08-06)
1. **Where does the code live?** Platform templates live in the platform monorepo 1. **Code lives here.** This repo (Bonna-Moon-Studio on Gitea) IS the backbone's
with a build chain (per CLAUDE.md, authoring a new template = days). Options: repo — vision, designs, prototype, and eventually production code. Follows
new `bms-backbone` template in the monorepo (FMB convention), or app code in the FMB own-repo convention; only shared templates live in the platform
this repo with its own build. FMB convention suggests the former. monorepo. When Phase 1 is worth hosting, a `bms-backbone` template entry
2. **One app or two?** Backbone (admin/ops) + existing `site` storefront, like points at this repo and builds from it. Until then the laptop prototype
FMB + fullmoonbakehouse.poweredbyotm.com. Probably: keep them separate, serves Bonna. (Tony is new to git — Claude drives commits/pushes; Tony reads
integrate inventory → shop later. history on Gitea's web UI.)
3. **Kiln controller interface** — what protocol/API will Tony's controller 2. **Two apps, either without the other.** Site storefront and backbone stay
expose? Drives how "fire my kiln" lands in the app. separate services (own containers/DBs/hostnames), like FMB + its site. Any
4. **Market scanner data source** — scraping? manual seed list + assisted search? future site↔backbone integration (shop inventory) is an optional bridge with
This one needs a feasibility pass; deadlines/fees aren't in any clean API. graceful fallback — decoupled by design, connected by choice.
3. **Kiln controller — parked.** Tony: "don't worry about this yet." Revisit
when the hardware project has a shape; Phase 5 stays last regardless.
4. **Market scanner = assisted search + manual seed list.** No scraping
infrastructure. Claude does periodic hunts for local markets/fairs
(deadlines, fees, distance) and logs findings; Bonna seeds/curates the list.
## Prototype (built 2026-08-06) ## Prototype (built 2026-08-06)