DOC #069 03_DEVELOPER_IMPLEMENTATION

SUBKUZ COMPLETE WEBSITE REPLACEMENT AND CONTROLLED LAUNCH MANUAL

Subkuz Global Governance Framework | Issued by Subkuz Media Networks Private Limited (CIN: U72900JH2020PTC014521)

Document #069 | Verified Master Version

Authoritative Release Sequence for the Global Public Governance, Newsroom, Commercial and Technology Architecture

1. Status and controlling authority

This Manual is the controlling developer and release-management instrument for replacing the testing-stage public governance, newsroom identity, commercial disclosure and contact architecture on Subkuz.com. It is not a public policy and must not be published as reader-facing content. The public website copies in the Complete Master package remain the controlling text for readers. Where an implementation instruction appears inconsistent with a public instrument, the release team must stop and obtain a documented decision rather than altering the public meaning silently.

The completed public architecture contains sixty-eight public instruments: eighteen core policies and procedures, thirty-six supporting public pages, notices, directories, centres, standards, registers and reports, and fourteen working public forms. A machine-readable security contact file is additional to that count. This Manual coordinates those instruments with the article system, edition system, applications, search controls, contact routing and launch governance.

2. Non-negotiable launch principles

  • No mixed state: obsolete policies, old controller notices and new pages must not remain simultaneously presented as current.
  • No fabricated scale: staff, editions, cities, languages, audience, technology, offices and performance claims must remain consistent with the locked corporate and operating records.
  • No invisible commercial influence: sponsored, advertorial, Brand Studio, partner and paid-publication material must remain visibly separate from independent journalism.
  • No artificial recency: migration, copyediting or metadata repair must not create a new editorial publication date.
  • No inaccessible accountability route: grievance, correction, privacy, copyright, accessibility and security routes must remain available without a paid account.
  • No search-only city pages: every indexed city or edition page must have an authorised purpose, useful content and a place in the edition directory.
  • No deployment without rollback: databases, media, configuration, redirects and forms must be restorable to a tested point.
  • No live promise without an operating owner: every response time, form, inbox and public register requires an assigned primary and backup function.

3. Release governance and decision rights

Function Final authority before launch Required evidence
Corporate and legal Authorised corporate and legal signatory Company particulars, notices, terms, statutory contacts and approved public identity
Editorial standards Publisher or authorised senior editorial authority Policies, labels, author structure, article trust components and correction system
Privacy and data governance Authorised privacy owner Controller map, purposes, vendors, consent, retention, rights routes and application disclosures
Security Authorised security owner Asset inventory, access controls, backups, incident route, vulnerability process and security.txt
Technology and operations Technical release owner Staging acceptance, database backup, redirects, forms, templates, monitoring and rollback
Search and discovery Search implementation owner Canonical URLs, schema, sitemaps, robots, hreflang, indexation and Search Console validation
Accessibility Accessibility review owner Keyboard, screen-reader, contrast, forms, captions, consent and document checks
Commercial governance Authorised commercial owner Advertiser standards, paid-content labels, link treatment, claims review and form routing

4. Required environments and access controls

The release must be assembled in a staging environment that is technically representative of production. Staging must be protected from public indexing through authentication or network access control, not by relying only on robots.txt. Production credentials must not be shared through ordinary documents or messaging. Each person receives an individual account with the minimum role required, and multi-factor authentication is enabled for domain, hosting, content management, source control, email administration, analytics, search consoles, consent management and application stores.

Before any deployment, the release owner records the production software versions, active extensions, theme, database version, scheduled tasks, integrations, advertising scripts, analytics, consent platform, application programming interfaces and external providers. Unused extensions, dormant administrator accounts and abandoned integrations are removed or disabled before launch.

5. Pre-deployment evidence pack

1. Create a complete database backup and a separate verified media backup.

2. Export the current URL inventory, response codes, canonicals, titles, indexation directives, language paths and inbound links available from analytics and search consoles.

3. Capture screenshots or rendered copies of the current footer, header, policy pages, forms, article template, author pages, city selector and application privacy screens.

4. Record the current sitemap and robots configuration even where it is defective or inaccessible.

5. Freeze public governance copy during the final staging cycle. Any later text change requires version control and re-test.

6. Test restoration of the production backup in an isolated environment.

7. Record the rollback decision-maker and an available technical operator for the complete launch window.

6. Current-site defects requiring correction in the same controlled release

The public homepage presently exposes repeated horoscope blocks, outdated footer links, testing-stage policy pages, inconsistent language placement and institutional claims that are repeated across unrelated pages. The launch must correct the underlying rendering or data loop rather than hiding the duplicate output cosmetically. The homepage, category pages and city pages must be tested for repeated components, runaway queries, duplicated identifiers, layout instability, page-weight inflation and structured-data repetition.

Testing-stage English pages that are currently placed within Hindi URL paths must be replaced or redirected under the canonical structure. Generic or template newsroom roles must not remain presented as named appointments. Old privacy and terms pages identifying a different controller or obsolete legal arrangement must be removed from current navigation and redirected to the authoritative versions. All repeated promotional statements must be limited to locations where they serve a genuine explanatory purpose and must link to the Network Facts and Media Architecture page.

7. Controlled deployment order

Sequence Deployment action Release gate
1 Freeze content and configuration, create final backups and enable heightened logging Backup restoration test passed
2 Deploy common templates, accessibility components, trust block, author profile template and article labels Template QA passed on desktop and mobile
3 Publish the sixty-eight public instruments without adding them to navigation yet All URLs return the intended status and content
4 Connect fourteen forms to reference generation, routing, secure storage and acknowledgements End-to-end test submissions received by primary and backup functions
5 Deploy canonical, hreflang, robots, sitemap and structured-data changes Validation tools show no critical errors
6 Activate redirects and verify every known legacy institutional URL No chain, loop, soft 404 or language mismatch
7 Replace header, footer, Policy Centre, article links and contact routes Navigation acceptance complete
8 Remove or archive superseded testing pages and regenerate sitemaps No obsolete current page remains indexable
9 Purge caches and content-delivery layers, then execute production smoke tests Critical user journeys pass
10 Submit sitemaps and selected priority URLs through official search tools Monitoring active and rollback window open

8. Production acceptance journeys

  • A reader can open About Subkuz, Newsroom, Ownership, Privacy, Terms, Grievance, Corrections, Copyright, Accessibility, Security and Policy Centre from the footer.
  • A reader can identify the content classification, author or desk, edition, language, publication time, update time and correction route on an article.
  • A grievance, correction, privacy, copyright, accessibility and security submission receives the correct reference and acknowledgement.
  • A screen-reader and keyboard user can reach and operate the menu, article, forms, consent controls and footer.
  • A search crawler can reach current public pages, read noindex on forms, and discover the main and news sitemaps.
  • A commercial page clearly identifies the payer, production relationship and paid-link treatment where applicable.
  • A translated or cross-edition page identifies its original edition and uses reciprocal hreflang only when both versions are complete.

9. Go or no-go rules

The release is no-go if any high-severity condition remains: an incorrect legal entity or contact, a non-working statutory grievance route, an unprotected administration account, a consent tool that activates optional tracking before the required choice, an unverified redirect affecting major indexed pages, a broken article byline or date system, missing backups, exposed credentials, a critical accessibility barrier in an accountability route, or a production error that duplicates large blocks of content.

Medium-severity defects may proceed only under a written exception that identifies the owner, temporary protection, public effect and completion date. Cosmetic issues may be scheduled after launch only where they do not affect meaning, rights, security, accessibility, indexation or public trust.

10. Rollback and preservation

Rollback is required when the release creates widespread server errors, form loss, inaccessible core navigation, incorrect legal or privacy text, broken article URLs, redirect loops, data exposure, uncontrolled optional tracking, inability to publish urgent news, corrupted structured data at scale or another material public risk. Rollback must restore the database, files, configuration and cache state as one coordinated action. Redirect rules and schema must not be rolled back independently where doing so would create a contradictory state.

Evidence of the failed release is preserved before rollback where safe: logs, screenshots, request identifiers, affected URLs, deployment commit, database timestamp and observed impact. Public correction or incident disclosure is considered where readers, sources, applicants, complainants or commercial users received materially incorrect information or their submissions may have been lost.

11. First seventy-two hours and stabilisation period

For the first seventy-two hours, the release team monitors server errors, form acknowledgements, email routing, consent choices, search crawler access, redirect failures, sitemap processing, structured-data errors, author links, live-news publishing, page speed, duplicate content, security alerts and accessibility reports. A named operator is available to disable a defective component without removing the entire public accountability architecture.

The first seven days include a crawl comparison against the canonical registry and a review of indexed legacy pages. The first thirty days include a correction of non-critical defects, validation of search-console coverage, review of application-store privacy alignment, form-response performance and publication of any material policy correction through the Change Log.

12. Completion standard

The controlled launch is complete only when all sign-off sheets are approved, the public index matches the live website, every required form has completed an end-to-end test, the redirect register has been verified, the current sitemaps have been accepted, machine-readable files are reachable, the old controller and policy pages are no longer presented as current, and the launch monitoring period closes without an unresolved critical defect. Completion is an operational state, not the upload of documents alone.

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