Maintains a historical index of all cross-project knowledge transfers for this project
Maintains a historical index of all cross-project knowledge transfers for this project. Tracks inbound and outbound transfers with status, source/target projects, dates, and routing decisions. Provides analytics on transfer patterns across sessions.Let CWK-026 and CWK-027 call this recipe automatically during their pipelines. Use report mode to check transfer activity before starting cross-project work. Use rebuild mode if the registry file is missing, corrupted, or out of sync with the actual packet files.
Cross-Project Transfer Registry
Tags: Introduced in Beta, Transfer, Registry, Cross-Project, Index, Analytics, Tracking, XFER, Cowork
TL;DR
What It Does
Maintains a historical index of all cross-project knowledge transfers for this project. Tracks inbound and outbound transfers with status, source/target projects, dates, and routing decisions. Provides analytics on transfer patterns across sessions.
How It Works
Three modes. In “update” mode (called by CWK-026 after export or CWK-027 after import), the recipe reads the registry file, adds or updates a transfer entry with metadata and status, updates aggregate counts by direction, appends to the recent transfers list (capped at 20), and writes back. In “report” mode (default), it displays a formatted summary with inbound totals (accepted/deferred/rejected by source), outbound totals (by target), and the 10 most recent transfers. In “rebuild” mode, it scans the transfers/ directory tree — outbound/, inbound/processed/, and inbound/pending/ — parsing each XFER-*.txt packet to reconstruct the registry from scratch.
What To Expect
In update mode: a confirmation that the entry was added. In report mode: a formatted transfer summary with counts and recent activity. In rebuild mode: a confirmation with the total number of transfers indexed. The registry file persists across sessions in the project workspace.
Best Results When You
Let CWK-026 and CWK-027 call this recipe automatically during their pipelines. Use report mode to check transfer activity before starting cross-project work. Use rebuild mode if the registry file is missing, corrupted, or out of sync with the actual packet files.
Typical Time
Under 30 seconds for update and report modes. 1–2 minutes for rebuild (depends on number of transfer packets to scan).
Difficulty
Beginner — the recipe is mostly automatic. Update mode is called by other recipes. Report mode produces a readable summary. Rebuild mode is a recovery tool that requires no configuration.
How To Start
This recipe is called automatically by CWK-026 (Knowledge Packager) and CWK-027 (Knowledge Receiver) during their pipelines. It can also be invoked standalone for reporting or rebuilding.
STEP 1Choose the Mode
Select update (add entry), report (view summary), or rebuild (reconstruct from files).
Available parameters
-
mode
· string · optional · default: report · options: update, report, rebuild
“update” adds or updates a single transfer entry. “report” displays the transfer summary. “rebuild” scans transfers/ and reconstructs the index from packet files. -
transfer_id
· string · optional
Transfer ID to update. Required when mode is “update.” Format: XFER-{SOURCE}-TO-{TARGET}-{DATE}-{SEQ}. -
direction
· string · optional · options: inbound, outbound
Direction of the transfer. Required when mode is “update.” Determines which aggregate counts are incremented.
Invocations
View Transfer Report
#H->AI::Directive: (Show transfer registry report)
Update After Export (Called by CWK-026)
#H->AI::Directive: (Update transfer registry with mode=“update”, transfer_id=“XFER-CP-061-TO-CP-060-20260415-001”, direction=“outbound”)
Rebuild From Files
#H->AI::Directive: (Rebuild transfer registry with mode=“rebuild”)
Usage Examples
Three scenarios — viewing the report, automatic update after a transfer, and rebuilding from files.
Example 1 · Viewing the transfer report
User:
Show me the transfer registry.
Cat:
Cross-Project Transfer Registry for CP-061. Last updated: 2026-04-15. Inbound: 5 transfers (3 accepted, 1 deferred, 1 rejected). By source: CP-059a: 3, CP-060: 2. Outbound: 8 transfers. By target: CP-060: 4, CP-067: 3, CP-059: 1. Recent: [table of last 10 transfers].
Example 2 · Automatic update after CWK-027
CWK-027:
Calls CWK-028 with mode=“update”, transfer_id=“XFER-CP-059a-TO-CP-060-20260302-001”, direction=“inbound”.
Cat:
Registry updated: XFER-CP-059a-TO-CP-060-20260302-001 (inbound). Inbound total: 6. Accepted: 4.
Example 3 · Rebuilding a corrupted registry
User:
The registry seems wrong — rebuild it from the actual transfer files.
Cat:
Scanning transfers/outbound/ — 8 packets found. Scanning transfers/inbound/processed/ — 4 packets. Scanning transfers/inbound/pending/ — 1 packet. Registry rebuilt: 13 transfers indexed. Inbound 5 (4 accepted, 1 pending), Outbound 8.
How AI Reads This Recipe
When this recipe is triggered, the AI processes transfer registry management in one of three modes. The AI should:
- DETERMINE MODE. Check the mode parameter: “update” proceeds to entry update, “report” proceeds to summary display, “rebuild” proceeds to full reconstruction. Default is “report.”
- UPDATE REGISTRY (mode=“update”). Read the registry file. If it does not exist, initialize an empty structure. Parse existing data. Create a new entry from the transfer packet metadata: transfer_id, direction, source, target, date, item_type, item_title, status, LL assignment, roadmap task. Update aggregate counts by direction. Append to recent_transfers (cap at 20). Update last_modified. Write back.
- REPORT (mode=“report”). Read the registry file. If missing, report that no transfers have been recorded. Display: inbound totals with accepted/deferred/rejected breakdown and by-source counts, outbound totals with by-target counts, table of the 10 most recent transfers (date, direction, peer, title, status).
- REBUILD (mode=“rebuild”). Initialize empty registry. Scan transfers/outbound/ for XFER-*.txt and parse metadata. Scan transfers/inbound/processed/ and parse metadata plus TRANSFER_RESPONSE status. Scan transfers/inbound/pending/ for unprocessed packets (status PENDING). Sort recent_transfers by date descending. Compute total_transfers. Write rebuilt registry.
Error handling: if the registry file is corrupted, use mode=“rebuild” to reconstruct from packet files. If the transfers/ directory does not exist, initialize it with empty structure. R-12 audit trail is recorded for all modes.
When to Use This Recipe
Use this recipe when you:
- Want to see a summary of all cross-project knowledge transfers for this project (report mode).
- Have just exported or imported a transfer and need to update the registry (update mode — usually called automatically).
- Suspect the registry is out of sync with actual transfer files and need to rebuild it (rebuild mode).
- Need analytics on transfer patterns — which projects you exchange knowledge with most, acceptance rates, transfer volume.
Do not use this recipe when:
You want to create or process a transfer — use CWK-026 (Knowledge Packager) to send and CWK-027 (Knowledge Receiver) to receive. CWK-028 is the bookkeeping layer: it tracks transfers but does not create or validate them.
Recipe FAQ
Q.What are the three modes?
“update” adds or updates a single transfer entry. “report” displays a formatted summary of all transfers. “rebuild” scans the transfers/ directory and reconstructs the registry from the actual packet files.
Q.How does the registry file persist across sessions?
The registry file is stored in the project workspace folder, which persists on the user’s computer. It survives session resets because it is a regular file in the workspace, not in the VM.
Q.What does the recent_transfers list track?
The last 20 transfers (most recent first) with date, direction, peer project, item title, and status. The report displays the 10 most recent for a quick overview.
Q.When should I use rebuild mode?
When the registry file is missing (first time), corrupted, or out of sync with the actual packet files. Rebuild scans all three transfer directories (outbound, inbound/processed, inbound/pending) and reconstructs the index from scratch.
Q.Is the registry automatically updated?
Yes, when CWK-026 and CWK-027 are used. Both recipes call CWK-028 with mode=“update” as part of their pipelines. The registry stays current without manual intervention as long as transfers go through the standard recipes.
Q.What counts does the registry track?
Inbound: total, accepted, deferred, rejected, and by-source project. Outbound: total and by-target project. These aggregate counts enable quick analytics on transfer patterns.
Version History
Changes to this recipe over time. Most recent first.
v1.01a
2026-03-15
Added rebuild mode for reconstructing the registry from packet files. Recent_transfers list capped at 20 entries. By-source and by-target breakdowns in aggregate counts. Error handling for missing or corrupted registry files.
v1.00a
2026-02-28
Initial release. Transfer registry with update and report modes. Tracks inbound/outbound transfers with status. Called by CWK-026 and CWK-027. Audit trail via R-12.
Get this recipe with CRAFT for Claude Cowork
Cowork recipes ship bundled with CRAFT for Claude Cowork — there’s no separate download. Clone the framework once, and your AI runs every recipe automatically when invoked.
Pull anytime to stay on the latest version — free to clone, no login or email required.
Then start your session
Once CRAFT is in your project folder, open a new Cowork session and ask Claude to initialize. For example:
You
Please initialize my CRAFT session.
Claude
CRAFT session ready. Your project is loaded, your persona is active, and your recipes are available. What would you like to work on?
Not familiar with Git? Download as a ZIP
No command line needed. Just download, move, and unzip:
- Open the CRAFT framework repo on GitHub.
- Click the green Code button, then choose Download ZIP.
- Move the downloaded ZIP into your Claude Cowork project folder.
- Unzip it: double-click on Mac, or right-click → Extract All on Windows.
