Adding small decoder to model architecture, recognized as required, keys categorized as junk

[Astropulse]

So, I'm adding a very small decoder to a v1 SD model, it has this structure:
0.weight [64,4,3,3] 0.bias [64] 2.conv.0.weight [64,64,3,3] 2.conv.0.bias [64] 2.conv.2.weight [64,64,3,3] 2.conv.2.bias [64] 2.conv.4.weight [64,64,3,3] 2.conv.4.bias [64] 3.weight [48,64,3,3] 3.bias [48]

I've added a component, component class, and architecture for both the decoder itself and the new model architecture ["UNET-v1", "VAE-v1", "CLIP-v1", "DECODER-v1"]. It also has a prefix of "decoder.". In the advanced section the decoder is recognized as a required part of the model, however once the full model is assembled the 10 keys of the decoder are seen as junk data, and all of the keys are seen as unknown, and the model cannot be saved. The decoder on its own is not viewed as junk, but once other components of the model are added (clip, unet, vae) it is seen as junk. The decoder requirement is being recognized as filled by the advanced tab, but the basic tab doesn't view it as a model component.

I'm at a complete loss, the architecture is being recognized, and the decoder itself is loaded as a valid model, but it cannot be assembled into a final model. Best I can figure, something is going wrong with get_allowed_keys but I haven't been able to figure out what.

Any help or guidance would be appreciated.