**The research becomes the doc becomes the deck becomes the app – and you still have five…
· Info Inlet
**The research becomes the doc becomes the deck becomes the app – and you still have five files and a chat log to reconcile** You start a project in a research tool, highlight a few key points, then copy them into a document. The document becomes a deck for a review. After the review you rewrite the deck into a spec, then the spec turns into code. Meanwhile you’re bouncing between Slack threads, a meeting transcript, and a notes app. At any point if someone asks “Why did we pick that approach?” you have to dig through three tools and a chat history that’s now a week old. The work is fragmented the moment it leaves your head. **The five-file shuffle** Every developer knows this flow. Research in Notion or Obsidian. Draft in Google Docs. Slides in Keynote or Google Slides. Code in VS Code. API docs in a browser tab. Then the chat log with your teammate who had the insight about the database schema. The connections between all those pieces live only in your memory or in a comment somewhere. When you need to revisit the reasoning behind a decision, you end up searching through five different places. This isn’t just a friction problem. It’s a context problem. The research that led to the doc, the doc that led to the deck, the deck that led to the app – each step loses information. The next person who picks up the project has to reconstruct the chain from scraps. **How it usually goes** Let me trace a typical week. Monday: you read three articles about vector search and take notes. Tuesday: you write a brief doc comparing two approaches. Wednesday: you build a slide deck to present to the team. Thursday: you decide on one approach and start coding. Friday: you realise the deck had a cost comparison that the code assumed was different. So you go back to the deck, check the doc, re-read your research notes, and find the discrepancy. That’s thirty minutes of archaeology for one data point. Over a month that adds up to hours of reconciliation. And the worse part – the exploration you did on Monday that led to a dead end? That knowledge is lost. The next person might go down the same dead end because your notes are buried in a different folder. **One thread from research to app** Xenition approaches this differently. Instead of being another tool that holds text and expects you to paste it somewhere else, it opens the real thing. Describe what you want in a conversation. Ask for a comparison of vector databases, and it opens a spreadsheet with the comparison. Ask for a landing page, and it opens a working one with a database behind it in minutes. Ask for a slide summary of that same comparison, and it opens a deck that is a live view into the same research. The key is that everything is one piece of work with a history. The research becomes the doc becomes the deck becomes the app. Not five files and a chat log to reconcile. One evolving thread. When you change the research, the deck updates. When you update the code, the doc can reflect it. The chain of decisions stays intact because nothing was ever copied and pasted out. **Real example: from idea to working app** You have an idea: a simple tool to track team stand-ups. You describe it to Xenition. It opens a document explaining the approach. You say “make it a single-page app with a text input and a timeline”. It opens a working app – real HTML, CSS, JavaScript. You inspect the code, modify it directly. You say “add a database so entries persist”. It opens a database schema and links it to the app. You test it. You say “turn this into a slide deck for the team”. It opens a deck with the architecture, screenshots, and rationale – all drawn from the same work. No pasting. No context switch. The research that led you to pick SQLite over Firebase? It’s in the history. The reasoning behind the UI layout? In the comments of the code that were generated alongside the first version. Everything is connected because everything lives in the same workspace, not separate tools. **What’s under the hood** I can’t give you a technical deep dive because Xenition is still new and I only know what I see. But the principle is clear: instead of building a chat interface that spits out text you then have to move, it directly opens the applications you already use. Spreadsheets, documents, code files, slides, databases. It creates real, editable things. You can keep working in them with or without the AI. The AI just gets you to a working state faster. And because all those things are born from the same conversation, they share a lineage. That lineage is the history of your project. You can go back to any point and see why a decision was made, because the research and the output are stored as one evolving piece of work, not as separate exports. **No pasting, no losing context** The biggest difference is that you never lose the context of why something exists. When you copy a paragraph from a research note into a doc, you lose the reference. When you paste a code snippet from an AI chat into your editor, you lose the surrounding reasoning. Xenition keeps the reasoning attached. The app knows it was built from the doc, which came from the research, which came from a question you asked. This matters when you revisit a project six months later. Instead of opening five different apps and a chat history, you open the workspace. One view shows the entire thread. The doc, the deck, the code, the database. The decisions are documented by the chain of actions, not by a separate log. **What to do next** If you’ve ever lost a decision’s context or spent hours reconciling files, try starting your next small project inside one Xenition workspace. Describe the problem, let it open the first document, then keep building from there. You don’t have to abandon your existing tools – just see how it feels when the research doesn’t have to leave home to become the app.