Release-readiness stage after Curator-like metadata export/write

[yha9806]

Hi NeMo Curator team,

I am exploring a workflow-native release-readiness stage that runs after Curator-like metadata export/write.

The goal is not to replace Curator, filtering, deduplication, GPU acceleration, or training workflows. The stage would take selected metadata records and emit small review objects for enterprise release handoff:

• source context status
• generated-media label posture
• missing fields
• policy lane
• owner route
• human gate state
• evidence references

The proposed placement is:

Curator-like metadata export -> release-readiness stage -> review packet -> human gate -> evidence ledger

I have built a public-safe synthetic package that exercises this stage with external-safe metadata rows and representative workflow-row shapes. I am not attaching that package here because this is a public discussion.

My question is about integration surface:

Is release-readiness the right downstream surface to discuss for Curator-style workflows? Who is the right technical or product owner to review this kind of stage contract?

If this belongs in a different channel, issue type, or forum category, I would appreciate being routed there.

[yha9806]

Update: I have now published a public, reproducible engineering handoff for the concrete boundary discussed above:

https://github.com/vulca-org/vulca-nemo-curator-adapter

It targets the real ImageWriterStage Parquet output boundary at the pinned Curator commit 15cc645cbf9e9314fed9e11fc89f6535ea9a8820.

The repository includes:

• a narrow downstream Parquet boundary adapter;
• public-safe synthetic fixtures;
• 87 passing tests;
• three source-derived evidence diagrams;
• a searchable two-page technical brief;
• explicit claim and compatibility limitations.

Technical brief:
https://github.com/vulca-org/vulca-nemo-curator-adapter/blob/main/docs/nvidia-maintainer-handoff.md

My review request is deliberately narrow:

1. Does this correctly model the relevant ImageWriterStage Parquet boundary?
2. Which NeMo Curator maintainer is the appropriate reviewer for this interface?
3. If the boundary is useful, should the next step be an upstream design issue, an example/tutorial, or a narrowly scoped contribution?

This remains an independent downstream adapter. No NVIDIA endorsement, generic NeMo/Cosmos compatibility, or upstream integration is claimed.

Routing request: @nemo-curator-leads