docs: add regulated-industries — structural fit of gitagent for compliance-heavy domains#44
Open
Priyanshu-Priyam wants to merge 1 commit intoopen-gitagent:mainfrom
Open
Conversation
…Close example Made-with: Cursor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
docs/regulated-industries.md— documenting the structural fit between gitagent's git-native architecture and regulated industries that have maker-checker controls, audit requirements, and exception workflows.Proposed by @shreyas-lyzr in the GitClose review.
What's in the doc
git log, SOD = branch protection, etc.)On the spec side
The
complianceblock (segregation_of_duties,supervision,recordkeeping) is the natural complement on the schema side. GitClose currently usesmetadatafor these fields — happy to follow up with an RFC if schema additions are wanted for finance/regulated agent types.