How RawParserKit Is Constructed

Thu, 30 Jul 2026 00:00:00 +0000

How RawParserKit Is Constructed

RawParserKit is RawCull’s camera-file boundary. It knows how Sony ARW and Nikon NEF files are structured, how to locate their embedded JPEGs and AF metadata, and how to turn those sources into orientation-normalized images and display-ready metadata.

The package stops at decoding. It does not score sharpness, generate embeddings, group bursts, cache application results, or decide which photo should be kept.

1. Begin With The Package Boundary

RawParserKit owns:

RawCull Packages

Thu, 30 Jul 2026 00:00:00 +0000

RawCull Packages

RawCull is split across four reusable Swift packages. Each package owns one kind of knowledge and deliberately avoids importing the others. RawCull is the composition root: it decodes a file and capture metadata with RawParserKit, asks PhotoAnalysisKit or PhotoAIKit to measure or index it, translates the evidence into RawCullCore values and decisions, and presents or persists the outcome.

flowchart LR
 Files["ARW, NEF, and rendered files"] --> Parser["RawParserKit\ndecode + capture metadata"]
 Parser --> Host["RawCull adapters\nsource and cache policy"]
 Host --> Analysis["PhotoAnalysisKit\nsharpness + focus evidence"]
 Host --> AI["PhotoAIKit\nimage/text embeddings + segmentation"]
 Analysis --> Host
 AI --> Host
 Host --> Core["RawCullCore\nburst grouping + ranking"]
 Core --> App["RawCull UI, persistence, and culling actions"]

The arrows are runtime data flow, not package dependencies. The four sibling packages do not depend on one another; the RawCull application imports and adapts them.

Raw on RawCull

How RawParserKit Is Constructed

How RawParserKit Is Constructed

1. Begin With The Package Boundary

RawCull Packages

RawCull Packages