NITETIME MUD // PHOTO HISTORY AND THE LAB
=========================================

YOUR PRIVATE CONTACT SHEET - VERIFIED / DEPLOYED

  photos                  newest 50 photographs owned by this Character
  photo <id>              inspect one photograph you own

PHOTO reports the subject, capture time, development state, incidental
visible people and any returned image or lab-error information. A focal
portrait subject appears as the Subject; the separate Visible people
line currently covers incidental Characters.

New SNAP captures are queued with automatic public-release intent.
Existing private captures remain private. Photo history is still
owner-only, and raw scene records stay internal. Public intent does not
mean an image is ready: the unattended renderer and complete Files/Gopher
delivery path remain unfinished. Deliberate portraits still require
capture consent; there is no separate publication-approval step for new
captures.

THE IMMUTABLE NEGATIVE - VERIFIED / DEPLOYED

SNAP stores a detached, structured scene snapshot and a verification
fingerprint. Later changes to a room, name, outfit, held object or
appearance profile cannot rewrite the photographed moment. The live
MUD is authority for what is true now; the snapshot is authority for
what was true when the shutter fired.

The game also creates an internal lab job carrying the capture and its
release intent and safely places a structured job envelope in its camera
outbox. The lab receives the snapshot, not access to the MUD's private
database.

THE DARKROOM - ACTIVE DEVELOPMENT

Image development is an external operation on the workstation. The server
supplies a leased worker contract for new automatic-public jobs, and the
workstation has verified the complete Files/Gopher delivery and receipt path
with one isolated test photo. Production processing is paused while the
metadata plate is replaced by an organ-local GPU renderer, so no new capture
should be treated as a finished scene image yet.

The live system can preserve jobs and apply checked lab results. That
foundation does not mean rendering, sanitized storage publication or
Gopher publication is automated end to end.

NOT DEPLOYED / PLANNED

These are not current player features:

  * organ-local GPU scene inference and visual continuity
  * player-facing completion receipts
  * automatic creation or selection of renderer reference images

Exit photography itself IS deployed. The isolated transport test is public,
but it is not visual-canon acceptance and must not be treated as a scene image.

Next: /mud/visual-continuity.txt