Docs: Only WooCommerce-synced species are selectable in UI and inference #12

New Issue

2026-09-01T22:53:50Z

Ty commented

2026-09-01 22:53:50 +00:00

Summary

The docs must state explicitly that the only species a user can interact with in the UI, and the only species the inference engine (Call 1) may select from, are the species synchronized from the WooCommerce species category.

No hardcoded, invented, or fallback species lists are permitted anywhere in the app or the inference pipeline.

Current gap

CONTENT-WOO describes filtering synced Woo categories into species and wood-category leaves, and the pricing rules are seeded from those synced species. But it never locks the hard exclusivity rule: the UI offers only synced species, and Call 1's taxonomy is constrained to that same synced set. The exclusivity is implied by the sync-and-seed flow, not stated as a requirement.

Required doc changes

CONTENT-WOO.md — state that species available to the user and to inference are exactly the synced species-category leaves; no other source.
PROMPTS.md — Call 1's constrained taxonomy must be built from the synced species set only.
ARCHITECTURE.md / IMPL-PLAN.md — reflect the synced-species-only constraint in the data flow and acceptance criteria.
AGENTS.md — add to the precedence notes so agents don't introduce fallback species lists.

Acceptance criteria

Docs state the exclusivity rule in plain language: synced species category is the sole source for UI selection and inference selection.
No doc implies a default or hardcoded species list exists.
A new species appearing in Woo is selectable only after the next sync; inference cannot name a species absent from the synced set.
Linked to branch docs/refactor-v2.

## Summary The docs must state explicitly that the **only** species a user can interact with in the UI, and the **only** species the inference engine (Call 1) may select from, are the species synchronized from the WooCommerce species category. No hardcoded, invented, or fallback species lists are permitted anywhere in the app or the inference pipeline. ## Current gap CONTENT-WOO describes filtering synced Woo categories into species and wood-category leaves, and the pricing rules are seeded from those synced species. But it never locks the hard exclusivity rule: the UI offers only synced species, and Call 1's taxonomy is constrained to that same synced set. The exclusivity is implied by the sync-and-seed flow, not stated as a requirement. ## Required doc changes - **CONTENT-WOO.md** — state that species available to the user and to inference are exactly the synced species-category leaves; no other source. - **PROMPTS.md** — Call 1's constrained taxonomy must be built from the synced species set only. - **ARCHITECTURE.md** / **IMPL-PLAN.md** — reflect the synced-species-only constraint in the data flow and acceptance criteria. - **AGENTS.md** — add to the precedence notes so agents don't introduce fallback species lists. ## Acceptance criteria - Docs state the exclusivity rule in plain language: synced species category is the sole source for UI selection and inference selection. - No doc implies a default or hardcoded species list exists. - A new species appearing in Woo is selectable only after the next sync; inference cannot name a species absent from the synced set. - Linked to branch `docs/refactor-v2`.

Ty added this to the POC milestone 2026-09-01 23:49:47 +00:00

Ty referenced this issue

2026-09-03 02:36:57 +00:00

Test plan: POC acceptance test cases for all milestone issues #19

Ty commented

2026-09-03 03:20:57 +00:00

Docs complete. All docs state that UI pickers, pricing seeds, and Call 1 species lists are exactly the synced species-category leaves. No doc implies a default or hardcoded species list exists. The synced-species-only exclusivity is stated in CONTENT-WOO §2.2, ARCHITECTURE §7, AGENTS §6, PROMPTS §Notes, UX, and UX-DESIGN.

Ty closed this issue

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

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Ty_Tech/SlabUploader#12