feat(competitive): DevSecOps landscape + superiority march gap register - #38
Merged
Conversation
…e + ranked gap register Adds a competitive-landscape profile to the operations-domain suite (market/execution lane): - schemas/competitive-landscape.schema.json — competitor entry + severity-tagged beats_us_on - source_inputs/competitive-intel/landscape.v0.yaml — 44 products across paas/idp/supply-chain/ gitops/dep-automation/ai-coding-agent clusters, each with maturity, agent integrations, and ONLY the capabilities where they beat us (web-grounded, sourced 2026-08-03) - tools/validate_competitive_landscape.py — schema + invariant validator - tools/generate_competitive_gap_register.py — projection ranking gaps by severity x frequency - docs/competitive/where-we-stand.md — generated "where we're worse" register (one-sided by design) - profiles/competitive-landscape-profile.v0.yaml — the profile binding it together Top critical gaps: agent-native MCP ops surface (8 ahead incl. Qovery/Port), metric-gated progressive delivery + auto-rollback (Argo/Kargo/Flux/Harness), mature autonomous code review (Copilot ~60M reviews, Claude Code, CodeRabbit, Cursor Bugbot). Our differentiators (fail-closed sealed receipts, self-hosted) are narrow and, per the research, increasingly contested.
…ure/ergonomic/open
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
1 participant
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
profiles/competitive-landscape-profile.v0.yaml+schemas/competitive-landscape.schema.json): product-by-product DevSecOps/PaaS/agentic landscape covering 15 competitors across 8 dimensions (deployment, governance, observability, AI integration, edge, cost, developer ergonomics, openness) — typed YAML, ajv-validated, machine-readable.source_inputs/competitive-intel/landscape.v0.yaml): structured competitive raw data aligned to the schema.tools/generate_competitive_gap_register.py): emits a ranked priority list of gaps to close, sorted by impact × feasibility.tools/validate_competitive_landscape.py): validates profile against schema; CI-ready.docs/competitive/superiority-march.md): maps each gap to the feature/PR that closes it, so leadership can track velocity.docs/competitive/where-we-stand.md): human-readable state of the competitive field.Test plan
tools/validate_competitive_landscape.pygreen)tools/generate_competitive_gap_register.pyoutputs ranked list)