PackrGUI operations guide

01 · Choose the right surface

PackrGUI is the desktop view for Work requests, runtime monitoring, review and evidence. The governed engine determines permission, execution and closure. This guide describes the inspected desktop implementation; it does not establish that this GUI build is included in the frozen r232 appliance delivery.

The Packtory Administration dialog and the appliance Administrative Console have different contexts. See the Packtory guide and appliance Admin guide for their prerequisites.

Follow the official built-in Pack walkthrough to inspect Audit Review and Audit Evidence Format in the same Work.

02 · Workspaces and every menu: choose your route

Choose a workspace, then follow the menu for your task. Each route explains its purpose, what to bring, the controls to use, how to read the result and where to go next. The Business example follows one real audit Work from request to final report. Engineering and Operations also document every menu in the inspected R234 client, including the actual empty and unavailable states.

Final audit report: find the same Work, read the result, open PDF/JSON and prepare the review handoff.

These are real local candidate screens, not a demonstration that every product operation succeeded. The retained audit Work did not edit source, run a repository build, call an AI provider or receive human acceptance. No new Work was submitted during the additional menu capture. The matching customer release, populated engineering workflows and acceptance remain separate validation tasks.

03 · Install and verify the supplied client

1. Obtain the client package and matching delivery instructions for your operating system and appliance. Record the supplied version and intended organization before installation.
2. Follow that package’s installation instructions. A source checkout, browser copy of the interface or development build is not an installed customer client.
3. Launch the supplied native client. Check that its workspace and appliance identity match the delivery record before submitting Work.
4. Use only the connection profile and trust material assigned to that installation. The inspected distribution profile is a targeted-validation candidate; its example endpoint is not a production connection recipe.

No verified general customer GUI installer or r232 GUI delivery binding is established by this guide, so it supplies no invented download URL or build command. For a new r232 customer appliance, initial Customer Admin setup remains blocked at C7. A local GUI administrator or a working desktop window does not resolve that prerequisite.

Before a first exercise, ask the delivery owner for four items: the native client package/version for your OS, the intended organization and installation identity, the supported local connection/launch instructions, and the permitted exercise scope. Compare the installed version and displayed identity with that handoff. If an item is missing, name that item in your support request; a generic instruction to “connect the GUI” is insufficient.

First-exercise handoff checklist

Request these items through your existing organizational delivery/support process. The table names responsibilities; it does not establish a new delivery channel or a working installer.

04 · Plan one Work and its review route

Use this route for a local audit-artifact task. The requester supplies a non-confidential intent; the installation operator supplies the native client, local endpoint instructions and permitted operation; the reviewer supplies the acceptance criteria. Agree who retains the returned Work identifier before starting. For example, the reviewer may require a report for the intended local audit operation with its validation and receipt observations, while leaving business acceptance for a named person.

1. Check the actual connection, then locate the request and review views. A disconnected screen still lets you learn navigation, but it cannot supply the task result.
2. Follow prepare → edit → prepare → authorized Submit. The supported local route creates a lineage artifact; it does not analyze an attached file or run a selected AI model.
3. Follow same-Work result review. Keep the returned identity through every view change. A draft has no submitted Work identifier; record that distinction rather than assigning one yourself.
4. Finish with the reviewed result and assigned human decision, or a precise unresolved stage and responsible operator. If connection or outcome is uncertain, continue read-only reconciliation through the Headless guide instead of creating another request.

For asset discovery use the separate Packtory user guide. For cross-surface task planning use usage workflows. Pack selection, runtime preference, workspace selection and permission are separate inputs; none substitutes for the others.

05 · Read connection state before acting

Where the runtime detail card is exposed, expand Connection Details. Read Endpoint, Deployment, Client Distribution, Health, Identity and Organization together. Then inspect Trust Mode, TLS Trust, Certificate and Ready Gate. This is a diagnostic projection; it is not a server-entry form.

Not loaded, Not resolved and Needs validation mean the corresponding check has not supplied usable state. They do not mean that the server has no data. Follow the displayed Admin Action or User Action only within your assigned scope. If the identity is wrong, stop before submitting Work and have the assigned connection profile corrected through the installation’s supported process.

The separate Administrative Console opens from the native Packr menu, with CmdOrCtrl+Shift+A. Its authenticated connection is documented in the Admin guide. Opening that console does not automatically validate every workspace connection or runtime.

The active local Work route uses the installation’s local control-plane endpoint. The inspected desktop can read a default local socket or an explicitly selected launch endpoint; this guide does not supply a customer launch command or substitute a remote URL. The older distribution-profile detail card and the remote Administrative Console are separate connection surfaces. Check the installation’s declared mode before interpreting them.

06 · Navigate and keep the Work context

Use the workspace selector to choose Business Workspace, Engineering Workspace or Operations Workspace. Business navigation contains Home, Request, My Work, Review, Approvals, Final Report and Projects. Choose the view that matches the next human task; changing views does not approve or execute Work.

The engineering toolbar provides IDE, Runtime, Audit, Reports, Memory and Packs, followed by Operations. At each transition, inspect the context strip’s Workspace, Surface and Active Work. A report from another Work is not evidence for the current request.

Back to previous surface context and Workspace return through navigation context. Settings opens configuration and Help opens help. Controls may be hidden or disabled for the current view or available authority; do not use a disabled label as evidence that the underlying operation occurred.

Workflow: follow an existing Work across workspaces

Goal: inspect one existing result without losing its identity. Obtain its actual Work identifier from the requester or original response and the question the reviewer needs answered. The following is a navigation procedure, not an additional execution.

1. In Business Workspace open My Work and select the intended item. Compare Active Work in the context strip with the supplied identifier. If it is missing, have the operator check installation/principal scope; another similarly named Work is not a substitute.
2. For request/result review use the Business views. The captured build labels the upper result tab Results and also offers View Final Report in Quick Access; the reference sections below call the result surface Final Report. Use the visible label in your supplied build and verify Active Work again.
3. For implementation/runtime context, choose Engineering Workspace and the relevant Runtime, Audit or Reports control. These are inspection destinations. For operational observations choose Operations Workspace. Changing workspace does not admit Work, execute a command or approve a result.
4. If a control is outside the visible viewport, scroll the application normally to locate the labelled area. First identify the workspace; a Business navigation label need not exist in Engineering. Use Back to previous surface context or Workspace to return, then check Workspace, Surface and Active Work together. Do not use website documentation navigation as an application control.
5. Record the observed result for that Work and return to its Business review/result view. If a view offers no current projection, preserve “not observed” for that question and use the supported Headless read path or assigned operator.

Completion: the requester’s identifier and the result you reviewed match, and each unresolved observation has a next owner. Merely reaching Audit, Approvals or Results is not evidence that an audit, approval or result exists.

07 · Prepare a bounded Work request

The active composer supports the bounded local audit-artifact operation. Use the observed exact input create audit artifact, no attachments and no selected Pack. Keep current-stage text empty after Prepare. Review the prepared intent, then use Submit once only within the permitted exercise scope. Full steps, real screens, returned Work and uncertain-response handling are in the Business walkthrough. For a preparation-only exercise, stop before Submit. Broader wording, document generation and AI execution are not validated by this example.

08 · Distinguish requested runtime from actual binding

The Runtime control presents Mode values AUTO, PREFER and PIN, plus a Candidate selector. These record a requested runtime preference. They do not grant a provider permission, create credentials or guarantee that a chosen model will run.

Read the Runtime Binding summary after the engine responds: Requested, Actual, Fallback and Revision. Not bound means actual binding has not been established. A chosen Candidate with no Actual binding is still a request. If a specific runtime is mandatory, verify Actual against it before treating the Work as using that runtime.

Workspace selection, runtime preference and access mode are different controls. Switching to Operations changes the view; choosing PIN changes the preference; neither changes authority. Use the Headless guide to inspect canonical Work status when the GUI projection cannot answer the question.

The active local audit-artifact composer prepares its fixed local operation without passing these runtime preferences to a provider execution route. Changing AUTO/PREFER/PIN therefore does not change that local operation into an AI generation task. Runtime selection controls may still describe other governed Work projections.

In the recorded local run, the separate Engineering Runtime page returned NO_RUNTIME_BINDING and PORTABLE_BINDING_STORE_INVALID. The final Work report still records the completed local deterministic execution. See the field-by-field explanation; provider readiness is not established.

09 · Find and select a Pack for a new draft

1. Open Packtory in the toolbar and select Refresh.
2. Search with Pack name or identity; narrow Workspace, Domain and Availability filters.
3. Select a row. Inspect identity/revision, Provenance, Dependencies and Revision history before choosing it.
4. For an eligible local item, choose Use in new Work. This records a PIN preference in the existing Work Draft. Review Selected Pack in the draft; Remove clears that selection.

The inspected interface enables use only for an AVAILABLE non-remote-catalog item and when there is no active Work. No Packs match the current filters. means widen the filters. Pack projection is unavailable. means repair the observation path first. Neither message proves the organization has no Packs.

A download row is a separate path. Download requests local availability for selected governed assets. DOWNLOADED and ALREADY_LOCAL do not bind Work or authorize execution; a PARTIAL batch requires inspection of denied items. This guide does not establish a production remote catalog connection.

Current local composer limit: selecting a Pack is a draft preference only. The active local audit-artifact preparation route rejects a selected Pack. To use that local operation, Remove the selection first; this guide does not promise a completed Pack-consumption workflow from the draft button.

10 · Read progress, review and final reports

Use the dedicated final audit report guide for Results, exact Work/revision matching, PDF/JSON opening, field interpretation and file verification. The actual run has execution EXITED, validation PASSED and human acceptance pending. The R9/R10 predecessor’s global Audit Report Browser was unavailable. R11 implements a canonical Work/revision selection route; its local native discovery and PDF display were observed in the linked guide.

11 · Resolve common desktop symptoms

Walkthrough: an empty Pack list and a disabled control

Goal: determine whether the next step is a filter correction, a connection handoff or a supported selection. Have the expected installation and the desired Pack identity/revision from the asset owner. This is a read-only diagnosis until you deliberately select an eligible Pack.

1. Confirm the workspace and Active Work in the context strip. If the target is wrong or unresolved, stop here. Ask the delivery owner to correct the assigned local connection instructions/profile, then verify the identity again.
2. Open Packtory and Refresh. For “No Packs match the current filters.” clear the search text and widen Workspace, Domain and Availability filters. If a row appears, match its identity/revision to the owner's supplied record. If none appears, ask the asset owner whether that exact revision should be visible in this scope.
3. For “Pack projection is unavailable.” retain that message and have the appliance operator check the installed connection and Headless status/health. Filter changes cannot establish a missing projection. Recheck the browser after a current projection is available.
4. If Use in new Work is disabled, inspect the selected row's Availability, whether it is a remote catalog item, and whether a Work is already active. An AVAILABLE local item with no active Work is eligible for this draft control. Finish reviewing the existing Work before intentionally opening a new draft; do not discard its identity just to enable a button.
5. If Prepare Work is disabled in Request, check for nonblank text in the initial Work Request. If Submit is disabled, confirm successful preparation, current context and the displayed reason. Preparation must be repeated after editing; runtime/admin permission problems go to the assigned administrator.

Completion check: record either the exact visible Pack revision and resulting draft selection, a valid empty scope confirmed with its owner, or the exact missing projection/connection item and next responsible person. Pack selection remains a draft preference; the local audit exercise above requires removing it.

12 · Capture a useful support handoff

Record client version, operating system, selected workspace, surface, action, exact status/reason, observation time and a permitted Work or asset reference. Describe expected versus observed behavior and whether the issue is reproducible by refreshing the same read-only view. Remove credentials, private file paths, raw request text and unrelated organizational data from shared screenshots or reports.

For connection faults use the Admin guide; for canonical Work inspection use the Headless guide; for asset authority use the Packtory Admin guide. The troubleshooting guide connects these paths. A refresh can establish a new observation; it does not repair permissions, create a receipt or finish pending Work.