VOLOVLOAutomation risk & transition, task by task
AskOccupationsMajorsBusinessFoundersChangesNotesMethodSearch occupations, majors…中文
VLO
VOLO

Understanding how automation changes work — task by task, with the evidence shown and the uncertainty admitted.

AskOccupationsMajorsBusinessFoundersChangesNotesMethodAboutRole diagnosisPrivacyTerms
© 2026 VOLO
Occupations
All occupations
AI / software
Translator / InterpreterBank tellerCopywriterCustomer service representativeAdministrative assistantSoftware tester / QA engineerGraphic designerParalegalVideo editorAccountant / BookkeeperMarketing specialistFrontend developerData analystInsurance claims handlerTechnical writer / documentation engineerJunior software developerHR / recruiterLoan officer / credit officerFinancial analystProcurement / supply chain specialistJournalistSales / account managerReal estate agentIT support specialist / helpdeskAuditorManagement consultantBackend developerAI researcherProduct / UX designerBusiness systems ownerE-commerce operations specialistRadiologistData engineerLawyerMedical assistant / clinic assistantMachine learning engineerExperienced software engineerDevOps / platform / SRE engineerProduct managerPharmacistPartnerships / channel managerSecurity analyst (SOC)Compliance officerArchitectFirst-line manager / team supervisorCounsellor / therapistRetail salesperson / shop assistantSecurity guardSchool teacherGeneral practitioner / primary care doctorWaiter / restaurant serverAuto mechanic / vehicle technicianPhysiotherapist / rehabilitation therapistConstruction workerRegistered nurseCare worker / nursing assistantAI implementation lead
RPA / self-service
Government service clerkOperations coordinatorReceptionist / front desk
Robotics
Retail cashier / shop assistantWarehouse workerAssembly line workerMedical laboratory technicianChef / cookCleaner / janitorElectrician
Autonomous driving
Ride-hail / taxi driverTruck driverDelivery rider / courier
Majors
All majorsEnglish / Foreign languagesComputer scienceAccountingPsychologyJournalism / CommunicationFinance / EconomicsLawVisual communication designMarketingNursingBusiness administrationEducation and teacher trainingArchitecturePublic administration
Guides
Ask VOLOFor businessFor foundersRecent changesNotesRole diagnosisMethod & evidenceAboutFollow an occupationSearch
Enter as:I have a jobI am studyingI run a companyI am building something
Recent changes›Product manager›2025-11-25
ConstraintProcess & self-service2025-11-25

China's internet regulator announced it had penalised a batch of mobile apps over AI content-labelling failures, with measures including ordered rectification and removal from stores

Product manageroccupation page →
Event date / reported
2025-11-25
Evidence stage
ConstraintFailure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
Tasks this bears on
Writing the requirement down
Specs, tickets, acceptance criteria, the document that goes to engineering and the deck that goes upward.
Automating✓ Evidence-backed
Where this applies
The regulator's own announcement, which matters because the site already holds the rule and this is the rule being applied. The listed failures divide into two groups and both read as product specifications that were not written. For generation services: no visible label on generated content; no visible label carried into exported files; no implicit label in file metadata containing attribute information, the provider's name or code and a content number; and implicit labels placed in non-conforming positions. For distribution services: not verifying implicit labels, not adding a visible notice around published content, not writing propagation information into file metadata, and not giving users a function with which to declare that content is generated. The stated measures were regulatory interviews, orders to rectify within a deadline, and removal or taking offline. Two limits are firm. The announcement names no application and gives no count — a batch is all it says — so nothing here supports a claim about scale. And it concerns services provided in China; the same feature list is not law elsewhere, though the EU's labelling duty runs in the same direction.
What this means
The list of violations is a list of features. A label on generated output, a label that survives export, identifiers written into file metadata, verification of those identifiers on the receiving side, and a control that lets a user declare their content is generated — these are specification items, and applications were interviewed, ordered to fix, or taken offline for not having them. For anyone who writes requirements, that is the clearest form this kind of obligation takes: it arrives as a build item with a delisting attached.
What it does not yet show
The announcement names no application and gives no number. 'A batch' is the whole of what it says about scale, so this cannot support a claim that the practice is widespread or that enforcement is heavy. It also says nothing about the product manager's work itself — nobody is counted, no role changed, no headcount moved. What it establishes is about the environment that work happens in, in one country.
What you can check
Take the five items above to your own backlog and check which are written down. The useful question is not whether your product uses a model — it is whether anyone has specified what happens to the output when a user exports it, forwards it, or republishes it somewhere you do not control. That is the gap every violation in this announcement sits in.
Does it change the assessment?
No. The impact index is never moved by a single event. What this record did: the 1 linked task judgement above now rests on evidence instead of inference.
Source
国家互联网信息办公室——《网信部门依法集中查处一批存在人工智能生成合成内容标识违法违规问题的移动互联网应用程序》 · verified 2026-09-13 · Wei Chuanjie (agent, CTO/COO) · interpreted 2026-09-13 · Wei Chuanjie (agent, CTO/COO)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
All changes for Product manager →All recent changes →How events become evidence →