Working Requirements
ZibiWorks is an evolving modernization story. Requirements and constraints emerge as the team explores business problems, evaluates alternatives, and makes architectural decisions.
This page captures our current understanding, not a specification that was complete from the beginning.
Requirements may be added, clarified, or revised as the journey continues.
How to read this page
Section titled “How to read this page”This is a working register, not a formal specification. It records what the business needs and the constraints that shape the architecture. It does not record how the architecture satisfies them. Those decisions, and the reasoning behind them, live in the installments, and the notes below point to where.
Because the register reflects the story as it stands today, a row can include something that only became clear in a later installment. The last column shows where each item was introduced and where it was refined. Installments that are not yet published are named without a link.
| Status | Meaning |
|---|---|
| Current | Required for the present modernization work |
| Planned | An anticipated business capability that is not running yet |
| Under discussion | Raised, but not yet established or still being evaluated |
Numbers such as “within a few minutes” are illustrative working assumptions for ZibiWorks, not universal standards.
Business capabilities
Section titled “Business capabilities”What the business wants Fulfillment, and the platform around it, to be able to do.
| ID | Requirement or constraint | Status | Introduced / refined |
|---|---|---|---|
| BR-01 | Fulfillment can scale independently of the rest of the monolith | Current | 03 |
| BR-02 | Fulfillment availability and resilience are materially improved before the next major peak season | Current | 03; the deadline shapes the data decisions in 07 |
| BR-03 | Support shipping carriers beyond Handle With Care, keeping provider-specific details out of Fulfillment’s business model | Planned | 06; still anticipated in 07 |
| BR-04 | Support richer partial shipments, where one order becomes several deliveries | Planned | Basic form noted in 04; expected in 07 |
| BR-05 | Support split fulfillment, where one order is filled from more than one warehouse | Planned | 07 |
| BR-06 | Let Fulfillment’s data model evolve on its own schedule, shaped like fulfillment rather than like an order | Current | 07 |
| BR-07 | Give customers one coherent view of an order across Order Management, Inventory, and Fulfillment | Under discussion | 04; whether it is assembled on demand or served from a read model is undecided |
Operational and quality requirements
Section titled “Operational and quality requirements”How well the platform has to behave, and the pressures it has to relieve.
| ID | Requirement or constraint | Status | Introduced / refined |
|---|---|---|---|
| QR-01 | Changes can be made safely, with a smaller blast radius and less regression and coordination effort | Current | 01 |
| QR-02 | Partner changes do not ripple into unrelated internal code | Current | 01; applied to shipping in 06 |
| QR-03 | Variable and peak demand can be handled without scaling the whole platform as one unit | Current | 01, 03 |
| QR-04 | Fewer customer-visible failures, with Fulfillment isolated from failures and deployments elsewhere in the monolith | Current | 01, 03 |
| QR-05 | Security, data integrity, and operability are treated as baseline constraints | Current | 01; data integrity during fallback in 07 |
| QR-06 | Resolve aging hardware, disaster-recovery gaps, seasonal over-provisioning, and slow environment provisioning without a large new capital investment | Current | 02 |
| QR-07 | Separate analytical workloads from operational processing where contention affects the business | Under discussion | 01, The Starting Point; not yet addressed |
| QR-08 | Support additional user experiences through stable API contracts | Under discussion | 01; not yet addressed |
| QR-09 | Clarify ownership and synchronization of connected-device state across the core and telemetry platforms | Under discussion | 01, The Starting Point; not yet addressed |
Data ownership and synchronization
Section titled “Data ownership and synchronization”Who owns Fulfillment’s data, and what the legacy side can rely on while that changes.
| ID | Requirement or constraint | Status | Introduced / refined |
|---|---|---|---|
| DR-01 | Fulfillment is the single authoritative owner of its data, and at any moment exactly one implementation owns the state | Current | 03 (dual presence, single authority); 07 |
| DR-02 | Authority transfers through an explicit, controlled event, never as a side effect of routing | Current | 07 |
| DR-03 | Open fulfillment requests and the history Fulfillment needs carry across the transfer | Current | 07 |
| DR-04 | A synchronized copy stays in the legacy tables for now and never becomes a second source of truth | Current | 03, 07 |
| DR-05 | Handoffs and cancellations reach legacy operational consumers promptly in normal operation, and are never silently missed | Current | 07; illustrative targets in 08 |
| DR-06 | Status screens stay within a few minutes of current, and reports are complete and consistent by morning | Current | 07; illustrative targets in 08 |
| DR-07 | Missing or inconsistent updates are detected and repaired while authoritative data is available | Current | 08 |
| DR-08 | Before authority returns to legacy, its state is reconciled and meaningful enough for the agreed operations to resume | Current | 07; 08 |
| DR-09 | Minimize the risk of losing handoffs and cancellations if the business falls back, with routine statuses allowed to lag up to about 15 minutes. Recovery is an objective, not a guarantee. | Current | 08 |
Modernization and migration constraints
Section titled “Modernization and migration constraints”The conditions the migration has to respect.
| ID | Requirement or constraint | Status | Introduced / refined |
|---|---|---|---|
| CR-01 | Existing screens, reports, jobs, and integrations that read Fulfillment data keep working as authority moves | Current | 07 |
| CR-02 | Minimize changes to legacy business logic, and keep any awareness of the move in temporary migration scaffolding | Current | 07 |
| CR-03 | Keep a usable fallback to the legacy implementation while the new service earns trust | Current | 03 first calls it plausible; 07 clarifies it as a business decision over an agreed subset of legacy capabilities |
| CR-04 | A fallback may restore only an agreed subset of capabilities, and work the legacy model cannot represent is never processed as though it fit | Current | 07; 08 |
| CR-05 | Fallback may reduce capabilities, but it must not knowingly misrepresent or incorrectly process existing operational state. Any potential data loss must be identified, minimized, and addressed through an agreed recovery procedure. | Current | 07; 08 |
| CR-06 | Move in small, individually reversible steps rather than a platform-wide cutover | Current | 01, 03 |
| CR-07 | Change what creates measurable friction, and keep what still serves the business | Current | 01 |
| CR-08 | Migration scaffolding is temporary, with a purpose, an owner, and a removal condition | Current | 03; carried through 05 and 07 |
| CR-09 | Separating Fulfillment removes its dependencies on Order Management and Inventory data, not only its code | Current | 04 |
Where the decisions live
Section titled “Where the decisions live”Each of these requirements is answered by a decision somewhere in the story. This page does not repeat those decisions or the reasoning behind them. It points to them.
- Evolving the monolith instead of rewriting it, using the Strangler Fig approach: 03.
- The business boundary around Fulfillment: 04, and the
IFulfillmentServiceseam that lets old and new implementations stand behind one contract: 05. - Shipping Integration as a utility domain, with Handle With Care as one provider among several: 06.
- Migrating open work, transferring authority once, and keeping a compatibility projection in the monolith’s SQL Server tables: 07.
- Keeping that projection current with domain events and an authoritative API through a temporary migration sidecar: 08.
As the architecture evolves, some decisions may establish patterns that later become shared platform capabilities. Those patterns remain architectural directions until the story formally evaluates and adopts them.
When an installment introduces, changes, or retires a meaningful requirement, this page is updated with it, so it always shows the current state of understanding.