Skip to content

Processes/product — standing up the product stackproduct

Set up a code hosting org — product processSet up a code hosting org

simplefully automatable🔁 once

Create the code hosting organization, configure repos, branch protection, and team access. GitHub is the canonical route.

GitHub API and MCP fully support org/repo/team management.

Current agent ceiling

An agent can run 4 of 5 steps 4 of them behind a human approval gate ⏸

No workaround yet (1): Create GitHub organization (manual form/portal — no API path)

How it runs

Route-coded block flow: emerald = agent, amber = manual form/portal, red = needs a human. ⏸ approval gate · ⏳ async wait.

01Create GitHub organization

manual form
GitHub logoGitHub71⏸ approval gate

or:GitLab logoGitLab54·Gitea logoGitea34

02Create repositories

agent
GitHub logoGitHub71⏸ approval gate

or:GitLab logoGitLab54·Gitea logoGitea34

1 API call
  • POST /orgs/{org}/repos

runs in parallel · 2

03Configure branch protection

agent
GitHub logoGitHub71⏸ approval gatemedium risk

or:GitLab logoGitLab54·Gitea logoGitea34

1 API call
  • PUT /repos/{owner}/{repo}/branches/{branch}/protection

04Create teams and set access

agent
GitHub logoGitHub71⏸ approval gatemedium risk

or:GitLab logoGitLab54·Gitea logoGitea34

2 API calls
  • POST /orgs/{org}/teams
  • PUT /orgs/{org}/teams/{team}/repos/{owner}/{repo}

05Invite team members

agent
GitHub logoGitHub71⏸ approval gate

or:GitLab logoGitLab54·Gitea logoGitea34

1 API call
  • POST /orgs/{org}/invitations

Context the agent needs first: name · engineers

The market options

Each role resolves against its arena’s live leaderboard — the default is the process’s canonical vendor, alternatives ranked by agent-readiness.

Simulate this process

simulated dry run from the mapped process — no real calls are made
For agents Process manifest (JSON)·/llms.txt