Use and review the official built-in Audit Packs

01 · Prepare the existing Work

Use the connected local candidate and retain the full Work ID and report revision from your result. The observed operation was create audit artifact, with one execution, validation PASSED and human acceptance pending. This walkthrough reopens that Work; it requires no new Submit.

Built-in official Packs, user-created Pack records and downloaded catalog assets are different things. An empty user Pack list does not remove the built-in Packs used by this Work.

02 · Open the Work and read the bound Pack

1. Open Business → My Work and identify the existing Work. If it is already active on Home, check that context first.
2. Read the Domain/Pack strip: the observation showed Audit and pack:audit-review · Bound.
3. Keep the full Work ID for later comparison; the top bar can shorten it.

Bound describes the recorded association. It is not a new execution or human acceptance. If the Work differs, return to the intended Work before interpreting its Pack fields.

03 · Inspect the main and supporting roles

1. Switch to Engineering, retain the same Active Work and open the top-level Audit tool. Scroll inside its Lifecycle audit panel to reach the Pack fields.
2. Read Bound Main Pack: pack:audit-review@1.0.0, MAIN, OFFICIAL.
3. Read Bound Pack set and Effective Packs: both Audit Review and pack:audit-evidence-format@1.0.0, SUPPORTING, OFFICIAL were present.
4. Confirm Effective composition is BOUND. Manual component selections was 0; the observed route used automatic resolution rather than manual selection of the supporting Pack.

The new local native observation confirms these populated fields. If a field is NOT_RECORDED, preserve that field and Work identity; do not infer the Pack is absent from the product.

04 · Read what each Pack contributes

In Audit, read Validation requirements and Evidence requirements. The supporting Pack contributes lineage-integrity checks; the main Pack contributes audit-result validation. Both have recorded evidence requirements. Compare the displayed requirements with the same Work’s validation and report.

Repository access authorized, Index access authorized and Execution authorized by composition all showed FALSE. Keep those exact values. A bound composition does not itself grant those permissions; actual execution is a separate record. The supporting role does not prove a second independent Pack execution.

05 · Troubleshooting: user Pack inventory is a separate scope

Open Engineering → Packs to inspect the selected Work’s user Pack selection and inventory projection. Keep its aggregate selectable/executable categories separate from individual user Pack rows and from the bound official Pack set you just inspected.

The current observation shows NO_PACK_SELECTED; Selectable 15, Executable 1, Unavailable 14; projected user Pack records 0 and index records 0. The header still shows the official audit Pack Bound. These aggregates are not installed-record counts. This Packs view does not display execution consumption. Do not treat this empty user list as evidence that Audit Review or Audit Evidence Format was not bound. A download catalog is another route and is not required to read this built-in Work.

06 · Match execution to the same report

1. Open Audit Report and select the exact Work and revision; the retained report is revision 16.
2. Match the PDF’s Work and original intent. Read execution count 1, validation PASSED and the pending-human-acceptance final result.
3. Use the report’s Execution summary to distinguish actual main Pack consumption from the composition’s supporting requirements. The recorded local operation made no provider call.
4. On the last page, read Closure before handing the result to a reviewer. Human acceptance remains required and unrecorded.

The prior R11 native demonstration verified this same PDF, external PDF opening and return. Follow the final report guide for exact file checks. This walkthrough also observed discovery and the same existing report; it created no new Work. Full report-body captures contain internal details and remain in internal local review.

07 · Return with a precise outcome

Return to the Work and confirm its identity and pending acceptance. You should now be able to name both official Pack revisions, explain MAIN versus SUPPORTING, distinguish binding from execution, and identify the same report.

This completes a bounded review of actual built-in Pack use. It does not establish custom Pack creation, Packtory library population, download success or final human acceptance. Return to PackrGUI overview or Engineering.

The separate R13 Packtory catalog walkthrough covers built-in discovery and details in the newer local candidate.