The repaired feed assembly rides inside a shock case as Nahuli, Ranuko, and Lahani cross back into Amber Wing. Kiryati remains in Avalon’s service bay with emitter three, overseeing its final bench cooldown.
Amber Wing’s local registry accepts the defensive salvage classification. The weapons are listed as recovered ship property, isolated from propulsion, navigation, and the confined assistant layer.
Ranuko
Accepted classification, then an overlap flag. Someone attached a prior claim to the military architecture, and the registry cannot distinguish hardware ownership from command inheritance.
A second pane identifies the claim as dormant but authenticated. No remote connection is active, and no signal leaves Amber Wing, yet the legal record marks the recovered systems as disputed.
Lahani
If Avalon recognizes that claim, the emitters may become seized evidence instead of defensive equipment. We should know who can invoke it before we submit the final ownership packet.
Ranuko
I can trace the registry lineage, but opening the full archive may trigger a mandatory disclosure. We have a clean local system now, and I would rather not advertise its military ancestry.
The documentation console waits beside the sealed shock case, offering three options: contest the claim, request its origin record, or submit the salvage unchanged and accept Avalon’s ruling.
“Why would there be a contest for tech that isn't from our fleets?”
SUCCESS (Legendary Reasoning, rolled +0)
Nahuli
Why would there be a contest for technology that isn't from any of our fleets?
Nahuli submits the origin-record request through the local archive, keeping the weapons isolated and the assistant layer excluded. The registry opens its authenticated lineage without transmitting a claim notice.
Ranuko
Because ownership follows architecture, not just hulls. This system was built under a military standard that outlived the fleet that registered it.
A provenance tree expands across the display: decommissioned defense contracts, transferred designs, and a dormant custodial authority. No Avalon fleet appears anywhere in the chain.
Ranuko
There is no active owner listed. The contest flag is between inherited command rights and recovered-property law, not between Avalon and another fleet.
Lahani
Then we challenge the inheritance. A dead command structure cannot claim hardware we recovered, repaired, and isolated ourselves.
Ranuko attaches the provenance record, repair logs, local authorization design, and quarantine history to a formal contest. The registry accepts the packet and marks the disputed claim inactive pending review.
“A weapon of this type and power level typically does not meet the standards for a military licensed weapon. That is why we kept to the support weapons, not the main ones. That would be a headache of paperwork for a ship like ours. Also, we are not a civilian ship.”
SUCCESS (Legendary Diplomacy, rolled +0)
Nahuli
This weapon's power level does not meet the standard for a military-licensed weapon. That is why we kept to support weapons, not the main systems. Treating it otherwise creates needless paperwork for a ship like ours. We are not a civilian ship.
Nahuli adds the technical classification to the contest packet, attaching the emitter's measured output, passive limiter design, and local authorization scheme.
Ranuko
The registry accepts the distinction. It reclassifies the emitter as restricted defensive salvage, not a military-licensed weapon system.
The disputed military designation disappears from the active review pane. The inherited command claim remains archived, but it no longer controls the weapon's legal category.
Lahani
That is a much smaller headache. Support hardware, locally authorized, and documented as recovered property.
Ranuko
I will amend the packet with our non-civilian operating status and the output analysis. No main weapons claim, no remote authority, and no military license required.
The registry issues a provisional defensive-salvage certificate for Amber Wing. Kiryati's emitter remains isolated for calibration, but its ownership and operating category are settled.
✓ Quest Accepted
Close the salvage registry session
“I archive the contest packet, then verify the session is fully closed.”
SUCCESS (Superb Computers, rolled +2)
Nahuli archives the completed contest packet under Amber Wing’s local ownership records, preserving the provenance tree, repair logs, output analysis, and authorization design.
The registry seals the archive with a local timestamp and checksum. The provisional defensive-salvage certificate remains attached, while the inherited command claim is marked inactive.
Ranuko
Archive integrity checks out. The contest packet is read-only, the supporting records are linked, and no external notification was generated.
Nahuli reviews the session ledger from the documentation console: no pending forms, open permissions, transmission queue, or unresolved ownership request remains.
Lahani
Then it is closed properly. Amber Wing keeps the hardware, Avalon has the record, and nothing outside the ship has a route through our systems.
Ranuko
Confirmed. Session terminated, archive locked, assistant access excluded, and the weapons registry is awaiting only ordinary calibration updates.
The console returns to its quiet maintenance screen. The legal dispute is archived, the review session is fully closed, and the repaired salvage remains under Amber Wing’s local control.
Quest Complete
Close the salvage registry session