A primary challenge in this task is the subtle variations in the SATF and SASF formats, specifically headers and sequence invocation, between NISAR and Psyche. While the command steps themselves are identical, the core structures differ.

Currently, the architecture defaults to a SeqJSON core output. Users can either extend this core for their mission, as we did for Clipper or bypass it entirely to generate custom outputs like SATF/SASF, as we did for Psyche and NISAR.

To address this, I propose integrating an AERIE SATF/SASF core similar to the existing SeqJSON core. This core can be customized for specific missions using adaptation files. This approach allows for extending the core output, rather than completely bypassing SeqJSON and building a custom solution with largely redundant code.

If a mission doesn't ouptut SeqJSON, SATF/SASF, the adaptation file can still completely bypass any of these core output. Alternatively, we could consider adding new the new outputs as separate cores, providing greater flexibility.

AERIE currently lacks the flexibility to choose the default core output.

To enhance this functionality, I suggest introducing options like default-seqJSON, default-satf, and default-sasf during parcel creation. This would configure the editor to use the desired core as output and enable missions to customize it via the adaptation for their specific needs, similar to how Clipper tweaked SeqJSON.