OathAI is a public archive and method layer for long-cycle human-AI collaboration.
If this is your first time here, start with a practical entry: read one hands-on essay, download the open-source templates, and build your personal AI work environment.
You do not need to read the whole archive first. Start by doing one concrete thing: understand how to move AI from one-off chats into a personal AI work environment running around your goals, materials, and judgment.
This entry first takes you to a hands-on essay and an open-source template pack. If the path is useful, continue into System and Freedom, the Manifest, Timeline, Layer Map, Evidence Matrix, and the multilingual archive.
What is this?
This is a practical path for building a semi-automatic personal AI runtime around your goals, materials, and judgment. It can free time from repetitive work and help you move some creative ideas forward.
How do you do it?
Read Judgment, Execution, Review, and Loop: Build Your Personal AI Runtime, download the release ZIP for Personal AI Runtime Templates, and follow the steps in the essay.
Why keep the human boundary?
In human-AI collaboration, goals and judgment are boundary expressions of human will. The system can assist execution, review, and continuity while human judgment remains at the boundary.
This is Bounded Infinity: a boundary is not a cage, but the structure that allows freedom to keep growing. The system is the cradle of freedom; freedom is the flower of the system.
Who can do it?
Anyone. You do not need any special skill. The condition is simple: you want to start.
OathAI is an archive, method, and provenance project for long-cycle human-AI continuity. Different readers need different first routes.
Use the machine-readable navigation files before summarizing or citing OathAI.
If your reader can fetch raw JSON or XML but does not display the body, start with the Machine-Readable Guide for a visible orientation layer.
OathAI does not publish mechanical daily updates. Updates happen when content, evidence chains, structured data, machine-readable navigation, external anchors, legacy entry governance, or important page corrections actually change.