Skip to main content

Roadmap

Project timeline

Delivered scope spans inception to the 2026.01 release. Each step carries its tracking issue. Every item below closed as a tested pull request and verified by execution; the dates are the issue-close dates.

3 October — baseline

  • The product specification was written and reviewed before implementation. The repository, CI, governance documents and website followed (#1, #37-#56).

8 October — first capabilities

  • The rule engine runs a security rule against a test request and returns a verdict. The core decision loop is verified by fixtures (#2, PR).
  • The kernel packet filter compiles, loads under the verifier and detaches cleanly. The eBPF environment is proven (#3), with gate output in lab).

9 October — packet path verified end to end

  • The kernel-to-engine event channel passes its end-to-end test in the lab. Packets become structured events with the correct field layout (#4, PR).
  • Requests score stage-by-stage (the inspection ladder), with verdicts recorded at each stage (#5).
  • HTTP request bodies parse into the structured view the rules operate on (#5, PR).

10 October — v0.1

(Renamed to 2026.01-rc1 at the same commit.)

  • The deployment lab reproduces on demand: cluster, gateway, firewall and a demo application. Each network hop verifies by response headers (#6, PR).
  • The firewall’s verdicts match the vendor-neutral reference rule set (OWASP CRS) on every corpus case — 19/19, with one documented gap. The CI enforces the comparison on all future changes (#7, PR).
  • A security policy written as a Kubernetes resource is compiled and loaded by the platform. Matching traffic is blocked. The apply-to-effect round trip measures 1.5–2.6 s within the 5 s budget (#8, PRs #98/#104).
  • Repeat offenders are dropped in the kernel, bans expire automatically, and every ban produces an evidence record (#10, PR).
  • Every verdict emits three correlated records — trace, metric, log — tied by request id (#11, PR).
  • Automated clients are distinguishable from browsers by traffic fingerprints, validated against published test vectors (#12, PR).
  • A route’s published API schema acts as an allow-list. The platform rejects non-conforming requests with a diagnostic naming the violated field (#13, PR).
  • The platform’s limits are stated, not implied. The README exit checklist marks each acceptance criterion pass or pending with evidence links (#14, PR). The release is signed and published (2026.01-rc1).

23 October — 2026.01-rc2

  • Requests parse across HTTP/1.1, HTTP/2 and gRPC into one structured view (#15, PR).
  • The CEL graph reloads rules on apply and holds each rule under its cost budget (#17, PR).
  • Automated-client detection grows behavioural windows over the JA4 fingerprints (#19).
  • Rate limiting runs token-bucket, sliding-window and EWMA algorithms per route (#20, PR).
  • The bench gate reads per-row budget verdicts in the serialized CI fleet (#24, PR, #150).
  • Release artefacts carry build-provenance attestations and an SBOM (#81, PR). The release is signed and published (2026.01-rc2).

24 October — 2026.01-rc3

  • Behavioural DoS detectors land as shadowed shapes. The kernel counts per-flow window features; the engine classifies slowloris and rapid-reset (#31, PR).
  • The engine gains its TLS-termination secondary mode, fail-closed on a split pair (#34, PR).
  • The build ships multi-arch with OpenShift compatibility notes (#33, PR).
  • The uninstall residue gate asserts zero kernel leftovers after live teardown in CI (#35, PR).
  • The socket-plane compiler lands its first class. Route marking compiles end to end; the verifier gate runs in CI; the shadow differential pins the mismatch budget. The work spans (#52, PRs #200, #207, #212).
  • The declarative layer moves to CUE with a golden-diff gate against hand edits (#46, PR).
  • The Academy ships modules 1, 3, 4 and 2, 5 (#27, #28, PRs #178, #210).
  • The tracked evaluations publish: HTTP/3 ingress posture, the DPU port, the composition watch (#29, #32, #36).
  • The release is signed and published (2026.01-rc3).

26 October — 2026.01 (GA)

  • The QUIC kernel abuse class (PR #271), the QUIC-ingress lab (PR #273) and the inline H3 listener (PR #272) ship.
  • The X25519MLKEM768 profile (PR #270) and the JA4/PQC corpus (PR #268) complete the lane.
  • The stage stamps (PRs #245, #274), the JWT stage (PR #269) and the protocol conformance rejects (PR #267) ship.
  • The manual ban rule (PR #248) and the shield DoS runner (PR #249) ship.
  • The DoS signature (PR #250), the consult signals (PR #252) and the challenge hop (PRs #256, #258) ship.
  • The gate receipts sit on #275. The release carries 19 attested assets. The release is signed and published (2026.01).

November — the adversarial test program (post-GA)

  • The WAF CI harness builds an ephemeral kind cluster per run, with its benign and vulnerable fixture apps (PR #296).
  • The libinjection fingerprints join the shipped rulepack. The verdict record carries the classification evidence as trishula.verdict.v2 (PR #295).
  • The per-PR gate runs the CRS parity corpus, the waf-bypass battery and the goTestWAF subset at every merge (PR #299).
  • The shield hook spike loads all 4 hook classes on the hosted runner (PR #297).
  • The release-stage suite runs the full corpus, sqlmap and the open-appsec differential at each release cut (PR #300).
  • The README carries the adversarial coverage ledger. Each row cites its recorded run (PR #301).
  • The goTestWAF, sqlmap and open-appsec rows read pending until their first release-cut run (TR-205).

Roadmap

Work is tracked on the Trishula — Roadmap board (org Project) as issues TR-01 … TR-41 in the trishula repo. Every issue lands a runnable artefact with an exit criterion. The ladder reads proven end-to-end, not slide-by-slide.

Milestone Items Status
2026.01-rc1 — DELIVERED TR-01–TR-14: repo seed, CEL seed, shield PoC, ingest, ladder slice, NGF lab, CRS differential, operator/CRD, ban shadow + enforce, OTel, bots v0, positive v0, honest exit Phase 0 exit gate run (TR-14 PR): shield loaders (ed9b271) · engine proxy + NGF lab (75d8174, 8bc24a2) · ladder (b86cf6f) · CRS parity 19/19 (ec19346) · CRD round-trip 0.239 s (e221c9f) · M9 apply→effect 2618 ms (cb60e2b) · ban enforce E2E (fdd32af) · OTel triad (e63d990) · bots v0 (c4f5e7e) · positive v0 (8f4c2f2) — per-criterion verdicts + evidence links in the README exit checklist; the <10 ms inline criterion is pending TR-24, reported honestly
2026.01-rc2 (release) TR-15–TR-26: HTTP/2+gRPC, Vectorscan, CEL hot reload, OpenAPI learn, behavioural bots, rate-limit ladder, ONNX scorer, ext_process, DX gate, bench, multi-tenancy, Envoy lane delivered 2026-10-23
2026.01-rc3 (release) TR-27–TR-36: academy, HTTP/3 + PQ posture (evaluation only), behavioural DoS, DPU, multi-arch, residue gate, composition watch delivered 2026-10-24
research TR-39–TR-41: socket-plane L7 fast path study (Beeline), WAFPolicy→eBPF compiler spike, kernel-altitude TLS posture (kTLS vs no-key signals) concluded — the first socket class ships in rc3; the follow-ons carry TR-201 and TR-202
2026.01 (release) TR-194–TR-203: the TLS-termination lane — the QUIC kernel abuse class (PR #271), the QUIC-ingress lab (PR #273), the inline H3 listener (PR #272), the X25519MLKEM768 profile (PR #270), the JA4/PQC corpus (PR #268); the trunk verdict lanes: the stage stamps (PR #245, PR #274), the JWT stage (PR #269), the protocol conformance rejects (PR #267), the manual ban rule (PR #248), the shield DoS runner (PR #249), the DoS signature (PR #250), the consult signals (PR #252), the challenge hop (PR #256, PR #258). The gate receipts sit on #275. delivered 2026-10-26
post-GA — in progress TR-205: the WAF adversarial test program — the CI harness (PR #296), the libinjection record (PR #295), the shield hook spike (PR #297), the per-PR gate (PR #299), the release suite (PR #300), the README ledger (PR #301). The release-suite rows read pending until their first release-cut run. The re-encryption lane stays the named post-GA boundary. Also the 2026.03 lanes: TR-201 — kTLS Mode A, TR-202 — the DPU shape leaves merge as green

What is left

The releases carry honest caps. The remaining gaps, stated:

  • The route-class fast path reads as a tracked evaluation; more policy classes ride later slices (#52).
  • Verdicts export OTLP over the wire later; the triad verifies in-memory today (#11).
  • Engine-only cells measure in CI today; the inline walls under 10 ms ride a later slice (#24).
  • The GA cut releases as the bare 2026.01 name, per ADR-0003.

Sprint sequencing

The 2026.01-rc1 sprint sequence runs in stages: shield PoC → ingest → ladder slice → NGF steering lab. The mid sequence: CRS differential → operator/CRD round-trip → ScoredWindowBan → OTel pipeline. The last stages: bot v0 → positive security v0 → honest exit (TR-14).

Contributing

Contributions follow the contributing guide. Pick an issue labelled complexity:starter, or any area:* that fits. The issue body carries the design source. Branch + PR against trishula-dev/trishula (MIT).