# Requirements for the Showcase Quality Profile in Archify: The 8 Validation Rules

> Discover the 8 validation rules for Archify's showcase quality profile. Ensure polished diagrams with zero edge crossings and a max stretch factor of 1.35 for public distribution.

- Repository: [tt-a1i/archify](https://github.com/tt-a1i/archify)
- Tags: architecture
- Published: 2026-08-30

---

**The `showcase` quality profile in Archify enforces eight strict geometric constraints—including zero edge crossings, zero bridge jumps, and a maximum stretch factor of 1.35—to guarantee diagrams are visually polished before public distribution.**

Archify validates diagrams against two named quality profiles defined in [`archify/schemas/common.schema.json`](https://github.com/tt-a1i/archify/blob/main/archify/schemas/common.schema.json). The `showcase` profile serves as a strict, opt-in production gate that prevents publication until a diagram satisfies tight visual and compositional rules documented in the project's research evolution files.

## Zero-Tolerance Routing Constraints

The showcase profile implements a zero-tolerance policy for visual clutter in edge routing, as specified in [`docs/research-visual-evolution-round-44.md`](https://github.com/tt-a1i/archify/blob/main/docs/research-visual-evolution-round-44.md).

### Zero Edge Crossings

No edges may intersect unrelated opaque nodes. Any crossing detected between an edge and a non-incident node constitutes a hard validation failure. This rule ensures planar routing that preserves visual clarity in dense diagrams.

### Zero Bridge Jumps

Edges cannot jump over other edges using "bridge" shortcuts. The validator rejects any routing that creates artificial crossings over existing edge geometry, enforcing true planar or grid-aligned routing without decorative bridges.

### Maximum Two Bends Per Edge

Each edge may contain no more than two directional-change points. This constraint forces direct, efficient routing between nodes and eliminates convoluted paths that degrade readability.

## Geometric Ratio and Length Constraints

Documented in [`docs/research-visual-evolution-round-4.md`](https://github.com/tt-a1i/archify/blob/main/docs/research-visual-evolution-round-4.md), these rules govern the mathematical properties of individual edge segments.

### Maximum Stretch Factor

The ratio of an edge's actual length to its orthogonal projection must not exceed **1.35**. This prevents excessively circuitous routing between connected nodes, ensuring edges follow reasonably direct paths even when orthogonal routing is required.

### Minimum Internal Segment Length

Any internal segment of an edge must be at least **16 px** long. This rule eliminates microscopic fragments that can render poorly at different zoom levels or complicate the geometry engine.

## Spatial Composition Requirements

These spacing rules ensure adequate clearance between diagram elements, also defined in [`docs/research-visual-evolution-round-4.md`](https://github.com/tt-a1i/archify/blob/main/docs/research-visual-evolution-round-4.md).

### Node-to-Node Spacing

Nodes must be spaced at least **40 px** apart. This minimum gap prevents overcrowding and ensures that distinct elements remain visually separable in exported artifacts.

### Container Gutter

The clearance between a node and the edge of its container must be at least **20 px**. This internal padding guarantees that nested layouts do not feel cramped against their parent boundaries.

### Label-Route Clearance

Labels must maintain at least **4 px** of clearance from any route they annotate. This padding prevents text from overlapping with connecting lines, preserving legibility.

## Schema Definition

The quality profile system is explicitly defined in [`archify/schemas/common.schema.json`](https://github.com/tt-a1i/archify/blob/main/archify/schemas/common.schema.json), which lists the two allowed profile values:

```json
{
  "enum": ["standard", "showcase"]
}

```

The `showcase` value triggers the full suite of eight validation checks described above, while `standard` applies a more permissive ruleset.

## Summary

- The showcase quality profile requires **zero edge crossings** and **zero bridge jumps** to enforce planar, unambiguous routing.
- Edge geometry is constrained to **at most two bends**, a **stretch factor ≤ 1.35**, and **segment lengths ≥ 16 px**.
- Spatial composition mandates **40 px node spacing**, **20 px container gutters**, and **4 px label clearance**.
- The profile is defined as a strict enum value in [`archify/schemas/common.schema.json`](https://github.com/tt-a1i/archify/blob/main/archify/schemas/common.schema.json) alongside the standard profile.

## Frequently Asked Questions

### What is the difference between the standard and showcase quality profiles in Archify?

The `standard` profile applies basic validation rules suitable for draft diagrams, while the `showcase` profile activates all eight strict geometric constraints documented in the research evolution files. Only diagrams passing the showcase tier are considered production-ready for public sharing.

### How does Archify calculate the stretch factor for an edge?

According to [`docs/research-visual-evolution-round-4.md`](https://github.com/tt-a1i/archify/blob/main/docs/research-visual-evolution-round-4.md), the validator computes the ratio of the edge's actual path length to its orthogonal projection (the direct horizontal or vertical distance between endpoints). If this ratio exceeds 1.35, the diagram fails showcase validation.

### Can I customize the threshold values for the showcase profile?

No, the showcase profile thresholds—including the 1.35 stretch factor and 16 px segment minimum—are hardcoded constants defined in the research documentation. Archify treats these as immutable production standards rather than configurable parameters.

### Where does Archify check for zero bridge jumps?

The bridge jump validation logic is implemented according to the specifications in [`docs/research-visual-evolution-round-44.md`](https://github.com/tt-a1i/archify/blob/main/docs/research-visual-evolution-round-44.md), where the engine verifies that no edge routes over another edge using bridge decoration shortcuts.