Platform-native execution
Target-specific executables, runtime assets, native argv, and standard process status.
A3S Use gives native tools and A3S cognitive plugins one verifiable package lifecycle across Linux, macOS, and Windows.
$ a3s install use --source releaseconvertREADYlibraryREADYreviewREADYreviewREADYdomain-knowledgeTARGETTraditional package managers stop after placing files. The target platform also verifies declared Tool, MCP, Skill, UI, and OKF knowledge surfaces, then projects readiness evidence to hosts.
Target-specific executables, runtime assets, native argv, and standard process status.
Content-bound instructions, tool dependencies, MCP services, sandboxed UI, and shareable OKF knowledge with no authority derived from text.
Select a surface to inspect its execution boundary
TASK / SERVICEA Tool is a Runtime-managed workload—not a private action protocol and not an MCP tools/list item.
Search reads signed metadata only. Before mutation, target, permissions, provider, and impact are bound into one immutable plan.
Refresh and search a TUF-signed catalog without package payloads.
Bind package digests, surfaces, permissions, and Runtime evidence.
Bind ACL policy and user confirmation to the same plan digest.
Verify the archive, ACL manifest, and content in a bounded root.
Prepare grants, Runtime bindings, projections, and dependency closure.
Switch capability generation atomically, then drain the old one.
CLI, Web, and agent management MCP share one Plugin Manager. A3S Use owns packages and evidence; Runtime owns workloads; hosts own policy, credentials, and rendering.
Read the architecture guideSkill text, UI messages, OKF knowledge, tool output, and remote content are data. Authority comes only from host policy, explicit grants, and generation-bound receipts.
Pin TUF roots, signed metadata, length, and SHA-256 while rejecting rollback and expired state.
Resolve again before apply. Version, content, permission, or provider changes require a new review.
Grants, Runtime bindings, route leases, and capability snapshots bind to one package generation.
macOS and Linux cover complete release archives and package lifecycle. Windows x86_64 is currently Preview while runtime and plugin lifecycle gates are completed.
Install the v0.2 release and run doctor plus capability snapshot. Use the schema-v3 contracts and roadmap for cognitive plugin development.