Gabriel Moreno
Development partnerDevelopment partner on Onerom and owner of the project’s GitHub repository.
GitHub Gabriel Moreno (new tab)Development with Gabriel Moreno. Breno built onerom_skeleton: a public base for Python bots used by Onerom Runner and AI Builder Runner. This module credit does not assign the whole platform to him.
Development with Gabriel Moreno. Breno built onerom_skeleton: a public base for Python bots used by Onerom Runner and AI Builder Runner. This module credit does not assign the whole platform to him.
Development partner on Onerom and owner of the project’s GitHub repository.
GitHub Gabriel Moreno (new tab)Credits provided by Breno Mayder · 2026-11-01
The platform includes RPA orchestration, automation execution and web apps. My identified work includes onerom_skeleton, a public base for Python bots.
The platform combines orchestration, portals and automation components. This describes its technical structure, not full authorship.
What each part does and which technologies support it. A module in the code does not mean all its features are complete or published.
Orchestration API.
Organizes contracts, authentication and agent/portal integration.
Portals for different audiences.
Interfaces and navigation have separate compositions linked to backend contracts.
Automation execution and preparation.
Execution agents stay separate from the API and UI to keep automation environment boundaries.
Automation library and inspection.
SDK and inspection components support routine development and integration.
Desktop automation runtime.
A component for interface, image and OCR automation, separate from portals and the server.
Enterprise operations with a dedicated backend and web interface.
A module with its own contracts, backend and frontend. Its presence does not assign full implementation to a contributor.
Reference base for new automations.
Development template, separate from a published operational service.
Public bot foundation developed by Breno.
Runtime, use cases, entities and automation elements, with local smoke checks and contracts for Runner and AI Builder Runner. Public code under MIT.
View module on GitHub ↗Portals use the backend. Runners and tools use automation contracts. Read Breno’s contribution as a specific part of the wider architecture.
PostgreSQL appears in backend dependencies. Execution state and automation-environment access belong to specific components.
Per-module checks and contract validation. A structure review does not certify every flow or assign all platform capabilities to a contributor.
Tell me what you need. The WhatsApp draft includes this project as a reference. You can edit it before sending.