Hi @funnelfiasco and @eddie-knight! Following up as promised now that PR #494 has successfully merged and the Gemara v1 migration is live.

I’ve pulled the latest main branch and spent some time reviewing the new architecture (specifically the types.Baseline struct and the gemara.ControlCatalog). Based on that, here is my proposed technical approach for generating the reverse crosswalk:

Proposed Implementation:

CLI Flag: Register a new --crosswalk-output flag in cmd/internal/cmd/compile.go alongside the existing --output and --checklist-output flags.

Data Transformation: Utilize the types.Baseline returned by loader.Load() . I will write a collection function that iterates through Catalog.Groups -> Controls -> Guidelines. It will build a reverse mapping structure (likely a nested map: Framework -> Requirement -> []Control IDs).

Output Generation: Create a new generator file (e.g., pkg/baseline/generator_crosswalk.go) that takes this mapped data and formats it into a clean Markdown table, maintaining alphabetical sorting for consistency in diffs.

Does this align with your vision for the feature? I'm open to suggestions and new ideas if you think a different approach would fit the new architecture better!

Create reverse crosswalks for other frameworks #379

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions