Who holds reproduction rights for designs whose sponsor has gone

The options

The order shown is not a ranking of preference.

1. Option 1

   Exclusive permission to the central restoration center

   Concentrates responsibility for preservation equipment and record interpretation in one place, providing consistent warranty, but local areas depend on transport, waiting, and the survival of a single body.

2. Option 2

   Independent permission for local workshops

   Expands the option to receive the design and usable records and reproduce with local raw materials, but buyers bear warranty differences by workshop and the burden of verifying compatibility.

3. Option 3

   Permission through a mutual inspection workshop alliance

   Shares reproduction rights and warranty burden across workshops through mutual inspection and a joint fund, but membership and inspection fees apply and access for workshops outside the alliance may be delayed.

The situation as it stands

If the renewal deadline passes, priority access to the preservation equipment expires, the cost of the central reproduction route rises, and local workshops will postpone their next production investments without knowing the scope of permission.

A fictional organization, the Zelkova Living Materials Trust, and the repair workshops of autonomous living districts

1. Premise 1Synthetic premise: the design of long-used storage modules and the permission to reproduce them remain with the trust, but support from the original maker has ended. The preserved quality records reference raw materials that cannot be obtained now and the approval of an inspection body that no longer exists.
2. Premise 2Synthetic premise: the trust can focus its funds either on maintaining the preservation equipment at the central restoration center or on building local inspection capacity. Long-term use results of new raw materials accumulate only after the renewal deadline, and the trust cannot control the independent products of local workshops.
3. Premise 3Synthetic premise: living district residents want to obtain components fitting their existing storage system nearby, and the central restoration center argues that dispersed permissions weaken the accumulated compatibility warranty. Local workshops object that the absence of the old body's approval becomes a permanent barrier to entry.

Where it holdsConfirm a single operating system linking permission to reproduce storage modules held by the trust with joint warranty.

What can be lost

• Residents using existing modules lose access to compatible components or bear the cost of replacing the entire storage system.
• Local repair workshops may lose a market entry opportunity for reproduction or the operating resources to bear an independent warranty.
• The central restoration center may lose its exclusive revenue and the base for maintaining preservation skills, or take on the warranty burden that comes with supply concentration.

What is still unknown

1. Unknown 1What performance the quality records obtained from the old raw material and inspection system can explain about new raw materials has not been verified.
2. Unknown 2How much skill not transferred beyond the central restoration center is needed to interpret preservation records is unknown.
3. Unknown 3Whether mutual inspection among regions will work as independent error detection or will share the same judgment errors has not been verified.

Signals to decide again

• Compatibility failures and use-life records for new raw material components — the living district joint inspection office compares them every half year, and when results fall outside the grounds of the warranty, the decision is revisited.
• Component waiting times by region and the results of permission application processing — the trust user audit team checks every quarter, and when access to a specific living district is cut off and persists, the decision is revisited.
• The stages at which independent reproduction performed with preservation records alone succeeds or fails — the external records verification team checks yearly, and when a dependency that cannot be transferred is found, the decision is revisited.