package.json

Only a cognet published on its own has one. A cognet inside an agent uses the agent's.

{
  "name": "@cody/fast-loop",
  "version": "0.2.0",
  "type": "module",
  "files": ["cognet.config.ts", "types", "src", "library", "plugins", "Cargo.toml", "Cargo.lock", "pyproject.toml", "uv.lock"],
  "dependencies": {
    "gpt-tokenizer": "^2.5.0"
  }
}

Field	Means
`name`	the registry name — always scoped, `@you/name`
`version`	immutable once published; `axonl publish` bumps it on a collision
`private`	`true` keeps it private
`files`	what ships — the source, never `.cognet/`
`dependencies`	npm packages the TypeScript uses

A cognet ships as source. Whoever installs it compiles it, against the kernel they run.

An agent selects it by name:

export default defineAgent({
    cognet: "@cody/fast-loop@^0.2.0",
})

Dependencies must be pure

A cognet has no filesystem and no network. Tokenizers, maths and parsers work; a package that opens a socket or reads a file will fail.