opschain academy
packs:academy
opschain academy <subcommand>
OpsChain Academy, in the product: the OpsChain Academy agent serves the
learning path — Foundations, and the tracks the licensed packs own — from
an OpsChain server of your own. Every
exercise is real work performed in that server — build the estate, run the
governed change, grant the access — checked against what the server's
state and audit events record, and sealed as metadata-only evidence for the
Academy Server that keeps the ledger and issues the badge. The agent never
writes to OpsChain and nothing but signed metadata ever leaves your
machine; opschain docs packs-academy describes the pack.
The agent is a separate binary this build pins: academy install --from takes the release archive for your platform, verifies it against
the digest committed in this build and installs it under the OpsChain
home directory (or installs a built binary as a local build — the product
never downloads the agent itself; the Academy Server lane will, once it
lands); academy show reports what is pinned, installed and how the
agent will be launched. The remaining subcommands run the installed agent
with the product wired in — the targeted OpsChain server travels as the
agent's OPSCHAIN_SERVER, a scoped API token minted under your login
(academy-agent <label>, 30 days, revoked when the agent exits; an
expired login is refused by name; OPSCHAIN_ACADEMY_TOKEN set by you is
used as given) as its OPSCHAIN_ACADEMY_TOKEN, the data directory
defaults under the OpsChain home, and every agent flag passes through by
name.
Subcommands
| Subcommand | Manual | Purpose |
|---|---|---|
install | cli/academy-install | install the agent from a file: the pinned release archive, verified, or a local build |
show | cli/academy-show | the pinned release, the installed agent and the launch configuration |
serve | cli/academy-serve | run the agent beside the targeted server, or learner-local with --single-learner |
register | cli/academy-register | register the agent with the Academy Server using a grant |
status | cli/academy-status | the agent's registration, store and pack cache |
sync | cli/academy-sync | push queued evidence and refresh the pack cache now |
rotate-key | cli/academy-rotate-key | rotate the agent's deployment key |
mcp | cli/academy-mcp | the learner-side tutor lane: a read-only MCP server over stdio for your own MCP client |
version | cli/academy-version | the installed agent's own version |
What the licence unlocks
packs:academy is in the Basic tier and is the gate on any academy
content: a server whose licence lacks it is served no path, and the
agent's pages say which entitlement unlocks the academy. With it, the
Basic tier unlocks the Foundations track; every other track is owned
by the OpsChain pack that ships its surface and opens with that pack's
entitlement (packs:change-governance, packs:security-governance,
packs:agent-governance, packs:agents, …). The agent shows the whole
path: a track your licence does not carry is locked and names the pack
that unlocks it, and never holds back the tracks after it.
A first session, learner-local
opschain login --server https://ops.example.com
opschain academy install --from ~/Downloads/academy-opschain-agent_0.1.0_darwin_arm64.tar.gz
opschain academy serve --single-learner --academy-server https://academy.limepoint.com --grant-file ~/academy-grant
Open http://127.0.0.1:8070/, enrol with your company address, and start
the first exercise. The registration grant is issued by LimePoint for your
organisation; the Academy Server URL is the one named with it.
See also
opschain docs packs-academy— the pack, the lanes and the evidence model.opschain docs model-providers— the catalogacademy serve --tutorreads.