feat: add verified compatibility preview - #130
Draft
ErenAri wants to merge 1 commit into
Draft
Conversation
ErenAri
force-pushed
the
agent/falco-conformance-pilot
branch
2 times, most recently
from
August 9, 2026 14:44
9c8cef5 to
5ab522a
Compare
35 tasks
ErenAri
force-pushed
the
agent/falco-conformance-pilot
branch
from
August 9, 2026 15:14
5ab522a to
23723cd
Compare
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.
Summary
Introduces a certification-like Verified Compatibility Preview, initially scoped to the exact Falco
scap-openbinary and its realmodern_bpfloader path.falco-modern-bpf-v0.1conformance profile and canonical five-kernel matrixbpfcompat conformance evaluatewith explicitconformant,nonconformant, andinconclusivedecisionsWhy
BPFCompat should make narrow compatibility claims that consumers can verify, not broad self-declared certification claims. This preview proves the model against Falco while retaining explicit scope and failure semantics.
Impact and merge timing
Draft: do not merge before v0.4.0 production graduation. This adds supported CLI and workflow behavior, so merging it during the active four-week evidence window could require a new release candidate and restart the campaign. It is staged as post-v0.4/v0.5 work.
This does not claim Falco or CNCF endorsement and does not certify the full Falco daemon or rules engine.
Validation
go test ./...go test -race ./...go vet ./...golangci-lint run --timeout=5m --new-from-rev=origin/maingo run github.com/rhysd/actionlint/cmd/actionlint@v1.7.11git diff --checkscap-open --modern_bpf --num_events 10dress rehearsal passed all five required KVM profiles and all eight profile assertionsTracks the post-v0.4 direction described in the existing graduation record; no new tracking issue is required.