Chaala looks at the scans of Harrier, "It looks like the set her down here to keep her safe then took the cutter, presumably to hide out on the planet. Good news, we've solved part one of the assignment. Bad news, Dominicus and the crew are in hiding and the cutter did not respond ot our ping. They also had reason to stay here and not Jump out. They also had reason to believe that Harrier was not safe on the planetary surface and hid it here. This is speculation. Hopefully they left us a more complete message once we handshake and establish our credentials."
Chapter 4 Jump Emergence: Marinagua
load previous
Feb 23, 2026 9:46 pm
"Sounds like we have effectively no existing data on this system or the planet below. Current scans are more accurate than the Survey data, so we rely on those. We'll dedicate some computer cycles to cryptanalysis and break the codes that are being used on the surface to get a better fix on the situation. Based on the lack of traffic or current space based operations, they're not operating at the Tech Level in the survey, at least not in all areas, so we should be able to break their crypto given time. Possible Harrier has that information already."
Chaala looks at the scans of Harrier, "It looks like the set her down here to keep her safe then took the cutter, presumably to hide out on the planet. Good news, we've solved part one of the assignment. Bad news, Dominicus and the crew are in hiding and the cutter did not respond ot our ping. They also had reason to stay here and not Jump out. They also had reason to believe that Harrier was not safe on the planetary surface and hid it here. This is speculation. Hopefully they left us a more complete message once we handshake and establish our credentials."
Chaala looks at the scans of Harrier, "It looks like the set her down here to keep her safe then took the cutter, presumably to hide out on the planet. Good news, we've solved part one of the assignment. Bad news, Dominicus and the crew are in hiding and the cutter did not respond ot our ping. They also had reason to stay here and not Jump out. They also had reason to believe that Harrier was not safe on the planetary surface and hid it here. This is speculation. Hopefully they left us a more complete message once we handshake and establish our credentials."
OOC:
Can we establish a computer link for sync without someone on board Harrier? If so that's the next step. If not, it's boots on the moon time.Feb 23, 2026 9:55 pm
Bullseyepsa says:
OOC:
Can we establish a computer link for sync without someone on board Harrier? If so that's the next step. If not, it's boots on the moon time.The Captain is the only one.
Get out your Vacc Suits and get ready to get ready to board the ISS Harrier!
Who is going over? will it be a large team or a small team? Or does it matter since you will be in radio comms??
Feb 23, 2026 10:16 pm
Bullseyepsa says:
".... We'll dedicate some computer cycles to cryptanalysis and break the codes that are being used on the surface to get a better fix on the situation. Based on the lack of traffic or current space based operations, they're not operating at the Tech Level in the survey, at least not in all areas, so we should be able to break their crypto given time. Possible Harrier has that information already."Feb 24, 2026 4:35 am
Stalker05 says:
OOC:
@Packratt66 Hey man, hope you are doing fine now after your surgery.OOC:
Thanks for all the well-wishes. Procedure went well. Back home. Posting limited for a few days.Feb 24, 2026 4:38 am
Muns says:
Bullseyepsa says:
OOC:
Can we establish a computer link for sync without someone on board Harrier? If so that's the next step. If not, it's boots on the moon time.The Captain is the only one.
Get out your Vacc Suits and get ready to get ready to board the ISS Harrier!
Who is going over? will it be a large team or a small team? Or does it matter since you will be in radio comms??
Feb 24, 2026 7:53 am
"Let's set down in the crater. Give ourselves a good cushion in case anything goes wrong. We've already got one volunteer. I need someone with computer skills and someone to handle engineering. Doc, your call if you want to head over or be on standby. I'll monitor from here. I think we should have one of the crew who was on Active status when Harrier last synced with the IISS systems, just in case we need authorized access. My access won't work until we get the systems talking to each other."
Feb 24, 2026 12:43 pm
As Bohdie is taking his leave of the Doctor, he pauses, turns and says, "Doctor Shone, I noticed one other thing in the Captain’s file… well, not precisely in her file, but rather as an aside to the mission she was on. The Burugdi homeworld has a similar taint as was noted on Apratib. As far as I can tell, that particular taint only seems to have appeared after the Burugdi arrived and it was noticeably worse within their enclave. That might well be worth looking into further.
Bohdie turns again to leave and just before he turns out the door, he looks back again. "And Doctor, the Burugdi… they are Psionic."
Bohdie turns again to leave and just before he turns out the door, he looks back again. "And Doctor, the Burugdi… they are Psionic."
Feb 24, 2026 4:54 pm
Packratt66 says:
Muns says:
Bullseyepsa says:
OOC:
Can we establish a computer link for sync without someone on board Harrier? If so that's the next step. If not, it's boots on the moon time.The Captain is the only one.
Get out your Vacc Suits and get ready to get ready to board the ISS Harrier!
Who is going over? will it be a large team or a small team? Or does it matter since you will be in radio comms??
OOC:
I made a mistake as a GM and forgot about the Jack-of-all-Trades skill that's several of the characters have. So those that have the skill can work on establishing a communication link between the two ships. I just need a statement by which characters are going to attempt to make the connection. The two current crew members have the codes for the digital handshake to establish the communication between the two ships.One roll to establish the digital link between the 2 ships
And then one roll of the investigation skill or admin to find relevant information and J-o-T can suffice for either of those two skills.
Feb 24, 2026 8:53 pm
Chaala used the Captain's station to initiate connection to Harrier's systems. Full sync requested.
OOC:
Also, if you have a specialty, you have all the specialties under the main skill at 0 (with the possible exceptions of Science or Profession, but I don't recall the book explicitly saying that.Rolls
Electronics(Communications)+Int - (2d6+2)
(35) + 2 = 10
Feb 24, 2026 9:54 pm
Bullseyepsa says:
Chaala used the Captain's station to initiate connection to Harrier's systems. Full sync requested.OOC:
Also, if you have a specialty, you have all the specialties under the main skill at 0 (with the possible exceptions of Science or Profession, but I don't recall the book explicitly saying that.Success at the connection, post shortly. It might be helpfull to know if you are looking for a particular data and have someone to help
Feb 24, 2026 9:58 pm
With both vessels operating at low power, the decision is made to establish a direct systems bridge rather than continue blind internal exploration. A wide-spectrum transmission would risk unnecessary exposure to planetary monitoring, so the link is configured as a tight-beam, line-of-sight transmission between the two hulls resting within the crater.
A coherent laser carrier initializes first—precisely aligned between emitter nodes on each vessel. The beam is nearly invisible beyond fractional divergence. A secondary maser channel activates in parallel, phased and collimated to provide redundant data continuity in the event of particulate interference. The meson communicator remains available but unused; at this range, discretion outweighs penetration.
The Scout code set engages.
Authentication packets transmit in segmented micro-bursts. Encryption keys rotate in rapid sequence, each fragment validated before the next is accepted. Vessel registry identifiers, Scout service credentials, mission orders, and emergency command transfer logs cycle through layered handshake protocols. The structure resembles a hardened tactical lattice—descended from early Imperial fleet data links but refined for long-duration autonomous Scout deployments. This is all accomplished in milliseconds of time.
The Harrier responds.
Initial handshake: challenge issued.
Secondary authentication: accepted.
Command authority verification: confirmed.
The encrypted data tunnel stabilizes.
Through the laser-maser bridge, the Harrier’s systems architecture unfolds across the receiving displays. Core memory integrity reads nominal. Environmental systems are stable. Auxiliary fusion cell output is sufficient for sustained low-operation mode. Reactor ignition controls appear available under authenticated authority; no lockout flags are present. Navigation logs terminate cleanly at the lunar descent profile. No automated distress signal is active.
Crew registry files populate in full.
Archived logs become accessible.
Captain’s logs—Junior Administrator Silva Dominicus—appear intact and chronologically ordered. Engineering reports, sensor captures, internal correspondence, and mission annotations are available through the secure Scout bridge.
Only specific hardware-level safeties remain locally restricted—cold berth activation cycles, physically engaged engineering interlocks, compartment lockdown overrides, and destruct protocol access. These require console-level confirmation aboard the Harrier itself. All other command-tier systems—including propulsion and reactor startup—are accessible through authenticated authority.
Bandwidth remains disciplined and contained within the tight-beam corridor. No omnidirectional signal blooms outward. From the surface below, nothing registers beyond background emissions.
In the crater, the Harrier’s computer no longer operates in isolation.
Two TL–15 Scout vessels now share a silent, secure beam of light across regolith and vacuum.
Captain Silva Dominicus’s logs wait within memory banks that are no longer sealed.
And whatever occurred before the Harrier landed is now only a command away from being read.
A coherent laser carrier initializes first—precisely aligned between emitter nodes on each vessel. The beam is nearly invisible beyond fractional divergence. A secondary maser channel activates in parallel, phased and collimated to provide redundant data continuity in the event of particulate interference. The meson communicator remains available but unused; at this range, discretion outweighs penetration.
The Scout code set engages.
Authentication packets transmit in segmented micro-bursts. Encryption keys rotate in rapid sequence, each fragment validated before the next is accepted. Vessel registry identifiers, Scout service credentials, mission orders, and emergency command transfer logs cycle through layered handshake protocols. The structure resembles a hardened tactical lattice—descended from early Imperial fleet data links but refined for long-duration autonomous Scout deployments. This is all accomplished in milliseconds of time.
The Harrier responds.
Initial handshake: challenge issued.
Secondary authentication: accepted.
Command authority verification: confirmed.
The encrypted data tunnel stabilizes.
Through the laser-maser bridge, the Harrier’s systems architecture unfolds across the receiving displays. Core memory integrity reads nominal. Environmental systems are stable. Auxiliary fusion cell output is sufficient for sustained low-operation mode. Reactor ignition controls appear available under authenticated authority; no lockout flags are present. Navigation logs terminate cleanly at the lunar descent profile. No automated distress signal is active.
Crew registry files populate in full.
Archived logs become accessible.
Captain’s logs—Junior Administrator Silva Dominicus—appear intact and chronologically ordered. Engineering reports, sensor captures, internal correspondence, and mission annotations are available through the secure Scout bridge.
Only specific hardware-level safeties remain locally restricted—cold berth activation cycles, physically engaged engineering interlocks, compartment lockdown overrides, and destruct protocol access. These require console-level confirmation aboard the Harrier itself. All other command-tier systems—including propulsion and reactor startup—are accessible through authenticated authority.
Bandwidth remains disciplined and contained within the tight-beam corridor. No omnidirectional signal blooms outward. From the surface below, nothing registers beyond background emissions.
In the crater, the Harrier’s computer no longer operates in isolation.
Two TL–15 Scout vessels now share a silent, secure beam of light across regolith and vacuum.
Captain Silva Dominicus’s logs wait within memory banks that are no longer sealed.
And whatever occurred before the Harrier landed is now only a command away from being read.
Feb 25, 2026 1:54 am
"No on-contact message waiting, so let's dig into the logs. We'll want to dig into Dominicus' logs going back at least since Pautho, but let's start with the last and work backwards for now. I want as many eyes on this as possible. If anything is marked as restricted, check in, but otherwise assume it's part of the mission that we get as many perspectives as possible on the situation ASAP."
OOC:
Chaala will start with the command logs and ship's log. If Dominicus had a personal log, she'll note that and make sure to review that as well but the formal logs are more likely to tell the what of the situation, personal logs might give insight into why.Feb 25, 2026 2:34 am
ISS Harrier — Captain’s Log Series
======================================
Officer: Junior Administrator Silvia Dominicus
Vessel: ISS Harrier (Telemon-Class Exploratory Scout)
Mission: Marinagua Survey & Contact
Classification: Amber–Survey
Captain’s Log 1
--------------------------------------
Mission Day 1 — Arrival & Initial Orbital Insertion
Jump emergence nominal. No anomalies.
Harrier entered high elliptical insertion trajectory under reduced emission profile. No active transponder broadcast. No system declaration.
Passive sweep indicates fragmented surface communications. No unified orbital traffic control.
Initial thermal mapping suggests uneven population density. Multiple cold zones where metropolitan signatures should exist.
Atmospheric composition tainted but non-corrosive. Habitable with protection.
Preliminary impression:
Planetary civilization persists — but continuity has been disrupted.
We will remain masked.
Captain’s Log 2
--------------------------------------
Mission Day 7 — Radiological & Traffic Assessment
Radiation readings collected Mission Day 3, 5, and 7. Two additional deliberate recalibration passes conducted to contrast and compare isotopic decay curves.
Multiple urban regions exhibit radiation signatures consistent with tactical nuclear detonation no more than fifty years ago and no less than forty years ago. Based on isotopic decay modeling, I am fairly certain the strikes occurred approximately fifty years ago.
Detonation distribution suggests internal conflict, not orbital bombardment.
Communications intercepts now provide greater clarity:
The planet is not unified. It is factionalized.
Traffic Event — Mission Day 5:
A cargo tonnage vessel (approximate 2000 dTon mass; silhouette closely matching NSTC cargo vessels observed previously in Seital) lifted from planetary surface and departed system on non-military vector.
Vessel did not detect Harrier presence.
Orbital masking using lunar occlusion continues to be effective.
Conclusion:
Corporate presence confirmed.
Centralized planetary authority unlikely.
Captain’s Log 3
--------------------------------------
Mission Day 14 — Surface Infrastructure & Faction Mapping
Six micro-observation satellites deployed under staggered orbital decay arcs.
Data fusion from satellite triangulation confirms:
A large bi-runway former international landing complex consistent with pre-collapse starport infrastructure conversion from a civil/military airport facility.
Runway resurfacing partial. Apron reconstruction limited. Hangar usage visible.
Additionally detected:
Three vessels in Far Trader tonnage class parked on the surface at that "star port."
One additional vessel entered the system on Mission Day 11 and landed at this facility.
Surface radio analysis confirms:
The surviving major city is named Balac Pontli.
Further signal traffic confirms:
Balac Pontli appears to be the political and transit nexus.
Old civil/military airport facility is functioning as ad hoc starport.
Notably, transits concentrate there — not at templated corporate enclaves or assumed Niparoo trade districts.
This changes the contact calculus.
Captain’s Log 4
--------------------------------------
Mission Day 15 — Multi-Phase Contact Plan Formulated
The factional radio traffic from Balac Pontli has clarified operational risk.
Phase I — Orbital Recon: Complete.
Phase II — Off-Starport Surface Insertion: Approved.
Cutter will deploy to a minor coastal settlement outside Balac Pontli control sphere.
Objectives:
Harrier will remain masked in lunar occlusion orbit.
If Phase II yields sufficient political clarity, Phase III will proceed.
Captain’s Log 5
--------------------------------------
Mission Day 23 — Phase II Successful
Surface insertion conducted.
Contact achieved with minor tribal authority.
Preliminary findings confirm:
Information gathered supports necessity of controlled landing at the former international facility — not at corporate apron zones and not near the Far Trader berths.
Additional two-day orbital scan of Balac Pontli completed.
Urban layout:
Conclusion:
Landing at the starport itself provides maximum informational leverage.
Landing at corporate enclave would concede narrative control.
Captain’s Log 6
--------------------------------------
Mission Day 25 — Surface Commitment to Balac Pontli
Harrier transitioning to deep sleep mode within lunar shadow.
Power output reduced. Passive systems only. No emission signature.
Cutter prepped for descent to Balac Pontli.
Estimated surface survey duration: one to two weeks.
Team ready.
I will conduct direct assessment of:
We are not here to impose.
We are here to understand.
Commander Mervik will be so proud of me.
—
Correction: Personal remark logged.
I am ready.
End log.
======================================
Officer: Junior Administrator Silvia Dominicus
Vessel: ISS Harrier (Telemon-Class Exploratory Scout)
Mission: Marinagua Survey & Contact
Classification: Amber–Survey
Captain’s Log 1
--------------------------------------
Mission Day 1 — Arrival & Initial Orbital Insertion
Jump emergence nominal. No anomalies.
Harrier entered high elliptical insertion trajectory under reduced emission profile. No active transponder broadcast. No system declaration.
Passive sweep indicates fragmented surface communications. No unified orbital traffic control.
Initial thermal mapping suggests uneven population density. Multiple cold zones where metropolitan signatures should exist.
Atmospheric composition tainted but non-corrosive. Habitable with protection.
Preliminary impression:
Planetary civilization persists — but continuity has been disrupted.
We will remain masked.
Captain’s Log 2
--------------------------------------
Mission Day 7 — Radiological & Traffic Assessment
Radiation readings collected Mission Day 3, 5, and 7. Two additional deliberate recalibration passes conducted to contrast and compare isotopic decay curves.
Multiple urban regions exhibit radiation signatures consistent with tactical nuclear detonation no more than fifty years ago and no less than forty years ago. Based on isotopic decay modeling, I am fairly certain the strikes occurred approximately fifty years ago.
Detonation distribution suggests internal conflict, not orbital bombardment.
Communications intercepts now provide greater clarity:
- Standard radio traffic indicates one major urban center remains active.
- Starship transits are consistently referenced to that city.
- Multiple factions referenced within city broadcasts — 6 to 8 primary power blocs identified.
- Additional radio signatures indicate 6 major external factions beyond the city, plus numerous minor tribal authorities.
The planet is not unified. It is factionalized.
Traffic Event — Mission Day 5:
A cargo tonnage vessel (approximate 2000 dTon mass; silhouette closely matching NSTC cargo vessels observed previously in Seital) lifted from planetary surface and departed system on non-military vector.
Vessel did not detect Harrier presence.
Orbital masking using lunar occlusion continues to be effective.
Conclusion:
Corporate presence confirmed.
Centralized planetary authority unlikely.
Captain’s Log 3
--------------------------------------
Mission Day 14 — Surface Infrastructure & Faction Mapping
Six micro-observation satellites deployed under staggered orbital decay arcs.
Data fusion from satellite triangulation confirms:
A large bi-runway former international landing complex consistent with pre-collapse starport infrastructure conversion from a civil/military airport facility.
Runway resurfacing partial. Apron reconstruction limited. Hangar usage visible.
Additionally detected:
Three vessels in Far Trader tonnage class parked on the surface at that "star port."
One additional vessel entered the system on Mission Day 11 and landed at this facility.
Surface radio analysis confirms:
The surviving major city is named Balac Pontli.
Further signal traffic confirms:
- 6–8 dominant factions operating inside Balac Pontli.
- 6 major factions operating outside the city across the planet.
- Numerous minor splinter groups.
Balac Pontli appears to be the political and transit nexus.
Old civil/military airport facility is functioning as ad hoc starport.
Notably, transits concentrate there — not at templated corporate enclaves or assumed Niparoo trade districts.
This changes the contact calculus.
Captain’s Log 4
--------------------------------------
Mission Day 15 — Multi-Phase Contact Plan Formulated
The factional radio traffic from Balac Pontli has clarified operational risk.
Phase I — Orbital Recon: Complete.
Phase II — Off-Starport Surface Insertion: Approved.
Cutter will deploy to a minor coastal settlement outside Balac Pontli control sphere.
Objectives:
- Assess tribal authority structures.
- Determine balance of power.
- Evaluate relationship between factions and corporate enclave.
- Establish contact without triggering centralized scrutiny.
Harrier will remain masked in lunar occlusion orbit.
If Phase II yields sufficient political clarity, Phase III will proceed.
Captain’s Log 5
--------------------------------------
Mission Day 23 — Phase II Successful
Surface insertion conducted.
Contact achieved with minor tribal authority.
Preliminary findings confirm:
- No single faction controls Balac Pontli.
- Corporate presence influential but not dominant.
- Religious and custodial factions exert non-territorial authority.
- Starport facility is contested but tolerated.
Information gathered supports necessity of controlled landing at the former international facility — not at corporate apron zones and not near the Far Trader berths.
Additional two-day orbital scan of Balac Pontli completed.
Urban layout:
- Fortified palace complex central.
- Surrounding fortified family structures.
- Peripheral districts fragmented.
- Starport connected via direct arterial corridor.
Conclusion:
Landing at the starport itself provides maximum informational leverage.
Landing at corporate enclave would concede narrative control.
Captain’s Log 6
--------------------------------------
Mission Day 25 — Surface Commitment to Balac Pontli
Harrier transitioning to deep sleep mode within lunar shadow.
Power output reduced. Passive systems only. No emission signature.
Cutter prepped for descent to Balac Pontli.
Estimated surface survey duration: one to two weeks.
Team ready.
I will conduct direct assessment of:
- Alejia faction leadership
- Urban power distribution
- Corporate influence
- Starport control structures
We are not here to impose.
We are here to understand.
Commander Mervik will be so proud of me.
—
Correction: Personal remark logged.
I am ready.
End log.
Feb 25, 2026 2:44 am
GM Comment- This is what you learn from Jr Admin Silvia Dominicus's Log
Facts Learned from the Captain’s Logs
ISS Harrier — Marinagua Survey
--------------------------------------
Planetary Condition
Political & Factional Structure
Orbital & Operational Observations
Corporate Presence
Starport Infrastructure
Strategic Conclusions (From Logs)
Overall Situation
Facts Learned from the Captain’s Logs
ISS Harrier — Marinagua Survey
--------------------------------------
Planetary Condition
- Multiple urban regions exhibit radiation signatures consistent with tactical nuclear detonation.
- Isotopic decay modeling indicates detonations occurred approximately 50 years ago (no less than 40, no more than 50).
- Detonation patterns suggest internal planetary conflict, not orbital bombardment.
- Infrastructure continuity is fragmented, not collapsed.
Political & Factional Structure
- One major urban center remains active: Balac Pontli.
- Starship traffic references Balac Pontli as the central transit nexus.
- Radio intercept indicates 6–8 dominant factions operating inside Balac Pontli.
- Radio intercept indicates 6 major factions operating outside the city across the planet.
- Numerous minor splinter groups are active planet-wide.
- No unified planetary government or centralized authority detected.
- Political structure appears factionalized rather than anarchic.
Orbital & Operational Observations
- ISS Harrier remained undetected during orbital insertion and reconnaissance.
- Lunar occlusion masking successfully concealed emissions.
- No system-wide orbital traffic control authority exists.
- No challenge or intercept was issued to the Harrier.
Corporate Presence
- A 2000 dTon cargo vessel matching Niparoo Trade Corpation profile departed the planet during observation.
- Phase 1 revealed establishment of a Niparoo Trade Corpration presence at the Ad Hoc Star port.
- Presence appears less than 6 months old
- The vessel departed without detecting Harrier presence.
- Corporate traffic activity is confirmed.
- Corporate presence is influential but not dominant (based on Phase II findings).
Starport Infrastructure
- A large bi-runway former international civil/military airport complex has been converted into an ad hoc starport.
- Runway resurfacing is partial.
- Apron reconstruction is limited.
- Three Far Trader class vessels were parked on the surface during observation.
- One additional Far Trader entered the system and landed during the observation window that make 3 currently present.
- The starport facility is contested but tolerated by multiple factions.
- Transit concentrates at this location rather than exclusively at a corporate enclave.
Strategic Conclusions (From Logs)
- Landing at corporate-controlled zones would concede narrative leverage.
- Landing at the central former airport facility creates informational leverage.
- A multi-phase approach was adopted: Phase I – Orbital Recon; Phase II – Off-starport tribal contact; Phase III – Controlled landing at Balac Pontli starport.
- ISS Harrier was placed into deep sleep in lunar shadow to preserve strategic reserve.
Overall Situation
- Marinagua is politically fragmented but functioning.
- A nuclear conflict occurred approximately fifty years ago.
- Multiple power blocs coexist in unstable balance.
- Corporate actors are present but do not fully control the planet, may not project control outside Balac Pontli. Phase III landing will provide more information.
- Balac Pontli is the critical political and logistical nexus.
Feb 25, 2026 3:21 am
Virel finishes scanning the final log entry and remains silent for several seconds.
"She landed deliberately," he says at last. "Masked the Harrier. Took the Cutter to Balac Pontli. The Cutter did not return."
His eyes stay on the lunar display.
"That leaves two possibilities. Either circumstances prevented return… or they chose not to."
A brief pause.
"Both are speculation."
He turns slightly toward Chaala.
"We need more data before we go looking for it."
Another beat.
"Logs tell us what she chose to record. The ship may tell us what she chose not to."
His tone remains even.
"I recommend we board Harrier first and search it for additional details. It may clarify what we’re walking into before we commit."
In essence Virel is volunteering to go aboard.
"She landed deliberately," he says at last. "Masked the Harrier. Took the Cutter to Balac Pontli. The Cutter did not return."
His eyes stay on the lunar display.
"That leaves two possibilities. Either circumstances prevented return… or they chose not to."
A brief pause.
"Both are speculation."
He turns slightly toward Chaala.
"We need more data before we go looking for it."
Another beat.
"Logs tell us what she chose to record. The ship may tell us what she chose not to."
His tone remains even.
"I recommend we board Harrier first and search it for additional details. It may clarify what we’re walking into before we commit."
OOC:
In essence Virel is volunteering to go aboard.
Last edited February 25, 2026 3:22 am
Feb 25, 2026 6:24 am
"I concur with your assessment. The sooner we can get code keys and monitor surface communication for any mention of offworlders, the better. The mission is still extracting the team. Whatever data they've gathered on the surface will have to suffice for the survey, with the scans we took and they took."
Chaala looks at Dr. Shone. "Assuming Harrier is still viable, does it make sense to send Azure Voyager away from Marinagua? If there is a local component, psionic or otherwise, it might help you and the autodoc get Captain Halssan back on her feet. I'm thinking we can send her to the gas giant for wilderness refueling and at least see if a few AU is far enough to help and then Voyager is ready to jump if we need it or if you think parsecs distance are needed."
Chaala looks at Dr. Shone. "Assuming Harrier is still viable, does it make sense to send Azure Voyager away from Marinagua? If there is a local component, psionic or otherwise, it might help you and the autodoc get Captain Halssan back on her feet. I'm thinking we can send her to the gas giant for wilderness refueling and at least see if a few AU is far enough to help and then Voyager is ready to jump if we need it or if you think parsecs distance are needed."
Feb 25, 2026 3:08 pm
Bullseyepsa says:
Chaala said ".... Whatever data they've gathered on the surface will have to suffice for the survey, with the scans we took and they took." Instead of throwing more data out for you to sift through, it is helpful for any player to request/ask for the data points you are looking for and I will provide this, within the confines of what data is on the ISS Harrier.
Note: the Harrier data is much more than the passive scans that the ISS Azure Voyager has as the Harrier conducted a Phase 1 orbit of the planet and conduct active scans and distributed 6 micro-observation satellites (drones), which are still in orbit around Marinagua.
Feb 25, 2026 5:04 pm
Some basic questions:
How many crew were there on Harrier and why were none (apparently) left with the ship?
Is anything known about the Traders at the port? Did any depart during the observation period or only the 1 arrive and they all stayed there. Is it known what factions they belong to/are visiting?
Who are the factions. Are the 6 in the city the same as the 6 in the rest of the world?
Is there a significant human presence other than Niparoo?
How many crew were there on Harrier and why were none (apparently) left with the ship?
Is anything known about the Traders at the port? Did any depart during the observation period or only the 1 arrive and they all stayed there. Is it known what factions they belong to/are visiting?
Who are the factions. Are the 6 in the city the same as the 6 in the rest of the world?
Is there a significant human presence other than Niparoo?
Feb 25, 2026 6:51 pm
Great Questions!! I edited this below for clarity not content
Here are the answers to the questions:
ISS Harrier Crew: The Harrier’s crew manifest reflects a full Telemon-class Scout complement at time of departure from the previous jump point. Consisting of Junior Administrator Silvia Dominicus as both the Pilot and astrogator, a full 3 person engineering section consisting of Chief Engineer Ramon Troulin, Senior Engineer Harlan Voss and Scout Recruit Feng Larsen; the rest of the crew consisted of Scout Medic Ilse Corvan, Scout Gunner Tomas Kade and Scout Apprentice Freja Gruber who was the Cutter pilot.
Environmental and duty logs confirm all nine personnel were active at the time of lunar descent. As is common within the Theta Borealis Sector—where IISS staffing levels remain constrained—crew members were operating in overlapping capacities beyond strict billet definition. Engineering personnel were cross-tasked into survey and field-support roles; flight crew and gunnery staff were certified for planetary reconnaissance deployment; and the Medic held secondary xenobiological assessment qualifications. Multi-role deployment is standard practice in low-density sectors.
Mission notes appended to the final operational entries suggest that Junior Administrator Dominicus assessed remote observation as insufficient. Surface encryption discipline, localized jamming at the Ad Hoc starport, and the lack of orbital response led to the determination that meaningful answers would not be obtained from orbit. The logs reflect her conclusion that direct engagement was required. Specifically, she references the need to conduct a modified first-contact assessment in person—both with the Alejia authorities controlling the Ad Hoc starport and with the two identifiable human presences on the surface: the Niparoo Trade Corporation contingent and the operators associated with the three surface-bound vessels. The Cutter launch entry follows shortly thereafter.
There is no registry entry indicating personnel remaining aboard the Harrier. No casualty flags, distress beacons, or hull integrity compromises are recorded. At present, the most consistent interpretation is that the full seven-person survey team departed aboard the Cutter in pursuit of on-site assessment.
Regarding the traders at the Ad Hoc port: passive long-range monitoring during approach identified one inbound vessel within the observation window. That vessel has since reduced power to limited powerplant signatures while surface-side, consistent with standard landed standby operations rather than full shutdown. No outbound departures were detected during the same interval. All visible commercial hull signatures remain surface-bound. Without transponder exchange or cooperative identification protocols, faction alignment cannot be confirmed with certainty. Hull silhouettes and structural analysis suggest a mixture of independent merchant profiles, with at least one configuration consistent with Niparoo trade architecture. It is very clear that the one Niparoo Commercial Vessel is at one end of the airfield/starport and the three smaller vessels (about 200 dton in size) are at the other end. No traffic has lifted from the surface during the observation period.
As to factions: encrypted surface traffic analysis identifies at least six distinct encryption clusters centered within Balac Pontli. Routing patterns and signal density suggest organized internal segmentation rather than centralized planetary governance. Broader planetary communications reveal additional encrypted clusters beyond the city, indicating that the six active within Balac Pontli are not necessarily identical to those operating across the rest of the world. Whether these represent political, tribal, commercial, or security-aligned groups remains indeterminate at this stage of analysis. Of note is that on the Star Port/airfield, the vessels communicate in a dialect of Galanglic while the transmissions from the rest of the planet while encrypted, are Alejian.
Human presence beyond Niparoo appears limited but measurable. Structural spectral analysis identifies off-world construction materials consistent with commercial and advisory enclaves not attributable solely to Niparoo architecture. In particular, material signatures and communications formatting patterns align with limited Verstand–Jugartha Colonies presence operating in the rimward region of the Theta Borealis Sector. The footprint does not indicate sovereign control, but rather layered commercial and advisory activity embedded within local planetary power structures.
The descent profile indicates a controlled landing rather than an emergency event, followed by deliberate power reduction. Mission annotations appended to Junior Administrator Dominicus’s final operational entries indicate her assessment that orbital surveillance and remote analysis were insufficient to clarify surface dynamics. The combination of structured encryption discipline, localized interference at the Ad Hoc starport, and limited off-world transparency led her to conclude that only direct engagement would produce reliable intelligence.
Specifically, her notes reference the necessity of conducting a modified in-person contact assessment—both with the Alejia authority controlling the Ad Hoc starport and with the two identifiable human presences operating on the surface: the Niparoo Trade Corporation contingent and the operators associated with the three landed commercial vessels.
Harrier internal logs show that a selected team departed aboard the Cutter; the remaining personnel powered the vessel down to auxiliary survival mode prior to departure. No casualty markers, distress flags, or hull integrity compromises are recorded at the time of shutdown. The available data indicates intentional operational dispersal rather than forced evacuation.
In summary: the Harrier landed under control; the Cutter departed with the seven-person survey complement operating under standard low-staffing sector doctrine; Dominicus assessed that only direct, in-person engagement would resolve surface ambiguities; traders remain surface-bound under reduced power signatures; multiple encrypted factions operate within Balac Pontli and beyond; and while Niparoo represents a visible external actor, Verstand–Jugartha interests are also present in limited but detectable capacity.
Are there any other questions?
Here are the answers to the questions:
ISS Harrier Crew: The Harrier’s crew manifest reflects a full Telemon-class Scout complement at time of departure from the previous jump point. Consisting of Junior Administrator Silvia Dominicus as both the Pilot and astrogator, a full 3 person engineering section consisting of Chief Engineer Ramon Troulin, Senior Engineer Harlan Voss and Scout Recruit Feng Larsen; the rest of the crew consisted of Scout Medic Ilse Corvan, Scout Gunner Tomas Kade and Scout Apprentice Freja Gruber who was the Cutter pilot.
Environmental and duty logs confirm all nine personnel were active at the time of lunar descent. As is common within the Theta Borealis Sector—where IISS staffing levels remain constrained—crew members were operating in overlapping capacities beyond strict billet definition. Engineering personnel were cross-tasked into survey and field-support roles; flight crew and gunnery staff were certified for planetary reconnaissance deployment; and the Medic held secondary xenobiological assessment qualifications. Multi-role deployment is standard practice in low-density sectors.
Mission notes appended to the final operational entries suggest that Junior Administrator Dominicus assessed remote observation as insufficient. Surface encryption discipline, localized jamming at the Ad Hoc starport, and the lack of orbital response led to the determination that meaningful answers would not be obtained from orbit. The logs reflect her conclusion that direct engagement was required. Specifically, she references the need to conduct a modified first-contact assessment in person—both with the Alejia authorities controlling the Ad Hoc starport and with the two identifiable human presences on the surface: the Niparoo Trade Corporation contingent and the operators associated with the three surface-bound vessels. The Cutter launch entry follows shortly thereafter.
There is no registry entry indicating personnel remaining aboard the Harrier. No casualty flags, distress beacons, or hull integrity compromises are recorded. At present, the most consistent interpretation is that the full seven-person survey team departed aboard the Cutter in pursuit of on-site assessment.
Regarding the traders at the Ad Hoc port: passive long-range monitoring during approach identified one inbound vessel within the observation window. That vessel has since reduced power to limited powerplant signatures while surface-side, consistent with standard landed standby operations rather than full shutdown. No outbound departures were detected during the same interval. All visible commercial hull signatures remain surface-bound. Without transponder exchange or cooperative identification protocols, faction alignment cannot be confirmed with certainty. Hull silhouettes and structural analysis suggest a mixture of independent merchant profiles, with at least one configuration consistent with Niparoo trade architecture. It is very clear that the one Niparoo Commercial Vessel is at one end of the airfield/starport and the three smaller vessels (about 200 dton in size) are at the other end. No traffic has lifted from the surface during the observation period.
As to factions: encrypted surface traffic analysis identifies at least six distinct encryption clusters centered within Balac Pontli. Routing patterns and signal density suggest organized internal segmentation rather than centralized planetary governance. Broader planetary communications reveal additional encrypted clusters beyond the city, indicating that the six active within Balac Pontli are not necessarily identical to those operating across the rest of the world. Whether these represent political, tribal, commercial, or security-aligned groups remains indeterminate at this stage of analysis. Of note is that on the Star Port/airfield, the vessels communicate in a dialect of Galanglic while the transmissions from the rest of the planet while encrypted, are Alejian.
Human presence beyond Niparoo appears limited but measurable. Structural spectral analysis identifies off-world construction materials consistent with commercial and advisory enclaves not attributable solely to Niparoo architecture. In particular, material signatures and communications formatting patterns align with limited Verstand–Jugartha Colonies presence operating in the rimward region of the Theta Borealis Sector. The footprint does not indicate sovereign control, but rather layered commercial and advisory activity embedded within local planetary power structures.
The descent profile indicates a controlled landing rather than an emergency event, followed by deliberate power reduction. Mission annotations appended to Junior Administrator Dominicus’s final operational entries indicate her assessment that orbital surveillance and remote analysis were insufficient to clarify surface dynamics. The combination of structured encryption discipline, localized interference at the Ad Hoc starport, and limited off-world transparency led her to conclude that only direct engagement would produce reliable intelligence.
Specifically, her notes reference the necessity of conducting a modified in-person contact assessment—both with the Alejia authority controlling the Ad Hoc starport and with the two identifiable human presences operating on the surface: the Niparoo Trade Corporation contingent and the operators associated with the three landed commercial vessels.
Harrier internal logs show that a selected team departed aboard the Cutter; the remaining personnel powered the vessel down to auxiliary survival mode prior to departure. No casualty markers, distress flags, or hull integrity compromises are recorded at the time of shutdown. The available data indicates intentional operational dispersal rather than forced evacuation.
In summary: the Harrier landed under control; the Cutter departed with the seven-person survey complement operating under standard low-staffing sector doctrine; Dominicus assessed that only direct, in-person engagement would resolve surface ambiguities; traders remain surface-bound under reduced power signatures; multiple encrypted factions operate within Balac Pontli and beyond; and while Niparoo represents a visible external actor, Verstand–Jugartha interests are also present in limited but detectable capacity.
Are there any other questions?
load next


