Hub framing
This hub keeps the conversation on department-owned workflow products rather than on a speculative cross-department platform.
Department workflow suite
A commissioner-facing orientation hub for three separate department-owned AI workflow microsites: Startup Haryana, PR Haryana, and Haryana Tourism PMIS.
Public portfolio context
Amit Kumar Agrawal, IAS
This hub keeps the meeting on department-owned workflows aligned to the current public portfolio context.
₹0
Registration fee on Startup Haryana
30 days
Published registration timeline
140+ / 28
Services / departments in the Invest Haryana single-window programme
Why workflow-first
The suite is intentionally split into separate sites so each workflow keeps its own source boundary, governance language, and operating context.
This hub keeps the conversation on department-owned workflow products rather than on a speculative cross-department platform.
The recommended path remains narrow and credible: build one operational workflow now, then use Invest Haryana / HEPC as the scale-up bridge later.
Portfolio anchors
Each site below corresponds to a department-owned workflow rather than to a generic AI platform claim.
Portfolio fit
Startup Haryana provides the strongest workflow proof-point because the public service already shows named document requirements, timelines, and a deficiency-removal window.
That makes the Startup build credible as a real officer-facing review layer rather than a conceptual AI front end.
Portfolio fit
PR Haryana already exposes a public release environment through PRMS, including release listings, language views, and downloadable release detail pages.
That gives the PR build a real public-source base for a briefing and background-note copilot.
Portfolio fit
The Tourism PMU RFP explicitly describes PMIS, dashboards, digital roadmap, data strategy, annual report support, and scheme monitoring scope.
That makes Tourism a valid second workflow build even though the live PMIS itself is not public.
Strongest recommendation
Startup Haryana Readiness Copilot should remain the strongest operational build because it sits directly on a published application service and checklist.
Invest Haryana / HEPC should remain the scale-up bridge only: the DNIT and corrigendum show an existing single-window operating context, not a greenfield platform pitch.
Cross-site posture
All three microsites remain static frontend prototypes with no backend persistence, no live departmental integration, and no cross-site runtime data exchange.
Each future production deployment would still require sovereign hosting, RBAC, audit trails, encryption, retention controls, and CERT-In-aligned review before any live workflow data is handled.
Deployable sites
The hub links outward to the working sites instead of embedding them as modules inside one shell.
Operational reference build
Officer-facing readiness review against the published Startup Haryana application structure, document list, timelines, and deficiency window.
Uses the public registration page, FAQ, and registration manual as the working backbone.
Standalone workflow site
Briefing-pack workflow based on public PRMS release pages, release metadata, language context, and human editorial review.
Uses the public PRMS listing and public release pages rather than an invented unpublished PR form.
Standalone workflow site
PMU review workflow grounded in the public RFP/TOR for PMIS, dashboards, digital roadmap, data strategy, and annual reporting.
Uses simulated workflow artifacts clearly derived from official public TOR requirements, not live Tourism data.