Status Legend
Purpose
Use this legend to label every LinkUp feature the same way. The label should describe the current truth, not the future plan.
Status labels
| Status | Meaning | When to use it |
|---|---|---|
| Implemented | The feature exists and matches the intended workflow. | Use after the feature has been checked in the app, admin panel, API, or mobile app. |
| Partial | Some pieces exist, but the full workflow is not complete. | Use when web, mobile, admin, or backend support is uneven. |
| Legacy Only | The feature exists only in the old system or old screen. | Use when the feature has not moved into the current LinkUp surface. |
| Missing | The feature does not exist yet. | Use when no route, screen, admin tool, or mobile flow can be found. |
| Planned | The feature is intended but not live. | Use for roadmap items, proposed workflows, or future policy. |
| Needs Verification | The docs or code suggest the feature exists, but it has not been tested. | Use when a human needs to check the real screen before publishing. |
Rule of thumb
If we are not sure, use Needs Verification. Do not turn uncertainty into a confident help article.
Implementation check table
| Expected behavior | Status | Surface | Manual check |
|---|---|---|---|
| Every KB article uses one of the approved status labels. | Implemented | BookStack | Review each page before publishing. |
| Unverified workflows stay marked until tested. | Implemented | Authoring process | Search BookStack for Needs Verification and [VERIFY:. |
Gaps / notes
This page is an authoring control. It does not prove whether a product feature works.
No comments to display
No comments to display