A known limitation should be easier to find than a sales argument.

No real product incident exists in this showcase. This register addresses each concept’s declared limitations, scope, workaround, and evidence still required.

Filter limitations View status

Not an incident history

Each identifier describes a concept limitation or missing evidence—never an outage, an affected customer, or an invented fix.

Eight addressable limitations, linked to their path.

Filters remain in the URL. Every row has a stable permanent link and connects the concept, documentation, roadmap, and changelog traces that provide context—without claiming to resolve the limitation.

Readiness for JiraEvidence required

limit-readiness-manifest

The published manifest, retention, and scopes do not exist yet

The permissions shown describe the functional intent of the concept, not a Forge manifest or production processing.

Scope: Future architecture · permissions, storage, and data lifecycle
Last review: August 12, 2026 · no delivery date
Rationale: No versioned app is distributed and no remote production architecture has been selected.
Workaround: Evaluate the local scenario only and pause any purchase review until the matching technical evidence is published.

The format will change only when a real product exists.

A future confirmed issue will remain separate from a vulnerability and a service incident.

01Verifiable product, hosting, version, and confirmation date.
02Observable symptom, scope, and trigger conditions.
03Tested workaround, side effects, and review owner.
04Fix state without an invented delivery date.
05Exact links to support, status, changelog, and corrected documentation.

A documented limitation protects better than an optimistic FAQ.

Open the relevant identifier, verify its workaround, and follow the linked work. A future outage belongs on Status; this register remains functional.

Choose an app View status