Skip to content

docs: publish DD-077 correctness primitives roadmap - #177

Open
larimonious wants to merge 4 commits into
mainfrom
docs/dd-077-correctness-primitives-publish
Open

docs: publish DD-077 correctness primitives roadmap#177
larimonious wants to merge 4 commits into
mainfrom
docs/dd-077-correctness-primitives-publish

Conversation

@larimonious

Copy link
Copy Markdown
Contributor

Summary

Publishes the approved DD-077 correctness-primitives roadmap on current main.

  • adds the reviewed eight-part durable-application correctness roadmap
  • records DD-077 supersession boundaries in the jobs roadmap
  • preserves current shipped DD-047 status while retaining its follow-on protocol-DD prerequisites
  • marks DD-077 and merged DD-078 approved in the design-doc index

Why this PR exists

The reviewed DD-077 commit existed only in a local worktree and was not present in GitHub or origin/main. This rebases that exact roadmap onto current main so DD-078 implementation slices can pin a real merged design identity and later land DD-077 prerequisite PRs such as callback bridge 0A.

Validation

  • local Markdown links: passed
  • git diff --check: passed
  • documentation only; no runtime behavior changed

@greptile-apps

greptile-apps Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR publishes the DD-077 correctness-primitives roadmap — a 1,619-line planning document that outlines eight tracks of durable-application primitives — and wires its references into the design-doc index and two existing DDs.

  • dd-077-correctness-primitives-roadmap.md (new): defines eight focused additions (scoped transactions/outbox, distributed-work primitives, opaque network capabilities, strict contracts, PostgreSQL streaming, observability, migrations, and pure fn), organised into four release waves (0–4) with PR slices, acceptance criteria, backend-parity tables, and a failure matrix.
  • design-docs/README.md: inserts DD-077 at its numeric position and promotes DD-078 from Draft to Approved.
  • design-docs/dd-047-std-netmon.md: adds a "Follow-on protocols" checklist and a Status Dashboard prerequisite item, each linking back to DD-077 via a relative Markdown hyperlink.
  • design-docs/dd-052-job-system-enterprise-features.md: inserts a supersession note directing readers away from unimplemented sections 4–5 and toward DD-077 Wave 2F–2H.

Confidence Score: 5/5

Documentation-only change; no runtime code is modified and all cross-document links are navigable.

All four changed files are Markdown documents. The new DD-077 file is well-formed with consistent internal cross-references. The back-links in dd-047 and dd-052 use correct relative paths. The README table row is inserted at the right numeric position. The previously raised concern about a missing hyperlink does not apply to the current diff — the link is present.

Files Needing Attention: No files require special attention.

Important Files Changed

Filename Overview
design-docs/dd-077-correctness-primitives-roadmap.md New 1,619-line roadmap document; well-structured with eight items, four release waves, per-PR acceptance criteria, backend-parity tables, and a failure matrix. Internal cross-references and relative Markdown links are consistent.
design-docs/README.md Adds DD-077 row at its correct numeric position and upgrades DD-078 status from Draft to Approved; both links are well-formed.
design-docs/dd-047-std-netmon.md Appends follow-on protocol checklist and Status Dashboard prerequisite; the DD-077 back-reference includes a proper relative Markdown hyperlink.
design-docs/dd-052-job-system-enterprise-features.md Inserts a two-sentence supersession blockquote for sections 4–5 with a correct relative link to DD-077; no other content changed.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    W0["Wave 0 — Foundations"]
    W1["Wave 1 — Atomic data & boundary contracts"]
    W2["Wave 2 — Scale, network authority & distributed work"]
    W3["Wave 3 — Operational context & observability"]
    W4["Wave 4 — Deterministic logic"]

    PR0A["PR 0A\nReusable callback bridge"]
    SP0B["Spike 0B\nOutbound transport binding"]
    SP0C["Spike 0C\nEffect metadata coverage"]

    PR1A["PR 1A\nScoped Postgres transactions"]
    PR1B["PR 1B\nMigration runner foundation"]
    PR1G["PR 1G\nTransactional outbox"]
    PR1F["PR 1F\nAtomic job acceptance"]

    PR2A["PR 2A\nPostgreSQL cursor batches"]
    PR2C["PR 2C\nNetwork config & capability core"]
    PR2D["PR 2D\nPolicy-bound HTTP transport"]
    PR2F["PR 2F\nJob lease & fencing"]

    PR4B["PR 4B\nEffect metadata"]
    PR4C["PR 4C\npure fn"]
    PR4A["PR 4A\nMatch exhaustiveness"]

    W0 --> PR0A & SP0B & SP0C
    W0 --> W1
    PR0A --> PR1A
    PR1A --> PR1G
    PR1F --> PR1G
    PR1B --> PR1G
    W1 --> W2
    PR0A --> PR2A
    PR1A --> PR2A
    SP0B --> PR2C
    PR2C --> PR2D
    W2 --> W3
    W3 --> W4
    SP0C --> PR4B
    PR4B --> PR4C
    PR4A --> PR4C
Loading

Reviews (2): Last reviewed commit: "docs: link DD-047 follow-on criteria" | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant