gdw is a production tracker application for leather goods manufacturing. Its purpose is to let a production manager monitor production output hourly — recording what each hour of production yields and seeing, hour by hour, whether output is on target or low.
The product intent is narrow and operational: a production manager on a factory floor needs a fast, exact, legible record of hourly output and a clear read of which hours are falling short. The audience is the production manager role in leather goods manufacturing; the primary user is Abdul Wahab, a production manager in India.
The application is delivered as a first-party web application with application-owned identity: a new production manager enrolls through self-service sign-up, a returning production manager verifies identity at login, and the hourly output records are protected behind that identity so each manager's records persist and can be resumed.
gdw is a single first-party web application composed of a React frontend, a shared FastAPI backend, and a MariaDB database for application-owned persistent data. The frontend presents an anonymous public entry (Landing), two identity-access surfaces (Sign Up, Login), and two protected working surfaces (Hourly Output, Record Output). The backend owns the domain APIs for accounts and hourly output records; the database persists accounts and hourly output entries so records survive across sessions and can be revisited.
The only active human actor is the Production Manager. There are no other human personas, no external providers, and no outbound recipients in the current scope. The system itself performs persistence, session verification, and hourly aggregation as supporting work behind the manager's own interactions.
Current accepted behavior:
Narrow exclusions: gdw does not include inventory, purchasing, payroll, machine telemetry, multi-role administration, or reporting beyond the hourly output view described here.
Removed from scope
gdw is delivered as a first-party application. The public entry (Landing) is anonymously reachable and explains the hourly production tracker before sign-in. Sign Up and Login are also anonymously reachable because a protected destination cannot own the interaction that establishes access to itself. The Hourly Output and Record Output surfaces require login: they hold durable, manager-specific hourly output state that must remain bound to the correct manager and be resumable on return.
Identity is application-owned and established by self-service enrollment (Sign Up) with returning verification (Login). This is the minimum identity continuity required by the accepted journeys; it does not introduce differentiated permissions, role-based visibility, or account-management capabilities. All current behavior is in the current delivery horizon; no future-horizon features are accepted.
Not applicable — no reference directive with content_source was supplied.
FR-1 — Record hourly production output (explicit) As a Production Manager, I should record production output for each hour so that the tracker holds an accurate hourly record of what the line produced.
FR-2 — View hourly production output (explicit) As a Production Manager, I should view production output for each hour so that I can monitor the line hour by hour.
FR-3 — Identify low-output hours (explicit) As a Production Manager, I should see which hours are low output so that I can act on shortfalls.
FR-4 — Self-service enrollment (required_inference) As a Production Manager, I should create an account through self-service sign-up so that my hourly output records are kept and can be resumed.
FR-5 — Returning identity verification (required_inference) As a Production Manager, I should verify my identity on return so that I can reach my protected hourly output records.
The creative direction is authoritative: Hourly output, set like a transit timetable, after the muse Erik Spiekermann — typographic infrastructure for shift work and data rows, with signal colours showing low output like a delayed transit line.
Colour tokens (light mode):
#F4F0E8 (warm paper ground, ~70% of screen)#FFFFFF#1C1B19 (ink, carries all data)#C8102E (signal red: low output and primary actions)#E8B500 (amber: on-target hours)#6B655CTypography:
clamp(...).Shape language: Square corners, 2px ink rules, chunky outlined buttons, colour-coded hour bars. No drop shadows.
Layout: 12-column grid with a left hour rail and a right data table; rows align like a timetable; small-caps labels above each value.
Imagery: Pictograms for cutting, stitching, and finishing; schematic line art of a leather panel as the only illustration.
Avoid: Rounded pill buttons and soft drop shadows; blue or indigo accents on white; glass panels, gradients, and blob shapes; identical hover-lift card grids; Inter, Roboto, or system-ui fonts.
The public entry is a full-width hourly timetable band. A 40px-to-72px condensed headline sits left on the warm paper ground. Below it, a live strip of 12 hour blocks runs edge to edge, each block coded red (#C8102E) or amber (#E8B500) like a transit line diagram. The sign-up button is a chunky ink-outlined block pinned at the band's left edge. Tabular numerals at 40px align right on a 2px rule in every output row, and small-caps section labels sit above a hairline like station signs. The concept recomposes only accepted content and controls — the hour strip illustrates the hourly output concept, and the sign-up block leads to Sign Up.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
#F4F0E8, condensed headline left, 12-block strip below, ink-outlined sign-up block at the left edge.prefers-reduced-motion, the hour strip provides a usable static arrangement (wrapped rows or horizontal scrolling) with every item fully readable.frontend, backend, and database services. No additional infrastructure is required for the current workflows.#C8102E).#E8B500).
Hourly line · output signal
Illustration of the hourly coding06:00 — 17:00
Returning manager?Log in to hourly output

Hourly line · output signal
Illustration of the hourly coding06:00 — 17:00
Returning manager?Log in to hourly output
No comments yet. Be the first!