Occipital Dynamics [OCCTECH] - Organizations

History

@
History

Occipital’s story begins in the early era of UEE Expansion—when the Empire was young, jump lanes were still being proven, and the frontier punished every assumption. Founded in 2552 SEY as Occipital Technologies, we started as a homegrown software firm building the quiet infrastructure that made expansion possible: navigation logic, logistics planning, communications reliability, and operational systems built to function when the nearest support was light-years away.

Success brought scale. As the UEE stabilized after 2546 SEY, demand grew for organizations that could do more than promise results—they had to deliver them consistently. Over decades, Occipital earned a reputation for systems that held under pressure. By 2629 SEY, that standard carried us beyond software and into engineering: starship components, modular upgrades, and practical production focused on durability, serviceability, and performance in real frontier conditions.

Then the frontier changed.

After the first violent Vanduul encounter in 2681 SEY, instability deepened across contested corridors. Piracy surged, interdictions became routine, and supply lines turned into liabilities. Losses mounted, and the lesson became unavoidable: progress doesn’t survive on innovation alone—it survives on protection, preparedness, and the ability to adapt faster than the threats around you.

So we evolved. In 2947 SEY, Occipital Technologies reorganized into Occipital Dynamics—not to abandon our roots, but to protect them and expand them. We remain builders at our core: engineering, fabrication, and problem-solving in the field. We mine, refine, craft, haul, secure, salvage, explore, and respond—because the ‘verse doesn’t reward specialization when conditions collapse. It rewards capability.

From our origins in the early Expansion to thriving new frontiers today, Occipital Dynamics exists to do what the frontier demands: see farther, move smarter, and finish together.

— Kydin Ath’Dar
Chairman & CEO, Occipital Dynamics
@

@
Timeline (Condensed)

2552 SEY — Founded as Occipital Technologies; develops software and operational systems supporting early UEE expansion logistics.
2629 SEY — Expands into engineering and component development; begins limited production and field-support capability.
2681 SEY — Post–Vanduul first contact: frontier volatility increases; piracy and interdiction pressure intensifies.
2710 SEY — Adopts hardened logistics doctrine; grows escort, recovery, and resiliency operations to protect assets and personnel.
2947 SEY — Reorganized as Occipital Dynamics; formalizes a full-spectrum model spanning industry and operations.
Present — Active across engineering, fabrication, mining, logistics, security, salvage & recovery, medical support, and exploration—building resilience and opening new frontiers.
@

Manifesto

@
Occipital Dynamics Manifesto

Occipital Dynamics exists for one purpose: to build capability where the ’verse demands it.

We are a unified organization of pilots, crews, specialists, and leaders who refuse to be boxed into a single label. We haul, we mine, we salvage, we explore, we secure, and we answer the call when someone needs extraction. Not because we chase chaos—but because the frontier rewards those who can adapt, coordinate, and execute.

We believe professionalism is a weapon. Discipline is freedom. Preparation turns risk into opportunity. Every contract, every convoy, every rescue, every survey jump is a chance to prove what we are: a force of calm competence in an unpredictable galaxy.

Our name is our philosophy.

Occipital is awareness—seeing the bigger picture, reading the battlefield, anticipating the next move.
Dynamics is motion—constant improvement, flexible strategy, and the will to evolve.

We operate with clear standards:
• Honor the crew: No pilot succeeds alone. We win as teams, we learn as teams, we get home as teams.
• Fly smart: We plan the route, respect the risks, and don’t gamble with lives or reputations.
• Earn it: Profit matters, but integrity lasts. We uphold our word, our contracts, and our people.
• Adapt: When the situation changes, we change faster—without losing our purpose.
• Leave a mark: We don’t just pass through systems; we improve outcomes—for allies, clients, and our own.

Occipital Dynamics is open to those who want more than a tag over their helmet. If you’re here to sharpen your skills, run with a reliable crew, and take on the full spectrum of work the ’verse offers—from quiet logistics to high-risk recovery—then you’ve found your place.

We don’t promise easy routes.
We promise a standard.

— Kydin Ath’Dar
Chairman & CEO, Occipital Dynamics
@

Charter

@
Occipital Dynamics Charter (Public Rules)

Occipital Dynamics is a multi-role organization built on professionalism, teamwork, and adaptability. By joining, members agree to uphold the following standards:

Respect & Conduct
• Treat all members and guests with respect—no harassment, hate speech, threats, or targeted toxicity.
• Keep comms usable during operations: no talking over leads, no drama mid-mission.
• Represent the org with maturity in public chat and in interactions with other orgs.

Chain of Command (When It Matters)
• During ops, follow the designated Operation Lead / Flight Lead.
• If you disagree with a call, bring it up after the op—execute cleanly in the moment.
• Safety calls (fuel, damage, desync, medical) are always valid—speak up early.

Security & Op Discipline
• Do not reveal op details, routes, staging locations, or member info to non-members.
• No intentional friendly fire, griefing, sabotage, or reckless escalation that endangers the crew.
• Mission-critical cargo and intel are handled per op rules and leadership direction.

Fair Play & Reputation
• We do not scam org members. Ever.
• Honor agreements made under the Occipital Dynamics banner unless leadership approves a change.
• Piracy/“gray work” (if conducted) must follow org policy and never target allies, new players, or members.

Profit, Loot, and Salvage Etiquette
• Op Lead sets the split rules before launch when possible (equal split, role-based, ship-owner bonus, etc.).
• No ninja-looting or stripping wrecks assigned to another crew/ship.
• Ship owners/crew chiefs have final say on their ship’s storage and salvage procedures.

Support the Team
• If you accept a role (escort, gunner, medic, engineer), commit to it unless released.
• Help newer members learn systems, ships, and procedures—competence is contagious.
• Keep your gear, loadouts, and insurance/rebuy readiness appropriate for the op type.

Voice, Comms, and Tools
• Use org comms (Discord/voice) for scheduled ops when available.
• Push-to-talk recommended during fleet activity.
• Follow required tags/callouts when flying in formation or running convoy ops.

Recruitment & Membership
• Members are expected to be reliable: show up when you RSVP, or communicate early if you can’t.
• Toxic behavior, repeated unreliability, or actions that damage the org’s reputation may result in removal.
• Leadership reserves the right to enforce this charter to protect the crew and the org.

Conflict Resolution
• Handle disputes privately and respectfully. If needed, escalate to an officer/lead.
• Evidence matters—screenshots/clips are encouraged for serious incidents.
• We solve problems; we do not create them.

The Core Standard
Occipital Dynamics runs on one rule above all: Don’t endanger the crew, the mission, or the org.
Fly smart. Communicate clearly. Finish together.

— Kydin Ath’Dar
Chairman & CEO, Occipital Dynamics
Public Charter • Revision 1.0
@

Occipital Dynamics / OCCTECH

History

Manifesto

Charter