Project settings
Configure the project boundary while keeping business behavior in source.
Project settings configure the platform resources surrounding a company OS. They should stay small. Business objects, rules, tools, loops, metrics, and app behavior belong in the project repository.
What settings own
IdentityProject name, ownership, membership, and platform roles.
SourceRepository provider, default branch, and source integration.
DeliveryEnvironment bindings, domains, and deployment policy.
ConnectionsInstalled providers, credentials, and allowed project access.
What belongs in source
If a change affects how the business behaves, it should usually be reviewable source: authorization policy, a tool, a loop target, an object schema, a skill, or an app.
Safe changes
Administrative changes should identify the actor, validate the target, and record an audit event. Consequential changes may require a second reviewer or a reviewed source change.