Having looked at this a bit more deeply:

1. Policy is used in Python code in daf_persistence, pex_config (makePolicy), obs_monocam, ip_diffim (for backwards compatibility once DM-21065 merged) and meas_algorithms (DM-21065).
2. Tests use Policy in daf_persistence and pex_config (makePolicy).
3. Many obs packages declare a pex_policy dependency even though they have no pex_policy paf files or code usage.
4. A PAF file is found in meas_extensions_photometryKron but removing it does not cause any failures and there is no obvious place where the paf file would be read.
5. There are a number of python examples that use Policy but it seems they are long bit-rotted referring to meas_astrom methods and packages that no longer exist.
6. astrometry_net_data seems to have many .paf files (also one in meas_extensions_astrometryNet) but removing the paf files doesn't break anything.
7. obs_cfht defines the Megacam filters in a paf file but I don't see the code to read that file.
8. cat package has two paf files that seem to be unused.

I think the plan on this ticket is therefore

1. remove the unused paf files to avoid future confusion.
2. Convert monocamMapper.paf to standard mapper YAML format used by other obs packages.
3. Remove pex_policy dependency from obs packages that don't use pex_policy.

There are nominally three distinct types of thing to review:

1. Removal of unused PAF files: afw, obs_test, meas_extensions_astrometryNet, astrometry_net_data, obs_cfht, cat, meas_extensions_photometryKron
2. Removal of broken examples that used pexPolicy: meas_astrom, meas_extensions_astrometryNet, meas_deblender, obs_cfht
3. Removal of unnecessary dependency on pex_policy: obs_decam, obs_lsst, obs_lsstSim, obs_comCam, obs_sdss
4. Switch from PAF mapper to YAML mapper and other cleanups: obs_monocam

Jenkins passes with these changes. The only thing that really needs review is obs_monocam.

Simon Krughoff I've been asked to ask you about the removal of the examples. Can you please take a look at the pull requests for meas_astrom, meas_extensions_astrometryNet, meas_deblender, and obs_cfht to ensure that there is not some gold in there that needs to be retained?

I asked about meas_deblender on Slack and Paul Price suggested that there was no problem with deleting those. For obs_cfht we know that the camera code from policy is broken (DM-11560) and is no longer the source of truth (DM-5524). I think you advocated its removal in DM-11560 and we of course will be wanting to rewrite all this using YAMLCamera.

Type 1, 3, 4 are OK.  Awaiting confirmation from others on Type 2.

Simon Krughoff The question for obs_cfht is whether the existing broken code will be at all helpful in writing the new YAMLCamera.

I absolutely think the broken examples and deprecated camera generation code should go away.

Thanks for the reviews. All merged.