Standard Operating Procedure // Protocol

SCA Protocol // Matrix

Comprehensive guide to the Shared Crew Access architecture. Learn how to seamlessly share a Mission (Campaign) between a Game Master (Referee) and multiple players in a fully collaborative environment.

Protocol Version 4.2 // SCA Hardened

Architectural Overview

The Shared Crew Access (SCA) Protocol is a high-level operational matrix designed to eliminate hardbound constraints on personnel assignment. Its primary function is to share a Mission (Campaign) between a Game Master (Referee) and multiple players in a fully collaborative environment. By tearing down structural silos, SCA enables rapid, frictionless redeployment of certified crew members across distinct Assets and operations within the same collaborative matrix.

Cross-Deployment

Phase: MECHANICS

Traditionally, personnel assigned to an Asset were rigidly tethered. The SCA Protocol introduces an abstraction layer allowing personnel, designated as is_shared, to break free from localized limitations:

» Pool Elevation: Once authenticated by the Master, a crew member is elevated to a globally accessible pool within campaign parameters.
» Instant Transfer: A Master can select any crew member with SCA clearance and immediately re-assign them to a secondary Asset within the fleet.
» Zero-latency: Data streams—covering salaries, skill matrices, and deployment history—are synced instantaneously across the holo-console.

Security & Visibility

Phase: AUTHORIZATION

Shared access does not bypass master-level security frameworks. It enforces a strict containment field based on explicit campaign signatures.

» Campaign Integrity: Personnel are only exposed to assets explicitly sharing the corresponding campaign signatures.
» Shielded Modes: Crew members lacking the is_shared flag remain strictly locked and shielded behind their primary Asset's sub-matrix.

SECURITY ADVISORY: Tampering with the `is_shared` flag outside of Master-Only controls will result in terminal de-sync.

Personnel Invite

Phase: ESTABLISH

The SCA matrix requires a valid Invite Code for players to join a mission. Masters can manage these codes via the Mission Details interface:

» Code Generation: Missions created after v3.8 auto-generate codes. For legacy dockets, use the Generate Code function.
» Secure Sharing: Codes are strictly classified. Share them only with authorized crew members to allow them to bind their matrix to the campaign.

Operative Roles

Phase: DELEGATION

Nav-Fi³ distinguishes between Structural Ownership and Operative Authority. Crew members can be granted granular access to ship subsystems:

SCA Pilot

Authorized to manage waypoints and execute J-Sync jumps.

SCA Cargo

Full access to cargo hold, loot management, and market trade.

SCA Finance

Permission to register costs and incomes on asset ledgers.

Note: Captains automatically inherit all SCA permissions for their assigned asset.

Protocol Sync

Phase: BACKGROUND

The SCA protocol integrates autonomously with the backend systems of Nav-Fi³, ensuring your Ledger and Mission parameters remain synchronized across the distributed matrix.

Beacon // Dock Ready