Niba Road
The information is scattered, the versions are confusing, and the process is memorized by people. The AI has to re-understand the background every time, and long tasks can easily get stuck.
Why after the emergence of strong models such as Claude Fable and GPT-5.6 Sol, some people have been racing all the way, while others still feel that they are not bad.
When a new generation of strong models such as Claude Fable and GPT-5.6 Sol appear, many people’s first question is: Do they need to upgrade now? Will it be too late? I'll look at one other thing first. Where have your knowledge base, workflow and knowledge flow been organized? The same supercar is completely different when driven on different roads. Who is
Anthropic’s Claude Fable and OpenAI’s GPT-5.6 Sol have different capability routes and delivery methods. What the two have in common is that the model can begin to handle longer and more complex knowledge work, research and tool operations.
As model capabilities continue to improve, the files, rules and workflows originally prepared by users will also more directly affect the final experience of use. Similarly, if you get a powerful model, some people can use it for long-term tasks, while others can still only use it for a single question and answer.
Official information:Claude Fable 5 ↗ OpenAI GPT-5.6 ↗
When automobiles were first invented, their speed and reliability did not necessarily surpass horse-drawn carriages immediately. Some people only see the comparison in front of them, while others begin to see another possibility: the car will continue to progress and the road will change accordingly.
When the road is still mud and gravel, the difference in feeling between a slower car and a faster car is limited. When the road surface turns into asphalt, the stability and speed of the car begin to be seen. Only when highways appeared did supercars really have room to perform. Strong models such as
The information is scattered, the versions are confusing, and the process is memorized by people. The AI has to re-understand the background every time, and long tasks can easily get stuck.
The files are centralized, the templates are fixed, and the input and output are clear. AI doesn’t have to understand you from scratch every time.
Data, knowledge, rules, permissions, acceptance and write-back are connected into a continuous operation path.
Mud Road can still use AI. General Q&A, single revision, and summary editing can still be done quickly. The problem occurs when the tasks start to become longer, the data starts to increase, and the judgment starts to become complicated.
At this time, the model can only guess the path on the loose ground. As the model becomes stronger, it can indeed guess more correctly. Without data, rules, and goals, it still doesn't have enough to work with.
The key to the asphalt road is to prevent the AI from understanding you from scratch every time.
Each project has a fixed folder, and the latest version of important information can be found.
There are templates, steps or checklists for each type of work.
AI knows where the input is, where the output is, and which step requires manual confirmation.
At this level, articles, briefings, meeting arrangements and research reports can begin to form a stable workflow. After the model is upgraded, it is easier to feel the difference because the tasks already have a clear route.
AI knows where to get facts and materials.
AI can see what it has done in the past and the reasons for its judgment.
AI knows what can be done by itself and what must be stopped to confirm.
Tasks have clear inputs, steps, outputs and handover methods.
After completion, you can check the file, format, link, number and status.
New judgments and lessons will be written back to the knowledge base or rule base.
After these structures are connected, AI has the opportunity to move from answering questions to taking over a piece of work.
I started using Obsidian in 2024, and later organized it all the way to driving engineering and loop engineering. This process has made me more and more certain of one thing: tools can be replaced, and my own files must continue to accumulate.
Moving costs are usually lower if the files are in common formats such as Markdown, plain text, CSV, etc. Change a set of AI, change an Agent, change a note-taking tool, and the originally organized content can still be used.
Facts, materials, experiences and judgments are also structured using folders, names and links.
The rules clearly describe the boundaries, and the process clearly describes how to start, complete and accept.
Articles, conferences, presentations, community recycling or project reports. Only when it happens repeatedly is it worth paving the way.
Confirm where the facts came from, which version is the latest, and where to return after finishing.
Write down the project goals, audience, common words, banned words, data location and completed appearance.
Add manual confirmation points, red lines and acceptance methods that can be inspected.
Observe where the AI misunderstands, misses information, and does the wrong order. Don’t rush to be fully automatic yet.
Add the deviations into the description, dictionary, process or acceptance checklist to make the next round smoother.
This is what I call a cycle project: input, execution, acceptance, correction, recording, and then entering the next round. Each round makes the road a little smoother.
Please help me take stock of this work and determine whether it is more like a dirt road, an asphalt road, or a highway. Job title: [fill in] Documents and data sources currently used: [Fill in] Current practice: [fill in] Results to be delivered upon completion: [Fill in] Please complete in order: 1. Identify areas where data sources are unknown, versions are confusing, and background is lacking. 2. Find judgments and steps that only exist in my mind and have not yet been written down. 3. Organize the work into inputs, steps, outputs, manual confirmation points, and acceptance methods. 4. Suggest which files need to be added or organized at least. 5. List the parts that will be handed over to AI in the first round, and the parts that will be temporarily retained for manual processing. 6. Finally give me a minimum paving list that can be completed in seven days. Don't just do full automation for me. First, clearly explain the current situation, gap and minimum next step.
Decluttering the environment can reduce model guessing, make tasks more stable, easier to repeat, and easier to change tools. It does not guarantee correct output every time.
After the road is paved, people still have to decide their destination, traffic rules and when to brake.
Stronger models are worth looking forward to. As the model improves, the amount of work we can hand over will indeed increase.
What can really be accumulated over the long term are your own files, knowledge, rules and workflow. When the road is still muddy, sort out a repetitive task first. When the asphalt road is paved, manual confirmation points and acceptance methods are added. When knowledge, processes, permissions and write-back are all connected, a stronger Agent can take over longer tasks.
Tacit knowledge refiner, AI application planner. Continuously organize practical methods of AI × knowledge management, control engineering and loop engineering.
If you want to organize your knowledge into a system that AI can help with, you can start with my knowledge structure.
Two free lectures every month to share practical experience and methodology.
Click me to join the LINE community ↗