Core workflows
How a project moves through Bloom, from the owner's seat: create a project, approve the plan,
Admin console basics
The admin console (apps/admin) is Bloom's operations surface: a separate SPA on its own
GitHub App setup
Bloom uses a GitHub App to create and manage repositories. One App (owned by the
GitLab setup
Bloom's VCS layer is platform-agnostic (M23): a project's repo target can name
Repository adoption
By default Bloom starts a project from nothing: on plan approval it creates a fresh GitHub
Knowledge skills
Skills are versioned, prompt-layer domain knowledge (M11-7): each one is a vendored
Skill vetting
Every PR that vendors or re-pins a third-party skill (make skills-import, M22-2) must include
Project migration
Bloom can export a project's SDLC state to a platform-neutral, versioned bundle and