Changelog

What shipped, and when

Decim is pre-release. This is the record of what exists, not what is planned: an item appears here only once it ships.

  1. 2026-10 v0.4

    Logs, tickets and reports

    • Jira Cloud: read-only OAuth; search and link an issue when opening an incident. Its description, comments and attachments are imported as an immutable snapshot and used as evidence
    • Google Cloud Logging: Google sign-in with the read-only logging.read scope; named log sources defined as Cloud Logging filters, which investigations read entries from
    • PDF board report in one click: executive summary, investigation timeline, root cause with confidence, evidence, verification, remediation and appendix. An in-progress incident exports as a clearly marked interim report
    • Solutions: an SQL repair (diagnostic SELECT, one bounded UPDATE, regression SELECT — never run by Decim), a repository patch checked to apply cleanly, both, “no fix required”, or “blocked” with the inputs still needed. One click opens a draft pull request on GitHub; nothing is merged automatically
    • Single sign-on with Microsoft Entra ID, Google and GitHub, alongside password sign-in and invitations
    • Audit log of every user action — actor, action, target, outcome — exportable to CSV and JSON
    • Pipeline discovery: pipelines identified by their trigger (schedule, cron or Hangfire job, queue consumer, file arrival, CDC, batch command); step graphs with the code lines behind each step, including stored procedures kept in the repository; connections marked direct or inferred; points of interest flagged; pipeline identity kept stable across rescans
  2. 2026-08-07 v0.3

    Remediations

    • Solutions tied to incident evidence
    • GitHub draft pull-request publishing where the solution supports it
    • Human approval remains required; automatic merge and review-driven revisions are not shipped
    • Replay, database changes and broader delivery mechanisms remain planned or human-run
  3. 2026-08-06 v0.2

    Pipeline topology

    • Pipeline context surfaced in the admin, discovered from code in GitHub
    • GitHub and Windows agent evidence available in the current workflow
    • Database catalogs, schedulers and broader runtime discovery marked as roadmap work
    • A declared-versus-observed provenance model remains a design direction, not shipped
  4. 2026-08-05 v0.1

    Investigations

    • Incident workflow connected to GitHub and the Windows agent
    • Evidence-backed investigation views with sourced claims
    • Pipeline discovery and evidence inspection in the current admin
    • SQL collection, redaction and policy controls remain planned