Author Arete Stack Artifacts

A good Arete stack is a small, app-facing read model. Do not begin by mirroring every IDL account. Start from what the application needs to read together, choose one canonical entity key, and prove every field and update route back to that key.

This skill ends with validated local artifacts. Hosted publication and deployment are separate, externally mutating work handled by arete-deploy.

Compose From Published Parts First

A stack is a group of live views and program SDKs. When published stacks already serve the views the application needs, and program packages provide the program SDKs, compose a stack from them instead of authoring a new read model. Composition needs no Rust toolchain:

a4 stack compose --name ore-plus-token \
  --live ore \
  --program spl-token \
  --selected-view ore=OreRound/latest \
  --selected-view ore=OreMiner/state

The command resolves the parts, checks that they compose, and writes [authoring.stacks.<name>] in arete.toml. You can also write the entry yourself: