> For the complete documentation index, see [llms.txt](https://riu-salze-studio.gitbook.io/cosmic-horizon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://riu-salze-studio.gitbook.io/cosmic-horizon/cosmic-horizon-start-here.md). # Cosmic Horizon: Start Here **Language:** English | [한국어](/cosmic-horizon/cosmic-horizon-start-here-kr.md) > **Are you using AI?**\ > Really? > > **Do you trust what it produces?**\ > Really? > > **Have you inspected what it changed, what it broke, and what you are now responsible for?**\ > Really? > > *** > > AI can now produce code faster than humans can verify it. > > **Cosmic Horizon** is a map for the work that remains human: judgment, verification, recovery, and responsibility. ## What Cosmic Horizon Means In astronomy, the cosmic horizon is the outer boundary of the observable universe: the farthest limit from which signals can still reach us. In this orbit, **Cosmic Horizon** names the entire observable world of AI-assisted development as I experience it—encompassing code, tools, prompts, documents, judgment, verification, recovery, and responsibility. It is the boundary line where raw technical signals meet the human decisions that hold them together. ## What This Archive Is Cosmic Horizon is an essay-driven engineering archive for turning observations about software, AI-assisted work, and human judgment into coordinates that can be understood, refined, and returned to. It focuses on structure, constraints, verification, recovery, and responsibility in software work shaped by AI. ## Who This Is For This archive is for developers, technical leads, and architecture-minded practitioners who work with AI without giving up structure, judgment, or responsibility.\ It is also my own landmark for returning to origin whenever the speed of my thinking outpaces observation. ## Reading the Metaphors > A month of typhoons in the China Sea, a cracked mainmast, and a crew on half-rations. > > Yet, it is all settled the moment the first chest is opened in London. > > One sip of that black tea, and you realize the ocean was never our master. This archive speaks in the language of navigation, orbit, signal, rations, and return. These terms compress the raw, complex realities of engineering: uncertainty, constraints, drift, recovery, judgment, and responsibility. They serve as a precise vehicle to carry technical weight across different minds, roles, and depths of knowledge. I enjoy reinterpreting my own understanding and reframing it for others. If these metaphors fail to land, it is simply because our focal points and perspectives diverge. *That, too, is by design.* What is your domain of choice? Bring it forward, and I will gladly re-map it into the metaphors of your own world. *This, too, is by design.* ## How to Read This Archive These pages may resemble essays at first glance, but they are more accurately understood as a **map**. This archive does not need to be read from beginning to end like a book. It is a map to reopen when a coordinate needs to be checked again. Some entries present perspective. Some define operating models. Others serve as field notes, templates, reusable records, and navigational instruments for the next round of execution. Many entries in this archive are case-driven. They begin with field friction, experiments, conversations, tools, or failures.\ Those observations are compressed into language, then branch into operating models, protocols, cases, templates, and reusable records. Rather than attaching examples to abstract principles, this archive turns lived cases into coordinates that can be returned to. ## Why This Archive Is Written Documentation is not debris left after thought.\ It is the act of turning the observation of an unfamiliar signal into a firm coordinate. I write this archive so that insight does not disappear as a passing reaction.\ When I observe something, I try to understand it.\ When I understand it, I try to declare it in a form I can return to. These pages are coordinates for returning to origin. When judgment moves too fast, when language becomes vague, or when AI accelerates work faster than responsibility can follow, this archive becomes a landmark for returning to origin. ## How This Archive Moves * Start with [Ride, Don’t Race](/cosmic-horizon/perspective/ride-dont-race.md) if you want the philosophy behind this archive. * Read [AI-Assisted Development Models](/cosmic-horizon/operating-system/ai-assisted-development-models.md) if you want to understand the operating model. * Read [FTL-Bound Agents](/cosmic-horizon/operating-system/pattern-ftl-bound-agents.md) if you want to design AGENTS.md, CLAUDE.md, or similar agent instruction files as boundary systems for AI-assisted work. * Explore [Codex Chat Viewer](https://github.com/RGJ-sw1123r/codex-chat-viewer) if you want to see an earlier practical artifact from this orbit: a local-first viewer for Codex CLI session logs, built to inspect, review, document, and revisit AI-assisted work. A newer version continuing this direction has since been released as [Codex JSONL Observatory](https://github.com/RGJ-sw1123r/codex-jsonl-observatory), extending the work from transcript viewing into versionable worklog bundle export. * Read [Why My Ship Is Ivory](/cosmic-horizon/operating-system/case-why-my-ship-is-ivory.md) to see how this archive turns an actual Figma MCP and Codex experiment into a record of execution, verification, and changing work boundaries. ## Links * GitHub: [@RGJ-sw1123r](https://github.com/RGJ-sw1123r) * LinkedIn: [Riu Salze](https://www.linkedin.com/in/riusalze) * Published Site: [Visit Cosmic Horizon](https://riu-salze-studio.gitbook.io/cosmic-horizon/) ## How to cite *Cosmic Horizon* was written and structured independently. Some surrounding themes may overlap with broader public discourse, but this archive does not claim ownership over general AI-assisted development discourse, third-party tools, public design materials, or concepts that may already exist elsewhere. When quoting, summarizing, adapting, or referencing this archive’s original naming, metaphors, terminology, structure, boundary models, documented patterns, or blueprints, please provide visible attribution. **Preferred citation:** > Riu Salze. (2026). *Cosmic Horizon*.\ > Published archive: \ > Repository: \ > License: CC BY-NC-SA 4.0 For detailed license terms, see the section below. ## License This work is licensed under [CC BY-NC-SA 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/). Cosmic Horizon is shared as a non-commercial, share-alike archive. You may read, share, quote, translate, and adapt this archive for non-commercial purposes, provided that proper attribution is given, changes are indicated where applicable, and adapted material remains under the same license. Commercial use, paid redistribution, paid training material, consulting material, productized reuse, or incorporation into commercial products or services requires prior written permission. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://riu-salze-studio.gitbook.io/cosmic-horizon/cosmic-horizon-start-here.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.