Ask a Reproducible Question

Ask a Reproducible Question

A good technical question should let another developer understand the boundary of the problem without guessing.

Include

• DigiEmu technology or component;
• version, revision, or release where known;
• environment;
• exact command or integration path;
• minimal input or artifact description;
• expected behavior;
• observed behavior;
• structured result or error output;
• relevant evidence or hashes;
• whether the issue is reproducible.

Minimal template

Technology:
Version / revision:
Environment:
Goal:
Input:
Steps:
Expected:
Observed:
Verification result:
Evidence:
Reproducible: yes / no / unknown

Protect sensitive material

Do not publish credentials, private keys, personal data, customer documents, confidential source material, or other restricted information.

Reduce the problem to a minimal safe example whenever possible.

Verification questions

If the issue concerns a verification result, include the exact state rather than saying only that “it did not work”.

See Verification Status.