{
  "markdown": "# GE Agent Factory\n\n**Turn an agent requirement into an implementation you can inspect, evaluate, and hand off for deployment.**\n\nGE Agent Factory turns an agent requirement into a versioned contract, generated implementation artifacts, evaluation evidence, and a handoff package for Google agents-cli / ADK / Gemini Enterprise.\n\nThe contract is stored in [OKF](docs/reference/okf.md), a Markdown-based format with structured metadata. The factory uses that contract to generate code, evals, synthetic source systems, and release evidence.\n\nThe factory does not replace agents-cli or ADK. It prepares and verifies the material handed to them.\n\n## Start with the artifact you need next\n\n| Goal | Command | Result to inspect |\n|---|---|---|\n| Capture the requirement | `ge capture` | A versioned Enterprise Agent Contract |\n| Check the generated implementation | `ge prove` | The workspace and its proof pack |\n| Find unfinished work | `ge status` | Current stage and next required action |\n| Enter the deployment path | `ge handoff agents-cli` | Handoff material for the configured runtime |\n\nRun the local proof before configuring cloud deployment. A generated workspace\nand a passing local proof are separate from a live tenant result. The\n[quickstart](#quickstart) gets you to the first inspectable proof.\n\n\n## Quickstart\n\nFrom a clone:\n\n```bash\ngit clone https://github.com/vamsiramakrishnan/ge-agent-factory.git\ncd ge-agent-factory\nmise run setup\nge prove\nmise run console\n```\n\nThe first proof runs locally. Cloud credentials are needed when you hand a proven workspace to Google Cloud.\n\nInstall the factory skills from GitHub without cloning manually:\n\n```bash\ncurl -fsSL https://raw.githubusercontent.com/vamsiramakrishnan/ge-agent-factory/main/packages/create-ge-agent-factory/bin/create-ge-agent-factory.mjs \\\n  | bun - -- --yes --skills agents\n```\n\n## Core workflow\n\nThe main path is three commands:\n\n```bash\nge capture\nge prove\nge handoff agents-cli\n```\n\n`ge capture` creates or registers an Enterprise Agent Contract.\n\n`ge prove` builds the workspace and runs the checks needed for the proof pack.\n\n`ge handoff agents-cli` passes a proven workspace into the deployment path managed by agents-cli / ADK.\n\nAt any point:\n\n```bash\nge status\n```\n\nreports the current stage and the first required next action.\n\n## Contract to runtime\n\n```text\nuser interview / BRD / PRD\n          │\n          ▼\nEnterprise Agent Contract (OKF)\n          │\n          ├── generated ADK code\n          ├── tool declarations\n          ├── evaluation cases\n          ├── synthetic source systems\n          └── trace / proof inputs\n          │\n          ▼\n       ge prove\n          │\n          ├── eval results\n          ├── spec-to-code checks\n          ├── simulation results\n          └── promotion checks\n          │\n          ▼\n      proof pack\n          │\n          ▼\n  agents-cli / ADK\n          │\n          ▼\n   Agent Engine\n          │\n          ▼\n Gemini Enterprise\n```\n\nThe contract is the input to generation and evaluation. Passing generation does not by itself prove the implementation satisfies the business requirement; the proof path exists to compare generated behavior with the contract's declared criteria.\n\n## Enterprise Agent Contract\n\nThe contract records the material the factory needs to build and test an agent, including behavior, tool intent, source systems, evaluation criteria, and generation metadata.\n\nIt is intended to be readable as a document and compilable as structured input.\n\nSee [OKF reference](docs/reference/okf.md) for the schema and examples.\n\n## Capture\n\nInteractive capture opens the browser-based interview flow:\n\n```bash\nge capture\n```\n\nRegister an existing contract:\n\n```bash\nge capture --from agent-spec.json\n```\n\nA fully terminal-native interview flow is not the default capture path in the current release.\n\n## Prove\n\n```bash\nge prove\n```\n\nThe proof path builds the agent workspace and evaluates the artifacts generated from the contract.\n\nDepending on the workspace, that includes:\n\n- ADK source generation;\n- tool generation;\n- synthetic source-system fixtures;\n- eval generation and execution;\n- spec-to-code trace checks;\n- promotion-gate checks;\n- proof-pack generation.\n\nUse watch mode while editing a contract:\n\n```bash\nge prove --watch\n```\n\n## Handoff\n\n```bash\nge handoff agents-cli\n```\n\nThe handoff step is where the local proof path crosses into cloud deployment.\n\nThe generated workspace is passed to agents-cli / ADK for the deployment and publication stages. Gemini Enterprise remains the end-user surface.\n\nNothing before handoff needs to mutate a Google Cloud deployment target.\n\n## Coding-agent support\n\nThe repository packages common factory operations as skills so coding agents can install, inspect, build, and prove workspaces using the same CLI and project files as a human operator.\n\nSupported installation paths include Claude Code, Gemini CLI, Codex-style sessions, Antigravity, and generic MCP clients. Product names here identify harness integrations; they are not required for the underlying CLI workflow.\n\nFor a checkout:\n\n```bash\nmise run skills-install\n```\n\nFor MCP clients:\n\n```bash\nbun tools/mcp-server.mjs\n```\n\nThe MCP server exposes factory operations over the same underlying functions used by the CLI.\n\n## Catalog\n\nThe repository contains generated agent specifications for horizontal business functions and industry-specific examples.\n\n- [Horizontal catalog](https://vamsiramakrishnan.github.io/ge-agent-factory/catalog/)\n- [Vertical catalog](https://vamsiramakrishnan.github.io/ge-agent-factory/catalog-verticals/)\n- [Catalog explorer](https://vamsiramakrishnan.github.io/ge-agent-factory/catalog/explorer/)\n\nThe catalog is generated from the repository registry rather than maintained as a separate hand-edited inventory.\n\nGenerated catalog output still depends on the registry generation and drift checks running successfully. A generated page is evidence of the current checked registry state, not a general guarantee that unrelated source files cannot diverge.\n\n## Console\n\nRun the local console with:\n\n```bash\nmise run console\n```\n\nThe console exposes the same workspace state used by the CLI: contract status, proof stages, repair work, and handoff readiness.\n\nIt is an operator surface over the factory state, not a second implementation of the pipeline.\n\n## Local and cloud boundary\n\nThe factory is local-first for contract capture, generation, simulation, and proof.\n\nCloud work begins when the user invokes a handoff or other command that explicitly targets cloud resources.\n\nThat boundary is deliberate because it lets contract and eval iteration happen without turning every proof run into a deployment.\n\n## Documentation\n\nPublished docs: <https://vamsiramakrishnan.github.io/ge-agent-factory/>\n\nUseful starting points:\n\n- [What is the factory?](https://vamsiramakrishnan.github.io/ge-agent-factory/start/what-is-the-factory/)\n- [Quickstart](https://vamsiramakrishnan.github.io/ge-agent-factory/start/quickstart/)\n- [GE Agent Factory vs agents-cli](https://vamsiramakrishnan.github.io/ge-agent-factory/start/vs-agents-cli/)\n- [Core concepts](https://vamsiramakrishnan.github.io/ge-agent-factory/concepts/)\n- [Cookbooks](https://vamsiramakrishnan.github.io/ge-agent-factory/cookbooks/)\n- [Console](https://vamsiramakrishnan.github.io/ge-agent-factory/console/)\n\n## Repository map\n\n```text\npackages/         CLI, factory packages and generators\nskills/           coding-agent skills\napps/             console and generated registry consumers\ndocs/             source documentation and references\ntools/            MCP and development tooling\n```\n\n## Boundaries\n\n- A generated implementation still needs evaluation against the contract.\n- A passing proof establishes the checks implemented by that proof path; it is not a universal claim about production behavior.\n- Synthetic source systems exercise integration logic but do not reproduce every production dependency.\n- Local proof does not deploy the agent.\n- `ge handoff agents-cli` is the explicit bridge into the cloud deployment path.\n\n## Development\n\n```bash\ngit clone https://github.com/vamsiramakrishnan/ge-agent-factory.git\ncd ge-agent-factory\nmise run setup\nmise run test\n```\n\nUse `ge status` or the repository task list when you need the next supported operation rather than guessing from internal file layout.\n\n## License\n\nSee [LICENSE](LICENSE).\n",
  "bytes": 8390,
  "sha": "7fbaefc209df1acdec2972843a4123881c439b171522868ec725583bda311744",
  "repo_slug": "vamsiramakrishnan/ge-agent-factory",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/okf_vamsiramakrishnan_ge_agent_factory_okf_i_b21ef431/readme"
}