Greenfield projects, governed from day one
Starting from nothing is the moment most platforms skip governance. agI3R runs it the same way as everything else: a charter interview, a human-confirmed wizard, a repo created where you work, and a scaffold that passes a gate before it lands.
How it works
A reverse interview covers purpose, target stack, scale, deploy target, and your conventions — and a malformed charter surfaces as needs-review, never as something quietly accepted.
The approved charter pre-fills the new-project wizard; a person still confirms the name, stack, components, and team before anything is created.
GitHub or Azure DevOps, in the org your admin configured — with the access token held in a secret manager and never stored or logged in the clear.
A guidelines file, a minimal stack skeleton, and your adopted components arrive as a single cross-checked proposal — the only path any code reaches the new repo.
The charter's preferences seed the project conventions that ground every later agent prompt — the first feature is built the way you said you build.
The agents behind it
Human control
The scaffold passes the same proposal gate as any code change — there is no ungated path into a new repo, even an empty one.