# Ask Bolt: deployment approach and public sample

15 October 2026 · Federal SI

Ask Bolt helps aviation and operations teams find supported answers, compare information against their criteria, and prepare useful work for review. **SI² — Super Intelligence × Squadron Intelligence** is our brand expression. Super Intelligence is product terminology, not a measured superhuman-performance claim.

Ask Bolt is deployed in Optimize. Capabilities, approved sources, access, and integrations are specific to each customer environment. This brief describes the public website and a reference approach for scoped deployments; it does not certify or audit a private environment.

## What the public website does

The [sample workspace](/workspace) uses authored synthetic records and explicit rules to demonstrate a complete training-reference review:

1. Identify a discrepancy between a current reference and an application checklist.
2. Inspect the passage, source version, freshness, and visible conflict.
3. Compare the reference versions and identify what remains unknown.
4. Change report-completeness assumptions and see **Yes**, **No**, or **Needs more information**.
5. Edit a report, record a final choice, inspect the proposed review destination, and copy or download the work with its sources.

Additional prepared examples cover an application-support question and a fictional map observation. The SuperAirspace integration is proposed. The [training and briefing examples](/readiness) retain fixed-snapshot comparisons, deterministic calculations, source inspection, and brief exports.

These examples run in the browser. They do not call a live model, retrieve customer records, change an application, provision an account, or submit a report. The completeness result checks the selected assumptions; it does not analyze edits to the draft. Unrecognized questions receive a boundary message instead of a fabricated live answer.

## Data and access in this release

Sample edits, assumptions, and choices are held in page memory. Resetting or leaving the workspace clears them. Copy and download are explicit visitor actions; downloaded files remain on the visitor's device. The public sample does not send prompts or drafts to a model, customer system, or analytics. Hosting providers may process ordinary request logs.

The [customer access page](/sign-in) explains the intended organization-workspace journey and provides a sample path. Customer authentication is not connected to this public site. No password is collected and no successful sign-in is simulated.

The pilot inquiry form prepares an email to Federal SI using the organization, work email, and workflow description the visitor supplies. The visitor reviews and sends the message in their email application. Preparing the draft is not submission or delivery. Keep inquiry content public and non-sensitive.

## Reference approach for a customer deployment

| Area | What must be established for that environment |
| --- | --- |
| Identity and access | Verify organization, role, allowed environment, source access, exports, and actions on the server. A browser selector never grants access. |
| Approved knowledge | Record source ownership, version, effective date, freshness, allowed uses, and withdrawal rules. Preserve the relevant passage and its location. |
| Evidence and decisions | Validate that a passage supports the answer. Keep deterministic calculations explicit. Show missing, stale, and conflicting information; retain the person's final choice. |
| Models and tools | Select and evaluate capabilities within the approved data boundary. Provider availability does not establish authorization for customer information. |
| Reviewable actions | Show destination, proposed effect, required approver, and connection status. Enforce permissions before execution and confirm delivery before displaying a submitted state. |
| Maintenance | Version reviewed corrections, preserve customer ownership and exportability, keep tenant information separate, and maintain regression examples. |

A connected deployment should keep identity, retrieval, model access, tools, and logs inside its approved boundary. This public Vercel website has no connection to Optimize's shared service. Customer systems and operational data are outside this website release.

## Evaluation before expansion

Agree a recurring workflow and measurable acceptance criteria with an accountable customer owner. Evaluate supported answers, citation validity, missing information, version conflicts, stale references, unsupported requests, permission failures, and service unavailability. Measure time to a supported answer, report completeness, review effort, and repeated clarification requests against the team's current process.

Cloud, on-premises, and disconnected requirements are assessed during scoping. Flight Bag, Outbox, Edge, Reconcile, and Field Kit hardware remain future directions for evaluation. A responsive website, local file export, or conceptual hardware image does not demonstrate disconnected operation.

## Start with one useful workflow

[Scope a Bolt pilot](/#pilot): one recurring workflow, one accountable owner, defined users, approved references, explicit capability boundaries, and agreed evaluation criteria. Intended deliverables are a configured experience, approved source set, demonstrated workflow, evaluation results, and rollout recommendation. Schedule and commercial terms are established during scoping.

The [brand and interface kit](/brand-kit/README.md) contains preserved artwork, typography, tokens, provenance, and reusable composition examples. It is design material, not a connected customer SDK. [Asset notices](/ASSET-NOTICES.md) retain artwork, font, and third-party attribution.

Federal SI is a brand of Federal AI LLC. Aircraft imagery and product terminology do not imply government or manufacturer endorsement, certification, or operational authority.