Project versus personal

Two kinds of decision shape a capsule, and they live in two places.

The project's, in Git

.devcapsule/devcapsule.toml is the manifest: what the project needs, the values it declares, the host access it recommends and why. Beside it the platform lock pins the exact component versions and the base image that satisfy the need. Both are committed. Anyone who clones the repository and runs project init gets the same environment, and project config need changes them for everyone on the next commit.

Yours, on your computer

Your checkout record holds what only you can decide: the authorizations you granted or refused, the values you set, the directories you bound, and the base image you consented to. Beside it, DevCapsule-managed directories hold the capsule's persistent home, the IDE's settings and plugins, and each agent's sign-in. None of this is in the repository, and none of it is shared with another checkout of the same project by default; What persists lists the directories.

A recommendation is the bridge: a project can recommend an authorization or a value, with its reason; config list labels such rows project-recommended; and you accept it, once, per checkout. A value you set with config set NAME default follows the recommendation; config unset NAME forgets your answer and follows it again.

When the project changes

A project that changes its manifest or lock can make your recorded choices stale: the base moved, a recommendation changed, a new tool needs consent. project run then stops and asks you to resolve:

~/.local/bin/devcapsule project config show
~/.local/bin/devcapsule project config resolve

show names each pending decision with the commands for its alternatives; choose one per decision, not all of them. To accept the project's current base recommendation, for example:

~/.local/bin/devcapsule project config authorize base-image default
~/.local/bin/devcapsule project config resolve
~/.local/bin/devcapsule project run

default accepts the current pin and nothing more: no host access, no future versions. Editing several choices is a sequence of edits and one resolve; a refused resolution leaves the previous plan intact. Installing a newer DevCapsule does not change any of this: your lock and your choices stay until you change them.