hanuman/verticals
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
All concrete verticals: cp-sonar, pex, domainforge, sahaaya.
3 commits 1 branch 0 tags 7.8 MiB
  • Go 76.7%
  • TypeScript 12.2%
  • Python 5%
  • Shell 3.4%
  • SCSS 1.3%
  • Other 1.3%
Find a file
Exact
Meka Reddy e64d33aef4 verticals: check in cp-sonar/backend/vendor/ for Fly builds 
The earlier `**/vendor/` gitignore rule was accidentally too broad;
cp-sonar's vendor/ is the source-of-truth for the Fly build
(build context = cp-sonar/, replace targets in platform/ are out
of context). Adding 35MB / ~2500 files of vendored deps.
2026-05-08 03:20:54 -05:00
cp-sonar verticals: check in cp-sonar/backend/vendor/ for Fly builds 2026-05-08 03:20:54 -05:00
domainforge Initial commit: A1 reorg materialization 2026-05-08 02:55:06 -05:00
pex Initial commit: A1 reorg materialization 2026-05-08 02:55:06 -05:00
sahaaya Initial commit: A1 reorg materialization 2026-05-08 02:55:06 -05:00
.gitignore verticals: check in cp-sonar/backend/vendor/ for Fly builds 2026-05-08 03:20:54 -05:00
go.work Initial commit: A1 reorg materialization 2026-05-08 02:55:06 -05:00
go.work.sum Initial commit: A1 reorg materialization 2026-05-08 02:55:06 -05:00
README.md Initial commit: A1 reorg materialization 2026-05-08 02:55:06 -05:00
workspace.yaml Initial commit: A1 reorg materialization 2026-05-08 02:55:06 -05:00

README.md

Hanuman Verticals

All concrete deployable verticals for the Hanuman platform. Each vertical is its own subdirectory with its own deployment cadence, its own Go modules, and its own database schema (vertical schema autonomy per A1 D6).

This repo depends on git.hanumanapps.io/hanuman/machine-protocol for contracts and on published git.hanumanapps.io/hanuman/platform/platform/... and git.hanumanapps.io/hanuman/platform/capabilities/... modules for kernel and capability code. It does not depend on the portals.

Verticals

Vertical Status Purpose
cp-sonar live (Fly.io demo) SonarCloud finding remediation. Implements the L4 SonarCloud adapter and the L3 remediation strategies for SonarQube quality-gate-driven workflows.
pex active Personal Execution Control — operator-facing task management surface.
domainforge active JBoss → modern-runtime migration vertical. Python + Ansible (no Go module).
sahaaya placeholder Reserved for the Sahaaya vertical when it lands.

Layout

verticals/
├── README.md
├── go.work                 # ties cp-sonar/backend and pex into one workspace
├── go.work.sum
├── workspace.yaml          # vertical inventory
├── cp-sonar/
│   ├── manifest.json
│   ├── backend/            # Go module — git.hanumanapps.io/hanuman/verticals/cp-sonar/backend
│   ├── frontend/           # Angular app
│   ├── migrations/         # cp-sonar's own DB schema
│   └── ...
├── pex/                    # Go module — git.hanumanapps.io/hanuman/verticals/pex
│   └── ...
├── domainforge/            # Python + Ansible (no go.mod)
│   └── ...
└── sahaaya/                # placeholder; README + manifest only

Cross-repo dependencies

  • cp-sonar/backend depends on machine-protocol, libraries/eventbus, capabilities/adapters/{sonarcloud,github}.
  • pex depends on machine-protocol (and possibly libraries/eventbus when its event flow lands).
  • Local development resolves these via go.work use clauses pointing at sibling folders in the workspace; production builds use published versions.

Build

cd /home/mreddy/hanuman/verticals
go work sync
go build ./...

Deploy

Per-vertical deploy configs live under each vertical's deploy/ subdirectory. Per A1, external components run single-tenant per deployment regardless of platform deployment topology.