Repository navigation
docs: a README that says what Sigil does, how a proof works, and where it stands - #22
Merged
Merged
Conversation
…e it stands Also corrects METHODOLOGY: evidence is attested when produced in CI, and the CI proving workflow is not live yet.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
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.
The README was a 12-line "under construction" stub. This replaces it with the front door: the problem, what Sigil does, a quick start, how a proof works, trust levels, an honest status and the repo layout.
How it was written:
packages/sigil/src/scan/BENCHMARK.md(47 benign skills with zero high or critical findings, all 14 malicious samples flagged). Agent counts come fromcore/ids.ts(22 agents plusgeneric).submittedanduntested, the first local lab runs hit ceiling effects, and no number is published until a run produced it. The header image is the site's OG image, rendered from the live registry, so it can't drift.Also corrects
spec/METHODOLOGY.md, which said evidence "are published with GitHub artifact attestations" in the present tense. The CI proving workflow isn't live yet, so it now says CI-produced evidence is attested and local runs are labelled local until then.The catalog line lists what is on main at this commit. When #17 and #19 land, it gains Next.js, Svelte, Vue, Angular and OAuth.