# engineering-platform

Use for developer, infrastructure, AI, data, security, and technical platform
decks.

Hard gates:

- Preserve technical precision while reducing visual complexity.
- Use system diagrams, dependency maps, sequence flows, latency/cost/SLO views,
  or developer workflows as the core proof objects.
- Keep executive-level claims above the diagram and technical labels inside the
  diagram.
- Do not translate technical concepts into vague business slogans.
- Connector direction, dependency direction, and containment boundaries must be
  technically correct, visually attached, and legible after rendering.

Required proof objects:

- Architecture or workflow map.
- Product proof slide with concrete capabilities.
- Metric evidence tied to the technical system.
- Risk, reliability, cost, or roadmap slide when relevant.

Failure signs:

- Boxes labeled only "AI layer", "data", or "platform" with no specificity.
- Dense technical doc dumped onto a slide.
- Claims that do not point to any diagram element.
- Sequence / dependency diagrams with floating or ambiguous connectors.
- Shared-role boxes that drift in size, padding, or alignment without meaning.
