Automated Bootstrapping for Derived Catalogs

Open
#2 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
go
Domain
cli, tooling

Research direction

No files or tests are named. Start by inspecting the existing extend/import implementation and the grcli command structure to understand catalog parsing, validation, and generation. Done should include a defined init workflow that validates the parent URI and Gemara data, records the parent version, supports selecting controls, and emits a child-catalog boilerplate.

Written by the indexing model from the issue text.

Description

enhancement Stale

Description

Currently, the Gemara spec supports creating a catalog based on another (inheritance/selection - extend/import), but the process is manual for creation. Based on the ORBIT Working Group discussion on 2026-05-07, there seems to be a growing need to create layered catalogs on top of the OSPS Baseline.

We need a bootstrapping mechanism in the SDK that supports a user to programmatically generate a "child" catalog from a "parent" catalog.

Proposed Workflow

  • User runs a command like grcli init --from [Parent-Catalog-URI].
  • User selects whether they want to inherit all controls or a specific subset.
  • The tool generates a new Gemara catalog file with metadata already populated.
Success Criteria
  • The bootstrapping logic ensures the parent URI is reachable and valid Gemara.
  • The metadata is automatically linked tso the child catalog knows which version of the parent it was created from.
  • Provide a boilerplate structure for the "new" controls to be added.

Context

  • Specifically addressed the friction point of keeping the Baseline clean while allowing specialized extensions.
  • This functionality would be supported the Gemara Hub initiative by making it easier to publish derivative works.
Dominant language
Go
Stars
0
Forks
2
Avg merge
1d 15h
Merged PRs (30d)
6

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gemaraproj/grcli

All issues in gemaraproj/grcli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.