Files

T

grokbot_ty 22599c924f docs(m3): expand Create SoT for submission-ready exit

Reorganize docs for humans: README map (goals / shipped / M3), PRODUCT
overview, and a specific CREATE.md that pulls Woo sync, metadata, pricing,
and inference requirements from main. Exit criteria is a slab submission-
ready for WooCommerce, proven with a SLAB-UAT-* draft. Add UAT-PRACTICE.

2026-09-16 21:03:46 +00:00

3.3 KiB

Raw Blame History

Docs map (branch `m3-ds`)

Read this file first. It tells you what SlabUploader is for, what already ships, and what Milestone 3 must build.

Who this is for. Mill owner (Ty), humans reviewing scope, and agents implementing on this branch.

Source of truth for Milestone 3. docs/CREATE.md plus the Ty conversations that wrote it. Older milestone and task splits on main are obsolete for M3. Do not open main for scope once you are coding on m3-ds.

High-level project goal

SlabUploader lists one-of-a-kind wood slabs on Whidbey Wood Store (WooCommerce).

One slab is one unit and one listing. Photos and metadata are the inventory record. The mill owner photographs a slab on a green or black sheet, gets store-ready transparent PNGs and measurements on the phone, fills the store's taxonomy and price, then creates a WooCommerce product.

Store: https://www.whidbeywoodstore.com/

What is already implemented (pre-M3)

Milestone	Spec	Status on this branch
1 Capture	`docs/CAPTURE.md`	Shipped. Browser-only mask, length axis, measure, inventory PNG, device draft.
2 Photos	`docs/PHOTOS.md`	Shipped. Batch photos, pick calibration, apply mask/crop to the batch, dimension overlay, Photos-ready lineup. UAT on `:10881`.

There is no Woo create yet. There is no Complete-listing taxonomy UI yet. There is no FastAPI Woo client on this branch (backend/ is a stub). Inference is not wired.

What Milestone 3 builds

Spec: docs/CREATE.md.

Exit criteria. A Photos-ready slab becomes submission-ready for WooCommerce, and a practice SLAB-UAT-* draft exists in the store that matches the reviewed ready set. Create must still work with inference off.

In plain terms, M3 connects the Photos-ready device draft to the real store:

Talk to WooCommerce with a WordPress application password (server-side only).
Sync and use Woo attributes (categories, five locked attributes, fig-* / feat-* tags) per the requirements taken from main and written into CREATE.md.
Pricing from species $/bdft rules, with user override.
Inference Settings (OpenAI-compatible URL, key, model) and Call 1 / Call 2 rules when enabled.
Review to the full ready set, then create the Woo product (force draft for SLAB-UAT-*).

Technical detail for Woo sync, metadata, pricing, and inference is copied into docs/CREATE.md from main so you do not need to open main while coding. Older milestone splits on main are still not the scope authority for what M3 includes.

How to read the folder

File	Role
`README.md` (this file)	Map: goals, shipped, M3.
`PRODUCT.md`	Product overview: complete listing, decision rights, seams.
`CAPTURE.md`	Milestone 1 Capture (shipped).
`PHOTOS.md`	Milestone 2 Photos (shipped).
`CREATE.md`	Milestone 3 Create (current work). Read this before task breakdown or coding.
`UAT-PRACTICE.md`	Human practice walk for a `SLAB-UAT-*` listing. Defers to `CREATE.md` on conflict.
`archive/`	Historical only. Not M3 scope.

Deploy reminders for this branch

UAT overnight Docker: ubudual5060 http://100.64.0.9:10881
Do not touch :10880 (Ty Node/SvelteKit)
Store URL (WOO_BASE_URL) lives in compose / host .env
Woo application password and inference URL live in encrypted Settings, not in compose

3.3 KiB Raw Blame History

Docs map (branch m3-ds)