Agentic Apps · 04.11
App Packages: Portable, Revision-Pinned Products
A .agentisapp v2 bundle carries the whole transitive App, an explicit revision target, and verified portable components.
The package boundary is the whole App
A manifest-v2 .agentisapp export carries the App's transitive workflows, surfaces, data contracts, runtime requirements, and content-addressed Component v2 files. It is a product boundary, not merely a workflow template. Preview and export traverse the same dependency set, so the package the operator approves is the package Agentis writes.
Active is the default; candidate is explicit
Every export resolves a declared revisionTarget. active is the safe default: the last promoted revision with trusted production standing. Exporting candidate requires an explicit request, and the preview reports the same choice before any file is created. That prevents an unverified editor draft from silently replacing the known-good product in a portable artifact.
Portability strips host accidents and verifies what remains
Exports remove local binary paths, commands, working and repository directories, environment values, and runtime project roots. Component files travel with hashes and dependency locks. Import rejects unsupported manifest/runtime combinations, unsafe paths or symlinks, checksum mismatches, missing locks, and missing entrypoints before activation. A bundle with no manifest version is treated as legacy v1 for compatibility; conflicting or unsafe bundles fail closed.