Packtory Administration guide

01 · Three meanings of Packtory

Current walkthrough status: normal macOS session renewal succeeded. A fresh Assets query returned AUTHORIZED with no visible User Pack assets. All eight administration tabs were inspected. An existing historical test evidence set produced a one-row Raw metrics preview and the same previously recorded export appeared in history. No new export or verification was performed. The dialog was closed and the existing Work remained selected.

Packtory in the desktop toolbar is the user asset browser. Packtory Administration is the enterprise asset and contribution dialog inside that client. Packtory storage and recovery are underlying appliance capabilities; the desktop dialog is not a cloud provisioning console.

This guide describes the inspected desktop source surface, with existing appliance capability and current production connection limits stated separately. It does not bind this GUI build to frozen r232 delivery. The separate VibePackr Administrative Console handles appliance state and configuration. A disabled future Rescue-to-Packtory adapter is a different integration and does not mean all Packtory capability is absent.

Use this guide to inspect asset identity, lifecycle and provenance, interpret administration status, and prepare a contribution preview/export in an already authorized installation. Customer initial Admin setup on fresh r232 remains blocked at C7; desktop sandbox initialization is not its recovery procedure.

02 · Start an Administration session: current walkthrough

Goal: enter the existing local administration area and identify the scope of the records you can inspect. You need an existing administrator assignment and access to your normal macOS authentication method. Keep your existing Work open; this task does not require another Work.

1. Choose Packtory in the top toolbar.
2. Choose Packtory Administration at the top right. On an initialized installation, this establishes or reuses a valid native administrator session.
3. If macOS asks you to authenticate, complete that system dialog yourself. Never paste a password into a Work, support message, or this guide. Cancel if you did not intend to enter administration.
4. After authentication, check whether the Administration dialog actually opens. A canceled prompt or an access denial is not a successful session. An existing assignment is still required after macOS verifies your identity.

Observed sequence: the restored Overview first displayed AUTHORIZED, but the first fresh Assets query returned DENIED / ADMIN_AUTHORIZATION_CONTEXT_EXPIRED. Normal macOS session renewal then succeeded and a fresh Assets query returned AUTHORIZED. This is why the new query result matters more than a retained header. The separately labelled historical Overview below remains earlier evidence.

Once the session opens, use Overview for scoped counts and Contribution for evidence-backed reporting. Record the displayed result before continuing. The current native session lasts up to 15 minutes in this app process and rechecks the existing grant for each request; reauthenticate through the normal entry when required.

Return to the existing Work

After inspecting all eight tabs, Administration was closed and the existing Work was still selected. The completed sequence covers renewed access, read-only tab inspection, historical contribution preview and history lookup. It does not claim completion of every administration operation.

03 · Renew an expired session, then check a fresh query

The actual Assets query returned DENIED with ADMIN_AUTHORIZATION_CONTEXT_EXPIRED. This identifies an expired authorization context; it does not establish missing assets or an unavailable Work service.

1. Close Packtory Administration using its close control.
2. Choose Packtory in the main toolbar, then Packtory Administration.
3. Complete the normal macOS authentication directly in its system dialog using your authorized account. If you cancel or it is denied, retain that result and leave the management task pending.
4. Once Administration opens, select Assets again to make a fresh query. Read its new status and reason before interpreting the inventory. A restored AUTHORIZED header alone is insufficient.
5. If the fresh query is authorized, continue the permitted inspection. If it still reports expiry or another denial, retain the exact reason and ask the installation administrator to check the session and existing assignment. Do not initialize another administrator to renew a session.

Observed renewal result: normal macOS authentication completed, and the new Assets query returned AUTHORIZED with no visible User Pack assets. The expired-session result above is the earlier step, not the final state. The query succeeded; no custom User Pack was present in this observed list. Official built-ins remain a separate library inventory.

04 · Earlier capture: unbound Administration Overview

This earlier retained single capture shows the actual Packtory Administration Overview in the local R234 candidate (bundle 0.99.0). It supplements the earlier library image; it is not a connected operation sequence. The previous library session did not establish this transition. Use the Packtory user guide for search, download and draft selection.

1. Identify Overview in the left navigation and the domain/status at the upper right.
2. Read domain:not-bound and Storage readiness: Binding required before interpreting the four counters.
3. Read Resource, Service, Domain binding and Backup as Unknown, and the Recent administration message requiring runtime binding. These fields leave connection and inventory unresolved.

The displayed AUTHORIZED status does not establish a connected domain, a populated authoritative inventory or successful administrator execution. This historical image alone did not establish an Assets or Contribution sequence. The current walkthrough now records a renewed Assets query, historical test preview and existing export history; production domain connection and customer delivery remain unproven.

05 · Open the administration dialog

1. Launch the supplied native client and confirm the intended workspace and installation. See the PackrGUI guide for installation and connection limits.
2. Choose the toolbar’s Packtory button.
3. If the installed authority is initialized, select Packtory Administration. The native adapter establishes an authorization context and checks effective authority before opening the normal administration view.
4. If you see Initialize Packtory Administration, the local authority is not initialized. Opening it leads to Binding Context. Read the local-sandbox scope before any initialization.
5. If neither entry is available, record the status and check the native runtime/installed identity. Do not infer an admin grant from your operating-system account or from the ability to browse assets.

A successful authorization context allows the permitted projection; it does not enable unavailable lifecycle commands. Close the dialog with Close Packtory Administration or Escape. Reopening may require a fresh native authorization check.

Before you open it

Confirm with the installation administrator that this Mac has the intended local administration identity. A connected Work service and a visible built-in Pack catalog do not by themselves establish that identity. Opening an initialized Administration entry may show the macOS authorization dialog. Complete only the normal system prompt for your own authorized account; never place a password in the enterprise, domain, identity or evidence fields. If you cancel, return to the library and retain the displayed reason. Opening an uninitialized entry only displays Binding Context; the separate Initialize administrator button performs setup.

Finish this access check by reading the resulting administration status, then close and confirm your original Work is still selected. A prompt appearing is an intermediate step, not a completed authorization check.

06 · Choose and prepare the administration task

The asset reviewer and contribution administrator have different deliverables. Choose one before opening tabs:

These inputs are supplied by your organization, not generated by typing sample values. If an input is missing, the remainder of the task is preparation: list the exact item and responsible person, then resume at that step when it is supplied. For appliance lifecycle work use VibePackr Admin; for choosing a Pack as a user use Packtory library.

Prepare a contribution handoff you can actually use

Ask the evidence owner for the report’s purpose, the exact scope type and identity, integer start/end values with their time unit, and the permitted evidence references. Ask the administration owner whether your current identity may preview and whether it may read export history; those permissions are not interchangeable. Ask the delivery owner how the exact CSV and receipt can be retrieved if export is part of your assigned task. Keep these answers together so you can restore the form after reopening the dialog. Sample values in this guide are reading exercises, not records you can query.

07 · Use Overview as a scoped inventory summary

Open Overview. Read Registered, Indexed, Superseded and Revoked. In the inspected implementation these counts derive from the User Packs supplied by the current control-plane projection. They are not a count of every object in a cloud bucket. A zero with an unavailable projection does not prove an empty enterprise inventory.

Refresh Packtory status refreshes the active management query. Its returned AUTHORIZED status describes the authority/context check; it is not evidence that every metrics or storage field has been freshly populated. The User Pack inventory updates when a control-plane projection arrives.

The Storage readiness band separates Resource, Service, Domain binding and Backup. The inspected dialog contains initial Unknown and Binding required values; its management handler does not fill these with production storage telemetry. Keep them unresolved. Do not turn a visible band or an authorized header into a storage health claim.

Read the result in three parts

• Access: AUTHORIZED answers whether this management context was permitted.
• Assets: Registered, Indexed, Superseded and Revoked describe projected User Pack records. The two official built-ins in the library are a separate inventory; they need not appear in these counters.
• Service information: Unknown storage values and placeholder tables remain unanswered even when access is authorized. Changing tabs or refreshing the management status does not load a separate directory, audit history or storage measurement.

If no User Pack row is available, finish with “no visible User Pack record to inspect in this projection.” Continue built-in inspection in the library; do not create a custom asset to populate an administration example.

Final fresh Overview observation

After renewal and tab inspection, a fresh Overview query returned AUTHORIZED. Registered, Indexed, Superseded and Revoked were all 0; storage fields remained Unknown. These are separate observations: access succeeded, the current User Pack counts were zero, and storage telemetry remained unpopulated.

08 · Inspect an asset and its revision

1. Select Assets. If a current User Pack projection exists, select its identity/revision in Asset inventory.
2. Match Identity / revision and Scope to the asset you intended to inspect.
3. Read Lifecycle, Registry reference and Index reference. Registration and indexing are distinct observations.
4. Read Provenance, Dependencies and Lineage before assessing reuse.
5. Check Superseded by, Revocation reference and Reuse monitoring. A historical revision may remain inspectable without being eligible for new Work.

Illustrative reading exercise: if an actual row has a Registry reference but no Index reference, report “registered; index not projected.” Do not report it as published or ready to consume. If No visible User Pack assets. appears, first distinguish missing projection from a valid empty scope. No sample asset record is supplied as production evidence.

Lifecycle Status contains a lifecycle table and filter controls, but its rows are not populated by the inspected management response. Use the functioning Assets projection for per-record inspection; a lifecycle placeholder is not an empty-inventory finding.

Walkthrough: review one revision without changing it

Goal: decide what the current asset view actually establishes. Obtain the expected asset identity, revision and scope from the asset owner. The following fictional worksheet uses illustrative values; it is not an asset record or an importable request.

1. Open Packtory Administration → Assets after the effective-authority check. Select the supplied identity/revision in Asset inventory.
2. Compare Scope, then read Provenance, Dependencies and Lineage. Record which references are present and which observations are unavailable.
3. Inspect Lifecycle, Superseded by and Revocation reference before discussing reuse. A selected row alone does not establish eligibility.
4. If the desired revision is missing, check the current User Pack projection with the appliance operator and confirm the expected scope with the asset owner. Refresh Packtory status alone only refreshes the management query; it cannot prove a new asset projection arrived.

Completion check: the review names one exact revision, its scope and the available lineage/lifecycle observations, with unresolved fields assigned to their owner. Finish without registering, revoking or restoring anything through this inspection view.

Finish the review with a revision-specific disposition

For the fictional training-pack-alpha revision 3 exercise above, record three separate answers: “Did I match the requested revision and scope?”, “Which source/validation/consumption and dependency/lineage references are visible?”, and “Is a successor or revocation reference present?” Read Reuse monitoring as its displayed consumed, validated-reuse and failed-reuse counts for this record; it is not a guarantee of future success. If revision 4 is the intended successor, ask the owner for that exact identity and inspect its own record instead of transferring revision 3's conclusions.

If Lifecycle Status remains a placeholder while Assets contains a record, continue the per-record review in Assets and label the aggregate lifecycle view unavailable. If the intended next task is REGISTER, INDEX, SUPERSEDE or REVOKE, finish this UI inspection and hand the exact requested action/revision to the asset authority owner. The capability table identifies the unavailable manual controls; this guide supplies no substitute mutation command. A request for publication is not fulfilled merely by an Index reference.

Observed Lifecycle Status

The Lifecycle Status tab retained its table placeholder. This did not add a lifecycle record to the authorized empty Assets view. No custom User Pack was created for this walkthrough; inspect the official built-ins in the separate library guide.

09 · Understand the action boundary

Open Capability Boundary to distinguish implemented engine routes from this dialog’s controls. The current Assets view offers inspection, not manual lifecycle mutation.

The inspected generic management-command route returns denial rather than applying a lifecycle mutation. Do not try to make an unavailable operation work by editing storage, changing a browser field or sending a hand-written internal request. The governed asset publication authority and other lifecycle integrations must be assessed on their own registered route; this panel does not authorize them.

When a deployment shows derivative controls such as Create Derivative or Request Publication, they belong to a separately configured lifecycle route. This guide does not establish that route as a production customer workflow.

The actual Capability Boundary tab displayed the operation table described here. Reading the table did not execute any listed command.

10 · Read Binding Context without confusing setup scopes

Binding Context shows Enterprise reference, Appliance Domain reference, SSO tenant reference and Administrator identity. These are query-context fields, not an activation wizard. Entering values does not provision storage, activate an SSO integration, assign a role or publish assets. Use existing installation references only; do not invent production identities.

The separate Local sandbox authority section shows Organization, VibePackr User ID, Grant and Credential adapter. Its Initialize administrator action invokes native macOS credential verification for sandbox authority. Use it only when you are explicitly setting up that local sandbox. It is not a supported bootstrap for a fresh r232 customer appliance, nor a way to grant remote customer authority.

NOT_INITIALIZED permits the local initialization control; INITIALIZED means that local authority state exists. A successful initialization still requires effective authorization for each operation. If native verification is canceled, leave it canceled and preserve the displayed reason. Do not replace it with hidden credentials or manual grants.

Workflow: resolve a context question without provisioning

1. State the question first, such as “Does this query refer to the enterprise and appliance domain assigned to me?” Obtain the exact four Binding Context references from the installation administrator.
2. Open Binding Context and compare Enterprise reference, Appliance Domain reference, SSO tenant reference and Administrator identity with the handoff. For a reading exercise, enterprise:training and domain:training are fictional labels, not assignments. Enter only the actual supplied references when a permitted query needs them.
3. Use the relevant supported query/Refresh Packtory status and retain the returned context/status or literal rejection. AUTHORIZED is an authority/context observation; it does not fill the storage telemetry or directory tables.
4. For a roles question, inspect Organization & Roles. If SSO directory mapping is not bound, ask the identity administrator for the installation's supported directory/membership observation. For an audit question, inspect Audit; if no scoped projection is available, ask the audit owner for the supported record tied to the operation reference.
5. Finish with a matched context and supported answer, or the exact unavailable observation plus its owner. Editing these references is not storage provisioning, SSO activation or granting a role. The separate sandbox initializer is outside this context-query task.

In the observed Binding Context, authority status was INITIALIZED and Initialize administrator was disabled. The Grant field still displayed its “Not initialized” placeholder. Read that field as an unpopulated display, not as proof that the effective grant was absent: the fresh administrative queries had succeeded. No initialization was performed.

11 · Prepare and preview contribution evidence

Open Contribution in an installation with a bound VibePackr User ID and permitted contribution scope. The preview uses existing canonical ETS evidence; it does not create source evidence from a description.

1. Fill the period, scope and evidence references.
2. Select Raw metrics for an initial reading, or the approved weighted policy.
3. Choose Preview.
4. Inspect Period, Scope, Row count, Policy, Evidence Set ID and the raw/weighted rows.

A structurally valid form can still be denied by the engine. An empty row set may be valid for the selected period/scope; it does not establish zero activity across the organization. Contribution is an evidence projection, not a performance, compensation, promotion or disciplinary decision.

Walkthrough: supply a reporting interval and preview it

Goal: preview an authorized evidence set, then continue to the export task below. Ask the contribution/evidence administrator for the exact scope type and identity permitted to you, the canonical ETS references for that scope, and start/end bounds in the same time representation as those records. For weighted reporting also request the approved Policy ID and exact revision. A reference is an existing evidence identifier, not an asset name, a Work description or a new record you create in this form.

The inspected form accepts positive whole numbers and passes them as unsigned integer bounds; the engine compares them directly with each evidence event's occurred_at value. This route establishes no calendar-date conversion or event-time unit. Do not assume seconds, milliseconds or a timezone from the integer alone. Ask the evidence administrator to supply the interval and its time convention; if unavailable, the missing delivery item is the approved reporting interval specification, not permission to guess a conversion.

Fictional form exercise — use these values only to understand the fields. The reference below is deliberately illustrative and must be replaced with a real authorized reference before Preview.

1. Replace the example interval, scope and reference placeholder with the administrator's supplied values. Check start is less than end. For the illustrative interval, an event at 1000 is included and an event at 2000 is excluded.
2. Choose Preview. A successful projection reports PROJECTED; compare Period, Scope, Row count, Policy and Evidence Set ID with your intended report. Raw metrics should identify RAW_ONLY. Inspect the returned rows before export.
3. If the period is reversed, the form asks for a valid period and does not proceed. Correct the original bounds. If CONTRIBUTION_EVIDENCE_INVALID is returned, ask the evidence administrator to verify the exact references; do not replace them with arbitrary text. For CONTRIBUTION_SCOPE_DENIED, have the administrator confirm the allowed scope instead of broadening it.

Completion check: the returned preview matches the intended interval/scope and you have reviewed the actual rows or the explicit no-rows result. “No evidence-backed projection available.” means no usable projection; “The selected evidence set produced no contribution rows.” is an actual empty result. Ask the evidence owner to explain an unexpected empty result before exporting it.

Observed preview using historical test evidence

Contribution first returned AVAILABLE. The supplied historical test form was then filled in Raw metrics mode and Preview returned PROJECTED: one row, ORIGINATED count 1, and RAW_ONLY. This is a projection of the retained test evidence, not a new customer contribution or a new execution of the built-in audit Work. The public image shows the ready screen; filled references and returned private rows are retained only in the separate internal walkthrough.

12 · Export, verify and revisit an export

1. Complete Preview and verify the requested period, scope, evidence set and policy. Export only data you are authorized to retain.
2. Choose Export CSV. This is a state-changing operation that records an export; Preview is not proof that export has occurred.
3. Inspect Export result: Export ID, VibePackr User ID, Period, Scope, Row count, Policy, Evidence Set ID, CSV SHA-256 and Evidence Receipt.
4. Choose Verify export when enabled for the returned export. Inspect Verification; a digest displayed beside “Not verified” is not successful verification.
5. Use Refresh history with the valid form context to revisit the scope’s export history. Match Export ID and digest, not just a similar timestamp.

Worked sequence using your own authorized record: Preview the exact reporting interval in Raw metrics, confirm the scope and row count, export once, then verify the returned Export ID. Keep the returned receipt with the approved CSV artifact. This is a procedure, not a claim that any sample export passed.

The inspected frontend displays the export manifest and verification result; it does not itself create a browser download/save dialog. Do not assume that clicking Export CSV saved a file to Downloads. Use the installation’s supported artifact retrieval path and confirm the actual file digest before sharing; this guide does not invent an unverified path.

Continue the task: export once, verify and obtain the file

1. Keep the reviewed form values unchanged after Preview. If you edit the interval, scope, references or policy, run Preview again and review that result before exporting.
2. Select Export CSV once. A normal export response reports EXPORTED and supplies Export ID, CSV SHA-256 and Evidence Receipt. Write down those actual values with Period, Scope and Evidence Set ID. An illustrative Row count of 2 means two contribution rows; it does not establish two Work executions or two source events.
3. Select Verify export for the returned Export ID. Read Verification: CONTRIBUTION_EXPORT_VALID is the integrity-success reason. A top-level VERIFIED response alone is insufficient; inspect the verification reason for that same export. A mismatch such as CONTRIBUTION_EXPORT_CSV_DIGEST_MISMATCH means stop sharing and send the Export ID and sanitized reason to the evidence administrator for reconciliation.
4. Use Refresh history with the valid form to locate the same Export ID and CSV SHA-256. This confirms which recorded export you are discussing; it does not download a CSV. If Verify export stays disabled because no Export ID was returned, preserve the export error and reconcile the recorded history before attempting another export.
5. To finish a file-delivery task, ask the installation delivery/support owner for the supported retrieval mechanism for that exact export, the CSV bytes, and the matching manifest/receipt. Check the delivered file's SHA-256 against CSV SHA-256 using your organization's approved file-verification method. Retain the matching evidence with the file before authorized sharing.

The inspected export and read-export desktop responses carry manifest/receipt information but omit the CSV bytes. The missing customer handoff is an established retrieval mechanism for the exact recorded export and its associated file/evidence, owned by the installation delivery/support team. This guide cannot supply a verified download button or filesystem location. If that handoff is unavailable, record “export/verification inspected; CSV delivery unresolved” with the Export ID. Completion of an actual file-delivery task remains pending even when the engine export verifies.

Revisit an export without creating another one

Keep a small reporting record: actual Export ID, Period, Scope, Evidence Set ID, CSV SHA-256, verification reason and file-delivery disposition. For the fictional project:training-alpha exercise, the final line might read “intended scope checked; integrity verified; CSV handoff pending.” This is an illustrative sentence, not a recorded outcome or a substitute Export ID.

1. Restore a valid Contribution form for the same authorized scope. Refresh history requires valid period, scope and evidence inputs even though the history query lists exports for the scope.
2. Select Refresh history and compare the actual Export ID and digest with your saved record. Generated time alone is not an exact match. A missing history projection differs from the explicit “No Core export history is recorded for this scope.” result.
3. The history table displays records; this guide does not promise that clicking a historical row selects it for verification. Verify export acts on the current export identifier returned to the dialog. If that identifier is no longer selected after closing/reopening, ask the evidence administrator for the supported retrieval/verification of the exact saved Export ID instead of exporting again to recover it.
4. If the form was changed after Preview, preview the new request before a deliberately new export. For an uncertain export response, retain the time and form context, inspect history and have its owner reconcile the original request before another Export CSV action.

Close the reporting task only when the intended interval/scope and verification are established and any required CSV handoff is complete. If the owner cannot supply the time convention, evidence references or retrieval route, leave that specific step pending and retain the successful earlier observations.

What the current history controls can do

Refresh history validates the full form first: period, scope, evidence references and, for weighted mode, the policy fields. Fill those with genuine supplied values even when you only want to list history. The returned history is a display table: it has no row-selection action that loads an older export into Verify export. Verification becomes available when the dialog receives an export manifest with an Export ID and acts on that current returned ID. Do not create another export merely to enable the button.

The one export identified in retained local test evidence was seeded for a native micro-E2E exercise on 23 August 2026. It is not a customer report or a contribution export from the built-in audit Work shown elsewhere in this manual. If encountered during inspection, treat it as historical test evidence, not evidence of a new export or customer delivery.

Observed history without another export

With the exact historical form retained, Refresh history returned AVAILABLE and one existing export with the same identifier and CSV hash as the retained record. Verify export remained disabled: displaying history did not select that record as the current returned export manifest. No Export CSV or Verify export action was performed. This confirms historical lookup only; it does not establish new export creation, verification completion or customer file delivery.

13 · Read role, audit and storage limits precisely

Organization & Roles displays an identity table with Identity, Role, Scope and Membership columns. Audit displays Time, Actor, Command, Target and Decision. In the inspected dialog, these are placeholder tables: the management query does not populate a directory or audit history. SSO directory mapping is not bound. and No scoped audit projection available. must remain unresolved observations. They do not establish absence of canonical roles or audit records.

Existing Packtory/appliance recovery includes authority checks, signed current-head verification, durable replay controls and backup/restore machinery. The current desktop lifecycle RESTORE limitation does not remove those capabilities. Appliance recovery belongs to its authorized operating path, not the Assets panel.

Current evidence is narrower than a production durability claim: bounded GCP fixture validation exists, while production initial GCS connection/write remains unproven. Fresh-target restore and product-service selection remain unconnected in the documented current state. Do not provision a bucket, attach a disk or restore a customer installation merely to clear an Unknown label. Use the Admin guide and authorized recovery procedure for that separate action.

Observed role and audit tabs

Organization & Roles displayed SSO directory mapping not bound. Audit displayed no scoped audit projection. These are the actual tab results; they do not establish absence of canonical assignments or audit records.

14 · Diagnose a denied or incomplete operation

For support, record the surface, exact status/reason, client version, time, operation, scope and permitted asset/export reference. Share only the minimum authorized details; omit credentials, full evidence payloads, internal policy contents and unrelated user data. Continue with the cross-surface troubleshooting guide.