# Implementation Architecture Diagram Experiment

Task: DIAGRAM-SFDC-IMPLEMENTATION-EXPERIMENT

## Source Inventory

- `sfdc_customer_zero_implementation.pdf`: one-page layered enterprise implementation architecture. It uses a title/legend band, horizontal layer bands, a left-side layer label rail, system cards, internal subcards, many vertical integration lines, and external/source systems at the bottom.

## Element Contract

- Audience: architecture reviewer evaluating system boundaries and data movement.
- Reading flow: top application layer down to source systems, with lateral data sharing between platform instances.
- Layers: Application/Service/Agentic, BI/Reporting, Data Platform, External Data, Source.
- Nodes: workspace cards, platform cards, external system cards, and integration bars.
- Connectors: mostly vertical, orthogonal, and labeled only for cross-layer meaning.
- Visual constraints: layer labels must align with bands, connectors must not hide system names, and dense icons should be abstracted into compact badges.

## Prompt Used

Create a layered implementation architecture diagram as SVG.

Use a top title band and compact legend. Build five horizontal layers with a
purple label rail on the left. In the top layer, place five organization cards
under a collaboration bar. In the reporting layer, place a central analytics
card. In the data platform layer, place two platform instance cards with data
space chips and feature blocks. In the external data layer, place a shared query
and federation bar plus three data platform cards. In the source layer, place
five source system cards.

Use vertical orthogonal connectors between layers and one horizontal connector
between platform instances. Abstract vendor icons as small colored badges. Keep
all text inside cards, avoid connector overlap with labels, and re-evaluate
layer heights after rendering.

## Evaluation Findings

- Dense enterprise diagrams need abstraction rules; copying every icon and micro-label from a reference makes the output unreadable.
- Layer bands are the primary structure; connectors should be secondary and lower contrast.
- The prompt must declare which labels are essential versus optional because source diagrams contain many small badges.
- Future master rules should add a density budget for architecture recreations: max cards per layer, max badges per card, and required zoom/screenshot review.