Packtory — inspect built-in Packs

01 · Open the built-in library

Local candidate; native inspection recorded. This walkthrough was performed in the local macOS candidate on 4 October 2026 using the original native application. The pictures are direct screen captures. The compiled registry supplies two metadata items: Audit Review and Audit Evidence Format, both revision 1.0.0. A registry-derived list is discovery information, not execution authority or proof that a Work ran.

Prepare: use the matched candidate supplied by your operator. If you are reviewing an existing Work, keep its full Work ID and report revision before opening the library. You do not need a custom Pack, a download catalog or a synthetic demonstration asset for this exercise.

1. Open Packtory in the desktop toolbar.
2. Find Built-in Packs and the Bundled metadata · Read only description.
3. Read the built-in section’s own status. Continue when it displays the expected items. If it says Built-in inventory is unavailable., follow the failure section; do not replace it with a downloaded asset.

The separate user/download area below may have its own unavailable message. Read each section’s status separately.

02 · Inspect the entry-point Pack

1. In Built-in Packs, select the Audit Review row.
2. Read Name, Identity and Revision in its detail. Confirm pack:audit-review and 1.0.0.
3. Read Origin OFFICIAL_BUILTIN, Catalog role Entry point, Domains audit and Workspaces BUSINESS.
4. Read Dependencies: pack:audit-evidence-format@1.0.0. Keep this exact identity and revision for the next step.

Completion: the row and detail identify the same bundled revision and its dependency. Entry point is a catalog role; it is not a newly bound MAIN Pack for your Work. Row selection only opens details.

03 · Inspect the supporting dependency

1. Select Audit Evidence Format.
2. Confirm Identity pack:audit-evidence-format, Revision 1.0.0 and Catalog role Supporting dependency.
3. Compare that identity/revision with Audit Review’s Dependencies. Read its own Dependencies field; None projected describes this metadata entry.
4. Read the Inspection only message. There is no Use or download checkbox in a built-in row, by design.

Completion: you can name the entry point and its supporting dependency. Two inventory rows do not mean two executions. This panel neither binds a Pack to Work nor grants execution permission; the lower user/download controls belong to separate workflows.

If the last line is below the panel edge, scroll inside Built-in Packs to read it.

04 · Search, filter and recover the full list

1. In Search built-in Packs, enter audit-review.
2. Read the one matching Audit Review row. The prior dependency detail clears because it is no longer in the result.

Now enter no-such-pack. 0 built-in Packs · Read only · No matching items. describes your filter result; it does not mean the bundled Packs were removed.

Choose Reset filters. The search clears, all scope filters return to All, and both items return.

Choose Supporting dependency under Catalog role. Only Audit Evidence Format remains.

Choose Domain audit and Workspace BUSINESS. The same one item matches all three filters. These choices filter catalog metadata; they do not change your current workspace or Work. Choose Reset filters again before closing.

05 · Close the library and return to your Work

1. Use Close Packtory (×).
2. If you began with an existing Work, compare its Active Work identity with the one you retained. A shortened header is insufficient for an exact identity check; open the Work detail when needed.
3. For recorded binding, use Engineering → Audit. For actual outcome, open the same Work’s Audit Report and revision. Follow the built-in Work inspection guide.
4. Record which two metadata revisions you inspected and any missing information. Do not record a new execution, download or acceptance merely because you viewed a row.

Completion: you have inspected both builtin entries, recovered from a no-match filter and returned to the intended context. This is a read-only catalog exercise; the native steps above were observed in this local candidate. The existing Work, execution and all seven retained report files were unchanged after inspection.

06 · Set or remove a Work draft preference

Separate conditional reference—not part of the built-in exercise. These controls apply to user/catalog or supplied lifecycle contexts. They are not enabled by inspecting a built-in row. A connected customer workflow is not validated by this candidate guide.

Prerequisites: the selected Pack is locally AVAILABLE, is not a remote-catalog row, and there is no active Work. The intended Work route must separately support consuming a Pack.

1. Select the exact eligible Pack and inspect its detail.
2. Read the message next to Use in new Work. If an active Work or unavailable state disables it, finish/reconcile the current Work or resolve the stated prerequisite first.
3. Choose Use in new Work when the intended task permits it. The client records a PIN preference in the existing Work Draft.
4. Return to the request and inspect Selected Pack. Compare identity/revision with your recorded asset.
5. To undo this local choice, use Remove on Selected Pack and confirm the selection is cleared.

Completion: the intended draft preference is visible, or has been cleared. Work submission and execution remain separate.

For the local audit exercise: remove the selected Pack and any attachments before Prepare Work. The inspected CREATE_AUDIT_ARTIFACT composer rejects them with ATTACHED_CONTENT_OR_SELECTED_PACK_OPERATION_NOT_SUPPORTED. Selecting an asset does not turn this route into a Pack executor.

07 · Request local availability and read each result

Separate conditional reference—not part of the built-in exercise. These controls apply to user/catalog or supplied lifecycle contexts. They are not enabled by inspecting a built-in row. A connected customer workflow is not validated by this candidate guide.

Configured demonstration scope. The inspected desktop download adapter uses a supplied sandbox configuration. It can create local availability and discovery records; this does not establish a production customer catalog or a customer setup procedure. Follow this recipe only in an already supplied, authorized demonstration context.

Prerequisites: your delivered installation has a configured governed catalog, shows the intended service identity and permits this download. This source-backed recipe does not establish that a customer production catalog is connected.

1. Refresh Packtory and read the catalog/download status. If it is unavailable or not configured, record the reason and ask the delivery/domain owner for the supported configuration.
2. Use the row checkboxes to select only the exact permitted assets/revisions. Compare the selected count with your list.
3. Choose Download once. While the request is pending, wait for the result rather than issuing another batch.
4. Read the batch reference, local count, denied count and reported binding/execution counts. Select each requested row and read its visible Availability. The inspected UI stores detailed per-item responses but does not display all denial reasons; if the reason is absent, ask the catalog/asset owner to reconcile the batch reference plus asset/revision. A batch-level message does not make every item successful.
5. Reinspect the selected revision and its current local availability before considering any separately supported Work use.

Completion: each requested revision has a known result. Download establishes local availability only; Work binding and execution permission remain separate. An uncertain response requires reconciliation of the existing batch, not a new request.

The inspected request supports 1–32 selected assets. A downloaded catalog row remains a catalog row, so Use in new Work may remain disabled after refresh. Ask the asset owner to reconcile the exact core projection and eligibility; do not assume download enabled Work use. This action is not a browser file-save operation.

08 · Follow the conditional sandbox derivative demonstration

Separate conditional reference—not part of the built-in exercise. These controls apply to user/catalog or supplied lifecycle contexts. They are not enabled by inspecting a built-in row. A connected customer workflow is not validated by this candidate guide.

Supplied sandbox demonstration only. The inspected adapter uses a sandbox configuration and labels these assets Synthetic Third Lifecycle. The procedure below explains that existing demonstration route. It is not a setup or publication recipe for production customer assets.

Some configured lifecycle projections expose Create Derivative, Publication scope, Request Publication and Contribution Correlation for the selected origin/derivative. These controls are conditional. A normal library row does not necessarily expose them; this guide supplies no customer lifecycle configuration.

1. Confirm the asset owner has assigned the exact origin and permitted lifecycle task. Inspect Origin, Originator, Work-use ETS and current Derivative fields.
2. If the origin is selected, no derivative exists and the permitted control is enabled, Create Derivative requests creation. Read the returned origin → derivative identity and refreshed detail before continuing.
3. If publication is separately permitted, select the approved Team or Organization scope and use Request Publication. Read the returned decision reason and refreshed Publication field. A request or authorization message alone is not proof of public remote distribution.
4. Where available, Contribution Correlation opens the related administrative view. Follow its effective access requirements and inspect the same lifecycle references.

Completion: the intended origin/derivative identity and exact returned decision are recorded. If controls are absent, disabled or return a denial, preserve that state and contact the lifecycle owner. Do not substitute an unrelated asset or broaden publication scope.

This describes inspected conditional controls. Their delivered customer configuration and a successful connected lifecycle demonstration have not been established by this documentation run.

Read the exact publication result: COMPLETED requires a returned distribution, AUTHORIZED alone may precede one, and DENIED preserves the reason. Reinspect the same origin/derivative and scope.

Inspect the related Contribution Correlation

1. From the supplied lifecycle context, choose the enabled Contribution Correlation control.
2. Read the same origin/derivative references, then choose the assigned Derivative policy revision (Revision1 or Revision2).
3. Preview Correlation should return PROJECTED. Compare Evidence set, Policy, user raw metrics and weighted scores.
4. Only when export is part of the permitted exercise, choose Export Correlation CSV and inspect the EXPORTED manifest, Export and Verification fields.

The inspected handler does not open a save dialog or download CSV bytes. A manifest is not a received CSV file; request the supported acquisition procedure from the operator. Keep this synthetic correlation exercise separate from ordinary Contribution exports.

09 · Resolve the failed step and hand off precisely

Built-in inventory unavailable: stop interpreting rows and ask the installation operator to verify the matched native candidate and public projection. Preserve the exact message and client version. Do not configure a download sandbox to repair the built-in metadata section.

No matching built-in items: Reset filters first. If the valid unfiltered list still differs from the supplied candidate inventory, record the identities/count and ask the operator to reconcile the version.

Historical user-library boundary: the older capture below showed an unavailable user/catalog projection. It is retained to explain that separate failure route and is not the current built-in inventory illustration. A missing download configuration does not prove the bundled Packs are absent.

Include client version, target reference, asset/revision, filter scope, failed step and sanitized reason. Include the batch or Work reference only when it exists. Never send credentials, confidential task input or a full asset inventory.

Packtory troubleshooting · Support handoff worksheet