The shape of a project

Project and workspace

A project has a shared identity in .foundry/project.toml. Each clone or worktree has its own workspace record. Registering a second checkout preserves the first checkout’s workspace.

Foundry Home

Foundry Home holds your Toolkit cache, run state, evidence, and run worktrees. The default path is ~/.e11-foundry. Set FOUNDRY_HOME to choose another location. Setup needs no administrator rights.

Publication root and initiative

Your publication root defaults to foundry. An initiative groups one effort under foundry/initiatives/<slug>/. The dashboard calls this effort an intent. Your checkout points at one current initiative.

Board and artifacts

The initiative’s board.yaml tracks its stories. Skills update status through e11 board. Artifacts are managed documents with a kind, revision, and recorded content digest. The dashboard shows whether the file matches its recorded revision.

Run, work item, and attempt

A run seals a plan from committed source documents. The plan contains work items and their dependencies. An attempt is one effort to deliver a work item. A continuation resumes the same attempt in the same worker session when an invocation reaches its allowance.

Worktree, branch, and report

The worker edits a worktree under Foundry Home on e11/run/<runId>. Your checkout receives the accepted commit when you land the work. The report records the run’s result, cost, and next steps at settlement.

Your checkout, committed
  .foundry/project.toml
  .foundry/pricing.json
  .foundry/profiles.toml
  .foundry/custom/  team overrides
  foundry/initiatives/  stories and shared documents
Your checkout, generated
  .foundry/local.json
  .foundry/initiative.json
  .foundry/config.toml
  .foundry/foundry/
  editor skill directories
Foundry Home, operational
  Toolkit cache
  workspace records and run state
  run worktrees and evidence

Follow the walkthrough to use these parts together.