Skip to content

Latest commit

 

History

History
33 lines (23 loc) · 3.21 KB

STATUS.md

File metadata and controls

33 lines (23 loc) · 3.21 KB

Implementation status

Current milestone

The approved source and evidence update is public at e3b02af. PostgreSQL 17 CI passed all 38 tests, including the timestamp-precision regression. Report exports and benchmark evidence are published with their original provenance.

Completed and verified

  • Published ezesecops/security-program-analytics with reviewed source commit e3b02afdd272e96ca8e9c36f129a64d5dd870f09.
  • CI run 41810508124 succeeded with PostgreSQL 17.11 and Python 3.12.15. JUnit records 38 tests, zero failures, zero errors, and zero skips in 6.461 seconds. The verification record preserves the source commit and artifact checksum.
  • The original CI run 41809088427 at 8bd60f6 passed 37 tests and produced the retained report exports and benchmark measurements.
  • A clean GitHub checkout installed the locked dependencies/package, initialized separate demo/test databases, loaded and validated the fixture, executed the tests, exported all six reports through the CLI, loaded portfolio data, and ran the index experiment.
  • Fixture results match the independent contract: backlog 4; accepted risks 1; exception findings F4/F6; weekly totals 4/3/5 (tested); remediation episodes 3, p50 4.0 days, p90 7.2 days; zero flow residual; portfolio rollout completion 50%.
  • Demo and portfolio generated data passed PostgreSQL integrity/report invariants. The portfolio load contains 12 teams, 2,000 assets, 25,000 findings, 77,119 finding events, 6 rollouts, 2,500 tasks, and 5,027 task events.
  • Before/after diagnostic-query medians were 55.5995 ms and 0.058 ms, with identical results. Raw plans, every timing, and limitations are in PERFORMANCE.md.
  • Downloaded report artifacts were checked against all 14 manifest file hashes before being copied into this checkout. The follow-up CI run reproduced every export hash; all seven report SQL hashes also match the published source.
  • Fractional seconds are preserved in CSV/JSON timestamps and manifests. The regression passed in PostgreSQL CI, and whole-second fixture hashes remain unchanged.

Blocked or remaining

  • The local workspace lacks Docker and blocks PostgreSQL shared-memory/socket use. The full Compose-based README rehearsal has not run on this Mac; clean-checkout database verification succeeded in GitHub Actions using its PostgreSQL service.
  • SQL explanation and live-change exercises in DEMO.md remain a personal practice checkpoint; software tests do not establish learning completion.

Decisions and deviations

  • All data is fictional; calculations remain in SQL.
  • Measurements use a shared GitHub runner and are labeled accordingly. No production performance or risk-reduction claim is made.
  • Raw CI artifacts retain original hashes and provenance. The first benchmark result and follow-up test verification are recorded separately.

Next actions

  1. Rehearse the full Compose quickstart on a machine with Docker.
  2. Complete the five-minute demo and live SQL exercises.