Limitations

Conservative by design

This MVP is intentionally limited. Clear limits increase trust and reduce the risk of misleading claims.

Complex workflows are why we’re here. We work in bounded stages so the workflow becomes understandable before anyone jumps to a fix.

What we do not promise

  • We do not guarantee bug fixes.
  • We do not certify production readiness.
  • We do not replace code review, testing, or security review.
  • We do not accept secrets, credentials, or private customer data.
  • We do not provide emergency incident response.

What reports depend on

  • The quality of the submitted workflow description.
  • The accuracy of submitted evidence.
  • Whether examples are redacted but still meaningful.
  • Whether the problem is bounded enough to analyze.
  • Whether follow-up evidence is available.

When the answer may be “not enough evidence”

Some problems cannot be responsibly analyzed from a brief description alone. In those cases, the report should say what evidence is missing instead of pretending to know the answer.

Security and privacy

The public MVP is not designed for secrets or regulated data. Users should redact sensitive information before submitting any problem brief.