Skip to content

Review documentation gaps for product defects and missing capabilities #213

Closed

Description

@rmcdaniel

Documentation reports can expose missing capabilities or runtime defects. Resolving the prose alone can leave the underlying user need unexamined.

Add a shared contributor rule: assess the user need and product contract before choosing documentation, a bug fix or a feature; record the decision and link implementation work. Current limitations should be documented honestly while implementation is pending. A workaround does not complete an accepted product requirement.

Acceptance: the organization guide states this review responsibility without requiring every limitation to become a feature or adding a separate tracking system.

Activity

  1. rmcdaniel commented on Oct 20, 2026

    @rmcdaniel
    MemberAuthor

    Applied the product-review rule to the documentation backlog

    Reviewed all 24 then-open documentation-labelled issues across the Website/PHP/Python SDK repositories, plus the five recently closed guidance issues durable-workflow/durable-workflow.github.io#258, durable-workflow/durable-workflow.github.io#264, durable-workflow/durable-workflow.github.io#266, durable-workflow/durable-workflow.github.io#281, durable-workflow/durable-workflow.github.io#284. The separate closed website dependency-security issue durable-workflow/durable-workflow.github.io#261 was also checked; it already had a real dependency fix and qualified publication.

    Docs wrappers superseded by actual product work

    Former Website ticket Product owner and remaining requirement
    durable-workflow/durable-workflow.github.io#302 workflow clock Shared #215: advancing replay-safe clocks and compatible existing-run migration.
    durable-workflow/durable-workflow.github.io#306 payload privacy Shared #217: opt-in client-side encryption hooks, fixed Avro wire format, key rotation and replay/inline/external qualification.
    durable-workflow/durable-workflow.github.io#272 checkpoints Shared #218: acknowledged checkpoint retrieval on replacement attempts; reuse #211's execution identity.
    durable-workflow/durable-workflow.github.io#273 recoverable bulk operations CLI #59: selected-run cancellation defect; CLI #60: durable inspectable resume manifests.
    durable-workflow/durable-workflow.github.io#269 payload/export lifetimes Server #520: self-contained cold-verified history archives.
    durable-workflow/durable-workflow.github.io#285 update recovery Shared #212: pending/read-later outcomes plus embedded and continue-as-new inspection.
    durable-workflow/durable-workflow.github.io#287 timeout compensation Workflow #863: opt-in durable cleanup under an immutable total cap.

    These seven wrappers are closed as superseded, not as implemented product fixes. Their useful current-behavior corrections and final documentation are retained in the implementation acceptance. Prepared durable-workflow/durable-workflow.github.io#307 and durable-workflow/sdk-python#169 explicitly remain interim truth, not delivery of #215.

    Further product corrections and features

    This creates eight correctly owned new product tickets, expands two existing SDK tickets, and reuses the existing clock/update/timeout/identity defects instead of duplicating them. Every new ticket states evidence limits and concrete implementation/qualification acceptance.

    Genuine documentation retained

    durable-workflow/durable-workflow.github.io#169, durable-workflow/durable-workflow.github.io#256, durable-workflow/durable-workflow.github.io#257, durable-workflow/durable-workflow.github.io#259, durable-workflow/durable-workflow.github.io#262, durable-workflow/durable-workflow.github.io#267, durable-workflow/durable-workflow.github.io#270, durable-workflow/durable-workflow.github.io#274, durable-workflow/durable-workflow.github.io#276, durable-workflow/durable-workflow.github.io#278, durable-workflow/durable-workflow.github.io#280, durable-workflow/durable-workflow.github.io#283, durable-workflow/durable-workflow.github.io#301, durable-workflow/durable-workflow.github.io#308 remain documentation or executable-example work on existing capabilities, with a recorded reason in each issue. Related actual defects remain linked, including durable-workflow/server#504 and durable-workflow/server#514 and durable-workflow/workflow#856 and durable-workflow/workflow#859. Removed the stale claim that delivered SQS chunking durable-workflow/workflow#851 is still open. durable-workflow/durable-workflow.github.io#277 is closed as actually delivered through durable-workflow/durable-workflow.github.io#291 and verified public publication; no unsupported sticky-owner hold was invented.

    Retry-default decision: keep one attempt for current 2.x applications. Automatically repeating external effects is a compatibility change; finite retries do not establish idempotency. durable-workflow/durable-workflow.github.io#301, durable-workflow/durable-workflow.github.io#304 must accurately show explicit bounded retry/backoff and total budgets. No automatic retry-default change was accepted for this train.

    The shared contributor rule is delivered through #214 at 3e950f03fb64a78667702c5fe909ec0a5d5eee9c. This audit closes triage, not the newly accepted implementations. Product tickets remain open until their real acceptance is delivered.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions