Specify a project's lifecycle
Metadata
Current evaluation
No evaluation has been recorded for this issue yet.
Issue body
### What needs to get done
Define and document:
1. When (and if) a Project gets created
2. How project mutation works (difficult case: `LifecycleService` writing `adopt-info`. See: https://github.com/canonical/craft-application/pull/217/files#r1496586665)
3. How commands and services should interact with Projects
Some questions to consider:
- Should a Project be frozen? (Pros/cons)
- What should/should not have access to a project?
- How do we handle commands where project access is optional? (e.g. remote-build)
### Why it needs to get done
This is loosely defined currently and has worked fine so far, but we're reaching edge cases that make us need a
Evaluation history
No evaluation history available.