08 · Operations · Notion + Miro/PDF
Supply Plan
After the company acquired another company, integrate both supply flows into one supply plan capable of serving all stores.
Project context — organizations, products, and platforms evidenced in the source
Pague MenosEExtrafarma
- Role
- Solutions Architect · Back-End
- Domain
- Operations
- Sources
- Notion + Miro/PDF
- Published artifacts
- 9
Evidence archiveMacro supply-flow diagram.
Context
The problem and its boundary.
Architecture study for direct-entry store replenishment, covering current and target flows, order states, data model, integrations, temporal gaps, retries and hybrid cloud/on-premises boundaries.
Alexsandro is explicitly credited in the artifact as Arquiteto Chapter Esmeralda.
Decisions & deliverables
- Macro Supply Flow
- Order Status Journey
- Entity-Relational Model
- Context Diagram
- Architecture diagram
- Authentication Flow
- AS-IS and TO-BE supply flows
- order lifecycle and entity model
- API and event integration
- AWS and on-premises boundaries
- authentication, retries and operational gaps
Technology
- PostgreSQL
- CloudFormation
- API Gateway
- Node.js
- NestJS
- TypeORM
Evidence archive
Real diagrams, interfaces and documents.
Open any artifact to inspect the full local image.
What this archive can prove
Published authorship. Claims proportional to the source.
- The visible page text does not name the client; Pague Menos is only filename-level evidence.
- No detailed responsibilities, repository, URL, scale, result or date is present.
- The page does not distinguish proposed design from deployed system state.