AgentSkillsCN

Arco Architecture

从集成者的视角出发,深入剖析 Arco 生态:品牌矩阵、传统与现代系统、数据源与事实依据。

SKILL.md
--- frontmatter
description: "Arco ecosystem from Integrator's perspective: brands, legacy/modern systems, sources of truth"
user-invocable: false

Arco Architecture

Arco ecosystem as seen from Integrator. This skill grows incrementally during debug sessions.


Brands

  • SAS (Sistema Ari de Sa)
  • SAE (Sistema de Apoio ao Ensino)
  • IS (International School)
  • NSE (sub-brands under NSE umbrella)

Details on sub-brands and brand-to-system mappings will be filled as we discover them.


Legacy 1.0 Systems

SystemDescription
Protheus SASERP for SAS brand
Protheus SAEERP for SAE brand
Protheus ISERP for IS brand
SAP1Legacy SAP instance
B2C StoreLegacy e-commerce (B2C)
B2B StoreLegacy e-commerce (B2B)

Modern 2.0 Systems

SystemDescription
CRM (Salesforce)Customer relationship management
OMS (Salesforce)Order management system
SAP4Modern SAP instance
WMS (Oracle)Warehouse management
TMSTransportation management
Meu Arco B2CModern B2C platform
Meu Arco B2BModern B2B platform
Configurador (Salesforce)Product configurator
4MDGMaster Data Governance SaaS -- product data management, registration centers, data quality

Sources of Truth

DomainSource
SchoolsCRM (Salesforce)
Products4MDG
RF / ParentsCRM (Salesforce)
Sales AgreementsLegacy ERPs (Protheus SAS/SAE/IS)

Order & Invoice Flows (per brand)

SAS:

code
SAS Stores 1.0 (+ Isaac as exception) -order-> Integrator -> OMS -invoice-> Integrator -> Protheus SAS (ERP 1.0)

Integrator handles both order ingestion and invoice delivery for SAS.

NSE:

code
Meu Arco B2B 2.0 -order-> OMS (direct, no Integrator)
OMS -invoice-> Integrator -> SAP1 (ERP 1.0)

Integrator handles only the invoice leg for NSE.

SAE:

code
OMS -> SAP4 (direct, no Integrator involvement)

General rule: Integrator sits in the order path only for 1.0 stores (+ Isaac as exception). 2.0 stores talk to OMS directly.

More flows will be added as we discover them.


Integrator's Role

  • Anti-corruption layer between 1.0 and 2.0 systems
  • Strangler-fig facade -- gradually replaces legacy integrations as 2.0 systems mature
  • Normalizes data formats, translates between system-specific schemas
  • Handles order ingestion from 1.0 stores (+ Isaac) to OMS
  • Handles invoice delivery from OMS to legacy ERPs (SAS -> Protheus SAS, NSE -> SAP1)
  • Grows incrementally as more flows migrate from 1.0 to 2.0