Phase 9 · Public production release 1.0.0

Public portal, controlled dynamic services.

The public portal has a production-capable service registry, validated application intake, acknowledgements and private status tracking. Intake remains closed until the competent authority activates an exact service record.

Public portal liveThe public portal is production-ready. No Zilla Parishad intake opens without a service-specific authorization record.

Dynamic service review matrix

Six controls, with clear ownership

Platform capability and service activation are reviewed separately. No service becomes open merely because the technical platform is available.

Service authorization

No service approved open

Approve the exact service, owner, authorization reference and opening window.

Review owner: CDO-cum-EO and responsible section
Current state: No service approved open

Form and eligibility rules

Platform ready; service record pending

Approve eligibility, fields, options, documents, declaration and acknowledgement copy.

Review owner: Responsible programme or establishment section
Current state: Platform ready; service record pending

Privacy and retention

Platform controls implemented

Approve purpose limitation, privacy notice, retention period and disposal process.

Review owner: Web Information Manager and competent data owner
Current state: Platform controls implemented

Operations and status updates

Operational nomination pending

Nominate processors, status-update procedure, timeline and escalation path.

Review owner: Designated service-processing section
Current state: Operational nomination pending

Technical production control

Public production capability ready

Confirm database migration, backups, abuse controls, monitoring and rollback procedure.

Review owner: Technical administrator
Current state: Public production capability ready

Public release

Public portal release requested; service activation separate

Maintain the public release record and authorize every service record separately.

Review owner: Competent Zilla Parishad publishing authority
Current state: Public portal release requested; service activation separate

Controlled dynamic boundary

The platform is live; collection stays authorization-led.

The database contains no seeded open service. A service appears only when its authorization, dates, approved fields, privacy notice, declaration, processing timeline and retention period all pass the activation gate.

Same-origin POST requests only
JSON content type and 32 KB request limit
Server-side allowed-field, type, option and length validation
Atomic recheck of service status and dates when writing
Idempotency key protection against accidental duplicate submission
Cryptographically random acknowledgement reference and tracking token

Service activation checklist

What must be confirmed before opening a service

The public portal release does not replace the competent authority's written service-activation process.

01
The D1 migration and three-table data model are approved for the authorized hosting environment.
02
Every activated service has a signed authority, owner, valid window and complete processing procedure.
03
Every published field is necessary, bounded and covered by the approved privacy notice.
04
Retention and disposal responsibilities are assigned before collecting any application.
05
Processors can update statuses without exposing submitted application data publicly.
06
Abuse monitoring, incident response, database backup and rollback responsibilities are recorded.
07
The acknowledgement and two-credential status lookup are accepted for citizen use.
08
File uploads remain disabled unless a separately reviewed R2 workflow is approved.
09
Public indexing and the custom-domain release are enabled; each service remains closed until written activation.

Approval roles

Service activation remains with government

The portal records roles and scope only. Names, signatures and dates should be entered in the department's authorized approval record.

CDO-cum-EO, Zilla Parishad

Institutional authority, service activation and publication decision

Pending

Responsible service section

Eligibility, fields, processing, status updates and service timeline

Pending

Web Information Manager

Privacy notice, content governance and public publishing record

Pending

Technical administrator

Database, deployment, backup, monitoring, security and rollback controls

Pending

Current release decision

Public portal live; hold service intake

A service-specific activation order and approved operating record are required before intake opens

Before opening any service

Create the reviewed service record with its exact authorization reference and dates.
Run the complete validation suite and record the immutable release identifier.
Verify processors, monitoring, backup, retention and incident contacts.
Publish only the exact approved service definition and preserve the activation record.