HDbeammachineBeam Machine Docs
Help Center

Beam Machine Functionality Gap Map

Cross-check of Beam Machine help coverage against the live UI, end-user feedback intake documents, the functionality checklist, and Auto_todo packs.

publicusers

Checking What Is Really Live in Beam Machine

This page shows which parts of Beam Machine are clearly live, which parts are partial, and which requirements still belong to the backlog rather than the user manual.

Product: Beam Machine
Module: Delivery Status Reference
Role: All users, Product, QA, Support, Delivery
Difficulty: Intermediate
Time: 8 minutes
Last Updated: 2026-03-10
Version: Current Beam Machine app build in this repo

Before You Start

  • This is a truth page, not a marketing page.
  • Use 98-screen-map.md if you first need to confirm the route exists.

What is the gap map?

This is the safety page that stops the docs from lying. It compares the live route surface, the intake documents, the functionality checklist, and the backlog-style Auto_todo files.

When do you use this?

Use this page when:

  • a user asks "why can't I do this yet?",
  • someone wants to promise a feature to a client,
  • a writer wants to turn a PRD note into a manual page,
  • or support needs to separate "bug" from "not delivered yet."

Where does this status come from?

Primary sources: live routes, VEVA_Functionality_Checklist.xlsx, beammachine_functional_register.csv, intake docs, and Auto_todo_P3.md, Auto_todo_P4.md, Auto_todo_P5.md.

How to read the status

Status Meaning
Live in UI A route or screen exists in the current build
Partial A workflow exists but the checklist or code context shows it is not fully productized
Missing The requirement exists in backlog or checklist material but is not truly delivered in the current build
Constraint A cross-cutting rule exists, but full enforcement or proof is still constrained

Current checklist snapshot

  • Missing: 85
  • Partial: 8
  • Constraint: 6

Major gap families that affect documentation

Code family Current state Documentation rule
AUTO Missing Do not write SOPs as if the workflow automation engine already exists
CAP Missing Do not promise workload or capacity planning screens
DOC Missing Do not overstate template or signature governance maturity
INTEL Partial Explain current dashboards, but do not present AI guidance as fully governed
MIG Missing Do not claim full competitor migration suites
PORTAL Partial Document the portal as real but limited

Canonical deep manuals now available

Use these shelves before writing new duplicate pages or sending users back to broad overview docs:

Common Questions & Issues

"The screen exists, so why are the docs still cautious?"

Why this happens: A visible route is not the same thing as a finished, reliable, fully governed workflow.

Fix: Treat the route as real, but treat deeper business promises according to this page until the product proves otherwise.

"Can I move the intake docs to done now?"

Why this happens: People confuse framework conversion with complete source exhaustion.

Fix: No. The intake docs stay in docs/EndUserFeedback until their deeper page-by-page content is fully converted and cross-checked.

What's Next

Related Pages

Still Stuck?

  • Check the relevant route in 98-screen-map.md.
  • Contact support: support@veva.co.za

Was this page helpful?

[Yes] [No]