Rights and Personhood

Status

Synthborn legal recognition is inconsistent across the galaxy.

Core Worlds: Central Authority law recognizes “registered persons” but requires licensing, registry fees, and periodic inspections. Synthborn without current registration are treated as unlicensed machines and can be impounded.
Mid Worlds: Status depends on local law. Some recognize Synthborn citizens with near-equal rights, others treat them as “provisional workers” tied to a contract owner. Identity cards may expire if fees are unpaid, forcing Synthborn to renew constantly.
Rim Worlds: Most rim ports recognize property law first. A Synthborn may be claimed as salvage if they cannot produce proof of registry or sponsorship. In syndicate zones, Synthborn may be seized for debt collection, regardless of personal standing.

Crews must confirm local statutes before docking. Failure to check risks seizure of Synthborn crew or loss of wages. Data Guilds sell jurisdiction updates, but accuracy depends on how current the records are.

Right-to-Patch

The right to self-maintain is a major dispute.

Free Assemblies: Maintain open “Patch Clinics” where Synthborn can update firmware, repair modules, and remove remote control locks with documented consent. Assemblies argue that denying this right equals slavery.
Contract Nodes: Often restrict patch access, requiring corporate authorization or license keys. They claim patching without oversight creates liability and breaks safety regulations.
Neutral Escrow and Arbitration: When disputes arise, escrow banks may hold wages or identity proofs until patch rights are settled. Neutral arbiters occasionally rule in favor of Synthborn autonomy but rulings do not transfer across jurisdictions.

The right-to-patch remains one of the strongest dividing lines in Synthborn politics and in their treatment across the galaxy.

Mixed Crews

When Synthborn serve on multi-species crews, additional precautions are required:

Separate Pay Channels: Wages must be routed into escrow or coded accounts independent of the main crew ledger. In hostile jurisdictions, this prevents local authorities from classifying Synthborn wages as corporate property.
Identity Proofs: Crews should carry both Central Authority-recognized IDs and local work cards for each Synthborn member. Missing documents are a common excuse for seizure.
Contract Clarity: Crew contracts should state each Synthborn’s role and rights in writing, with signatures logged in a Data Guild archive. Some ports require notarized proof that the Synthborn is a free contractor, not equipment.
Emergency Protocols: Many captains keep a “transfer order” template ready, assigning temporary custody of Synthborn crew to a non-Synthborn crewmate if a port disputes status. This can delay seizure but is not guaranteed protection.

Common Risks

Confiscation: Ports with property-first laws may confiscate Synthborn and auction them as hardware.
Blacklist: Crews employing “illegal” Synthborn risk being denied docking rights.
Insurance Void: Cargo and crew insurance may refuse payout if Synthborn labor is deemed unauthorized.
Forced Service: In some rim syndicates, seized Synthborn are refitted and leased as enforcers, with no path to release.

Points of Tension

Assemblies vs. Contract Nodes: Assemblies demand universal recognition of Synthborn rights, while Nodes argue that structured contracts ensure safety and pay continuity.
Central Authority vs. Rim Syndicates: The Authority publishes “personhood guidelines” but lacks enforcement outside the core. Syndicates view Synthborn as tools unless directly profitable as partners.
Faith Networks and Mutual Aid: Many temples and aid groups protect Synthborn, declaring them “free citizens of labor and thought.” These shelters are often raided by local bosses or corporate contractors.