Business Workspace: all seven menu routes

01 · Confirm the local operating context

Purpose: create one approved local audit artifact and carry its identity into review. Obtain the supplied native client, intended installation/endpoint, authorized operator account and permission for this operation from the delivery contact and administrator. Agree who reviews the result. Open Business Workspace and Home; check Control Plane availability.

The captured starting view had an available Control Plane and no selected canonical Work. Availability alone does not grant submission authority. If disconnected, keep the displayed reason and ask the installation operator to resolve the target; do not fill in missing credentials or switch accounts.

02 · Choose a route through all seven menus

Business is the request and result workspace. For a new permitted local operation, follow Home → Request → Prepare → Submit → My Work → Review → Results. Inspect Approvals when a recorded approval is relevant, and Projects when you need project/thread/handoff context. These are distinct questions, not seven mandatory execution steps.

For an existing Work, obtain its full ID and intended installation from its owner and begin with Home/My Work. Do not choose New Work merely to inspect an existing result. Keep the assigned reviewer and permitted action scope available. The recorded example covers one local audit execution. Home, Review, Approvals and Projects were subsequently inspected for that same Work without another submission; conditional branches remain source-based.

03 · Home: decide whether to create or inspect

1. Choose Home in Business. Read Current Workspace State: Current position, Meaning, Available action, Blocked conditions and Next transition.
2. Compare Current Work with the full ID supplied by the requester. Read Review and Approval separately; neither a blank field nor “None” means accepted.
3. For an existing Work, continue to My Work and its review/result. For a genuinely new approved request, choose New Work and follow Request below. New Work starts a local draft and changes the selected context; it does not recover a previous execution.

Source-defined empty branch: no selected Work means local intent has not become submitted Work. Obtain the original ID/account/installation if you expected an existing record. If the Control Plane is unavailable, preserve its reason and ask the installation operator before creating anything. Finish Home orientation when you know the intended Work or the authorized new-request purpose and next menu.

Observed in the R10 navigation session: The existing Work was observed as AWAITING_HUMAN_ACCEPTANCE, with Review None and Approval None. Its current Work row remained present.

04 · Write the supported request

Open Request and type create audit artifact. This precise non-confidential intent was used in the observed exercise. Leave attachments and manually selected Packs out of this bounded local route. It creates a structured audit artifact; it does not audit an uploaded document or ask an external provider to edit code.

Read the entered text before Prepare. At this point it is local intent, not submitted Work. If the requested task is different, obtain its supported operation and input requirements instead of improvising in this exercise.

05 · Prepare and review before Submit

Choose Prepare. Look for Prepared request, the exact intent, and “Prepared locally; Packr Engine has not admitted Work.” The observed run used Prepare once. A prepared request is not admitted or executed Work.

If text is wrong, use Edit request, correct it and prepare again before submission. The original R9 submission did not exercise editing; the later R10 draft-only observation below did. Read any current-stage context and runtime preference before deciding. A preference such as AUTO is not proof of an actual runtime binding. If Submit is disabled, retain the current stage/reason and return to the prerequisite owner; do not bypass the state.

Leave the current-stage text field empty. Adding text here changes the prepared request and the active handler requires re-preparation. For a change, use Edit request, change the original request and Prepare Work again before reviewing it.

Observed draft-only edit branch

After reopening the client, Request was blank. The operator entered create audit artifact, used Prepare Work once, and saw the locally prepared request with Submit and Edit request. Choosing Edit request returned the text to an editable input. The operator cleared that draft and returned to My Work; the retained Work and Execution counts remained one. No additional Submit occurred. Preparing again after changed text was not exercised; the required re-preparation procedure above is source-based.

06 · Submit once and read the returned state

When the prepared request and authorization are correct, choose Submit once. The observed run used Submit once and recorded Execution EXITED, Validation PASSED and Closure AWAITING_HUMAN_ACCEPTANCE. No provider call was performed.

The current-stage field changed to AWAITING HUMAN ACCEPTANCE and Submit became disabled. This is the recorded state, not a frozen button to click again. Retain the returned Work identity. If the response is interrupted, inspect My Work under the same installation/account before any new request; ask support to reconcile if the identity cannot be established.

07 · After Submit: distinguish progress from a terminal result

Keep the same Work selected and read its current stage, execution, validation and closure independently. The captured local audit completed quickly: it showed EXITED/PASSED/AWAITING_HUMAN_ACCEPTANCE. It did not demonstrate a long-running progress sequence, pause/resume or cancellation.

1. If the current Work is recorded as RUNNING, treat it as execution in progress, not validated completion. Read the displayed reason and observation freshness.
2. Use the available Control Plane Refresh for a read-only projection update, then compare the original Work ID and recorded state. Do not press Submit again to refresh.
3. If refresh fails or the result is uncertain, retain the existing Work and visible error, then ask the operator for same-Work reconciliation. Do not infer failure or zero effects from a lost display.
4. When an outcome is present, continue through Review and Results. A failed or partial outcome needs its recorded effects and reason reviewed before any further action.

These conditional branches are source-based reading guidance, not additional states executed in the recorded run.

08 · Find the same Work and hand it to review

Open My Work. Compare the current Work row and Active Work with the original returned identity. In this run the row remained AWAITING_HUMAN_ACCEPTANCE. The separate recent list could still say “No recent Work”; that does not erase the current Work row.

Choose Results or Quick Access View Final Report and confirm the identity again. PASSED means recorded validation passed, not that a person accepted the result. The task is ready for the named reviewer when the same Work and report are located; pending acceptance remains explicit. If the expected row is missing, verify target/account and original ID rather than choosing a similarly named item.

09 · Review: inspect the execution record

Input: the intended Work ID and the reviewer’s question. Open Review. The active renderer lists Execution, State, Validation and Review; the execution cell includes its Work reference. Compare that reference rather than assuming every row belongs to Active Work.

1. Find the execution belonging to the intended Work. Compare its State and Validation with the result you retained.
2. Read Review as RECORDED or NOT_RECORDED. A listed execution and PASSED validation do not constitute a human review decision.
3. Continue to Results for the report, receipt and acceptance boundary, then give the reviewer the exact Work and relevant outcome.

The active table renders records; this route does not itself write a review decision. A “Nothing needs review” empty message means this view has no execution rows to show, not that the result was accepted. If the expected record is missing or differs, retain the discrepancy and ask the Work owner/operator to reconcile it. Completion is a matched review record or a named missing record and next owner.

Observed in the R10 navigation session: The same execution row was observed with State EXITED, Validation PASSED and Review NOT_RECORDED. No review decision was recorded by this inspection.

10 · Approvals: read a decision record without granting one

Open Approvals when the Work requires approval or when a reviewer asks what decision was recorded. The source-defined columns are Approval, State, Reason and Created; the approval cell includes its Work reference.

1. Match the Work reference before interpreting an approval row.
2. Read the exact state, reason and time. Missing reason/time stays “Not recorded”.
3. Compare the final report’s human-acceptance field separately. Admission approval and final acceptance are different decisions.

This displayed table is not an approve/reject form. If it says “Nothing needs approval”, do not infer that pending human acceptance was waived. Ask the responsible administrator/reviewer for the supported decision procedure and required authority. Record the remaining decision and owner; do not create credentials, grant access or repeat Submit from this menu.

Observed in the R10 navigation session: The actual empty row read Nothing needs approval, NONE, Not recorded and Not recorded, while the same Work still awaited human acceptance.

11 · Results: reach the final audit report for this Work

Open Results, or Quick Access → View Final Report. The page heading is Final Report. Match the full Work ID and report state before reading execution, validation, evidence, receipt and human acceptance. A closure record may exist while its disposition remains AWAITING_HUMAN_ACCEPTANCE.

Follow the dedicated final report procedure to open the exact revision’s PDF/JSON through Control Plane, compare file identity and hand the result to the reviewer. In the R9/R10 predecessor, the global Audit Report button opened a separate registry browser. The linked guide distinguishes that observation from the R11 canonical Work report route, with observed local native discovery and PDF display. Neither an empty registry browser nor an unavailable Work Asset field proves the Work PDF is missing.

If there is no report context, return to My Work and verify the selected Work. If the report is missing/stale, retain that state and request reconciliation instead of resubmission. Finish when the intended report is identified, its actual outcome is explained and any pending acceptance has an owner.

12 · Projects: inspect linked context and its current limit

Open Projects when you need to establish how the selected Work relates to a project, discussion or handoff. Keep the same Work ID. The current source defines three cards: Current Project, Threads and Handoffs, marked NOT_AVAILABLE_IN_CURRENT_TYPED_PROJECTION.

1. Read each card separately; a project link, thread and handoff are different relationships.
2. The source-defined empty presentation says no project, threads or handoffs are linked to the current Work. Do not substitute a similarly named project or infer a relationship from the Work title.
3. If your review requires one of these relationships, ask the project/Work owner for its exact identity and supported handoff outside this unavailable projection.

This candidate route does not demonstrate project creation, linking, thread creation or handoff execution. It provides no basis for inventing those controls. Finish by recording the displayed context or the exact missing relationship and its owner, then return to My Work/Results.

Observed in the R10 navigation session: The three actual cards showed no project, threads or handoffs linked to the current Work. No linking action was performed.

13 · Continue with the same Work

Continue to the final report walkthrough for outcome, receipt, human acceptance and PDF/JSON opening. Return to the PackrGUI overview to choose another surface. Retain the original Work identity through every transition; do not submit a replacement to repair a missing view.