Garment Intake Deprecated

Photograph a garment, and it is ingested, classified and queued for a one-keystroke confirmation. Fully specified, not yet built.

Deprecated. Retired in a fleet code-standard review because it held no runnable product: a complete spec with no code, whose first step, a throwaway prototype timing the photo step, was never built.It was fully planned on paper but never built, so it was retired.

Feasibility: 4/5

Scored 1–5 on what stands between the idea and a working version: whether the data is reachable through a supported channel, whether anything gates it (approval, cost, another person acting), whether it keeps working unattended, and how much is left to build once the data is in hand.Scored 1 to 5 on what is actually in the way: whether the information can be got hold of properly, whether anyone has to approve it or charge for it, whether it will keep working on its own, and how much work is left once the data is available.

A 4, and unusually for a backlog project the uncertainty is not technical. Twenty design documents and nine ADRs already settle the capture path, the domain model, the schema and the taxonomy. What is unresolved is the one assumption the whole design rests on: that a Back Tap shortcut really captures a garment in under four interactions. The plan opens with a two-day spike to find out.

Four out of five. The design is finished in unusual detail. The one real unknown is whether the phone gesture that starts the whole thing is actually as quick as assumed, which a two-day test would settle.

What would raise the score