[{"data":1,"prerenderedAt":529},["ShallowReactive",2],{"docs-navigation":3,"docs-\u002Fbuilding\u002Fmore-than-one-conversation":264,"surround-\u002Fbuilding\u002Fmore-than-one-conversation":526},[4,33,96,124,183,222,241],{"title":5,"path":6,"stem":7,"children":8},"Start","\u002Fstart","1.start",[9,13,18,23,28],{"title":10,"path":6,"stem":11,"description":12},"Start here","1.start\u002Findex","What Desifex is, and how to get an application of your own running.",{"title":14,"path":15,"stem":16,"description":17},"What Desifex is","\u002Fstart\u002Fwhat-desifex-is","1.start\u002F1.what-desifex-is","An application factory where conversation is the interface — and the handful of things it deliberately will not do.",{"title":19,"path":20,"stem":21,"description":22},"Your first application","\u002Fstart\u002Fyour-first-application","1.start\u002F2.your-first-application","From a sentence to something running, in about twenty minutes, with nothing to install.",{"title":24,"path":25,"stem":26,"description":27},"The workbench","\u002Fstart\u002Fthe-workbench","1.start\u002F3.the-workbench","A tour of the screen you will spend your time on — the conversation, the seven tabs, and the menu.",{"title":29,"path":30,"stem":31,"description":32},"What to expect","\u002Fstart\u002Fwhat-to-expect","1.start\u002F4.what-to-expect","How long things take, what a good working rhythm looks like, and the parts that genuinely go wrong.",{"title":34,"path":35,"stem":36,"children":37},"Building","\u002Fbuilding","2.building",[38,41,46,51,56,61,66,71,76,81,86,91],{"title":34,"path":35,"stem":39,"description":40},"2.building\u002Findex","Getting what you actually wanted out of the conversation.",{"title":42,"path":43,"stem":44,"description":45},"Describing what you need","\u002Fbuilding\u002Fdescribing-what-you-need","2.building\u002F01.describing-what-you-need","How to phrase a request so that what comes back is what you meant.",{"title":47,"path":48,"stem":49,"description":50},"Watching a build","\u002Fbuilding\u002Fwatching-a-build","2.building\u002F02.watching-a-build","What the steps mean, what is happening underneath, and why you are not shown a log.",{"title":52,"path":53,"stem":54,"description":55},"Changing your mind","\u002Fbuilding\u002Fchanging-your-mind","2.building\u002F03.changing-your-mind","Interrupting a build, correcting a misunderstanding, and undoing something you asked for.",{"title":57,"path":58,"stem":59,"description":60},"More than one conversation","\u002Fbuilding\u002Fmore-than-one-conversation","2.building\u002F04.more-than-one-conversation","Putting a piece of work down and starting the next one cleanly — what the builder keeps, what it forgets, and when a fresh conversation is the right move.",{"title":62,"path":63,"stem":64,"description":65},"A board of work","\u002Fbuilding\u002Fa-board-of-work","2.building\u002F05.a-board-of-work","The Work tab — writing down everything you have thought of, deciding what is ready, and letting the builder take them one at a time.",{"title":67,"path":68,"stem":69,"description":70},"When a build fails","\u002Fbuilding\u002Fwhen-a-build-fails","2.building\u002F06.when-a-build-fails","What a failure actually means, what to try, and when to ask us.",{"title":72,"path":73,"stem":74,"description":75},"Showing it a file","\u002Fbuilding\u002Fshowing-it-files","2.building\u002F07.showing-it-files","Attaching a screenshot, a spreadsheet or a document to the conversation — often faster than describing it.",{"title":77,"path":78,"stem":79,"description":80},"Choosing a design system","\u002Fbuilding\u002Fchoosing-a-design-system","2.building\u002F08.choosing-a-design-system","What a design system decides, how to pick one, and what changing it later does.",{"title":82,"path":83,"stem":84,"description":85},"Asking for settings","\u002Fbuilding\u002Fasking-for-settings","2.building\u002F09.asking-for-settings","The conversation reaches the whole platform — addresses, icons, redirects, users, integrations and shipping. If you do not know where a setting is, ask.",{"title":87,"path":88,"stem":89,"description":90},"When it asks you","\u002Fbuilding\u002Fwhen-it-asks-you","2.building\u002F10.when-it-asks-you","Some decisions arrive as a screen rather than a message — a table to correct, a list to choose from — and the build waits for your answer.",{"title":92,"path":93,"stem":94,"description":95},"Starting from what you have","\u002Fbuilding\u002Fstarting-from-what-you-have","2.building\u002F11.starting-from-what-you-have","A spreadsheet, a document, a picture or a page of your own site — attached, read, and built from.",{"title":97,"path":98,"stem":99,"children":100},"Shipping","\u002Fshipping","3.shipping",[101,104,109,114,119],{"title":97,"path":98,"stem":102,"description":103},"3.shipping\u002Findex","Getting what you built in front of people, and getting back to an earlier version.",{"title":105,"path":106,"stem":107,"description":108},"Versions","\u002Fshipping\u002Fversions","3.shipping\u002F1.versions","Every build is kept, named after what was asked for, and can be compared and restored.",{"title":110,"path":111,"stem":112,"description":113},"Environments","\u002Fshipping\u002Fenvironments","3.shipping\u002F2.environments","Preview, test and live — what each one is, who can reach it, and why their data is separate.",{"title":115,"path":116,"stem":117,"description":118},"Deploying","\u002Fshipping\u002Fdeploying","3.shipping\u002F3.deploying","Putting a version into test or live, what happens while it deploys, and what happens if it fails.",{"title":120,"path":121,"stem":122,"description":123},"Going back","\u002Fshipping\u002Fgoing-back","3.shipping\u002F4.going-back","Restoring an earlier version when a change turned out to be wrong.",{"title":125,"path":126,"stem":127,"children":128},"Running","\u002Frunning","4.running",[129,133,138,143,148,153,158,163,168,173,178],{"title":130,"path":126,"stem":131,"description":132},"Running it","4.running\u002Findex","Everything in Settings — addresses, access, people, files, integrations and what crawlers are told.",{"title":134,"path":135,"stem":136,"description":137},"Addresses and domains","\u002Frunning\u002Faddresses-and-domains","4.running\u002F01.addresses-and-domains","The address an application gets, and how to put it on a domain you own.",{"title":139,"path":140,"stem":141,"description":142},"Who can reach it","\u002Frunning\u002Fwho-can-reach-it","4.running\u002F02.who-can-reach-it","Open, behind one shared password, or accounts — and why the choice is enforced in front of the application.",{"title":144,"path":145,"stem":146,"description":147},"People who sign in","\u002Frunning\u002Fpeople-who-sign-in","4.running\u002F03.people-who-sign-in","The workspace's user directory — adding the people who use your applications, which ones each may open, what you can keep about them, and two-step sign-in.",{"title":149,"path":150,"stem":151,"description":152},"Published files","\u002Frunning\u002Fpublished-files","4.running\u002F04.published-files","Documents your application hands to its users — a price list, a brochure, a form — with a stable address and no build to change them.",{"title":154,"path":155,"stem":156,"description":157},"Integrations","\u002Frunning\u002Fintegrations","4.running\u002F05.integrations","Email, SMS and Google — connected once, used by the application without it ever holding a credential.",{"title":159,"path":160,"stem":161,"description":162},"Appearance","\u002Frunning\u002Fappearance","4.running\u002F06.appearance","The browser tab, the icon, what a link looks like when somebody pastes it, and adding it to a phone's home screen.",{"title":164,"path":165,"stem":166,"description":167},"Redirects and search engines","\u002Frunning\u002Fredirects-and-search-engines","4.running\u002F07.redirects-and-search-engines","Old addresses that still get visited, and what crawlers are told about each environment.",{"title":169,"path":170,"stem":171,"description":172},"Configuration values","\u002Frunning\u002Fconfiguration-values","4.running\u002F08.configuration-values","Named values the application needs but must not contain — API keys, account numbers, thresholds.",{"title":174,"path":175,"stem":176,"description":177},"Your data","\u002Frunning\u002Fyour-data","4.running\u002F09.your-data","The Data tab — reading, correcting, adding to and clearing out what your application has stored, one environment at a time.",{"title":179,"path":180,"stem":181,"description":182},"Visitors","\u002Frunning\u002Fvisitors","4.running\u002F10.visitors","Who is using the application, counted without identifying anybody and with nothing to set up.",{"title":184,"path":185,"stem":186,"children":187},"Workspace","\u002Fworkspace","5.workspace",[188,192,197,202,207,212,217],{"title":189,"path":185,"stem":190,"description":191},"Your workspace","5.workspace\u002Findex","What every application in it shares — the domain, the design systems, the people, the user directory and, if you want it, one set of records — and how to be in more than one.",{"title":193,"path":194,"stem":195,"description":196},"People and roles","\u002Fworkspace\u002Fpeople-and-roles","5.workspace\u002F1.people-and-roles","Three roles, what each can do, how they apply to the builder as well as to the buttons, and why they belong to a workspace rather than to an account.",{"title":198,"path":199,"stem":200,"description":201},"More than one workspace","\u002Fworkspace\u002Fmore-than-one-workspace","5.workspace\u002F2.more-than-one-workspace","Belonging to several, switching between them, the role you hold in each, and why nothing crosses over.",{"title":203,"path":204,"stem":205,"description":206},"Organising applications","\u002Fworkspace\u002Ffolders-and-organising","5.workspace\u002F3.folders-and-organising","Folders on the dashboard, and how to keep a growing list navigable.",{"title":208,"path":209,"stem":210,"description":211},"Your own design systems","\u002Fworkspace\u002Fyour-own-design-systems","5.workspace\u002F4.your-own-design-systems","Authoring a design system for your brand, or a client's, by importing guidelines, a website or a Figma library.",{"title":213,"path":214,"stem":215,"description":216},"Your profile","\u002Fworkspace\u002Fyour-profile","5.workspace\u002F5.your-profile","Your name and how you are addressed, your password, your picture, two-step sign-in by email or text, and the theme.",{"title":218,"path":219,"stem":220,"description":221},"Where records live","\u002Fworkspace\u002Fwhere-records-live","5.workspace\u002F6.where-records-live","One store per environment, one across an application's environments, or one the whole workspace shares — what each costs you, and how to change it.",{"title":223,"path":224,"stem":225,"children":226},"Developers","\u002Fdevelopers","6.developers",[227,231,236],{"title":228,"path":224,"stem":229,"description":230},"For developers","6.developers\u002Findex","What is actually generated, and what to do when you inherit one.",{"title":232,"path":233,"stem":234,"description":235},"What gets built","\u002Fdevelopers\u002Fwhat-gets-built","6.developers\u002F1.what-gets-built","The stack, the shape of the repository, and the parts the platform provides rather than the application.",{"title":237,"path":238,"stem":239,"description":240},"Taking one over","\u002Fdevelopers\u002Ftaking-it-over","6.developers\u002F2.taking-it-over","For the developer who has just been handed an application built here.",{"title":242,"path":243,"stem":244,"children":245},"Reference","\u002Freference","7.reference",[246,249,254,259],{"title":242,"path":243,"stem":247,"description":248},"7.reference\u002Findex","Terms, limits, and what to do when something specific has gone wrong.",{"title":250,"path":251,"stem":252,"description":253},"Glossary","\u002Freference\u002Fglossary","7.reference\u002F1.glossary","Every term this documentation uses, in one place.",{"title":255,"path":256,"stem":257,"description":258},"Limits","\u002Freference\u002Flimits","7.reference\u002F2.limits","The boundaries that are real, so you do not discover them at an inconvenient moment.",{"title":260,"path":261,"stem":262,"description":263},"Troubleshooting","\u002Freference\u002Ftroubleshooting","7.reference\u002F3.troubleshooting","Specific symptoms, and what each one usually means.",{"id":265,"title":57,"body":266,"description":60,"extension":519,"hidden":520,"meta":521,"navTitle":522,"navigation":523,"path":58,"seo":524,"stem":59,"__hash__":525},"docs\u002F2.building\u002F04.more-than-one-conversation.md",{"type":267,"value":268,"toc":504},"minimark",[269,273,276,281,289,297,307,311,314,320,336,343,346,351,356,365,368,371,382,390,394,397,403,409,413,424,428,450,454,457,468,475,479,486,490,497],[270,271,272],"p",{},"An application lasts longer than any one piece of work you do to it. The\nconversation that took a stock list from nothing through eleven corrections is\nnot a good place to ask for an invoice layout.",[270,274,275],{},"So an application can have several conversations. One is on screen at a time,\nand the bar above the conversation says which.",[277,278,280],"h2",{"id":279},"starting-one","Starting one",[270,282,283,284,288],{},"Open the conversations menu — the name at the top of the conversation — and\nchoose ",[285,286,287],"strong",{},"Start a new conversation",".",[270,290,291,292,296],{},"You are in it immediately. The hand-over described below takes a few seconds to\nwrite, and it is written while you are already in the new conversation rather\nthan before you get there — you will see ",[293,294,295],"em",{},"Carrying over where this application\ngot to…"," at the top while it is being written, and the note itself when it\nlands. You can start typing straight away.",[298,299,301],"note",{"type":300},"warning",[270,302,303,304,288],{},"You cannot start one while something is being built. The build in flight is\nwriting into the conversation you are about to put down. Wait for it, or press\n",[285,305,306],{},"Stop",[277,308,310],{"id":309},"what-the-builder-takes-with-it","What the builder takes with it",[270,312,313],{},"This is the part worth understanding, because it is the whole reason to do it.",[270,315,316,319],{},[285,317,318],{},"A new conversation is a clean slate."," The builder no longer re-reads the\nearlier exchange. What it reads instead is:",[321,322,323,330],"ul",{},[324,325,326,329],"li",{},[285,327,328],{},"the application's code",", in full, as it stands — which is where nearly\neverything you asked for actually ended up;",[324,331,332,335],{},[285,333,334],{},"a hand-over note",": a short written summary of where the application got to,\nwhat was decided deliberately, and anything left unfinished.",[270,337,338,339,342],{},"You can read the note yourself — ",[285,340,341],{},"Carried over from earlier work",", at the top\nof the new conversation — so there is no question about what the builder was\ntold.",[270,344,345],{},"If you send your first message before the note has finished being written, the\nbuild waits for it rather than starting without it. That wait is a few seconds\nagainst a build that takes minutes, and starting without the note is the\nexpensive half of the trade.",[298,347,348],{},[270,349,350],{},"The hand-over is a courtesy, not the record. The code is the record, and the\nbuilder reads that either way. If the summary could not be written — it is a\nbrief call to a small model and it occasionally fails — the conversation says\nso, and carries on. The builder still knows the application from its code.",[352,353,355],"h3",{"id":354},"if-you-want-a-genuinely-clean-slate","If you want a genuinely clean slate",[270,357,358,359,361,362,288],{},"Open ",[285,360,341],{}," and press ",[285,363,364],{},"Do not use it",[270,366,367],{},"The builder then reads this application's code and nothing else — no account of\nwhat was decided before, no note of what was left unfinished.",[270,369,370],{},"That is worth doing when the earlier work is the problem rather than the\ncontext: a stretch that went wrong, an approach you have abandoned, a direction\nyou do not want argued back at you. Inheriting a careful summary of a bad\nafternoon is inheriting the bad afternoon.",[270,372,373,374,377,378,381],{},"The note is not deleted. It stays in the conversation, struck through and\nmarked ",[293,375,376],{},"not being used",", and ",[285,379,380],{},"Use it after all"," puts it back. Both take effect\non the next build, not retroactively — a build already running was given its\nhistory when it started.",[298,383,384],{"type":300},[270,385,386,387,288],{},"The code is still the record. Clearing the note stops the builder reading an\naccount of the earlier work; it does not undo that work, and the application is\nexactly as it was. To remove something that was built, ask for it back or\nrestore an earlier version — see ",[388,389,120],"a",{"href":121},[277,391,393],{"id":392},"why-bother","Why bother",[270,395,396],{},"Two reasons, and the first one is money.",[270,398,399,402],{},[285,400,401],{},"A long conversation is re-read on every turn."," Nine months of settled\nargument is re-read before the builder answers your next question, and you are\nbilled for reading it. A fresh conversation is markedly cheaper and quicker for\nthe same request.",[270,404,405,408],{},[285,406,407],{},"It also answers better."," A builder holding four hundred exchanges about a\nstock list is a builder that keeps bringing up the stock list. Asked for an\ninvoice layout in a conversation of its own, it reads the job in hand.",[277,410,412],{"id":411},"when-to-start-one","When to start one",[321,414,415,418,421],{},[324,416,417],{},"The work has visibly changed subject — a different part of the application,\na different audience, a different problem.",[324,419,420],{},"The last piece of work is finished and deployed, and you are starting the\nnext one.",[324,422,423],{},"Builds have begun feeling slow or expensive relative to what you are asking\nfor.",[277,425,427],{"id":426},"when-not-to","When not to",[321,429,430,436,444],{},[324,431,432,435],{},[285,433,434],{},"Mid-argument."," If you are three corrections into getting one screen right,\nthe detail of those corrections is exactly what you want kept. Starting over\nmakes the builder re-derive it — or fail to.",[324,437,438,441,442,288],{},[285,439,440],{},"Because something went wrong."," A fresh conversation is not a fix. See\n",[388,443,67],{"href":68},[324,445,446,449],{},[285,447,448],{},"Out of tidiness."," One long conversation is not a problem to be cleaned up.\nMost applications never need a second.",[277,451,453],{"id":452},"going-back-to-an-earlier-one","Going back to an earlier one",[270,455,456],{},"Pick it from the same menu. Everything said in it is still there, and it reads\nexactly as you left it.",[270,458,459,460,463,464,467],{},"An earlier conversation is ",[285,461,462],{},"read-only",". The composer is closed, and the bar\nsays ",[293,465,466],{},"earlier work"," with a way back. This is deliberate: a message sent into a\nconversation that has been put down would be answered in a conversation nobody\nis looking at.",[270,469,470,471,474],{},"Press ",[285,472,473],{},"Back to now"," to return to the one work goes into.",[277,476,478],{"id":477},"naming-them","Naming them",[270,480,481,482,485],{},"A conversation is named after the first thing you asked of it, which is usually\ngood enough to recognise it by. ",[285,483,484],{},"Rename this one…"," in the same menu gives it\na name of your own, and once you have named one the builder never renames it.",[277,487,489],{"id":488},"reading-a-long-one","Reading a long one",[270,491,492,493,496],{},"The conversation loads its most recent exchange and fetches the rest as you\nscroll up, so opening an application that has been worked on for a year is as\nquick as opening one built yesterday. ",[285,494,495],{},"Show earlier messages"," at the top\nfetches the previous stretch if you would rather press something.",[270,498,499,500,503],{},"Scrolling up while a build is running stops the conversation following it, so\nyou can read without being dragged along. ",[285,501,502],{},"Latest",", bottom right, goes back to\nthe newest message and starts following again.",{"title":505,"searchDepth":506,"depth":506,"links":507},"",3,[508,510,513,514,515,516,517,518],{"id":279,"depth":509,"text":280},2,{"id":309,"depth":509,"text":310,"children":511},[512],{"id":354,"depth":506,"text":355},{"id":392,"depth":509,"text":393},{"id":411,"depth":509,"text":412},{"id":426,"depth":509,"text":427},{"id":452,"depth":509,"text":453},{"id":477,"depth":509,"text":478},{"id":488,"depth":509,"text":489},"md",false,{},null,true,{"title":57,"description":60},"KAvAjY5LR_b8CX-Ac4IAXTyn8zfXSoB51lrX0aZ3inw",[527,528],{"title":52,"path":53,"stem":54,"description":55,"children":-1},{"title":62,"path":63,"stem":64,"description":65,"children":-1},1793657361790]