Your applications

Status is now a dot, not a badge. That departs from the design system's own rule ("status is a mono uppercase badge, never a coloured dot") and from the neutral-fill rule, by the designer's decision. Every state carries a glyph as well as a hue, because colour alone as the only channel fails WCAG 1.4.1 and this product targets 2.2 AA (NFR-09). The six states themselves remain FR-03's undefined vocabulary.

Each card carries a photograph, and nobody owns choosing one. The treatment is baked rather than rendered, for a reason that is not performance: the shader dithers for display, so a live version would ship the untouched photograph in public/ for anyone to open. Baking destroys the faces and the unit insignia in the file itself. The same ownership gap as the glyphs applies one size larger — an image asserts something about what an application is — and the FR-17 onboarding contract has no field for either. An application with no image renders a dashed placeholder, which nothing in these fixtures reaches. The preset, the provenance and the re-bake script live in docs/design/app-imagery/, deliberately outside this directory because this directory gets deleted.

Two things about it are still the designer's to settle. A revoked or device-blocked tile currently carries the same vivid image as an eligible one, so the photograph says nothing about whether the tile works. And the ground behind the dither does not flip with the theme, so a light-mode card is a white panel holding a warm dark block. Both are held until they can be looked at rather than argued about.

Each card carries an application glyph, and the ownership of those glyphs is unowned. The top-right slot shows what the application is at rest and the navigation arrow on hover — and an inert card keeps its glyph dimmed and shows no arrow, because that is what the arrow's own opacity used to encode. The glyphs themselves are chosen here, not specified anywhere: FR-03 says nothing about iconography and the FR-17 onboarding contract has no field for one, so an application onboarded tomorrow has no icon and nobody to assign it. Unmapped applications render a dashed placeholder rather than a plausible default.