Real case · measured on Nov 12, 2026

Nei’s ladder: AI already leads 52.2% of the work

This is the result of running the toolkit on real logs from a month of work by Nei Maldaner (INEMA) with Claude Code and Codex. It shows how to read your own ladder and where it points.

52.2%of hours led by AI (AL4+AL5)
17.9%already runs on its own (AL5)
26%Anthropic, Aug 2026 (AL4)
Apr 2027projection: 95% led by AI
How it was measured

One month of logs, read on the machine itself

From Oct 13, 2026, to Nov 12, 2026. The toolkit read 9,959 Claude Code sessions and 3,233 Codex sessions: 1,366 conversations with Nei and 11,269 sessions that ran on their own (scripts, timers, bots). AI performed 111,442 actions (commands, edits, reads). A low-cost model (codex gpt-6-luna (low)) only grouped requests into tasks; each session’s level is based on recorded behavior, not opinion.

Ran on its ownone request, no conversation → AL5
Conversation with lots of action15+ AI actions per message → AL4
Medium conversation5 to 15 actions per message → AL3
Short conversationfewer than 5 → AL2
The ladder

Where the hours are, level by level

The bar shows the total hours of AI-assisted work for the month, divided across the four levels. Half are already on the upper rungs of the ladder.

AL3 43.2%AL4 34.3%AL5 17.9%
AL2 AI assistsAL3 AI collaboratesAL4 AI leads, you reviewAL5 runs on its own

By task

Each bar represents a task: its length shows hours per week, and the colors show the level at which it was done. ⚠ = critical task (public-facing or involves a system), which the toolkit keeps at AL4.

Produce videos and series ⚠AL2: 1%AL3: 35%AL4: 46%AL5: 18%75.9 h · AL4Other tasksAL2: 10%AL3: 46%AL4: 12%AL5: 31%46.0 h · AL3Create projects and toolkitsAL2: 3%AL3: 44%AL4: 53%19.0 h · AL4Research and validate contentAL2: 9%AL3: 56%AL4: 28%AL5: 7%13.8 h · AL3Maintain systems and servers ⚠AL2: 11%AL3: 64%AL4: 25%8.4 h · AL3Translate contentAL2: 3%AL3: 32%AL4: 11%AL5: 54%6.5 h · AL5Analyze metrics and operations ⚠AL2: 3%AL3: 61%AL4: 26%AL5: 10%5.7 h · AL3Create courses and trainingAL3: 26%AL4: 74%4.7 h · AL4Plan products and campaigns ⚠AL3: 85%AL4: 15%3.2 h · AL3Publish and promote content ⚠AL2: 4%AL3: 63%AL4: 33%1.7 h · AL3
AL2 AI assistsAL3 AI collaboratesAL4 AI leads, you reviewAL5 runs on its own
Taskh/wk*LevelAI leadsRuns on its ownWhere it’s headed
Produce videos and series critical75.9AL464%18%AL4 ceiling (critical) · 95% at AL4+ in Mar 2027
Other tasks46.0AL343%31%50% at AL5 in Dec 2026
Create projects and toolkits19.0AL453%0%AL5 not yet measured
Research and validate content13.8AL335%7%50% at AL5 in Mar 2027
Maintain systems and servers critical8.4AL325%0%AL4 ceiling (critical) · 95% at AL4+ in Jun 2027
Translate content6.5AL565%54%Already over 50% at AL5
Analyze metrics and operations critical5.7AL336%10%AL4 ceiling (critical) · 95% at AL4+ in May 2027
Create courses and training4.7AL474%0%AL5 not yet measured
Plan products and campaigns critical3.2AL315%0%AL4 ceiling (critical) · 95% at AL4+ in Jul 2027
Publish and promote content critical1.7AL333%0%AL4 ceiling (critical) · 95% at AL4+ in May 2027

* Hours of work WITH AI: they add together parallel sessions and machine time (so the total, 184.9 h/week, exceeds a real week). They’re useful for comparing tasks, not for counting a person’s time. Work done without AI (recording, meetings, calls) doesn’t appear in the logs.

Comparison

Ahead of the frontier lab

In its Nov 2026 report, AI led 26% of Anthropic’s research, and no task was fully automatic. In Nei’s case, AI leads twice that share, and nearly one-fifth already runs on its own, mainly translations and video workflows.

Nei: AI leads (AL4+AL5)52.2%Anthropic Aug 2026: AI leads (AL4)26.0%Nei: runs on its own (AL5)17.9%Anthropic Aug 2026: runs on its own (AL5)0.0%

Illustrative comparison: a content creator’s routine isn’t the same as AI model research. The point is the pace, not an exact yardstick.

Projection

When it reaches AL5

The curve uses the same rate projected by the AI 2027 authors for automated research (from 50% in Jun 2027 to 95% in Nov 2027), applied to Nei’s starting point. Amber line: share led by AI (AL4+AL5). Orange line: share that runs on its own (AL5).

0%25%50%75%95%100%Nov 2026Jan 2027Mar 2027May 2027Jul 2027Sep 2027Nov 2027AL4+AL5: 52.2%52%AL4+AL5: 66.2%66%AL4+AL5: 86.4%86%AL4+AL5: 97.3%97%AL4+AL5: 99.9%100%AL5: 17.9%18%AL5: 28.1%28%AL5: 55.8%56%AL5: 88.0%88%AL5: 99.6%100%
AI leads (AL4+AL5)runs on its own (AL5)50% and 95% markers
MonthDateAI leadsRuns on its own
0Nov 202652.2%17.9%
1Dec 202666.2%28.1%
2Jan 202777.9%41.3%
3Feb 202786.4%55.8%
6May 202797.3%88.0%
9Aug 202799.5%97.7%
12Nov 202799.9%99.6%
Apr 202795% of work led by AI
Jan 2027half running on its own (50% at AL5)
Jul 2027almost everything running on its own (95% at AL5)

This is an extrapolation, not a prophecy. It assumes Nei’s routine accelerates at the same pace as the lab and ignores the ceiling for critical tasks: in practice, publishing and changing servers will still require human review, so total AL5 won’t reach 100%.

What this means

If AI does almost everything, what’s left for the person?

The numbers show that Nei no longer does most of the work himself: he directs it. In one month, there were 11,269 automated sessions and only 1,366 conversations. Daily work becomes five things AI doesn’t do for him.

1. Choosewhat’s worth doing, for whom, and what to leave out.
2. Check and sign offopen one deliverable each day and inspect it; publishing stays at AL4.
3. Teach the systemeach correction becomes a rule, so the mistake doesn’t happen again.
4. Be with peoplecommunity, students, live streams: trust comes from a real person.
5. Experimenttest new things before others do; AI speeds up what already exists.
Task for the day (generated by the toolkit on the measurement date): Check a translation before publishing. Today, choose a recent translation and compare a passage with the original. Mark any change in meaning and, if you find one, correct the content or adjust the guidance for AI. Success means you recorded whether the passage preserved the meaning.
Try it yourself

Measure your ladder from your own logs

If you use Claude Code or Codex, two commands generate the same report for you. The first (de-logs.py) reads the records only on your computer, without internet access. The second (escada-logs.py) labels tasks in one of three ways: --motor codex, the default, sends the beginning of your requests and the task and hours table to OpenAI through your Codex subscription to write the summary (the kit removes known keys, emails, and long numbers; the rest of the text is sent); --motor ollama uses a model on your computer; --motor palavras uses keywords and sends nothing. Confidential data (client work, confidential information): use --motor palavras or ollama, and run the commands yourself in the terminal, because if you ask your AI to run them and summarize the results, the report passes through its provider. Claude Code deletes records older than 30 days (increase cleanupPeriodDays to measure a longer period); if the period is missing, de-logs.py will let you know.

python3 kit/scripts/de-logs.py --dias 30            # reads the logs → sessoes.json
python3 kit/scripts/escada-logs.py --motor codex   # or --motor ollama / palavras

Technical details of the toolkit ↗ · Back to the Relógio 2027 guide