Verified protected conveyance — 2027-R1 TEAM_A to TEAM_B (top-4 protected, fallback 2028)
2027 · Round 1 · verified-2027-protected-conveyance-alpha · HUMAN_VERIFIED · not synthetic
HUMAN_VERIFIED · arrangement status HUMAN_VERIFIEDVerified by loop4-human-verifier · Aug 6, 2026(2026-08-06T15:00:00Z)
003 (Tier2 Spotrac) confirms top-4 protection and 2028 fallback; 012 (Tier1 league doc) confirms protection mechanics. Manual scenarios: pos 2 retained by A with fallback, pos 10 conveyed to B.
Sources (2)
- Future Draft Records — Protected Conveyance TEAM_A → TEAM_B (2027-R1, top-4 protected)Tier 2 · structured_referenceSpotrac · published Aug 1, 2025
src-2025-reg-003Structured reference confirming 2027-R1-TEAM_A protected 1-4 to TEAM_B with 2028-R1 fallback obligation.
- Official League Document — Ranked Pool Allocation Principles (2025 Draft Procedures)Tier 1 · league_documentNBA Official League Office · published Apr 15, 2025
src-2025-reg-012League procedure note describing ranked-pool ranking by favorability (lower number = more favorable); supports interpretation across all RANKED_POOL arrangements.
Transaction chain — fallback obligations (1)
Structured obligations emitted by the engine when a protected pick does not convey. Future-season picks are not auto-resolved.
fallback-2028-A-to-B-alpha:2028-R1-TEAM_ATEAM_A → TEAM_B (FALLBACK_OBLIGATION_CREATED) — Fallback obligation if 2027 pick is protected; unprotected 2028 conveyance. Engine emits but does not resolve this future season.
Pick origin
Where each pick right originated and which rule moves it.
| Pick | Origin | Rule | Recipient |
|---|---|---|---|
2027 R1 2027-R1-TEAM_A | Team A | Team A → Team B (2027-R1-TEAM_A, protected positions 1, 2, 3, 4; fallback 2028-R1-TEAM_A → Team B) | Team B |
Participants
TEAM_ATeam B TMB TEAM_BOriginal picks
2027-R1-TEAM_A— Team A (2027 R1)2028-R1-TEAM_A— Team A (2028 R1)
Rule summaries
PROTECTED_CONVEYANCEconveyance-2027-A-to-B-alpha: Team A → Team B (2027-R1-TEAM_A, protected positions 1, 2, 3, 4; fallback 2028-R1-TEAM_A → Team B)
Example scenarios
One-sentence answer
Team A receives 2027-R1-TEAM_A.
Positions
| Pick | Team | Position |
|---|---|---|
| 2027-R1-TEAM_A | Team A | 1 |
| 2028-R1-TEAM_A | Team A | 2 |
Allocations
| Pick | Recipient | Reason |
|---|---|---|
| 2027-R1-TEAM_A (Team A) | Team A (TEAM_A) | PICK_PROTECTED_RETAINEDPick '2027-R1-TEAM_A' at position 1 is protected; retained by holder 'TEAM_A'. |
Fallback obligations
fallback-2028-A-to-B-alpha: 2028-R1-TEAM_A TEAM_A → TEAM_B (FALLBACK_OBLIGATION_CREATED)
Trace
| # | Rule | Event | Explanation |
|---|---|---|---|
| 1 | VALIDATION | VALIDATION | Scenario validated: pick '2027-R1-TEAM_A' has a valid position (1) in range 1-30. |
| 2 | conveyance-2027-A-to-B-alpha | PROTECTION_EVALUATED | Protection evaluated for pick '2027-R1-TEAM_A' at position 1. Protected positions: [1, 2, 3, 4]. Result: PROTECTED. |
| 3 | conveyance-2027-A-to-B-alpha | NOT_CONVEYED | Pick '2027-R1-TEAM_A' did not convey to recipient 'TEAM_B' because position 1 is within the protected range [1, 2, 3, 4]. |
| 4 | fallback-2028-A-to-B-alpha | FALLBACK_CREATED | Fallback obligation created: when pick '2027-R1-TEAM_A' is protected, the future pick '2028-R1-TEAM_A' is conveyed from 'TEAM_A' to 'TEAM_B'. This future season is emitted but not resolved by this engine. |
| 5 | conveyance-2027-A-to-B-alpha | PICK_ALLOCATED | Pick '2027-R1-TEAM_A' allocated to 'TEAM_A' with reason code 'PICK_PROTECTED_RETAINED'. |
| 6 | RESOLUTION_COMPLETE | RESOLUTION_COMPLETE | Protected conveyance resolution complete. |