feat!: adds initail monorepo structure

[jpower432]

Types of changes

• Hot fix (emergency fix and release)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation (change which affects the documentation site)
• Breaking change (fix or feature that would cause existing functionality to change)
• Release (develop -> main)

Quality assurance (all should be covered).

• My code follows the code style of this project.
• Documentation for my change is up to date?
• My PR meets testing requirements.
• All new and existing tests passed.
• All commits are signed-off.

Summary

Adds uv monorepo implementation. This is still WIP and very early. Adding a PR for early feedback.
Closes #1877

Key links:

• Sonar coverage

Before you merge

• Ensure it is a 'squash commit' if not a release.
• Ensure CI is currently passing
• Check sonar. If you are working for a fork a maintainer will reach out, if required.

[jpower432]

@degenaro @vikas-agarwal76 @butler54 Opening this for early feedback. I'm running into some test failures in a couple pipelines, and haven't had a chance to fully investigate yet. If anyone has the time to take a look and offer suggestions on fixing these, your help would be greatly appreciated!

[degenaro]

After a brief review, this looks like a great start. Some random comments: - should trestle-cli and trestle-sdk have similar sub-structure? For example, trestle-sdk has *src* but trestle-cli has *trestle*. - should both have *tests*? - we seem to be inconsistent with respect to use of hyphen and underscore in folder names

…

On Mon, Jul 14, 2025 at 8:12 PM Jennifer Power ***@***.***> wrote: *jpower432* left a comment (oscal-compass/compliance-trestle#1904) <#1904 (comment)> @degenaro <https://github.com/degenaro> @vikas-agarwal76 <https://github.com/vikas-agarwal76> @butler54 <https://github.com/butler54> Opening this for early feedback. I'm running into some test failures in a couple pipelines, and haven't had a chance to fully investigate yet. If anyone has the time to take a look and offer suggestions on fixing these, your help would be greatly appreciated! — Reply to this email directly, view it on GitHub <#1904 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAD66XNLT2RKRL23CTGF4LT3IRBP3AVCNFSM6AAAAACBQLRMXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANZRGM4TCNRZGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jpower432]

Some random comments:

• should trestle-cli and trestle-sdk have similar sub-structure? For example, trestle-sdk has src but trestle-cli has trestle.

This structure was created by uv init. trestle-sdk has src because I set it as a library type.

• should both have tests?

I think they should, but trestle-sdk only have the OSCAL classes right now that did not have associated tests.

• we seem to be inconsistent with respect to use of hyphen and underscore in folder names

Good catch! Thanks. I can take a look at that.

[butler54]

I'll take a look at this see what we want to do moving forward

[github-actions]

This pull request has been automatically marked as stale because it has not had activity within 90 days. It will be automatically closed if no further activity occurs within 30 days.