Configuration Behaviors

Use cases and scenarios for the OAM::CFG (Configuration) area of the Functional Domain Taxonomy. This area covers the behaviors that help a new tenant configure the system for productive use: starting from scratch or imported data, phasing rollout gradually, learning the physical implementation, and persisting display preferences for users and tenants.

OAM::CFG::0001 — Deferred Validation During Onboarding

New tenants can accept AI-inferred item data immediately and validate it later, reducing the friction of initial setup. The system tracks confidence scores for inferred fields and queues uncertain items for later review rather than blocking the onboarding flow.

Persona	Owen Ownerton (Business Principal), Irene Itemsworth (Inventory Manager)
Depends	REF::ITM (items produced by initial bulk import)
Status	Partial

OAM::CFG::0001::0001.US — Accept AI-Inferred Data and Review Later

During onboarding, the user uploads order history or imports an item list. The system uses AI inference to populate item fields such as name, category, minimum stock level, and reorder quantity. The user accepts the inferred data as-is rather than reviewing each record individually. Fields with low confidence are flagged for deferred review. The system presents a “review later” queue so the user can return to uncertain items after completing the initial setup.

This scenario is the primary path for customers importing from Amazon, Uline, or other distributor export formats. The deferred validation model allows the tenant to have a working system within minutes of signup, with data quality improving over subsequent sessions. Items validated by a user have their confidence flags cleared; items remaining in the queue are surfaced in periodic review prompts.

OAM::CFG::0002 — Phased Rollout by Inventory Area

A new tenant implements the Arda Kanban system incrementally, starting with one category, vendor, or physical location rather than attempting to onboard the entire inventory at once. This reduces risk and allows the team to develop operational habits on a small scope before expanding.

Persona	Owen Ownerton (Business Principal)
Status	Partial

OAM::CFG::0002::0001.US — Start Small with One Inventory Area

The user selects a single category, vendor group, or physical storage area as their first rollout scope. All other items are deferred. Within the selected scope, the user configures minimum stock levels, prints cards, and establishes the physical bin structure before moving to the next area. The system does not enforce this phased approach structurally — it is an operational pattern supported by filtering tools in the Item list (such as filtering by vendor) that allow the user to focus on a subset.

OAM::CFG::0003 — Physical Implementation Guidance

First-time users need guidance on how to physically arrange bins, cards, dividers, and inventory areas to support a Kanban replenishment workflow. This content-delivery use case covers examples and instructional material that accompany the product.

Persona	Owen Ownerton (Business Principal)
Status	New-distinct

OAM::CFG::0003::0001.US — Access Physical Setup Examples and Videos

The user navigates to a help or onboarding section and finds examples showing how to organize bins, cards, and dividers in a physical shop environment. Content includes photos or videos of common configurations (single-card bins, dual-bin Kanban, card board setups). The user applies the guidance to set up the physical side of their system before or alongside configuring items in the software.

OAM::CFG::0004 — User and Tenant Display Preferences

The system applies and persists display preferences for list views — column visibility, column order, and column widths — per user and per tenant. These preferences govern the initial state of every entity list page and are saved automatically when the user changes the configuration.

Persona	Irene Itemsworth (Inventory Manager)
Depends	GEN::LST::0001
Status	Covered

OAM::CFG::0004::0001.FS — Apply Initial Display Preferences

When a user navigates to an entity list (Items, Order Queue, Purchase Orders, etc.), the system looks up the stored column configuration for that user and tenant. If a preference exists, the list renders with the saved column set and order. If no preference exists, the system applies business-requirement-driven defaults for that entity type.

This scenario is the read-side companion to the persist scenario below. It fires on every list page load, making preferences observable to the user across sessions and across devices that share the same account. The preference lookup is performed server-side during the BFF response composition for the page.

OAM::CFG::0004::0002.FS — Persist Column Configuration

When a user changes column visibility or column order in a list view, the system saves the new configuration as a preference associated with that user and tenant. The preference is stored per entity type and per tab (e.g., Published Items and Draft Items in the Items list maintain independent configurations). On subsequent page loads, the saved configuration is applied automatically.

Column resize events are also persisted, allowing the user to widen or narrow columns to fit their content. The persistence mechanism is currently implemented via localStorage keyed by tab, with synchronization to the server as a planned enhancement.

Summary

Use Case	Scenarios	US	FS	UC
OAM::CFG::0001 Deferred Validation During Onboarding	1	1	0	0
OAM::CFG::0002 Phased Rollout by Inventory Area	1	1	0	0
OAM::CFG::0003 Physical Implementation Guidance	1	1	0	0
OAM::CFG::0004 User and Tenant Display Preferences	2	0	2	0
Total	5	3	2	0

---