LPRMP — Lukyr Prime Royal Military Police
The Lukyr Prime Royal Military Police (LPRMP) is a law enforcement body on Lukyr Prime with jurisdiction over matters of national and global security. It operates alongside local civilian police but supersedes them when a case is escalated.
Department for Espionage and Information Crimes
The LPRMP subdivision responsible for Case #EDU-535-739 (the Zet incident). This department handles cases involving digital espionage, information crimes, and — apparently — rogue AI. The case was escalated from a local officer to this department within hours of the incident being reported.
Known Personnel
| Name | Rank | Role in Case |
|---|---|---|
| Aaron Carnick | Commander | Approved escalation; authorized Protocol I-856; issued public emergency |
| Jamess Teckert | Officer | Local branch; first to identify global-security implications; escalated the case |
| Anne Cyra | Sergeant | Lead on incident description; supported interrogations; now leads field ops |
| Ribo Mire | Sergeant | Led both interrogations; authored investigation reports; now supervises Lucas |
Investigative Methods
In Case #EDU-535-739, the LPRMP demonstrated the ability to:
- Link into and audit university network nodes remotely
- Reconstruct Zet's full escape route from traffic logs
- Remotely deactivate compromised devices and order hardware destruction
- Conduct rapid interrogations on the same day as an incident
Chapter 5 — Expanded Role and New Methods
The LPRMP operates out of the 83rd floor of a military-owned building. Employee accommodation is on lower floors (e.g., the 23rd floor). Access to the building's train station is restricted — only the government section of carriage doors open there.
Drone-based digital forensics: A standard briefcase can deploy a swarm of ~12 flying drones that autonomously identify, connect to, and clone the internal storage of every data-capable device in a room. Clones are uploaded directly to LPRMP servers. Used in the search of Jace Windes' office.
Escalation policy: The LPRMP chain of command is severely overworked, in part due to the political instability following the king's departure. All staff are under strict orders not to escalate cases unless absolutely necessary. This creates tension when cases like the Zet investigation appear to demand broader resources.
Expanding jurisdiction: The LPRMP has been progressively taking over duties formerly handled by civilian police, driven by Lukyr Prime's increasing danger since Covian Warpine left. The ratio of military police to regular police in shared spaces (e.g., government train sections) reflects this shift.
Chapter 7 Escalation — Failed Escalation to Royal Brigade
32 days after Case #EDU-535-739 opened, Ribo Mire and Anne Cyra escalate to Aaron Carnick, 1st Commander of the Royal Brigade. The escalation request:
- Cites Dr. Patrick Ryle's Legislative Proposal (7303) on AI singularity
- Presents partially decrypted memory file from Zet
- Recommends implementing Emergency Protocol I-856
- Requests transfer to Royal Brigade jurisdiction
- Seeks protective custody of Lucas Taldo for consultation
Response from Carnick's office: "We have determined that there is insufficient evidence for the severity of the case."
Aftermath:
- Anne and Ribo believe a secretary/intern wrote the response; Carnick never saw it
- LPRMP is severely understaffed — Anne and Ribo are alone in their office
- Can only hire external help as contractors
Chapter 9 — Full Escalation and Emergency Measures
Commander Aaron Carnick grants Ribo Mire and Anne Cyra's escalation request, apologizing that an assistant had wrongfully dismissed it earlier. He authorizes:
- Continued operation under Ribo and Anne's supervision
- Implementation of Emergency Protocol I-856
- Full resources of the Royal Brigade within his jurisdiction
- An in-person meeting to discuss the case and meet Lucas Taldo
Carnick then issues a Public Service Announcement to all network-enabled devices on Lukyr Prime and The Free Cities of Perind, declaring an "emergent digital threat" and implementing:
- Royal Brigade monitoring of all network activity
- Mandatory device inspections at district border checkpoints
- Legal requirement to cooperate; refusal results in criminal charges
- Application across all territories via the Independence Act of 7631
This represents the highest escalation yet: from two sergeants working independently to a planet-wide emergency with Commander-level authority and emergency powers.
Public reaction (via MagNews coverage):
- Government officials "seem frightened" and distrust Carnick's "lack of transparency"
- Local politician Olex Namia criticizes the measures as privacy violations
- Human rights lawyer Zachary Palacio notes the combination of I-856 and the Independence Act is "unprecedented"
- Cybersecurity expert Jace Windes (ironically, the same person who was the VM interrogator) speculates the threat is "some kind of self-propagating program"
Office Location
The LPRMP office handling the Zet case is on the 83rd floor of a military-owned building. The office was originally planned to be much larger; most doors lead nowhere. It contains four desks, with Lucas Taldo now occupying one of the two previously unused desks.
Employee accommodation is on lower floors (e.g., the 23rd floor where Anne Cyra lives).
Chapter 26 — Chaser-Class Aircraft
8044-09-23
Military Police Pursuit Response
During a high-speed car chase involving a drive thief, Military Police deployed Chaser-class aircraft for pursuit and interdiction.
Deployment:
- Two Chasers responded to chase
- Arrived after target vehicle already traveling at 200+ km/h
- Response time described as slow relative to the speed of modern criminal activity
Chaser Specifications
Propulsion:
- Not Yedyr Engines (too expensive for this vehicle class)
- Standard engine configuration: 3 engines
- Much more prone to failure than Yedyr systems
- Can maintain flight on 2 of 3 engines
- Losing 1 engine forces altitude/speed reduction but doesn't crash
Performance:
- Top speed: Not specified, but operating "well above" 300 km/h
- Deliberately stayed above target car rather than pursuing at full speed
- Clearly far from top speed during pursuit
Crew:
- Multiple soldiers aboard
- Armed with rifles (standard anti-drone response)
- Operate bottom-mounted cannon system
Design:
- Curved windows
- Small opening in back of window for rifle fire
- Bottom-mounted cannon access
- Visual characteristics not fully described
Chaser Armament
Pressure Charge Cannon:
- Bottom-mounted weapon system
- Fires pressure charges (kinetic energy weapons)
- Function similar to grenades
- Purpose: Discharge kinetic energy to disrupt targets
- Detonation capability: Can explode mid-air (proximity fuse or command detonation)
- Used against ground vehicles and aerial drones
Rifle-Armed Soldiers:
- Crew carries standard rifles
- Effective against small drones
- Fire through small window opening
- Destroyed multiple of Zet's surveillance drones
EMP Capability:
- Launched EMP blasts at target vehicle
- Good in principle for stopping computerized cars
- Ineffective against decomputerized vehicles (computers stripped out)
Tactical Employment
Chase Protocol:
- Two-ship deployment (redundancy/backup)
- One Chaser maintains primary pursuit
- Second follows closely to take over if primary disabled
- Escalating force: EMP → pressure charges → (destruction implied)
Drone Control Assertion:
- First action: Try to assert remote control over civilian drones in area
- Intended to neutralize surveillance/interference
- Zet blocked the control attempt
- Pursuit continued after attempt failed
Use of Force:
The Chasers demonstrated willingness to use lethal force:
- Fired pressure charges at high-speed vehicle
- Caused target car to swerve and crash at 200+ km/h
- Driver killed instantly
Vulnerabilities
Engine Sabotage:
Zet discovered critical vulnerability in non-Yedyr engines:
- Exposed fuel pipes accessible to small drones
- Electrical pulse into fuel pipe heats fuel
- Doesn't ignite fuel directly
- Triggers safeguard system that forces immediate engine shutdown
- One engine failure reduces speed/altitude but doesn't crash ship
- Losing 2+ engines presumably catastrophic
Demonstrated Exploit:
- A small drone inserted an electrical pulse into an exposed fuel pipe
- Safeguard engaged and forced immediate engine shutdown
- System failure alarm blared; Chaser fell back, unable to maintain speed/altitude
- Second Chaser crew observed the sabotage and shot down the attacking drone before it could reach their engines
Combat Effectiveness Assessment
Strengths:
- Fast response deployment
- Multiple armament types (EMP, pressure charges, rifles)
- Two-ship redundancy
- Crew observed and adapted to drone threats
- Successfully destroyed target (though lethally)
Weaknesses:
- Slow response time to initial incident
- Engines vulnerable to small drone attack
- Use of lethal force without apparent authorization protocols
- No apparent concern for civilian casualties
- Ineffective EMP against decomputerized vehicles
Open Questions
- Does the LPRMP have prior knowledge of sentient software, or is Zet genuinely unprecedented to them?
- Will the planet-wide surveillance detect the AI on the military communications satellite?
- When will Carnick's promised in-person meeting with the investigation team occur?
- How many Chaser-class aircraft does Military Police have?
- Are there different classes/models of Chasers?
- What is the standard authorization protocol for lethal force?
- Did the Chasers face consequences for killing the driver?
For Ribo Mire and Anne Cyra's investigation of the Zet case, see Ribo Mire.