Final Go-Live Evidence, Departmental Approval and Post-Launch Control Record
1. Purpose
This Pack records whether the complete Subkuz public architecture is ready for controlled production release. It is completed against the staging and production systems, not signed on the strength of documents alone. A blank, assumed or verbal approval is not acceptance. Each function identifies the reviewer, date, evidence and any exception.
2. Master completion statement
The public governance inventory contains sixty-eight instruments and one additional machine-readable security contact file. The developer implementation package contains eight controlling specifications and the accompanying registers, templates and validation files. The release owner confirms that the final live website, applications and public routes correspond to the current Master package and that superseded testing material is no longer presented as current.
3. Legal and corporate sign-off
| Check |
Status |
Evidence or exception |
| Corporate Legal Notice uses the locked company identity and official offices |
|
|
| Terms, jurisdiction language and statutory routes are approved |
|
|
| Ownership, ultimate beneficial ownership, funding and related-party disclosures are current |
|
|
| India grievance officer, contact, timing and escalation information are operational |
|
|
| Copyright, licensing, advertising and commercial terms are approved |
|
|
| No obsolete controller or legal entity remains in current pages or application screens |
|
|
4. Editorial sign-off
| Check |
Status |
Evidence or exception |
| All core editorial policies are live and linked through Policy Centre |
|
|
| Newsroom and author profiles identify accountable real people or authorised desks |
|
|
| Article labels and trust block work across every content type |
|
|
| Dates, bylines, edition and language are consistent in visible and machine fields |
|
|
| Corrections Register and correction request route are live |
|
|
| Investigations, fact-checks and anonymous-source work support methodology disclosures |
|
|
| Commercial content cannot be published through the independent-news workflow |
|
|
5. Privacy and data sign-off
| Check |
Status |
Evidence or exception |
| Controller and provider roles match contracts and live systems |
|
|
| Cookie inventory and consent choices match actual scripts |
|
|
| Optional tracking remains inactive before the required choice |
|
|
| Privacy and account-deletion forms work end to end |
|
|
| App permissions and store disclosures match released versions |
|
|
| Sensitive forms exclude advertising and session-replay data collection |
|
|
| Retention and deletion categories are assigned |
|
|
6. Security sign-off
| Check |
Status |
Evidence or exception |
| Administrator access is individual, least-privilege and protected by MFA |
|
|
| Backups exist and restoration was tested |
|
|
| Unused extensions and accounts were removed |
|
|
| Security Vulnerability page, form, inbox and security.txt are live |
|
|
| Secrets are not stored in documents or public code |
|
|
| Logs and incident escalation are active |
|
|
| Critical and high findings are closed or subject to approved protection |
|
|
7. Technical and search sign-off
| Check |
Status |
Evidence or exception |
| Every canonical URL in the registry returns the intended status |
|
|
| Every known redirect resolves in one hop |
|
|
| No redirect loop, soft 404 or conflicting canonical remains |
|
|
| Public pages, forms and archived policies carry the correct indexation directive |
|
|
| Main, news, page, author and edition sitemaps are valid |
|
|
| Hreflang is reciprocal and limited to complete equivalents |
|
|
| Article, author, organisation and breadcrumb schema validate |
|
|
| OAI-SearchBot is allowed and GPTBot follows the authorised licensing choice |
|
|
| Homepage duplicate components are corrected |
|
|
8. Accessibility sign-off
| Check |
Status |
Evidence or exception |
| Header, menu, article and footer operate by keyboard |
|
|
| Visible focus and logical reading order are present |
|
|
| Forms have labels, errors, confirmation and accessible alternatives |
|
|
| Cookie controls expose equal accessible accept and reject choices |
|
|
| Images, charts, audio and video have appropriate alternatives |
|
|
| Zoom, reflow, mobile layout and contrast pass the defined review |
|
|
| No third-party component blocks the core accountability routes |
|
|
9. Commercial sign-off
| Check |
Status |
Evidence or exception |
| Advertiser and ultimate client identification is required |
|
|
| Sponsored, Advertorial, Brand Studio and Partner labels are persistent |
|
|
| Paid links receive rel=sponsored |
|
|
| Prohibited and restricted category screening operates |
|
|
| No ranking, indexing, media-pickup or AI-citation guarantee appears |
|
|
| Commercial pages receive search-integrity review |
|
|
| Advertiser scripts comply with privacy, accessibility and security requirements |
|
|
10. Launch-day sequence
| Window |
Action |
| T minus 24 hours |
Final content freeze, database and media backup, restoration confirmation, monitoring activation |
| T minus 4 hours |
Staging smoke test, DNS and certificate review, owner availability confirmation |
| T minus 60 minutes |
Pause non-essential publishing and commercial changes; record deployment baseline |
| T zero |
Deploy templates and public instruments, connect forms, activate redirects and navigation |
| T plus 15 minutes |
Purge caches and run critical page, article, form, consent and administration tests |
| T plus 60 minutes |
Validate sitemaps, robots, schema, redirects, logs and email acknowledgements |
| T plus 4 hours |
Review errors, crawler access, form queue, duplicate components and security alerts |
| T plus 24 hours |
Issue first launch health record and decide whether rollback window can narrow |
| T plus 72 hours |
Complete enhanced monitoring review and record remaining medium or low defects |
11. Rollback triggers
- Incorrect legal, ownership, grievance, privacy or security information is live.
- Critical forms lose or misroute submissions.
- Public pages expose personal data, credentials, unpublished material or confidential-source information.
- Optional tracking activates contrary to the public consent model.
- Major article, policy or edition URLs fail or redirect incorrectly at scale.
- The homepage or major templates duplicate large content blocks or become unusable.
- Publishing operations cannot issue urgent verified news.
- A critical accessibility barrier blocks a complaint, privacy, security or consent route.
- A deployment creates a sustained security or availability incident.
12. Defect severity
| Severity |
Definition |
Release treatment |
| Critical |
Immediate legal, security, privacy, source, data-loss or publishing-continuity risk |
Rollback or immediate containment |
| High |
Material public inaccuracy, broken statutory route, widespread indexing or accessibility failure |
No-go unless fully protected and authorised |
| Medium |
Significant but contained usability, metadata, routing or consistency defect |
Time-bound written exception |
| Low |
Cosmetic or minor non-substantive issue |
Post-launch remediation with owner and date |
13. Monitoring record
| Metric or signal |
Owner |
Review frequency during first 72 hours |
| Server and application errors |
Technology |
Continuous alerting and scheduled review |
| Form receipts and acknowledgements |
Process owners |
At least every four hours |
| Security alerts and authentication failures |
Security |
Continuous alerting |
| Consent and script behaviour |
Privacy and technology |
After launch and after each cache or tag change |
| Redirect and 404 reports |
Search and technology |
At least twice daily |
| Structured-data and sitemap errors |
Search |
Daily |
| Article publishing, byline and date integrity |
Editorial |
Each major content type and daily sample |
| Accessibility reports |
Accessibility owner |
Daily and urgent escalation |
| Commercial labels and paid links |
Commercial compliance |
Every commercial publication |
14. Final acceptance certificate
The authorised signatories confirm that the evidence identified in this Pack has been reviewed, the live system corresponds to the current Subkuz Complete Master, all critical and high defects are closed, any approved medium exceptions are documented, the rollback and incident owners are available, and the release may enter normal controlled operation.
| Function |
Name and authority |
Decision |
Date and signature |
| Corporate and legal |
|
|
|
| Editorial |
|
|
|
| Privacy and data governance |
|
|
|
| Security |
|
|
|
| Technology and operations |
|
|
|
| Search and discovery |
|
|
|
| Accessibility |
|
|
|
| Commercial governance |
|
|
|
| Final release owner |
|
|
|
15. Thirty-day closure
At thirty days, the release owner records search coverage, redirect stability, form performance, response-timer performance, accessibility issues, security reports, consent defects, application-store alignment, commercial publication compliance and any policy correction. The launch programme closes only after the record identifies completed remediation, accepted residual risks and the owner of continuing annual transparency reporting.
| DOCUMENT CONTROL |
DETAILS |
| Issued by |
Subkuz Media Networks Private Limited |
| Corporate Identification Number |
CIN U72900JH2020PTC014521 |
| Document classification |
Developer implementation instrument |
| Effective date |
6 August 2026 |
| Last reviewed |
7 August 2026 |
| Previous legal name during statutory disclosure period |
Subkuz Media Networks Private Limited |