Appendix A: aip.json Full Schema Reference

This document provides a comprehensive reference for all valid fields in the aip.json manifest file.

Full Example

{
  "tenant": "my-corp",
  "name": "example-pack",
  "version": "1.2.0",
  "display_name": "Example Pack",
  "description": "An example pack that demonstrates key features.",
  "author": "My Corp <dev@my-corp.com>",
  "views": {
    "home": { "title": "Dashboard" }
  },
  "capabilities": [
    "net.access"
  ],
  "dependencies": [
    "worka/browser"
  ]
}

---

Root Fields

Field	Type	Required	Description
tenant	string	Yes	A unique namespace for the pack author, like a GitHub username or company name.
name	string	Yes	The machine-readable name of the pack (e.g., my-cool-pack).
version	string	Yes	The pack version, should follow SemVer (e.g., 1.0.0).
display_name	string	Yes	The human-readable name shown in the Worka UI.
description	string	Yes	A short description of the pack's purpose.
author	string	No	The name and/or email of the pack author.
license	string	No	The license for the pack (e.g., MIT, Apache-2.0).
views	object	No	Optional static views exposed by the pack (for default pages).
capabilities	array	No	An array of strings declaring the permissions the pack requires. See details below.
dependencies	array	No	An array of strings (<tenant>/<name>) identifying other packs this pack depends on.

---

Notes on Backend Logic

Worka v2 packs expose a single MCP server inside the pack’s WASM. You do not declare Docker images or external servers in aip.json. The host discovers tools directly from the WASM module.