Reusable projects · 23 / 23

Assemble a reusable team project

Combine defaults, module inputs, confined files, typed outputs and user references in one working stack.

YOUR TASK

Make this happen

3 steps

Set team_name to Fulfillment.
Use the module’s own purpose.txt file for its description.
Connect Alice through module.dispatch.id; check, inspect and simulate.

THE IDEA BEHIND IT

Review the whole source closure

The root declares intent, passes a setting into a module, and connects a lookup through an output. The module loads its own file; it cannot reach parent project files. Each part remains independently understandable.

Before real deployment

Pull and commit the matching schemas/testing contracts. Run local check and test, inspect skipped validators, and review the hosted plan before apply. Git modules need explicit installation and a committed lockfile; never edit a downloaded cache. Environment selection must be explicit.

Limits and destructive changes

Stable addresses and collection keys are critical. Removing declarations or module calls can delete resources. A sensitive variable has no committed default and may flow only to permitted write-only fields. The browser never reads shell secrets, installs Git modules or approves real changes.

Checks use local schemas. Plans and changes use a fixture account; Lua suites run only in the explicit test lessons.

Read the starter files

main.cococo

variable "team_name" { default = "TODO" }
module "dispatch" {
  source = "./modules/team"
  inputs = { name = var.team_name }
}

team_membership "alice" {
  teamId = module.dispatch.id
  userId = user.alice.id
}

modules/team/cococo.module.toml

format = 1

modules/team/main.cococo

input "name" { type = "string" }
team "this" {
  name = input.name
  description = file("purpose.txt")
}
output "id" {
  type = "identity<team>"
  value = team.this.id
}

people.cococo

user "alice" {
  email = "alice@example.com"
}

modules/team/purpose.txt

TODO