PKPEEK Docs
Docs/My Work

Linked work, external packages and handoffs

Register external research or planning packages, accept handoffs, review changed inputs and resolve link conflicts (M01–M14).

Acquisition Planner · Research owner · Authorized business owner

/pdcc/my-work/linked?tab=queue&screen=M01
Live walkthrough · Linked work, external packages and handoffs
/pdcc/my-work/linked?tab=queue&screen=M01
/pdcc/my-work/linked?tab=intake&screen=M02
/pdcc/my-work/linked?tab=status&screen=M03
/pdcc/my-work/linked?tab=changed&screen=M04
/pdcc/my-work/linked?tab=coverage&screen=M10

Linked work connects modules — or the outside world — without hidden dependencies. Research done elsewhere can feed planning; a native research report can hand off to planning; and every accepted input is pinned by version.

Register an external package (M02)

  1. 1

    Choose research input (M01)

    Pick native research or an external package.

  2. 2

    Register external package

    Type, source, version, author and approval evidence; upload supporting files to quarantine.

  3. 3

    Validate package

    Hash, structure and compatibility are checked. Upload and validation do not mean approved or accepted.

Accept a handoff (M03)

The receiving owner reviews the package for acceptance: accept the verified package, return with reason, or keep the current baseline. Acceptance binds the exact version, digest, rationale, actor and authority, and grants no evidence or SI rights.

Review changed input (M04)

  1. 1. New version arrives

    e.g. EXT-RESEARCH-007 v3 with revised delivery assumptions.

  2. 2. Impact review

    Compared with the accepted baseline (v2) and your local edits.

  3. 3. Decide

    Keep accepted baseline, or create an adoption draft. Adoption may invalidate dependent review decisions.

Other linked-work screens

ScreenPurpose
M05 Accepted work historyHistorical inputs stay accessible under current rights regardless of module purchase.
M06 Research coverageNative, external, unknown or missing research for an acquisition — unknown never implies *not performed*.
M08 / M09 New capability & adoptionKeep, supplement or replace — distinct choices with a preview.
M10 Link conflictConfirm record identity and source versions; cross-tenant links are rejected.
M11 Handoff status & recoveryTransfer, validation, acceptance and filing receipts; unknown outcomes are reconciled before retry with the original operation identity.
M12–M14 Core-only pathsMy Day with Core, planning with external research, research with manual assessment.
Heads up — Report approval and receiving-module acceptance are different events. A new report cannot overwrite an accepted planning baseline.

Related guides

Review queue and review assignments

Open the exact package and role assigned to you, check authority, and decide, return, request reassignment or delegate (MW02).

Modules: Core and optional

What Core always includes, what each optional module adds, and how the app keeps working when a module is absent or disabled.

Acquisition Actions: planning workspace

Assemble research, requirement, estimates and review into a versioned plan; prepare follow-on acquisitions (AP01, AP02).

Document matching and evidence versions

Resolve ambiguous acquisition associations and review new evidence versions without replacing what findings cite (EV04, EV05).