Skip to content

What real-world action would break Dataoad's assumptions? #25

Description

@atikakernel

Dataoad needs real workflows that falsify its execution contract—not feature requests.

If you work with a side-effecting action, submit the smallest case where the caller can lose certainty after the downstream system may have committed:

Describe a real-world action

The form asks only for:

  • Downstream system
  • Side effect
  • Ambiguous failure
  • Native idempotency: yes/no
  • Authoritative read-back: yes/no
  • Outcome that is impossible to distinguish

The most useful evidence is a pair of externally different outcomes that remain observationally identical to the caller and verifier.

Activity

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