@happyvertical/smrt-assets
Provider-neutral asset storage, metadata, versions, associations, and AI-assisted operations.
What it gives you
Provider-neutral asset storage, metadata, versions, associations, and AI-assisted operations.
This package is one focused part of the s-m-r-t stack. Its decorated models participate in the same manifest, tenancy, persistence, and generated-interface conventions as the rest of the framework.
Version and derive assets through the runtime
createNewVersion maintains primaryVersionId and findVersions history. AssetRuntime exposes createAssetRuntime, storeSourceAsset, storeDerivedAsset, linkDerivation, and setExtractionStatus. ASSET_ROLES, ASSET_METADATA_KEYS, and ASSET_EXTRACTION_STATUS give integrations a shared vocabulary; AssetAssociation records polymorphic provenance.
Serving has explicit response semantics
serveAsset and resolveAssetForServing choose 403, 404, redirect 302, or upstream failure 502 based on access and availability. remoteMode chooses proxy or redirect. FolderCollection uses SmrtHierarchical getTree and getPath; load a planned subtree rather than recursively resolving each node to avoid an N+1 query pattern.
Package UI
Components in this package
Import these public components directly. When the package also exports playground entries, the next tab renders its real components with package-owned example data.
Package previews
Try the working views
These previews are owned by the package and use its public components. Mock mode is intended for safe browsing; live mode appears only where the package supports it.
Generated interface
REST
The exact route set comes from each model's @smrt({ api }) policy
and the application manifest—not from a second controller definition.
GET /api/assets
GET /api/assets/:id
POST /api/assets
PATCH /api/assets/:idWhat stays consistent
- Tenant scope and operation permissions run before model access.
- OpenAPI and generated clients use the same manifest fields.
- Packages can expose read-only or custom action sets.
Generated interface
MCP
AI tools are generated from the methods you explicitly include. Their inputs are validated against the same model metadata used by REST and CLI.
assets_list({ where, limit, orderBy })
assets_get({ id })
assets_create({ data })
assets_update({ id, data })Agent-safe by construction
- Tool availability can be narrower than the HTTP API.
- Principal execution intersects RBAC, agent ceilings, and persona tools.
- Descriptions and schemas are emitted from source metadata.
Browser-native agent interface
WebMCP
The generated web definitions carry the same tool names, descriptions, and JSON Schema
inputs as MCP. smrt-web registers them with document.modelContext.
import { webMcpToolDefinitions } from '@happyvertical/smrt-virt-web';
import { registerWebMcpTools } from '@happyvertical/smrt-web';
// Omitting an exposure policy registers read-only tools only.
const dispose = registerWebMcpTools(webMcpToolDefinitions);The page keeps its security boundary
- Tools execute through generated REST fetchers as the signed-in page user.
- Authentication, tenant gates, permissions, and field policy stay server-side.
- Feature detection makes registration a safe no-op outside supported browsers.
Generated interface
CLI
The app CLI turns manifest resources into predictable operator commands while keeping package-specific actions close to their models.
smrt assets list --limit 25 --order-by created_at:desc
smrt assets get <id>
smrt assets create --from-file ./record.jsonMade for automation
- Machine-readable output and file-based input.
- The same include/exclude policy as other surfaces.
- Migration, introspection, dispatch, and knowledge commands stay in smrt-cli.