Security event CEL engine handoff#62
Closed
ebursztein wants to merge 1214 commits into
Closed
Conversation
feat: make capsem shell launch the TUI control plane
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
Security-event/CEL engine lane is complete and ready for network-team reconciliation. This PR is intentionally a draft handoff branch, not a direct merge into current
main.The branch finishes the unified security event spine:
SecurityEvent/CEL projection for enforcement and detectionSecurityEventTypecontract with family consistency and callback validationNetwork-team handoff
Network/parser work should integrate here before the separate
origin/mainintegration sprint. The dependency surface is the typed security event contract, not callback strings or local policy shortcuts.Network-team invariants to preserve:
SecurityEventfields before CEL projectioncapsem-security-engine; no second decision providerWhy draft
This branch is currently behind
origin/mainby 118 commits after fetch. Incoming main includes large MCP runtime/load, network parser, DB write/logger, telemetry, security-engine, and benchmark-path changes. Those should be reconciled as a dedicated integration sprint, not accepted as merge fallout.Verification
just benchmarkpassed on macOS arm64: 11 passed, 7 deselecteduv run pytest tests/test_archive_superseded_benchmark_artifacts.py tests/test_benchmark_contract.py tests/capsem-serial/test_endpoint_latency_benchmark.py::test_endpoint_latency_percentile_keeps_p95_distinct_from_max -qpassed: 12 passeduv run python scripts/archive_superseded_benchmark_artifacts.py --dry-runreports no superseded benchmark artifactsgit diff --checkcleanNext sprint
origin/mainwith focused invariant tests and benchmark comparison.