You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
P2: Add Protocol Review pipeline for Own.NET obligation findings #46
Own.NET should own the semantic checking for obligation/barrier protocols. OwnAudit should consume the resulting findings and turn them into adoption-friendly review artifacts: baselines, SARIF, markdown, verdicts, and new-vs-existing gates.
This mirrors the existing architecture-review direction: Own.NET emits facts/findings; OwnAudit owns baseline/diff/reporting/risk.
What old/baselined violations remain visible but non-blocking?
Which findings are deterministic/blocking vs advisory?
What should a reviewer look at first?
What evidence/path did Own.NET provide?
Example:
FAIL: 1 new protocol violation.
OWN201: DocumentLoading crosses OnPropertyChanged(Document)
Evidence:
IsLoaded=false at BigDocumentViewModel.cs:184
OnPropertyChanged(Document) at BigDocumentViewModel.cs:241
IsLoaded=true only at BigDocumentViewModel.cs:260
Scope
OwnAudit should not implement obligation analysis. It only consumes Own.NET output.
Acceptance criteria
Consumes protocol findings from Own.NET JSON/SARIF.
Maintains a protocol baseline file.
Fails only on new non-baselined blocking findings.
Keeps existing/baselined findings visible in the report.
Emits SARIF and markdown.
Produces a small machine-readable verdict for CI/007.
Non-goals
No second checker in OwnAudit.
No LLM-as-truth. LLM can summarize deterministic evidence later.
No perf gates in this slice.
Why this matters
Protocol findings are useful only if they are adoption-safe in dirty legacy code. Baseline/diff is the difference between "this tool caught a regression" and "this tool screamed about ten years of archaeology and got disabled by lunch."
Activity