# .md Studios Photography

## Purpose

Photograph accountable work—not startup theater. Images must show a real operating context, named process, physical constraint, or transfer artifact.

## Subjects

- Annotated paper, prototypes, field notes, and physical workflows
- Operator hands performing real work with consent
- Packaging, routing, inspection, repair, and logistics details
- Diligence rooms, evidence binders, and documented handoff artifacts

## Direction

Use directional natural or practical light. Preserve material texture and purposeful negative space. Favor documentary distance over staged triumph. Crop 4:5 portrait, 3:2 landscape, or 1:1 editorial only when the operating object remains legible.

## Reject

- Server racks, hooded coders, neon terminals, blue holograms
- Generic offices, handshake photography, floating dashboards
- Untraceable stock imagery or generated “evidence”
- Images that imply a result the receipt does not support

## Provenance

Every production image requires a sidecar record validated by `imagery/provenance.schema.json`, including creator, date, context, source, license, consent or release status, allowed uses, and AI-generation status.

Evidence-surface photography must declare `ai_generated=false`. AI imagery may illustrate a concept only when visibly labeled as illustration and never when presented as market, product, operator, customer, or diligence evidence.

## Accessibility

Provide useful alt text naming the operating subject and relevant action. Do not encode status or decision meaning in photography alone.