Repository navigation
Fill in ORBIT records for Privateer and the Gemara whitepaper - #72
Merged
Merged
Conversation
eddie-knight
force-pushed
the
orbit-gemara-privateer
branch
from
November 17, 2026 18:11
b655bdb to
b58730a
Compare
Privateer: Security Insights link (privateerproj/pvtr), description from privateerproj.com, relationships (implements gemara, consumes osps-baseline, produces gemara), personas and problems. Its Security Insights row is added to the snapshot; other rows are left as they were. Gemara whitepaper: personas and problems about the model's principles, as distinct from Gemara's schemas and SDKs. Gemara gains a hedged package-manager persona note. osps-baseline: gemara edge is implements, not consumes; the catalog is written in Gemara's schema rather than reading Gemara data. Drop the stale ORBIT note from uncategorized.yml. Signed-off-by: Eddie Knight <knight@linux.com>
eddie-knight
force-pushed
the
orbit-gemara-privateer
branch
from
November 17, 2026 18:35
b58730a to
8895380
Compare
| note: >- | ||
| Reads risk and compliance status rolled up through Gemara's model rather than from disconnected, | ||
| hand-assembled spreadsheets. | ||
| - id: developer |
Collaborator
There was a problem hiding this comment.
The linter doesn't like this indentation.
| - id: developer | ||
| note: >- | ||
| Capture all requirements, from security to design documents, into machine-ready specifications | ||
| to ensure that your developer and agents have shared clarity on what is needed at every stage. |
Collaborator
There was a problem hiding this comment.
Suggested change
| to ensure that your developer and agents have shared clarity on what is needed at every stage. | |
| to ensure that your developers and agents have shared clarity on what is needed at every stage. |
| Maps threats, controls, and evidence onto Gemara's layered schema to drive automated, | ||
| repeatable risk assessment. | ||
| Capture all requirements, from security to design documents, into machine-ready specifications | ||
| to ensure that your developer and agents have shared clarity on what is needed at every stage. |
Collaborator
There was a problem hiding this comment.
Suggested change
| to ensure that your developer and agents have shared clarity on what is needed at every stage. | |
| to ensure that your developers and agents have shared clarity on what is needed at every stage. |
| compatible_with: [darnit, minder, privateer] | ||
| relationships: | ||
| - kind: consumes | ||
| - kind: implements |
Collaborator
There was a problem hiding this comment.
Given that we have a produces relationship, that seems appropriate here?
funnelfiasco
approved these changes
Nov 18, 2026
funnelfiasco
left a comment
Collaborator
There was a problem hiding this comment.
I'd like to see Evan's comments addressed, but I don't see any of them as a blocker
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.
Privateer: Security Insights link (privateerproj/pvtr), description from privateerproj.com, relationships (implements gemara, consumes osps-baseline, produces sarif), personas and problems. Its Security Insights row is added to the snapshot; other rows are left as they were.
Gemara whitepaper: personas and problems about the model's principles, as distinct from Gemara's schemas and SDKs. Gemara gains a hedged package-manager persona note.
osps-baseline: gemara edge is implements, not consumes; the catalog is written in Gemara's schema rather than reading Gemara data.
Drop the stale ORBIT note from uncategorized.yml.