Extension modes
2
The current model separates blueprint and script modes, with blueprints first.
Extensions
Organize blueprints, scripts, and version delivery into a controlled extension layer.
The NavaX extensions page is grounded in the current admin, client API, and desktop blueprint package code: authors, categories, market scope, version upload, install/download, ratings, and comments are already separate flows for blueprint extensions and later script extensions.
Market scopes
3
all, spot, and futures scopes can filter extension availability.
User actions
4
Install, download, rate, and comment form the client loop.
Package format
1
Version upload is centered on the NavaX .fsvb blueprint package.
Extension Layer
Extensions are not a generic store. They are distribution for trading strategy assets.
The extend modules in the software already split author certification, categories, listings, version packages, ratings/comments, and user installs. The site should explain how that layer serves the desktop trading client instead of showing generic extension cards.
Blueprint packages
Version upload reads manifest, blueprint.preview, and runtime bundle data from .fsvb files for protected display and execution.
Authors and categories
Admin keeps author identity, website, certification, categories, keyword filters, and publishing status in separate controls.
Market scope
Extensions can target all markets, spot, or futures so the client can filter assets by trading context.
Ratings and feedback
Ratings, comments, replies, and visibility status have their own API paths for quality review and operations.
Distribution Flow
Extension TypesThe path from author submission to desktop install is clear.
Admin handles review, classification, and versions; the client API handles public listings, details, downloads, and user install records; the desktop client imports, previews, and runs blueprint packages.
01
Prepare author and category
Maintain author identity, certification, and categories so extension source and purpose stay traceable.
02
Create the extension record
Submit title, description, thumbnail, mode, market scope, score baseline, and publishing state.
03
Upload the version package
Use .fsvb files, then read the version, package size, and download URL after upload.
04
Install and download
Users install the extension, then download the latest enabled version while download counts update.
05
Review and operate
Ratings, comments, replies, and hidden states move through admin review to protect quality.
Package Design
Blueprint packages can be previewed while protecting the core implementation.
.fsvb containers can include manifest, blueprint, blueprint.preview, and runtime.bundle files. Protected exports show preview and parameters while runtime bundles carry execution.
Manifest metadata
Stores author, description, market scope, runtime mode, parameter schema, visibility, and signature information.
blueprint.preview
Keeps name, description, parameters, and protected messaging visible even when source is unavailable.
runtime.bundle
Separates the executable result from the source node graph for a steadier desktop delivery artifact.
Extension Types
Extension formats start with blueprint packages and leave room for scripts.
Blueprint packages are the strongest current path; script mode, protected runtime bundles, and admin governance form the base for the broader extension layer.
Blueprint package
Blueprint Extension Package
Distribute reusable strategies, parameter schemas, preview data, and runtime bundles as blueprint extensions for desktop install and download.
manifestblueprint.previewruntime.bundle
- Supports public and protected blueprints
- Parses version and package size after upload
- Fits commercial strategy asset delivery
Script extension
Script Extension Channel
The extension model already reserves script mode for later lightweight tools, strategy helpers, or scripted execution components.
mode:scriptmarket scopeversion channel
- Shares authors and categories with blueprints
- Reuses install, download, and comment flows
- Can open finer-grained capabilities later
IP protection
Protected Runtime Bundle
Blueprints can export preview documents and runtime bundles so runnable assets are delivered without exposing the full node graph.
sourceAvailable:falseparameterSchemaprotected preview
- Keeps readable description and parameters
- Hides the full node structure
- Better fit for commercial strategy assets
Operations
Review & Distribution
Authors, categories, versions, publishing, comments, and ratings have separate admin entry points, so the extension ecosystem can be reviewed, ranked, and removed.
authorcategoryscore
- Publishing state is controllable
- Comments can be replied to or hidden
- Sorting can use downloads and release time
Operations
Make strategy assets distributable, manageable, and operable.
The extension layer connects author identity, version rollout, feedback quality, and category discovery into one operating flow. A blueprint package is not just downloaded; its source can be trusted, its version controlled, its feedback curated, and its desktop delivery kept current.
Trusted source
UID, name, website, and certification status help users judge source and accountability before installing a strategy.
Version rollout
Each extension can maintain multiple versions, while enabled state controls the build delivered to the client for rollout, rollback, or suspension.
Feedback quality
Comments, replies, hidden states, and deletion move through admin review so useful feedback is preserved and noise is reduced.
Discovery controls
Categories, sorting, release time, downloads, and market scope shape exposure so the right strategies are easier to find.