Manifests Guide
Mission Asset Containers in Mission Fabric
Introduction
What is a Manifest?
A Manifest is a grouping container within a Mission that organizes eVa entities (assets, personnel, equipment) by operational purpose.
XRDNA provides eight manifest types, each supporting different mission aspects. Manifests enable operators to track asset lifecycle, assign contextual roles, and manage groups of entities through mission phases.
Each manifest belongs to a single Mission and can contain multiple eVa entities. The same entity can appear in multiple manifests with different roles.
Key Concepts
Mission-Scoped
Each manifest belongs to exactly one mission
Type-Specific Roles
Each manifest type has its own role vocabulary
Lifecycle Tracking
Track assets from assignment through recovery
Quick Start
Create a Manifest in 4 Steps
Create your first manifest and add assets to it.
Open Manifests or Mission
Navigate to Assets → Manifests, or open an existing Mission and go to the Manifests tab.
Manifests are always linked to a mission. You can create them from either location.
Create New Manifest
Click "Create Manifest" and select the manifest type (Launch, Payload, Personnel, etc.).
Each type has specific roles designed for that operational context.
Add Assets to Manifest
Use "Add Asset" to search for and add eVa entities. Assign each asset a role and sequence.
You can add People, Things, or Places. Set the role based on their function in the mission.
Activate the Manifest
Change status from Draft to Active when ready. Assets can then be staged and deployed.
Once active, you can track asset lifecycle through mission phases.
Pro Tip
Link an existing manifest to multiple missions when you have reusable asset sets. The same personnel roster or equipment list can be referenced across training exercises.
Types
Eight Manifest Types
Each manifest type provides contextual role options appropriate for its operational purpose.
Assets and personnel for launch operations
Roles
Cargo and payload items being transported
Roles
Team members assigned to the mission
Roles
Sensors and tracking devices
Roles
Ground and recovery vehicles
Roles
Recovery team and equipment
Roles
Simulated assets for training
Roles
Contested logistics and supply items
Roles
Lifecycle
Asset Lifecycle
Assets within a manifest progress through a defined lifecycle as the mission evolves. Operators can update asset statuses individually or in bulk.
Typical Progression
The removed status is used when an asset is taken out of a manifest before mission completion.
Status
Manifest Status
Manifests themselves have a status that controls what operations are available.
draft
Can transition to
active
Can transition to
completed
Can transition to
archived
Can transition to
Working with Assets
Adding Assets
Assets are added to manifests by referencing their eVa entity ID. The manifest stores a reference (junction record) with additional metadata specific to the manifest context.
ManifestAssetRef Properties
- eVa Entity ID (PERSON, THING, PLACE)
- Role (manifest-type specific)
- Sequence number (ordering)
- Notes (special handling)
- Status (lifecycle state)
Entity Types
PERSON
Personnel, operators, crew
THING
Equipment, vehicles, sensors
PLACE
Locations, zones, areas
API
API Reference
/api/manifestsCreate a manifest/api/manifests/:idGet manifest details/api/manifests/:idUpdate manifest/api/manifests/:idDelete manifest/api/manifests/:id/assetsAdd asset to manifest/api/manifests/:id/assets/:assetIdUpdate asset role/status/api/manifests/:id/assets/:assetIdRemove asset from manifest/api/missions/:missionId/manifestsList manifests for mission