Learn Vantage.
One discovery at a time.

A Windows computer and an approved Vantage release.

1. Open the Download page. Download the signed Windows beta installer. An account or subscription does not itself install the application.
2. Check the requirements, version and release notes supplied with that release. Keep an existing workspace backup before changing installations.
3. Open Seraph Vantage. Choose or create a Multirotor project from the project selector. Fixed-wing, rocket and balloon projects are not supported.
4. Open Preferences and choose your appearance and units. You can explore System, Aircraft and local Controls studies without connecting an aircraft.

Vantage opens with a selected drone project. You know which release you are using.

Check About & updates for the installed version. A local update check compares installed release folders; it is not an online update service.

Access to your email inbox.

1. Open Create account and enter your email and a password of at least ten characters. Account creation is free.
2. Submit once, then follow the confirmation email if confirmation is requested. Open the most recent link; an older link may have expired.
3. Sign in on the website. In the desktop application, open the account controls in Settings and sign in with the same email.
4. Check your account and package access. Buying the beta subscription is a separate checkout action. Free registration does not start a paid subscription.

Your website and desktop sessions use the same account identity.

If no confirmation email arrives, check spam and the email spelling. If delivery continues to fail, use Report an issue; repeatedly creating accounts will not fix mail delivery.

No hardware required.

1. Use System to describe components, connections, aircraft geometry and reusable packages.
2. Use Mission to plan a geographic route and connect actions, conditions and recovery paths.
3. Use Sim and Tools to explore behavior, calculate responses, review source, test assumptions and inspect recorded evidence.
4. Connect supported hardware through Equipment for bench readings and supported reviewed operations. The current engineering release does not provide physical flight-control or a Deploy destination.

You can choose the right workspace for your next task.

A design check, numerical study or scenario result has its own scope. None establishes that a physical aircraft has passed flight validation.

The email you used to create your Seraph account.

1. Open Sign in. New here? Create a free account, then confirm your email using the link in your inbox.
2. After signing in, you arrive at Your account. Overview shows your software subscription. AI credits shows what is available to spend. Security lets you request a password reset.
3. Use this same account in Vantage’s Account & plan. A second email creates a separate identity; purchases do not automatically transfer between accounts.

Your email appears at the top of the account page. Check it before making a purchase.

Use Forgot password on the sign-in form to email a reset link. If a service is unavailable, wait and retry; creating another account will not repair the original one.

A signed-in account with a Stripe billing record.

1. Open Overview and choose Manage billing. Stripe opens a secure billing portal for the account you signed in with.
2. Review invoices, payment details and your subscription. To stop future renewals, use the cancellation controls in Stripe and review the effective date before confirming.
3. Return to your account and choose Refresh account. A scheduled cancellation keeps the paid period visible until its end; it does not delete your saved engineering projects.

The account page shows the current plan and renewal or end date.

No subscription yet? Your Seraph account is still free. You can purchase AI credits independently; a top-up does not subscribe you to Vantage Beta.

A confirmed Seraph account. A software subscription is not required for a top-up.

1. Open AI credits. Available credit is split into Monthly, Purchased and Promotional. Amounts held for requests in progress are excluded from the available balance.
2. Choose $5, $10, $25, $50 or $100. Each amount adds the same dollar value in AI credits. Review the 12-month expiry, accept it, then continue to Stripe to pay once.
3. After payment, return to your account. Credits appear after the payment is verified. If verification is still in progress, refresh the balance instead of paying again.
4. Use hosted Vantage Assistant in the desktop application. Monthly credits are used first, followed by promotional and purchased credits. The activity list shows expiry dates and the latest usage.

For example, 100,000 input tokens and 10,000 output tokens use $0.09 in credits at the current GPT-5 mini rates. Review Vantage AI rates before purchasing; the number of requests varies with their size.

The $0.75 beta allowance expires at the end of its paid month and does not roll over. Purchased credits keep their own 12-month expiry, even if you cancel the beta subscription. Your own provider API key uses that provider’s billing, not this wallet.

Vantage open with no hardware connected.

1. Open the project selector and create a Multirotor project. Give it a recognizable name, such as Survey drone.
2. Go to System → Structure. Open Add component and search the library for a flight controller, a battery and a range sensor. Place them on the canvas.
3. Select each component. Review Values and Ports before wiring it. Enter known specifications; leave unknown measurements unavailable instead of inventing values.
4. Connect matching supply and signal ports. A connection represents your design; it does not configure or energize a physical device.
5. Open Run system check. Select each finding to inspect its component. Resolve incompatible connections and review missing information.
6. Wait for the saved state. Open System → Aircraft and inspect the shared inventory and mass subtotal.

The same component identities appear in Structure and Aircraft, with a saved architecture and a reviewed set of findings.

If a library entry does not expose the port you need, inspect its definition before choosing another. Do not connect unrelated ports just to make the diagram look complete.

Your selected project; no hardware required.

1. Open Tools → Controls and choose the altitude study. Start with the reference defaults, checking which values come from System.
2. Set a target altitude and study duration. Use a short duration within the supported 5–3,600 second range for this first calculation.
3. Run the calculation. Inspect the response curve, peak and final error together with the model assumptions.
4. Change one editable gain and calculate again. Compare the behavior rather than treating a smoother curve as proof of a better physical aircraft.
5. Save or export the current result using the study controls. If you edit an input again, rerun before replaying or exporting the new result.

You have a repeatable local study connected to your project.

A System-owned value should be changed at its source. If export becomes unavailable after an edit, the previous result is stale; calculate again.

A selected project for project-specific results.

1. Press Ctrl+K on Windows, or select workspace search. Type a destination, component name, saved report, source filename or device profile.
2. Use Up and Down to select a result, Enter to open it and Escape to close search.
3. Use Overview, System, Mission, Sim and Tools to move between the main groups. Choose Structure, Aircraft, Equipment or Packages beneath System.
4. Use Back and Forward to retrace navigation. Selecting a device search result opens its destination; it does not connect hardware.

You arrive at the relevant page or exact project item.

If one search source fails, use its retry action. Results from the other sources can remain available.

System → Structure or Mission → Autonomy.

1. Select a node to open its details. Use the Structure panel to find nested items when the canvas is crowded.
2. Drag an item to reposition it. Use multiselect to move a group. Alignment guides help placement; Alt bypasses alignment where supported.
3. Choose Pan to move the view without moving nodes. Use zoom and Center diagram or Fit to regain an overview.
4. Use undo/redo, copy/paste and the context menu for edits. Fullscreen retains the workbench tools and inspectors.
5. Close an inspector when you need more canvas space. At compact widths the left and right panels may replace one another.

You can navigate a large document without changing its structure accidentally.

Dragging a node edits its position; panning only changes the view. Practice the distinction in the canvas below.

A selected project.

1. Open the notification bell. Use All for the project summary and recent activity; use Attention for unresolved items.
2. Select Review checks or the relevant error action to open the affected workspace.
3. Check save status near the operation. A successful save means persistence completed, not merely that saving started.
4. Clear activity only when you want to remove its history. Reading or dismissing a notification does not resolve the underlying problem.

You know which item needs attention and where to resolve it.

Notifications are project-specific. If a read fails, retry it before interpreting an empty panel as an all-clear.

The appropriate workspace or control has focus.

1. Press Ctrl+K to open workspace search. Up/Down selects a result, Enter opens it and Escape closes the search.
2. Use Tab to reach a control and Shift+Tab to go back. In a tab list, use its arrow keys; Home and End select the first and last available tabs.
3. Use Shift+F10 or the Context Menu key on a supported item to open the same actions as right-click. Escape closes the menu and returns focus.
4. In the code editor, Ctrl+Z undoes an accepted local change. In the terminal, Ctrl+C interrupts a running command or copies a selection; Ctrl+Shift+C/V copy and paste.
5. In the AI composer, Enter sends and Shift+Enter inserts a newline. These shortcuts act on the focused workspace, so click or focus the intended surface first.

You can navigate and edit without relying on a pointer.

Do not use arrow keys to pan while a numeric input or editor has focus; those keys belong to that control. The practice canvas below Navigation’s related System chapter provides a keyboard movement exercise.

Open Manage projects from the project selector or search.

1. Search the active list and choose Open to select a project. Pinned projects appear first.
2. Use the row action menu to Rename or Pin. Renaming changes the display name without changing the project identity or saved files.
3. Before switching an active hardware project, complete the application’s disconnect or activity checks. Do not assume switching projects transfers an existing hardware operation.
4. Use the project selector to confirm the new selection before editing, recording or exporting.

The selected project owns the work you are viewing.

If a project cannot open because its aircraft kind is unsupported, its retained files are not automatically converted into a drone project.

Manage projects.

1. Choose Delete from the project’s action menu and review the confirmation. An active recording or failed disconnection can block this action.
2. Open Recently deleted to see retained project entries and deletion dates.
3. Choose Restore to return the same project identity and saved files to the active list.
4. Use Storage & backups for disk management. Removing a project from the active list does not permanently erase its saved directory or reclaim its disk space.

You can recover a removed project without rebuilding its contents.

If restoration reaches a workspace capacity limit, resolve that limit first. Do not manually rewrite the project index.

Any editable workspace.

1. Watch pending, saved and failed indicators after an edit. Use Retry after a failed save while keeping the edited values intact.
2. Ordinary navigation retains many canvas, editor and study states for the selected project. Explicitly saved project files provide restart persistence.
3. Save source and explicit configuration drafts before closing the application. An unsent AI prompt or an in-memory editor state is not a workspace backup.
4. Create a backup before moving storage or making extensive changes. Verify the completed backup rather than copying a single visible file.

You know which work is persisted and which is still a draft.

If loading fails, retry instead of replacing the document with an empty version. See Backups and recovery for workspace-level failures.

A supported connection for live data; saved evidence can be viewed offline.

1. Open Overview and check the connection identity. Match the reported controller and interface to the hardware you intended to connect.
2. Read the units and source alongside each measurement. A connection heartbeat does not mean every sensor is reporting.
3. Look for freshness labels. A stale value is the last known reading; an unavailable value is not zero.
4. Inspect attitude, battery, position and signal trends where supplied. Keep above-ground altitude distinct from home-relative altitude.
5. Open saved evidence from its link to inspect the exact report and time rather than rerunning a check unintentionally.

You can distinguish what is being measured now from historical or missing information.

If just one field is missing, inspect that source in Equipment. Reconnecting the entire application may not provide a sensor the controller does not report.

A supported source reporting the values you need.

1. Choose the recording action and confirm the selected project and connection.
2. Start recording and observe the active status. You may navigate to another workspace while recording continues.
3. Stop the recording when the observation is complete. Wait for the session to be saved.
4. Open Logs to replay the saved session and inspect its measurements and events.

A recorded session is available for later inspection.

A recording can be incomplete or belong to another project; read its status and project label before comparing it with current work.

A supported device, a data-capable cable and any required vendor driver.

1. Open System → Equipment. Review Connected hardware and the individual discovered interfaces.
2. Match the device’s port, model and reported firmware identity. Two devices with similar identifiers are still separate interfaces.
3. Open the device’s setup action if required. When the exact model is ambiguous, choose the actual board; a generic USB bridge does not identify it reliably.
4. Connect using the supported adapter and inspect readings. Expand the controller’s component list to see components it actually reports.
5. Use the compatibility guide to distinguish bench telemetry, reviewed settings and supported board uploads.

The device has a clear identity, connection state and source-specific readings.

For a busy port, close the other program using it. For no device, check the cable, driver and ignored/preferred COM-port settings before retrying.

The exact supported board model selected in Equipment.

1. Open the chosen board’s setup. Review the required toolchain, board core and plugin rather than installing an unrelated family.
2. Use Hardware & tools to inspect installed-tool status. Complete any explicit installer or setup steps and recheck their status.
3. Build the intended board source through its supported workflow. Review build output, target model, port and firmware identity.
4. Use the explicit upload review and confirmation when the selected adapter supports it. Verify the reported outcome before moving on.

The supported toolchain and selected target agree.

Automatic ArduPilot, PX4 and Betaflight flight-controller flashing is not included. A compiler installation or vendor SDK alone does not add a working Vantage device adapter.

A supported network adapter or controller connection.

1. Expand Wireless setup in Equipment. Select or configure the saved network connection for the intended device.
2. Check the device address, transport and network reachability. Explicit network discovery can request Windows network permission.
3. For supported parameter changes, read the current values and prepare a draft. Inspect current versus proposed values before confirming.
4. Wait for transport acknowledgement and read-back verification. If the device or project changes during review, refresh the review.

A supported connection or parameter update has an explicit, verifiable result.

Keep unavailable GPS/RTK readings unavailable. Location permission, GPS fix quality and network connectivity are separate prerequisites.

Equipment open; the exact board model identified.

1. Open the device’s setup and review plugin status. Install the plugin for the exact board or supported device family when requested.
2. Continue to Choose firmware and review the offered firmware source and required toolchain. Installing a plugin prepares support; it does not silently flash a board.
3. Build the selected firmware and review errors before using an available explicit upload operation. Check the target port again before transfer.
4. Use plugin management to inspect or remove an installed plugin. Stop related operations first, read the removal scope and confirm only the intended plugin.

The selected device has an understood plugin, firmware and toolchain state.

A vendor plugin or SDK may expose setup information without a working control adapter. Removing a plugin does not establish that firmware on a device has been removed.

A selected Multirotor project.

1. Open System → Structure and choose Add component from Structure or the + tool.
2. Search the library, select the insertion destination and click or drag to place the component. Keep library open when adding several parts.
3. Select the component and inspect Values, Ports, Code and Notes. Record its actual specifications and any source notes.
4. Use Structure to rename and organize items. Keep exact component identities when another workspace already references them.

Each component has a location, identity and inspectable properties.

Missing data is a review item, not permission to guess. AI component research should be checked against the actual manufacturer and part.

Components with compatible interfaces.

1. Inspect both ports before connecting them. Check the interface category, direction, units and relevant electrical assumptions.
2. Draw the connection between compatible ports. Select the connection or component to review details.
3. Group related items into a subsystem using the canvas or Structure controls. Use subsystem ports to expose the connections needed outside the group.
4. Open nested subsystems from Structure. Preserve meaningful names so a linked mission or report remains understandable.
5. Run system check after the change and inspect conflicts, missing data and review items.

The diagram expresses your design and its boundaries.

A visual wire is an architecture relationship. It does not prove physical wiring, install code or command hardware.

A saved or edited System document.

1. Choose Run system check. Select a finding to navigate to the affected component or interface.
2. Correct known problems at their source. Review related Aircraft, Power or Autonomy values that depend on the component.
3. If using Assistant, inspect the proposed components, connections and changed values before applying the draft.
4. Refresh any preview made before a later document edit. Wait for saving to finish and run the check again.

Findings correspond to the current design, and accepted changes are saved.

A stale proposal cannot be treated as current. If regeneration fails, retry the attempted assignments rather than applying an older preview.

A STEP, STL or OBJ file you are allowed to use.

1. Open System → Aircraft and use the CAD import control to choose your file.
2. Watch import progress. Cancel if you selected the wrong file; a failed import should preserve the earlier geometry.
3. Select the correct units and scale. Mesh formats may not provide trustworthy units, so verify against a known dimension.
4. Use orbit, fit, face alignment and wireframe to inspect orientation and geometry. Review the imported filename.
5. Confirm removal only when you intend to remove geometry. Importing CAD does not automatically populate all component specifications.

The model has an intentional orientation and scale.

If dimensions are implausible, check units before changing the aircraft measurements. Do not infer physical dimensions from an uncalibrated mesh.

Known measurements or a component inventory.

1. Enter the measured all-up mass in the aircraft profile using the displayed units.
2. Compare it with the System component subtotal. Physical components contribute; protocol nodes and subsystem containers do not.
3. Inspect the incomplete indication when component masses are missing. Follow an inventory link to the exact Structure component.
4. Record dimensions and build notes. Keep measured total mass distinct from an estimate assembled from component data.

Aircraft measurements and design assumptions remain separately identifiable.

Changing display units does not reinterpret CAD calibration or change stored physical quantities. Review System-owned inputs before running a study.

A selected project and access to the chosen package.

1. Open System → Packages, or Packages in Autonomy for a mission starter. Search or filter the catalog and inspect compatibility and access labels.
2. Open the preview. Assign existing components where appropriate and inspect the exact proposed connections and reused identities.
3. Change assignments deliberately and wait for the refreshed preview. Closing the preview leaves your document unchanged.
4. Use the explicit add action when the proposal is correct. Inspect the resulting document and wait for saving.
5. For package configuration and scenarios, select the exact sources, verify units and freshness, enter the relevant parameters and save before review.

A package is part of the project with intentional component assignments.

A locked package requires the corresponding account access. A monitoring or decision-study package is not a live autonomous flight adapter.

A saved package configuration and the required input roles.

1. Open its scenario tools in Sim. Confirm the source identity and each required input role.
2. Run the nominal scenario, then inspect noise, disconnect, stale-reading and mismatched-source cases provided by the scenario tools.
3. Read the observations, validity, decisions and feedback. Monitoring packages report observations; decision studies may produce proposals.
4. Change one configuration field, save and rerun. Keep the resulting evidence associated with the configuration that produced it.

You can explain both a normal result and the response to invalid inputs.

A wrong source, unit, frame or timestamp can invalidate a reading even when the number looks plausible. Scenario evidence does not validate physical execution.

Position and attitude observations together.

1. Open Packages and select Navigation monitoring. Check its access label and the project compatibility.
2. Bind position and attitude from the intended sources; check fix quality, WGS84 position and orientation conventions.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Inspect position and attitude timestamps together. Missing attitude must not be replaced with a guessed orientation.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Observe temperature with its source and age.

1. Open Packages and select Temperature monitoring. Check its access label and the project compatibility.
2. Bind the temperature sensor, confirm °C conversion and set the allowed reading age.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Compare nominal, stale and disconnected readings. Monitoring should not produce an output command.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Explore stopping decisions from forward range and speed.

1. Open Packages and select Braking study. Check its access label and the project compatibility.
2. Bind forward range and forward velocity in matching body frames. Set minimum distance, assumed deceleration, latency and clearance margin.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Compare available range with the assumed stopping requirement. This produces study decisions, not aircraft braking commands.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Inspect voltage and current from an identified battery.

1. Open Packages and select Battery monitoring. Check its access label and the project compatibility.
2. Bind voltage and current, checking scale, polarity and battery identity.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Inspect measurement freshness and sign conventions before interpreting electrical power.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Explore trigger and recovery thresholds.

1. Open Packages and select Temperature gating. Check its access label and the project compatibility.
2. Choose the temperature source, trigger temperature and recovery temperature.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Test values on both sides of the thresholds and a stale-reading case. Inspect proposed state changes without treating them as hardware output.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Branch on a sensor reading with declared units.

1. Open Packages and select Sensor response. Check its access label and the project compatibility.
2. Bind the sensor quantity and units, then enter trigger and recovery values.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Inspect both threshold branches and missing-input behavior. Review any custom capability implementation separately.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Evaluate a proposed launch, return and landing sequence.

1. Open Packages and select Launch & return study. Check its access label and the project compatibility.
2. Bind position, ground altitude and landed feedback. Set home coordinates, altitude, tolerances and timeout.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Inspect approximate home distance and altitude error. Completion needs feedback; the study does not fly the aircraft.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Evaluate arrival and return decisions.

1. Open Packages and select Waypoint & return study. Check its access label and the project compatibility.
2. Bind position and ground altitude. Set destination, home, altitude, position and altitude tolerances, and timeout.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Inspect arrival and return conditions with fresh readings. A route plan does not add physical navigation control.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Observe forward distance within the declared sensor coverage.

1. Open Packages and select Range monitoring. Check its access label and the project compatibility.
2. Bind the forward range source, verify metres, mounting frame and reading age.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Inspect distance and invalid cases. A single forward reading does not describe clearance in every direction.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Observe the radio signal the device actually reports.

1. Open Packages and select Radio monitoring. Check its access label and the project compatibility.
2. Bind the exact signal source and inspect its reported scale.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Compare fresh, stale and disconnected values. Raw signal units should not be presented as an invented percentage.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Inspect reported actuator position.

1. Open Packages and select Actuator monitoring. Check its access label and the project compatibility.
2. Bind physical position feedback and confirm its fractional scale.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Observe feedback changes. A command acknowledgement alone does not establish physical position.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Retain reported location with source context.

1. Open Packages and select Location recording. Check its access label and the project compatibility.
2. Bind a position source with valid coordinates, fix quality and timestamps.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Inspect the captured location and invalid-fix behavior. Do not substitute a previous fix for a current observation.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Explore sustained low-signal and recovery decisions.

1. Open Packages and select Radio response study. Check its access label and the project compatibility.
2. Bind signal, then set low and recovery thresholds and their durations in the reported scale.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Compare brief noise with sustained degradation and recovery. Decisions remain proposals, not physical-flight takeover.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Evaluate a release sequence using position and load feedback.

1. Open Packages and select Payload release study. Check its access label and the project compatibility.
2. Bind actuator position and payload load. Set release position, tolerance, released-load threshold and confirmation timeout.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Require fresh position and load evidence for completion. No physical payload operation is established by this study.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Keep position evidence associated with a site observation.

1. Open Packages and select Site recording. Check its access label and the project compatibility.
2. Bind the intended position source and inspect its fix, frame and timestamps.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Review the saved evidence and its source. A saved location is not a complete site survey.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

Estimate a return reserve with explicit assumptions.

1. Open Packages and select Return reserve study. Check its access label and the project compatibility.
2. Bind measured remaining charge. Set usable capacity, return distance, speed, power, reserve and uncertainty allowance.
3. Save the configuration, then open the package’s review or scenario tools in Sim. Check each required input’s source, units, frame and freshness.
4. Vary distance and power assumptions and inspect the proposed decision. The estimate does not command a return or guarantee sufficient energy.

A saved package configuration and a scoped observation or decision-study result.

If an input is unavailable, stale or mismatched, resolve its source before interpreting the result. Changing configuration invalidates earlier review evidence.

A selected project; internet access for map tiles and address search.

1. Open Mission → Route. Search for your planning location and review it on the map before adding a stop.
2. Add waypoints and give them useful names. Select a marker or stop-list entry to edit the exact coordinates.
3. Set ground-relative altitude and optional navigation speed using the displayed units. Review launch settings separately.
4. Drag route controls to shape curves and reorder stops in the list. Recheck the geometry and distance after each change.
5. Wait for the saved state. If a numeric field is invalid, correct it rather than navigating away expecting it to save.

You have a named, ordered and saved route.

The map below is for learning waypoint interaction at Buffalo Bayou Park in Houston. It is not a flight authorization or an assessment of that location’s airspace.

A saved route.

1. Open route review and inspect coordinates, altitude references, route order and launch settings.
2. Inspect available airspace information and its source. Map coverage or a drawn route is not permission to operate at the location.
3. Use the Autonomy handoff action. Open Mission → Autonomy and inspect the generated steps and their parameters.
4. Resolve requirements and connect the route to decisions or recovery paths. Review before generating code.

The geographic plan has a corresponding mission design.

If map tiles fail, retry the map separately from the saved plan. Avoid replacing a saved route merely because the background cannot load.

A selected project and any System components your actions reference.

1. Open Mission → Autonomy. Use + to open the action library, then click or drag an action onto the canvas.
2. Choose the mission’s starting step. Connect action outputs to their next steps and add conditions for branching.
3. Select each step to edit Values, Connections, Code and Notes. Bind sensor actions to the exact System component and output.
4. Define alternative and failure paths. The Structure panel’s document order is not the execution order of a branching graph.
5. Open mission settings and Run system check. Review both mission requirements and linked System findings.

A connected graph describes the intended sequence and its alternatives.

Renaming or removing a referenced System component can affect a mission. Resolve missing links before code generation.

A reviewed mission graph.

1. Open Walkthrough and supply hypothetical outcomes for the actions being explored.
2. Follow the highlighted path through success, condition and recovery branches. Pause and inspect the selected step as needed.
3. Resolve missing implementations and requirements. A walkthrough does not command an aircraft.
4. Choose Build code when available. Open the generated editable copy in Tools → Code and review it.
5. Keep earlier edited copies if you regenerate the mission. Compare the new output before replacing your own work.

You have inspected the mission logic and, when requirements allow, generated source for further review.

A walkthrough pauses when hidden. A background build should not force you away from another workspace.

The local simulation dependencies required by your chosen setup.

1. Open Sim and review preparation status. Complete missing dependencies through the offered setup path.
2. Choose a reference aircraft such as X500, Iris or Matrice 100. The visual and numerical reference profile change together; System-owned properties keep priority.
3. Select the environment and inspect physical-model assumptions. Reference battery and drag values may be estimates.
4. Edit simulation settings, validate them and explicitly save. Invalid parameters must be resolved before preparation.
5. Prepare the local flight-software process where required and check configuration-ready status before starting.

The selected environment and saved configuration agree.

A familiar reference model does not establish compatibility with that manufacturer’s physical flight link.

A prepared simulation and a supported input device or available input mode.

1. Open controller setup or Change input. Discover the input device and move each control to observe its actual axis, button or knob.
2. Map observed controls to the intended functions. Inspect direction and range before accepting the mapping.
3. Start the simulation deliberately and use its instructions to control the local session. Observe the model and reported values together.
4. Stop the session when finished. Navigating away releases embedded input ownership; switching projects stops the previous simulator.
5. Return to the same project to continue editing retained settings and package drafts.

The local simulator responds to the intended input mapping.

If a control is missing, repeat discovery while moving it. A disconnected or hidden input surface should not continue sending foreground controls.

A selected project and known model assumptions.

1. Open Tools → Controls and choose the altitude or rotation-rate study.
2. Review mass, thrust, gains and source ownership. Use editable reference assumptions only where the project has not supplied authoritative System values.
3. Set the target and duration. Altitude duration accepts decimal values from 5 to 3,600 seconds.
4. Run the calculation. Inspect peak response, settling behavior, final error and any saturation or model warnings.
5. Use playback and timeline inspection to understand the curve. Change one parameter at a time and calculate again.
6. Export the current result when available. Any changed input invalidates the previous replay or export until a successful rerun.

You can explain how an input change affected the calculated response.

The learning chart below uses Vantage’s altitude model with reference assumptions. It is a numerical study, not tuning advice for a physical aircraft.

A supported connected controller and valid current readings.

1. Open controller tuning and inspect the connection, current native values and status.
2. Prepare a draft or import a compatible study. Compare each proposed value with the current controller value.
3. Open review and confirm the intended target and parameters. Keep the project and connection unchanged during review.
4. Confirm only the reviewed update. Wait for transport acknowledgement and read-back verification, then inspect the result.

The supported update has been checked against the controller’s returned values.

Leaving the page cancels an active review. If readings, connection or project context changed, prepare a fresh review rather than reusing an old one.

Battery specifications and defensible component load assumptions.

1. Open Tools → Power. Enter battery capacity and nominal voltage in the units shown.
2. Set the reserve and inspect how much energy remains available for the estimate.
3. Add component budget entries with a load and quantity. Avoid counting a component twice through both an observed total and individual estimates.
4. Review total estimated load and endurance. Change one assumption to understand how sensitive the estimate is.
5. Save the plan and check its saved state. Keep reserve assumptions in the plan rather than interpreting them as battery-health measurements.

You have an explicit, revisable power estimate.

Invalid capacity, voltage, reserve or quantity fields must be corrected. A long calculated duration is only as reliable as its load assumptions.

A supported source reporting voltage and current.

1. Inspect the live measurements separately from the saved plan. Confirm the battery source and reading age.
2. Check whether voltage and current describe the same observation period before interpreting power.
3. Use the explicit observed-load capture action when the reading represents the condition you want to study.
4. Compare the captured load with your component budget and record the context. Review again when the operating condition changes.

The plan identifies when an estimate uses an observed load.

Unknown charge remains unknown. Voltage or one measured load does not by itself establish battery health, usable capacity or flight endurance.

A selected project and source files you intend to edit.

1. Open Tools → Code. Use Files to create or import supported source and select a file to open its editor tab.
2. Use search, selection and the source context menu to inspect the code. Syntax coloring identifies language patterns; it does not prove target compatibility.
3. Edit and save. Check the saved state before exporting, building or asking another tool to use the saved file.
4. Use the tool dock to inspect diagnostics and build configuration. Resolve the reported file and line rather than treating all warnings as build failures.
5. Use export to keep a copy outside the project when needed. Generated configuration may be read-only; edit its owning settings instead.

The intended file revision is saved and ready for review or a supported build.

On a source load or save failure, retain your work and use Retry. A successful editor save is separate from a successful compilation.

Tools → Code.

1. Open Terminal to start PowerShell. Check your current directory before running commands that change files.
2. Use Ctrl+C to interrupt a running command; selected text can change that shortcut’s behavior. Ctrl+Shift+C/V copy and paste.
3. Collapse and reopen the terminal to retain its session. Type exit when you intend to end the shell.
4. After external source edits, exit the shell and use the explicit terminal-source import workflow. Review revisions before importing changes.
5. Use the undock controls for Files, Workspace or Terminal to move that panel to another display. Dock or close its window to return the mounted content.

You can arrange tools without losing editor models, undo history or terminal state.

Navigating away from Code returns detached panels. External changes and unsaved editor revisions require review; neither should silently overwrite the other.

A saved source file; an AI connection only for AI changes.

1. Select the relevant code and choose Explain or Change with AI, or use the bottom composer with Code context.
2. Describe the intended behavior and constraints. Inspect the proposed inline diff before choosing Accept or Discard.
3. Save accepted edits and run the available inspections. A proposal based on an older source revision must be refreshed.
4. Select the supported build target and verify its required toolchain. Read the build output and resolve errors.
5. If the target offers upload, review the exact device, source and transfer operation before confirming. A successful build does not mean the device was updated.

Your saved source and reviewed build or upload result are traceable.

AI changes never remove the need to inspect source and test it. Unsupported targets remain unsupported even if the file has valid syntax.

A compatible source file and a supported transfer target.

1. Open Code and inspect the Live edits toggle. Check which saved files and destination will be reused from the previous session.
2. For a new or ambiguous target, complete the inline setup. Select the compatible files and exact device; provide SSH connection details only when that transport requires them.
3. Enable Live edits when you intend to sync those files. This toggle starts the guarded syncing workflow directly; the separate Upload action retains its own review dialog.
4. Watch Live edits on, Edits queued, Syncing edits or Live edits paused. Inspect a pause or failure before continuing to change files.
5. Use Manage to change the inline setup or turn Live edits off to stop. Do not treat file transfer as a successful compilation, firmware execution or physical test.

You know whether the selected source is actively syncing, queued, paused or off.

Not every upload target supports live edits. For an unknown SSH destination, inspect the host fingerprint before trusting it; connection secrets are not guide content.

A loaded project and the prerequisites shown for the selected check.

1. Open Tools → Tests and inspect the available readiness groups and local mathematical checks.
2. Select the check and review its inputs, scope and missing prerequisites. Start it explicitly.
3. Read the resulting status with its explanation: passed, failed, attention or untested. Unknown duration may show indeterminate progress.
4. Open the detail view and inspect source, time, plots and limits. A partial readiness result is not a complete validation.
5. After changing the relevant inputs, rerun the check to obtain current evidence.

You can say what was checked, against which inputs and with what result.

A successful local or virtual test is not physical flight validation. If the project fails to load, retry loading before running against an empty fallback.

Supported connected input hardware and the application’s calibration prerequisites.

1. Open Tests → Controller setup and select the intended device.
2. Observe the reported controls and inspect the mapping shared with Sim. Move one input at a time to identify its actual response.
3. Follow the receiver calibration workflow offered for that adapter. Review proposed settings before any supported write.
4. Complete the review and inspect the acknowledged result. If the connection changes, restart the review for the current device.

The supported receiver setup has a reviewed mapping and result.

Simulation input mapping and receiver calibration serve different purposes. Discovery alone does not mean calibration has completed.

At least one saved report.

1. Open report history and select the desired result. Opening a report does not rerun its check.
2. Confirm its source, project and timestamp, then inspect the stored result.
3. Export from the selected report so the exported evidence matches what you reviewed.
4. To remove a report, use its Keep/Delete confirmation. The application uses the Recycle Bin path; deleting the selected report clears its loaded view.

The report you share is the result you intended to share.

Do not combine a new project configuration with an old report without identifying that difference.

A live source for recording, or an existing session for replay.

1. Open Tools → Logs. Start recording from the recorder controls when a supported source is available.
2. Stop and wait for saving, then select the session in the library.
3. Play, pause and scrub the timeline. Inspect attitude, measurement traces and events at the same time position.
4. Use search to locate sessions and inspect their project and source labels. Replay pauses when the workspace is hidden; an independent live recording may continue.

You can investigate a recorded event without confusing it with current telemetry.

An empty or interrupted session differs from a completed saved session. Check the session’s status before interpreting missing measurements.

A selected saved session.

1. Export CSV for tabular measurements or the session format for retained session data.
2. Use import to open a supported session and inspect its source and scope before comparing it with your project.
3. Use confirmed deletion for individual sessions. Check the selected item before accepting the Recycle Bin operation.
4. For older recording cleanup, use Settings → Storage & backups. Review the scope and use Undo last cleanup if needed.

You can share and manage recordings without losing their context.

A load error should offer Retry. Do not overwrite an unreadable recording with a blank session.

A confirmed account with available hosted AI credit.

1. Sign into the desktop account controls with the account used on the website. Refresh access if a recent purchase has not appeared.
2. Open Settings → AI and choose Vantage Assistant. Check the available account credit before sending a request.
3. The active $1/month beta includes $0.75 of monthly AI credit. Hosted GPT-5 mini usage deducts credits at Vantage AI rates.
4. Send a question and inspect the updated balance after settlement. Monthly allowance expires rather than accumulating indefinitely.
5. Use your website account to manage billing. Account registration is free; future paid plans and top-ups should only be purchased when actually offered.

Your hosted requests use the signed-in account’s available credit.

If credit is unavailable, check account identity, confirmation and access refresh. Repeatedly clicking Send does not replenish credit.

A working AI connection.

1. Open the bottom composer and choose Current page, a specific workspace or Question only.
2. Use Sources and errors to attach the intended saved source or visible error. Review the selected context before sending.
3. Ask a specific question, such as “Explain the missing input in this range study.” Enter sends; Shift+Enter adds a line.
4. Use Stop to cancel a request when needed. Expand the conversation to inspect sources and next steps.
5. For a proposed System, Autonomy or Code change, inspect its review or diff and explicitly accept or discard it. Refresh a proposal if the underlying document changed.

The answer is grounded in the context you selected and changes remain reviewable.

Saved context may differ from an unsaved edit. Check the context pane rather than assuming the assistant sees every current selection or field.

An API account or compatible local server, with an appropriate credential where required.

1. Open Settings → AI → Add connection. Choose the provider and enter its API credential directly into the application.
2. Choose the model, save the named connection and set it as default when intended.
3. Use Test connection to check a small structured response. This can incur provider charges; it does not send project context.
4. For a custom connection, use an endpoint supporting the required OpenAI-compatible structured response format. HTTPS is required except on loopback.
5. Remove or switch connections explicitly. Removing the default leaves AI disconnected; Vantage does not silently choose another provider.

New requests use your selected provider and its billing, separately from hosted Vantage credits.

OpenAI, Gemini and Claude connections use API credentials. A ChatGPT subscription is not an API key. Component web research currently requires OpenAI.

A saved conversation or configured connection.

1. Use the conversation history controls to reopen completed chats for the intended project and workspace.
2. Review retention settings in AI preferences. Unsent drafts and saved conversations have different lifetimes.
3. Use Question only when you do not want workspace context included. Attach source only when it is relevant.
4. Use Privacy & permissions to control AI generation. Saved API credentials are protected in the local connection store and excluded from workspace backups.

You can control the context and retained conversations used by the assistant.

After moving to another computer, configure provider credentials again. A project backup is not a credential transfer.

Preferences open from the toolbar.

1. Choose Light, Dark or System in Appearance. Adjust interface scale, text size and reduced motion to suit your display.
2. In Workspace, choose startup behavior and whether to restore the last project.
3. Select Metric, Imperial, Aviation or custom display units. Choose the application default or an explicit project override.
4. Use Coding workspace settings for editor size, indentation, wrapping, minimap and sticky headers.
5. Check the saved state. Changes to displayed units do not rewrite source data, raw exports or native firmware parameter units.

The interface and supported displays follow your preferences.

Use Use app defaults to remove a project unit override. CAD calibration and specialist native-unit fields still require their own unit checks.

A website account; a subscription only if purchased.

1. Open Account and confirm the signed-in email before managing a subscription.
2. Use the offered billing-management action to review the actual subscription and payment details.
3. After a purchase or account change, return to desktop account settings and refresh access.
4. Treat software/package access and AI credit as separate balances. A paid-through date, expired allowance and a canceled subscription can have different effects.
5. To reset a forgotten password, use the sign-in page’s reset flow and the latest email link. Never include passwords or API keys in an issue report.

The website and desktop reflect the same account’s current access.

If a payment completed but access did not update, report the time and account email privately through support. Do not purchase a second subscription to force a refresh.

An idle workspace with hardware, recording, simulation and AI activity stopped.

1. Open Settings → Storage & backups. Inspect the current project-data location and storage totals.
2. Choose the backup operation and its destination. Review the scope before starting.
3. Wait for the completed result. The backup includes the saved project index and native project data such as source, routes, studies, reports and sessions.
4. Keep the complete backup folder and manifest together. API credentials, installed tools, temporary simulation runs and browser caches are excluded.

You have a verified workspace backup suitable for the application’s restore workflow.

Do not treat a manually copied project index as a full backup. The restore process checks manifests and file integrity.

A complete backup for restore, or an available destination for a move.

1. Stop active hardware, recording, simulation and AI work. Open Storage & backups and select the intended operation.
2. Choose the backup or destination and inspect the review. Confirm only after checking its scope.
3. Let Vantage copy and verify the data, switch the workspace location and restart. Avoid unplugging the destination drive during this process.
4. After restart, inspect the project list and open representative saved files. The previous data location is retained as a recovery point.
5. Use Recover previous workspace when an operation needs rollback. If the chosen drive is missing, restore its availability instead of creating an accidental empty workspace.

The application opens the intended verified workspace.

A validation or hash failure should stop restoration. Preserve the backup and error details; do not edit the manifest to bypass the check.

Settings → Storage & backups or Privacy & permissions.

1. Use recovery-copy export for project recovery material and select the destination explicitly.
2. For recording cleanup, review old completed recordings before confirming. Interrupted recordings are excluded; Undo last cleanup can restore the last cleanup.
3. Use diagnostics export when support needs application and tool status. Choose where to save the report.
4. Review any files before attaching them to an issue. Diagnostics export is local; it does not automatically upload a report.

You have the recovery or diagnostic material intended for the problem.

Diagnostics omit project names, source, prompts, credentials and telemetry. Add a concise description of the steps that failed when reporting an issue.

The website address, time and sign-in action that failed.

1. Confirm you are using seraphaero.com/account/. Reload once to rule out a temporary connection failure.
2. Check your email spelling and use the most recent confirmation or password-reset email. Check spam and allow time for delivery.
3. If the same error remains, record which page and action triggered it. Do not paste raw tokens, password-reset links or API credentials into a report.
4. Use Report an issue with the time and visible error. Include a screenshot only if it helps explain the problem.

Support receives enough context to distinguish a delivery problem from an account-service failure.

Do not create multiple accounts or repeat checkout to work around a sign-in error.

System → Equipment and the intended hardware available.

1. Check the physical connection and data cable. Verify the operating system can see the device and its driver.
2. Close another application holding the port. Check ignored ports and the preferred port in Hardware & tools.
3. Retry discovery and confirm the exact interface, model and firmware. Review unsupported or ambiguous status before proceeding.
4. For stale values, inspect the source timestamp and whether that measurement is actually reported. Keep missing data distinct from zero.

You identify whether the problem is discovery, port ownership, compatibility or a specific measurement.

A successful heartbeat does not prove sensor availability. A vendor utility installed on the computer does not establish a Vantage adapter.

The affected workspace and its visible error.

1. For a map, check network access and retry tiles separately from the saved route. Keep the route document intact.
2. For CAD, check supported format and units. Retain the previous geometry if import fails.
3. For simulation, review preparation dependencies and invalid settings, save corrections and prepare again.
4. For a build, inspect the target, toolchain and first relevant error. Source syntax coloring is separate from compilation.
5. For a save failure, keep the draft and retry. If the storage location is unavailable, reconnect it before trying a recovery operation.

You address the failed dependency without replacing valid saved work.

Attach the exact error, app version and smallest repeatable set of steps to a report. Use a backup before attempting workspace recovery.

Settings → AI and the selected account or provider.

1. Check whether the selected connection is Vantage Assistant or your own provider. They have separate access and billing.
2. For hosted AI, confirm the account and available credit. Refresh access after a recent purchase.
3. For your own provider, verify the saved credential, selected model and provider account status. Test connection can incur a small charge.
4. Check AI permission and the chosen context. Shorten an oversized source attachment and retry a failed request only after addressing its error.
5. If the outcome is uncertain, inspect the conversation and balance before sending the same task again.

You can locate the failure in account access, provider configuration, request context or permissions.

Do not include provider keys in screenshots or reports. An interrupted response and a rejected request can have different accounting outcomes.