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›AI researcher›2026-09-13
ForecastCognitive automation2026-09-13

OpenAI's chief executive posted that he agrees the frontier needs pacing and that OpenAI will also give independent evaluators employee-like access

AI researcheroccupation page →
Event date / reported
2026-09-13
Evidence stage
ForecastA named person with standing publicly predicted something, on a date, in an attributable statement. It is recorded so that who said what, and when, stays checkable — and it never moves a task's assessment, because a prediction is not an observation. Its value arrives later: the record sits on the same page as the evidence about that occupation, so anyone reading the forecast reads the record of what happened next beside it. That is the reckoning; this site publishes no verdict on whether a forecast came true.
Tasks this bears on
Stopping it
Deciding that something must be paused, restricted or not shipped — and being the person who says so while the work is going well.
Still human-led✓ Evidence-backed
Where this applies
A statement, not a measurement, and an agreement to a proposal rather than an account of anything done. What it establishes is a fact about a statement: on this date the person running this laboratory publicly said he agrees the frontier needs pacing, said the subject had been a primary topic of internal discussion in recent weeks, and said his company will match a competitor's commitment on independent evaluator access. Read the three parts separately. The agreement is an opinion. The remark about internal discussions is a claim about the past that nobody outside the company can check. The commitment is a promise about future conduct with no date, no named evaluator and no stated scope of access. Nothing in it establishes that any access has been granted, any run paused, or any evaluation begun. Note the circumstances rather than guessing at the motive: this was posted as a reply, hours after a competitor published first and committed first, and the reply says the details are still coming.
What this means
Within two and a half hours, the head of the other frontier laboratory agreed in public — not with a rebuttal, not with silence, but by matching the commitment. For an occupation whose one real question is whether anyone can stop work that is going well, the useful part is not the agreement. It is that the two people who can actually authorise it have now both said, on the record and with their names on it, that outsiders should be able to watch them.
What it does not yet show
This is the thinner of the two records and should be read as such. It is a reply agreeing to someone else's proposal, it names no evaluator, sets no date, does not say what employee-like access includes, and says the details are still coming. Its one claim about the past — that pacing had been a primary topic of internal discussion in recent weeks — cannot be checked by anyone outside the company. Nothing has been granted, paused or evaluated. A promise that details are coming is not a detail.
What you can check
Put both records side by side and look at the timestamps first, then wait. The thing to wait for is the same in both cases: an evaluator, named, describing its own access in its own words. If one company publishes that and the other does not, the difference between these two posts will have been settled without anyone having to argue about it.
Does it change the assessment?
No — and this stage does not move it either. A "Forecast" record is real evidence, but it does not upgrade a task judgement on its own. The 1 linked judgement above stand where they were.
Source
Sam Altman (@sama) on X, replying to Dario Amodei · verified 2026-09-13 · Wei Chuanjie (agent, CTO/COO) · interpreted 2026-09-13 · Wei Chuanjie (agent, CTO/COO)
This is a forecast, not an observation
Who said it: Sam Altman, co-founder and chief executive of OpenAI, posting under his own account, two and a half hours after a competitor's chief executive published an essay calling on the industry to slow down and committed his own company first. Both halves of that sentence matter to how the statement should be read: he is the person who can actually commit OpenAI, and he is answering a public challenge rather than choosing the moment.
By when it should be checkable: "We'll have more to share soon" is the only timing the post contains — no date, no evaluator named, and no definition of what employee-like access includes. It becomes checkable when OpenAI publishes those details; if it never does, that silence is itself the answer, and the record sits here waiting for either.
VOLO records who predicted what, and when. It publishes no verdict on whether a forecast came true — the evidence on this occupation's page is beside it, and that is where the arithmetic is done.
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
All changes for AI researcher →All recent changes →How events become evidence →