@aglyn/aglyn 1.0.0-beta.270 → 1.0.0-beta.272

package/src/lib/app-utils/docs-index.generated.js

@@ -184,7 +184,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'AI credits',
         heading: 'Credits each month',
         anchor: '#monthly-credits',
-        text: 'Each plan includes a band of credits every month, and the Aglyn AI add-on widens it:\n| Plan | Included each month | Added by the Aglyn AI add-on |\n| Free | 300 | Not sold on Free |\n| Starter | 750 | 4,000 |\n| Pro | 2,750 | 9,000 |\n| Business | 7,500 | 19,000 |\n| Scale | 10,000 | 34,000 |\n| Advanced | 13,000 | 49,000 |\n| Agency | 58,000 | 149,000 |\n| Enterprise | Set in your agreement | Included in your agreement |\nThe band resets on the first of each month (UTC). Credits you did not use do not carry over.\nOn Starter, the included credits pay for the assistant: answers, page-aware guidance and offers to open a page. Building pages, forms, emails and the rest needs the add-on.'
+        text: 'Each plan includes credits every month, and they pay for all of Aglyn AI: answers, copy, and building pages, forms, emails, products and the rest. An Aglyn AI tier adds more on top:\n| Plan | Included each month |\n| Free | 300 |\n| Starter | 750 |\n| Pro | 2,750 |\n| Business | 7,500 |\n| Scale | 10,000 |\n| Advanced | 13,000 |\n| Agency | 58,000 |\n| Enterprise | Set in your agreement |\nThe pool resets on the first of each month (UTC). Credits you did not use do not carry over.\nOn a paid plan, credits past the pool are billed per 1,000 at your plan\'s rate, unless you turn on the stop at the included band in Billing. See Billing & Plans.'
     },
     {
         path: '/ai/ai-credits',
@@ -196,9 +196,9 @@ export const DOCS_SECTION_INDEX = [
     {
         path: '/ai/ai-credits',
         title: 'AI credits',
-        heading: 'The Aglyn AI add-on',
+        heading: 'Aglyn AI tiers',
         anchor: '#the-aglyn-ai-add-on',
-        text: 'The Aglyn AI add-on is bought once for the whole workspace, on any paid plan. It adds the credits in the table above to the same pool and turns on building with AI on every site. Its price is on aglyn.com/pricing and in Billing before you confirm. See Add-ons.'
+        text: 'Need more than your plan includes? An Aglyn AI tier adds credits to the same pool every month, on top of what your plan includes. You choose the tier on its own: any paid plan can have any tier, and changing your plan keeps your tier.\n| Tier | Adds each month |\n| Spark | 4,000 |\n| Boost | 9,000 |\n| Plus | 19,000 |\n| Max | 34,000 |\n| Ultra | 49,000 |\n| Studio | 149,000 |\nA tier is bought once for the whole workspace. Free has no tiers, and on Enterprise more AI is part of your agreement. Each tier\'s price is on aglyn.com/pricing and in Billing before you confirm. Moving up is charged now, for the rest of the period; moving down or removing it takes effect at the end of the period you have paid for. See Add-ons.'
     },
     {
         path: '/ai/ai-credits',
@@ -240,7 +240,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'AI credits',
         heading: 'See your credits',
         anchor: '#see-your-credits',
-        text: '- Billing → Usage → AI credits shows the credits drawn this month against the included band, and what the add-on adds. A workspace whose plan includes no AI credits sees that said here instead, with See plans linking to Billing.\n- Who is generating what, on the same page, lists each member\'s credits by month. See Billing & Plans.\n- The usage line in the assistant and the AI dialogs shows your own credits, the workspace\'s and your last request. See Your usage while you work.\n- A site\'s AI jobs page shows what each job used. See AI jobs and activity.\nTo give one member or one site its own monthly share, see AI allotments.'
+        text: '- Billing → Usage → AI credits shows the credits drawn this month against the pool, and how many of them your tier adds. A workspace whose plan includes no AI credits sees that said here instead, with See plans linking to Billing.\n- Who is generating what, on the same page, lists each member\'s credits by month. See Billing & Plans.\n- The usage line in the assistant and the AI dialogs shows your own credits, the workspace\'s and your last request. See Your usage while you work.\n- A site\'s AI jobs page shows what each job used. See AI jobs and activity.\nTo give one member or one site its own monthly share, see AI allotments.'
     },
     {
         path: '/ai/ai-credits',
@@ -700,9 +700,9 @@ export const DOCS_SECTION_INDEX = [
     {
         path: '/ai/create-with-ai',
         title: 'Create with AI on every list',
-        heading: 'Without the add-on',
+        heading: 'On every plan',
         anchor: '#without-the-add-on',
-        text: 'On a paid plan without the Aglyn AI add-on, the button is still there. It opens a short window saying what it would make and that Create with AI comes with the Aglyn AI add-on:\n- an owner or admin sees Add Aglyn AI, which opens Billing to add it, or Not now;\n- anyone else is asked to have a workspace owner or admin add it.\nA Free workspace does not buy the add-on: its buttons work from the 300 AI credits it gets each month.'
+        text: 'On every paid plan, Create with AI runs on the AI credits your plan includes each month; nothing else needs to be bought. An Aglyn AI tier adds more credits on top when you need them, and an owner or admin chooses it in Billing.\nA Free workspace\'s buttons work from the 300 AI credits it gets each month.\nIf Create with AI is switched off for your workspace, the button is still there and opens a short window saying what it would make:\n- an owner or admin sees Add Aglyn AI, which opens Billing to choose a tier, or Not now;\n- anyone else is asked to have a workspace owner or admin choose one.'
     },
     {
         path: '/ai/create-with-ai',
@@ -1106,16 +1106,16 @@ export const DOCS_SECTION_INDEX = [
     {
         path: '/ai/overview',
         title: 'Aglyn AI: the AI website builder',
-        heading: 'The Aglyn AI add-on',
+        heading: 'Plans and Aglyn AI tiers',
         anchor: '#the-add-on',
-        text: 'Aglyn AI is an add-on, bought once for the workspace on any paid plan, not per seat and not per site. With it on, every member who has the permission to generate can use every door above, on every site in the workspace.\n- It adds a band of AI credits to the band your plan already includes.\n- Every paid plan, Starter included, already includes some credits and the guided assist, so the add-on widens a band you have rather than opening your first one.\n- Enterprise workspaces carry generative building in their agreement rather than buying the add-on.\n- Free workspaces do not buy it. A Free workspace gets a small monthly allowance of credits instead, enough to try generating, and it stops at that allowance rather than billing you.\nWhat the add-on costs, and the size of the band it adds, are on aglyn.com/pricing and in Billing before you confirm — see Add-ons.'
+        text: 'Aglyn AI comes with every plan. Each plan includes AI credits every month, and they pay for everything above: the assistant\'s answers and building for you, on every site in the workspace, for every member who has the permission to generate.\n- An Aglyn AI tier adds more credits on top of your plan\'s, bought once for the workspace, not per seat and not per site. There are six, from Spark to Studio, and any paid plan can have any of them.\n- Enterprise workspaces carry their AI in their agreement.\n- Free workspaces have no tiers. A Free workspace gets a small monthly allowance of credits instead, enough to try generating, and it stops at that allowance rather than billing you.\nWhat each tier costs, and the credits it adds, are on aglyn.com/pricing and in Billing before you confirm — see AI credits and Add-ons.'
     },
     {
         path: '/ai/overview',
         title: 'Aglyn AI: the AI website builder',
         heading: 'Credits and caps',
         anchor: '#credits-and-caps',
-        text: 'Everything AI does — an answer from the assistant, a rewrite, a generated section, a whole site — is metered in AI credits from one workspace pool. There is no second meter per feature.\nWhat a request costs is not fixed: a rewrite of one headline is small, a site scaffold is large, and a job tells you its estimate before you confirm it. The shape of the limits is the part worth knowing:\n- An included band each month, from your plan plus the add-on, reset monthly.\n- Past the band, a paid workspace keeps working and the extra credits bill on the monthly invoice at your plan\'s rate. A switch under Billing → Usage stops AI at the included band instead; it is off unless you choose it.\n- A ceiling you set, so overage can never pass a figure you are comfortable with.\n- Alerts on the way there, to the workspace\'s owners and admins.\n- Allotments, which give one member, one site collaborator or one whole site its own monthly share of the pool, hard or soft — see AI allotments, usage and model choice. An agency can give each client site its own share so one site running out never touches another.\n- A short-term rate limit per person, which smooths bursts rather than capping your month. If you see "Too many AI requests", wait a moment and try again.\nA request that fails before the model answers does not spend credits. An answer that was generated and then refused for breaking a building rule does — the rules page says which, and why.\nWhat each plan includes, what typical jobs cost and when credits are given back are on AI credits. The billing figures behind all of that are on Billing & Plans, and your own usage is on Billing → Usage.'
+        text: 'Everything AI does — an answer from the assistant, a rewrite, a generated section, a whole site — is metered in AI credits from one workspace pool. There is no second meter per feature.\nWhat a request costs is not fixed: a rewrite of one headline is small, a site scaffold is large, and a job tells you its estimate before you confirm it. The shape of the limits is the part worth knowing:\n- An included band each month, from your plan plus your tier, reset monthly.\n- Past the band, a paid workspace keeps working and the extra credits bill on the monthly invoice at your plan\'s rate. A switch under Billing → Usage stops AI at the included band instead; it is off unless you choose it.\n- A ceiling you set, so overage can never pass a figure you are comfortable with.\n- Alerts on the way there, to the workspace\'s owners and admins.\n- Allotments, which give one member, one site collaborator or one whole site its own monthly share of the pool, hard or soft — see AI allotments, usage and model choice. An agency can give each client site its own share so one site running out never touches another.\n- A short-term rate limit per person, which smooths bursts rather than capping your month. If you see "Too many AI requests", wait a moment and try again.\nA request that fails before the model answers does not spend credits. An answer that was generated and then refused for breaking a building rule does — the rules page says which, and why.\nWhat each plan includes, what typical jobs cost and when credits are given back are on AI credits. The billing figures behind all of that are on Billing & Plans, and your own usage is on Billing → Usage.'
     },
     {
         path: '/ai/overview',
@@ -1129,7 +1129,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Aglyn AI: the AI website builder',
         heading: 'Switch AI off for one site',
         anchor: '#switch-ai-off-for-one-site',
-        text: 'AI is on for every site in a workspace. A site admin can switch it off for one site on that site\'s Admin → Plugins → AI page, and the page says, beside the switch, what switching it off stops and what it leaves running.\nWith AI off for a site:\n- the assistant, Create with AI on the Pages, Templates, Layouts, Forms, Components and Media pages, the SEO and theme cards, the editor\'s Rewrite with AI, Generate a section with AI and Make a reusable component with AI controls, and the AI columns on the site\'s collaborators card are gone from that site;\n- every AI request made for the site is refused with AI is switched off for this site., including one sent from a tab that was open before the switch;\n- an AI job already queued for the site stops with the same sentence, and spends no credits. A job that stopped does not restart when AI is switched back on.\nSwitching AI off for a site does not stop the workspace\'s AI add-on, credits, allotments or overage billing. AI keeps working on the workspace\'s other sites and on workspace pages such as Billing, and an agency batch still builds the sites in it that have AI on.'
+        text: 'AI is on for every site in a workspace. A site admin can switch it off for one site on that site\'s Admin → Plugins → AI page, and the page says, beside the switch, what switching it off stops and what it leaves running.\nWith AI off for a site:\n- the assistant, Create with AI on the Pages, Templates, Layouts, Forms, Components and Media pages, the SEO and theme cards, the editor\'s Rewrite with AI, Generate a section with AI and Make a reusable component with AI controls, and the AI columns on the site\'s collaborators card are gone from that site;\n- every AI request made for the site is refused with AI is switched off for this site., including one sent from a tab that was open before the switch;\n- an AI job already queued for the site stops with the same sentence, and spends no credits. A job that stopped does not restart when AI is switched back on.\nSwitching AI off for a site does not stop the workspace\'s AI tier, credits, allotments or overage billing. AI keeps working on the workspace\'s other sites and on workspace pages such as Billing, and an agency batch still builds the sites in it that have AI on.'
     },
     {
         path: '/ai/overview',
@@ -1222,6 +1222,13 @@ export const DOCS_SECTION_INDEX = [
         anchor: '#choose-a-style',
         text: 'The Style step of Start your site offers these styles, each as a card with a picture of an example home page of that kind, drawn in its style. Pick for me, first and chosen unless you choose another, uses the style that what you said the site is suggests, and names it.\n| Style | For |\n| Business & services | A local business or service company. The fallback when nothing else fits. |\n| Home services & trades | Roofers, plumbers, electricians, cleaners and other trades. |\n| Law, finance & consulting | Professional practices. |\n| Health & wellness | Clinics, therapists and practitioners. |\n| Restaurant & café | Restaurants, cafés, bakeries and bars. |\n| Online store | A shop that sells products. On a paid plan it adds products. |\n| Portfolio | Showing your work. |\n| Design studio & agency | Studios and agencies. |\n| Photography | Photographers. |\n| Blog & writing | Reading-first pages. On a paid plan it adds posts. |\n| Events & weddings | An event, a venue or a planner. |\n| Fitness & sports | Gyms, trainers, teams and clubs. |\n| Yoga & mindfulness | Studios and teachers. |\n| Beauty & salon | Salons, barbers and spas. |\n| Real estate | Agents and agencies. |\n| Courses & education | Classes, tutors and schools. |\n| Nonprofit & community | Charities, groups and clubs. |\n| Music & bands | Musicians and bands. |\n| Personal & resume | A personal site or a resume. |\n| Landing page | One offer on one focused page. |\n| Coming soon | A placeholder that collects interest. |\nEach card says, in a line, what its look is like. Its picture is one variation of the style; your site gets its own. A style also suggests the pages that kind of site usually has, such as a menu for a restaurant or services for a trade.'
     },
+    {
+        path: '/ai/site-looks',
+        title: 'Looks and themes for AI sites',
+        heading: 'Each style\'s layout',
+        anchor: '#each-styles-layout',
+        text: 'A style also decides how its pages are laid out, so two styles never read as the same page in different colors. Each style opens its pages in one of two ways of its own, and your site gets one of the two:\n- A photo across the whole page, with the words over it at the start (a trade, a nonprofit, a band) or centered in large type (a restaurant, a coming soon page).\n- A photo filling half the page, edge to edge, with the words in the other half (health and wellness, fitness).\n- The words beside a photo (business and services, courses and education), or beside two overlapping photos (an online store, an event, a salon).\n- A white card over a photo, holding the words (law, finance and consulting, real estate).\n- Large type above a wide photo (a design studio, a portfolio) or a centered heading above a wide photo (a blog, yoga, a landing page).\n- A round portrait above the words (a personal page).\nThe style also sets how its header is arranged, how its lists and cards are drawn (cards, lines under thin rules, or icons), whether its sections of text take a photo beside them, and whether a heading sits beside its items. The words, the sections and their order are still written for your business.'
+    },
     {
         path: '/ai/site-looks',
         title: 'Looks and themes for AI sites',
@@ -1262,49 +1269,49 @@ export const DOCS_SECTION_INDEX = [
         title: 'Start a new site with AI',
         heading: 'How do you want to start?',
         anchor: '#how-do-you-want-to-start',
-        text: 'The first step asks for the site\'s Site name and Subdomain, its free address on Aglyn. The subdomain follows the name until you change it, and is checked as you type: if it is taken, the field says so and offers available ones to pick. Then it offers two cards:\n- Start from the starter site gives the site a ready-made home page with a header, footer and contact form, live at its address, for you to edit.\n- Start with AI (marked Recommended) asks the questions below and builds the site for you. On the Free plan the card says how many pages a Free start makes.\nNo site exists until you choose. Start from the starter site and Skip (in the bar at the top) create the site with the starter home page and open it. Plan my site creates the site and starts planning it. The close control and the Escape key create nothing: the window closes and no site is made. If you have typed or picked something, the window first asks Leave without your answers?, because what you typed is not saved. Once the site is being planned, closing only closes the window; the job carries on.\nIf your role cannot create sites, or your plan has no site left, Create site says so before asking anything. Plan my site checks that planning can start before it creates the site. If it cannot, the window says why and no site is made. On the Free plan, a start that may need more credits than you have left asks first, and the site is created only once you choose. If planning still cannot start after the site is created, the window says why; leaving then gives that site the starter home page, so it is never left empty.'
+        text: 'The first step asks for the site\'s Site name and Subdomain, its free address on Aglyn. The subdomain follows the name until you change it, and is checked as you type: if it is taken, the field says so and offers available ones to pick. Then it offers two cards:\n- Start from the starter site gives the site a ready-made home page with a header, footer and contact form, live at its address, for you to edit.\n- Start with AI (marked Recommended) asks the questions below and builds the site for you. On the Free plan the card says how many pages a Free start makes.\nBring my site (rolling out, not yet available) is a third card for moving the website you have now into Aglyn. See Bring my site.\nNo site exists until you choose. Start from the starter site and Skip (in the bar at the top) create the site with the starter home page and open it. Plan my site creates the site and starts planning it. The close control and the Escape key create nothing: the window closes and no site is made. If you have typed or picked something, the window first asks Leave without your answers?, because what you typed is not saved. Once the site is being planned, closing only closes the window; the job carries on.\nIf your role cannot create sites, or your plan has no site left, Create site says so before asking anything. Plan my site checks that planning can start before it creates the site. If it cannot, the window says why and no site is made. On the Free plan, a start that may need more credits than you have left asks first, and the site is created only once you choose. If planning still cannot start after the site is created, the window says why; leaving then gives that site the starter home page, so it is never left empty.'
     },
     {
         path: '/ai/start-with-ai',
         title: 'Start a new site with AI',
         heading: 'The questions, one at a time',
         anchor: '#the-questions',
-        text: 'Start with AI asks one thing per step. The bar under the title shows where you are: Start, Your site, Audience, Style, Details and Review (on a phone, Step 3 of 6 and a progress bar). Next moves on and Back goes back; your answers are kept either way. Pressing Enter in a text answer is the same as Next. If a step cannot move on, the reason shows under the field and the cursor goes to it. Skip and the close control stay in the bar at the top on every step.'
+        text: 'Start with AI asks one thing per step. The bar under the title shows where you are: Start, Your site, Audience, Style, Details and Review (on a phone, Step 3 of 6 and a progress bar). Next moves on and Back goes back; your answers are kept either way. Pressing Enter in a text answer is the same as Next. If a step cannot move on, the reason shows under the field and the cursor goes to it. Skip and the close control stay in the bar at the top on every step.\nEvery question step also has More details, a closed section under its answers with optional extras that fit the step. Open it to tell the site more about your business, or leave it closed. Everything in it can be changed later. If something in it cannot be used, Next opens it and says why under the field.'
     },
     {
         path: '/ai/start-with-ai',
         title: 'Start a new site with AI',
         heading: 'Your site',
         anchor: '#your-business',
-        text: 'What kind of site are you creating? is the one required answer. A few words is enough, such as a neighborhood dog groomer that takes bookings, or pick the closest card under the field: Local service business, Restaurant or cafe, Professional practice, Trades business, Shop, Nonprofit, Personal portfolio or Event. A card fills in the field for you. Keep it under 120 characters.\nWhat you write here picks the site\'s style, unless you choose one yourself, and decides which pages it usually has and what each page says.'
+        text: 'What kind of site are you creating? is the one required answer. A few words is enough, such as a neighborhood dog groomer that takes bookings, or pick the closest card under the field: Local service business, Restaurant or cafe, Professional practice, Trades business, Shop, Nonprofit, Personal portfolio or Event. A card fills in the field for you. Keep it under 120 characters.\nWhat you write here picks the site\'s style, unless you choose one yourself, and decides which pages it usually has and what each page says.\nMore details here: a Tagline, a short line about the business in your words, and the Year founded.'
     },
     {
         path: '/ai/start-with-ai',
         title: 'Start a new site with AI',
         heading: 'Audience',
         anchor: '#audience',
-        text: 'Who is it for? is optional. It is who every page and every search listing is written for, and it decides which questions the contact form asks. For example, local dog owners who want a regular groom booked online.\nBoth answers also fill your site\'s business profile, which every later AI job for the site reads.'
+        text: 'Who is it for? is optional. It is who every page and every search listing is written for, and it decides which questions the contact form asks. For example, local dog owners who want a regular groom booked online.\nBoth answers also fill your site\'s business profile, which every later AI job for the site reads, and so do the areas you serve, from More details.\nMore details here: the Areas you serve (cities, towns or neighborhoods, one a line), your Price range ($ to $$$$) and the Languages you serve customers in.'
     },
     {
         path: '/ai/start-with-ai',
         title: 'Start a new site with AI',
         heading: 'Style',
         anchor: '#style',
-        text: 'The Style step shows each style as a card with a picture: an example home page of that kind of site, drawn in its style. A photographer\'s opens on a gallery, a café\'s on its menu, an online store\'s on its products, a blog\'s on its latest posts, an events site\'s on its program and a real estate site\'s on its listings, so you can see each style\'s colors, fonts, buttons and corners, and the shape of its pages, before you pick. Pick for me comes first and is chosen unless you choose another. It names the style your first answer suggests, such as From your answer: Home services & trades. The style decides how the site looks and which pages it usually has: an online store, a portfolio, a restaurant, a blog and so on. Each site gets its own variation, so two sites with the same style still look different, and yours will not match the picture exactly. See Looks and themes for AI sites.'
+        text: 'The Style step shows each style as a card with a picture: an example home page of that kind of site, drawn in its style, each with a photo. A photographer\'s opens on a gallery, a café\'s on its heading centered over a photo of the café with its menu under it, an online store\'s on two photos of what it sells, a blog\'s on a centered heading above a wide photo, an events site\'s on its dates beside two photos of the day and a real estate site\'s on a card over a photo of a home, so you can see each style\'s colors, fonts, buttons and corners, and the shape of its pages, before you pick. The picked card is outlined in color and carries a check. See each style\'s layout. Pick for me comes first and is chosen unless you choose another. It names the style your first answer suggests, such as From your answer: Home services & trades. The style decides how the site looks and which pages it usually has: an online store, a portfolio, a restaurant, a blog and so on. Each site gets its own variation, so two sites with the same style still look different, and yours will not match the picture exactly. See Looks and themes for AI sites.\nMore details here: a Brand color, picked from the colors shown. It becomes your site\'s main color, kept readable everywhere it is used. Let the style choose leaves it to the style.\nSites you like {#sites-you-like}\nSites you like (rolling out, not yet available) is an optional block under the style cards. Type the address of a website whose look you like, such as https://example.com, in Site 1. A paid plan can name up to three sites. On the Free plan, Site 2 and Site 3 are shown but cannot be used, with the reason and an Upgrade link.\nAglyn AI takes only how those sites are laid out and styled: the order of their sections, their spacing and header, their color'
     },
     {
         path: '/ai/start-with-ai',
         title: 'Start a new site with AI',
         heading: 'Details',
         anchor: '#details',
-        text: '- Where do form submissions go? decides where messages from the site\'s contact form land:\n- The Inbox (the default): every message is one to read and reply to.\n- The Inbox, and CRM as a lead: every message with an email address is also a lead to follow up.\nYou can change this on the form itself afterwards.\n- Pages is how many pages to write: 4 to 8 on a paid plan (5 unless you change it), 1 or 2 on the Free plan.\n- Welcome email (paid plans): Draft one writes a welcome email for the people who get in touch through the site, saying what became of their message. It is a draft design. Nothing sends it until you put it in an automation or a campaign. Free starts do not draft one.'
+        text: '- Business phone and Business email come first. Both are optional. When you give them, your site shows them from the start: on the contact page, in the footer of every page and on the buttons that ask a visitor to call or write, as links that open the phone or the email app. Your site\'s search listing details and the information AI assistants read carry them too. Without them, no page shows a phone or email row, and nothing is made up.\n- Where do form submissions go? decides where messages from the site\'s contact form land:\n- The Inbox (the default): every message is one to read and reply to.\n- The Inbox, and CRM as a lead: every message with an email address is also a lead to follow up.\nYou can change this on the form itself afterwards.\n- Pages is how many pages to write: 4 to 8 on a paid plan (5 unless you change it), 1 or 2 on the Free plan.\n- Welcome email (paid plans): Draft one writes a welcome email for the people who get in touch through the site, saying what became of their message. It is a draft design. Nothing sends it until you put it in an automation or a campaign. Free starts do not draft one.\nMore details here: the Street address, City or town, State or region, ZIP or postal code and Country; the Opening hours, picked a day at a time (a switch for each day, and its times from a list); and your Social profiles, one link a line, such as instagram.com/yourbusiness.'
     },
     {
         path: '/ai/start-with-ai',
         title: 'Start a new site with AI',
         heading: 'Review',
         anchor: '#review',
-        text: 'The last step lists every answer: the kind of site, who it is for, the style, where form submissions go, the pages and, on a paid plan, the welcome email. Edit beside an answer opens its step, and Back to review returns here. Plan my site starts the site.\nOn a paid plan a Model switch sits beside Plan my site. Leave it on Auto unless you have a reason to choose; see Choosing a model.'
+        text: 'The last step lists every answer: the kind of site, who it is for, the style, where form submissions go, the pages and, on a paid plan, the welcome email, then every detail you gave, such as the phone, the email, the address and the opening hours. Edit beside an answer opens its step, and Back to review returns here. Plan my site starts the site.\nOn a paid plan a Model switch sits beside Plan my site. Leave it on Auto unless you have a reason to choose; see Choosing a model.'
     },
     {
         path: '/ai/start-with-ai',
@@ -1318,7 +1325,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Start a new site with AI',
         heading: 'What gets built',
         anchor: '#what-gets-built',
-        text: 'Plan my site starts the job straight away. A guided start has no plan to approve. It builds, in this order:\n1. A look: a base theme, colors, fonts and the style of buttons, cards and forms, made for your kind of site. See Looks and themes.\n2. A header and footer, as the layout every page sits in, with a link to each page.\n3. A contact form, saved on the Forms page, routed the way you chose, and placed on the page that needs it.\n4. Your first posts or products, when the site is a blog or, on paid plans, a store. See A store from the start and A blog from the start. Your first events, when your business holds them and your workspace has the Event Calendar add-on. See Events from the start.\n5. Your pages, each with its sections, its address and its own search title and description. A home page opens with a hero and has several bands below it, such as services, about, social proof and a closing call to action. Photos come from your media library or a stock photo.\n6. A welcome email draft, if you asked for one.\n7. Publishing: see Published, and found by search engines.\nContact details are never made up. A phone number, address or opening hours appear only when you have entered them in your site settings.'
+        text: 'Plan my site starts the job straight away. A guided start has no plan to approve. It builds, in this order:\n1. A look: a base theme, colors, fonts and the style of buttons, cards and forms, made for your kind of site. See Looks and themes.\n2. A header and footer, as the layout every page sits in, with a link to each page. The footer shows the phone and email you gave, as links that call and write.\n3. A contact form, saved on the Forms page, routed the way you chose, and placed on the page that needs it.\n4. Your first posts or products, when the site is a blog or, on paid plans, a store. See A store from the start and A blog from the start. Your first events, when your business holds them and your workspace has the Event Calendar add-on. See Events from the start.\n5. Your pages, each with its sections, its address and its own search title and description. A home page opens with a hero and has several bands below it, such as services, about, social proof and a closing call to action. Photos come from your media library or a stock photo, and every photo gets a description for screen readers and search engines. The page with your contact form also shows the phone and email you gave. A list a page shows, such as your packages or your questions and answers, is kept as a dataset on plans that include datasets. It is shared with this site only, so you edit it on the Data page, and it is deleted with the site if you delete the site.\n6. A welcome email draft, if you asked for one.\n7. Publishing: see Published, and found by search engines.\nContact details are never made up. A phone number, email, address or opening hours appear only when you gave them on the Details step or entered them in your site settings.'
     },
     {
         path: '/ai/start-with-ai',
@@ -1346,14 +1353,21 @@ export const DOCS_SECTION_INDEX = [
         title: 'Start a new site with AI',
         heading: 'Published, and found by search engines',
         anchor: '#published-and-indexable',
-        text: 'A guided start publishes the site when it finishes, so it is live at its address:\n- the new home page takes the site\'s address, and an untouched starter home page is moved to the trash;\n- each page gets an entry in the header\'s navigation;\n- a page that cannot be published stays a draft, and Building your site names it with the reason, for you to fix in Edit your pages and publish.\nThe site is open to search engines from the start. A guided start never hides a site from search. If you want to keep it out of search results for now, use the site\'s search indexing setting.\nUntil the site is built, its address shows a short coming soon page with the site\'s name, which search engines are asked not to index.'
+        text: 'A guided start publishes the site when it finishes, so it is live at its address:\n- the new home page takes the site\'s address, and an untouched starter home page is moved to the trash;\n- each page gets an entry in the header\'s navigation, and takes its place in Pages in the order the plan lists it, which the built-in error page\'s links follow too;\n- a page that cannot be published stays a draft, and Building your site names it with the reason, for you to fix in Edit your pages and publish;\n- a page that Couldn\'t be built, or stayed a draft, is linked from nowhere on the published site: its header and footer entries, and the buttons on other pages that went to it, are taken out, so no visitor follows a link to a missing page. Try again what failed adds the page\'s header entry back once it is built; a button you want on another page, add in the Besigner.\nThe site is open to search engines from the start. A guided start never hides a site from search. If you want to keep it out of search results for now, use the site\'s search indexing setting.\nUntil the site is built, its address shows a short coming soon page with the site\'s name, which search engines are asked not to index.'
     },
     {
         path: '/ai/start-with-ai',
         title: 'Start a new site with AI',
         heading: 'The site\'s search listing',
         anchor: '#the-sites-search-listing',
-        text: 'The site\'s own search title and description, the fallback for every page without its own, are not saved for you. The site\'s SEO section shows them in a card, The listing your answers describe. Put in the form stages them in the SEO form below as unsaved changes, and the form\'s Update saves them.'
+        text: 'The site\'s own search title and description are the fallback for every page without its own, and what search results and AI assistants read about the site as a whole. When the site is published, your answers become them, led by the site\'s name, as long as the site still has the title and description it was created with (its name and Welcome to …).\nA title or description you changed yourself is never replaced. Instead, the site\'s SEO section shows the start\'s in a card, The listing your answers describe. Put in the form stages them in the SEO form below as unsaved changes, and the form\'s Update saves them.'
+    },
+    {
+        path: '/ai/start-with-ai',
+        title: 'Start a new site with AI',
+        heading: 'Your business, for search engines and AI assistants',
+        anchor: '#business-details',
+        text: 'When the site is published, your answers also fill the site\'s structured data in Setup → SEO, so search engines and AI assistants can tell who runs the site and how to reach you:\n- Entity: the business\'s name and description, its phone and email (with Contact is for set to customer support), its address, and what kind of business it is, from the style you picked (a plumber, a restaurant, a salon), with the areas it serves, its opening hours, its price range and its social profiles where you gave them. A personal site is published as a person.\n- Entity logo: your site logo, when the site already has one.\n- AI agents: when an assistant should use the site, and how to reach a person there. These open the site\'s guide for AI assistants, so an assistant asked about your business finds what it does, where it works and how to reach you.\nThe email and the street address also fill Setup → Details → Business details, as the site\'s support email and postal address.\nOnly empty fields are filled, so nothing you already entered there is replaced. Change any of it in Setup → SEO at any time.'
     },
     {
         path: '/ai/start-with-ai',
@@ -1409,7 +1423,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Stock photos in AI sites',
         heading: 'Where the photos come from',
         anchor: '#where-the-photos-come-from',
-        text: 'Photos come from Pixabay, a library of free photos. The job searches it with words from your page and your kind of business, such as ceramic serving bowl for a potter\'s work card or dog grooming salon for a groomer\'s hero, and picks a photo that fits the space.\nA picture of a thing only takes a photo that shows that thing in your line of work: a potter\'s bowl is never filled with a bowl of fruit or a bird at a feeder. When nothing shows the thing itself, the space gets a photo of your craft instead, such as handmade ceramics. One start never uses the same photo twice.\nWhen the search finds nothing at all, or stock photos are not available on the deployment your workspace runs on, the space gets one of the starter photos that come with every site.'
+        text: 'Photos come from Pixabay, a library of free photos. The job searches it with words from your page and your kind of business, such as ceramic serving bowl for a potter\'s work card or dog grooming salon for a groomer\'s hero, and picks a photo that fits the space.\nA picture of a thing only takes a photo that shows that thing in your line of work: a potter\'s bowl is never filled with a bowl of fruit or a bird at a feeder. When nothing shows the thing itself, the space gets a photo of your craft instead, such as handmade ceramics. One start never uses the same photo twice.\nWhen a photo cannot be copied into your library, for example because Pixabay is busy and asks to wait, the job waits and tries again. If it still cannot, the space takes one of the photos the same start already placed on your site, on another page or on a dataset\'s records, chosen to suit the space and never the same one as the picture beside it. Only a start that has no photo of its own yet, or a deployment without stock photos, uses the starter photos that come with every site.\nWhen the search finds photos but none of them fits the space, the space is left without a picture: its section shows its own background, and the words take the space. A page whose every picture would be left out this way keeps one: its first picture takes one of the start\'s own photos, or a starter photo.'
     },
     {
         path: '/ai/stock-photos',
@@ -2762,6 +2776,55 @@ export const DOCS_SECTION_INDEX = [
         anchor: '#related',
         text: '- Reusable components\n- How Aglyn AI builds'
     },
+    {
+        path: '/building-sites/custom-domains/buy-a-domain',
+        title: 'Buy a domain',
+        heading: '',
+        anchor: '',
+        text: 'Buy a domain\nGive your site its own address, like yourbusiness.com, without leaving Aglyn. You search, pick a name, and say who it\'s registered to. Aglyn registers it to you and connects it to your site, with its security certificate, so there are no DNS records to add. www.yourbusiness.com forwards to it as well.\nPlan availability Starter and above. On Free, the card says domains can be bought on the Starter plan and above, with a See plans button.'
+    },
+    {
+        path: '/building-sites/custom-domains/buy-a-domain',
+        title: 'Buy a domain',
+        heading: 'Steps',
+        anchor: '#steps',
+        text: '1. In the site\'s Admin page, choose Custom Domain. The Get a domain card is at the top.\n2. Type your business name or the domain you want into Search for a domain. Results appear as you type, each with its price: this year and every year after. A name someone already owns shows as Taken.\n3. Press Buy beside the name you want.\n4. Fill in Who the domain is registered to. Every domain is registered to a real person or business, who owns it. These details go to the registrar and are hidden from public domain lookups.\n5. Tick the box to agree to the domain registration terms, then press Buy for $….\nThe card switches to Your domain and follows the setup: Registering…, then Connecting to your site…. Most domains are live within a few minutes, and you can leave the page while it finishes.'
+    },
+    {
+        path: '/building-sites/custom-domains/buy-a-domain',
+        title: 'Buy a domain',
+        heading: 'One thing to do afterwards: confirm your email',
+        anchor: '#confirm-email',
+        text: 'ICANN, which oversees domain names, requires every domain owner to confirm their email address. The registrar sends one email to the address you gave. Open it and follow its link. Until you do, the card shows the date you must confirm by; a domain whose owner never confirms can be suspended. We also email you reminders. If the email never arrives, check your spam folder, then contact support.'
+    },
+    {
+        path: '/building-sites/custom-domains/buy-a-domain',
+        title: 'Buy a domain',
+        heading: 'Prices and renewals',
+        anchor: '#renewals',
+        text: '- The price you see is the price you pay. Many endings cost less in their first year than they do to renew, so the results always show both.\n- Auto-renew is on when you buy. We email you about 45 days before the domain renews, naming the price, and charge the card on file about 30 days before. You are never charged more for that renewal than the email said.\n- Turn auto-renew off with the switch on the card. The domain then expires at the end of its year, and we remind you before it does.\n- If a renewal can\'t be charged, we email you and try again automatically. You can update your card on the Billing page and press Renew now at any time.\n- Domain charges appear on your invoices on the Billing page.'
+    },
+    {
+        path: '/building-sites/custom-domains/buy-a-domain',
+        title: 'Buy a domain',
+        heading: 'If something goes wrong',
+        anchor: '#problems',
+        text: '| What you see | What it means |\n| A notice above the search | Something has to happen before this site can buy a domain, and the notice says what — for example, a domain is already connected, or only a member who manages billing can buy. |\n| "The price changed a moment ago" | The registrar\'s price moved while you were filling in the form. The dialog shows the new price; press buy again if you still want it. |\n| "That name was just taken" | Someone else registered it first. Pick another. |\n| An email saying we couldn\'t register it | The registrar couldn\'t complete the registration. Any charge was refunded automatically. |\n| Not connected on the card | The domain is yours but isn\'t connected to this site (another domain was connected meanwhile). Press Connect it. |'
+    },
+    {
+        path: '/building-sites/custom-domains/buy-a-domain',
+        title: 'Buy a domain',
+        heading: 'Moving a domain to another registrar',
+        anchor: '#transfer',
+        text: 'The domain is yours, and you can move it to another registrar at no charge. Press Move to another registrar, then Show transfer code, and give that code to the registrar you\'re moving to. Your workspace\'s owners are emailed whenever the code is shown. Registries lock a newly registered domain for 60 days; the card tells you the date it can move.\nTo keep your site working at the domain after moving it, keep its DNS records pointing at Aglyn at your new registrar — see Connect a domain.'
+    },
+    {
+        path: '/building-sites/custom-domains/buy-a-domain',
+        title: 'Buy a domain',
+        heading: 'If your site is deleted or your plan ends',
+        anchor: '#after',
+        text: 'The domain stays registered to you. It keeps renewing while auto-renew is on, until you turn it off or move it. Another site in your workspace can use it: its Get a domain card lists your workspace\'s unconnected domains with Use for this site.\nIf a domain expires, your site goes back to its free Aglyn address, so it stays online. For a short while after expiring, a domain can usually still be renewed with Renew now.'
+    },
     {
         path: '/building-sites/custom-domains/connect-a-domain',
         title: 'Connect a domain',
@@ -3537,7 +3600,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Versions & scheduled publishing',
         heading: 'Plan requirements',
         anchor: '#plan-requirements',
-        text: 'Gating is enforced where you click:\n- Creating versions requires Pro or above — on a lower tier the editor answers "Versioning requires a Pro plan — see Billing to upgrade" instead of opening the name dialog.\n- Scheduled publishing requires Business or above.\n- A version is snapshotted from the saved document, so the editor asks you to save the canvas first rather than silently capturing (or losing) unsaved edits.'
+        text: 'On a plan without a feature its buttons stay on screen, disabled, with a note naming the plan that includes it and an Upgrade button to the plans on Billing:\n- Creating versions requires Pro or above — on a lower tier New version is disabled and the Versions dialog says "Included from Pro".\n- Scheduled publishing requires Business or above — on a lower tier every Schedule button is disabled and says "Scheduled publishing is included from Business."\n- A version is snapshotted from the saved document, so the editor asks you to save the canvas first rather than silently capturing (or losing) unsaved edits.'
     },
     {
         path: '/building-sites/screens-and-layouts/versions-and-publishing',
@@ -3754,7 +3817,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Design custom error pages',
         heading: 'What the built-in fallback gives you',
         anchor: '#what-the-built-in-fallback-gives-you',
-        text: 'The fallback is not a blank error page. It renders under your site\'s theme and carries your logo, links to your site\'s public top-level pages, a search box (on the 404) and a footer — so a visitor who lands on a missing address can always get somewhere.\nWhat it cannot do is show the header, navigation and footer you designed: those live in the page you built them on, and on a 404 that page is precisely the one that wasn\'t found. Its page links come from your published pages, and only the public ones — an unlisted, password-protected or members-only page never appears there.\nAssigning a designed page is still the better answer for any site that cares how this moment looks. The fallback is the floor beneath it.\nAssigned error pages are automatically kept out of search results, so a 404 page can\'t itself turn up in a search. A missing address also answers with a real 404 status and a server-rendered page title — your 404 page\'s SEO title when you\'ve set one, otherwise Page not found followed by your site\'s title — so the browser tab and search engines know what the page is before any script runs.'
+        text: 'The fallback is not a blank error page. It renders under your site\'s theme and carries your logo, links to your site\'s public top-level pages, a search box (on the 404) and a footer — so a visitor who lands on a missing address can always get somewhere.\nWhat it cannot do is show the header, navigation and footer you designed: those live in the page you built them on, and on a 404 that page is precisely the one that wasn\'t found. Its page links come from your published pages, and only the public ones — an unlisted, password-protected or members-only page never appears there. They are listed in the order the pages have in Pages, then by name.\nAssigning a designed page is still the better answer for any site that cares how this moment looks. The fallback is the floor beneath it.\nAssigned error pages are automatically kept out of search results, so a 404 page can\'t itself turn up in a search. A missing address also answers with a real 404 status and a server-rendered page title — your 404 page\'s SEO title when you\'ve set one, otherwise Page not found followed by your site\'s title — so the browser tab and search engines know what the page is before any script runs.'
     },
     {
         path: '/building-sites/site-protection/error-screens',
@@ -5910,7 +5973,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Term reference',
         heading: 'Platform & accounts',
         anchor: '#platform--accounts',
-        text: 'Aglyn\nThe platform these docs cover — the console you build in and the sites you publish. Pronounced AG-lin — "ag" as in agriculture, with the stress on the first syllable (IPA /ˈæɡlɪn/).\nAglyn AI\nThe generative side of the assistant: the doors that build a page, layout, page template, reusable component, form, email, campaign, product copy, SEO text or theme change from a description. An add-on on any paid plan, carried by agreement on Enterprise, and metered in credits. Everything it makes is a draft — it never publishes, changes a live page in place or sends anything. → Aglyn AI, Add-ons\nAglyn Assist\nThe chat helper in the console, which answers questions about the product from this documentation and cites the sections it drew on. Aglyn AI is the same assistant when it builds rather than explains. → Aglyn Assist\nOrganization (org)\nThe account entity: one subscription, one team roster, one plugin switchboard, one data-isolation boundary. Everything you own in Aglyn — sites, datasets, media, installs — belongs to an organization. In code and APIs this is always org. → Glossary, Teams & roles\nWorkspace\nThe same entity as an organization, in the product\'s user-facing language — "your workspace", including the {slug}.aglyn.com workspace URL. Workspace never names anything in code; it\'s the word the UI uses for your org. → Glossary\nTenant\nThe published-site runtime: the single deployment that takes any incoming domain, resolves it to one of your sites, and renders its published pages. "Tenant" always means this serving side of the platform — it is not another word for organization. → Glossary, Architecture & multi-tenancy\nHost\nOne site, as the data model sees it: its subdomain or custom domain, its pages and layouts, its media, its member-role projection. An organization o'
+        text: 'Aglyn\nThe platform these docs cover — the console you build in and the sites you publish. Pronounced AG-lin — "ag" as in agriculture, with the stress on the first syllable (IPA /ˈæɡlɪn/).\nAglyn AI\nThe generative side of the assistant: the doors that build a page, layout, page template, reusable component, form, email, campaign, product copy, SEO text or theme change from a description. Included on every plan and metered in its AI credits, with Aglyn AI tiers that add credits on top; carried by agreement on Enterprise. Everything it makes is a draft — it never publishes, changes a live page in place or sends anything. → Aglyn AI, Add-ons\nAglyn Assist\nThe chat helper in the console, which answers questions about the product from this documentation and cites the sections it drew on. Aglyn AI is the same assistant when it builds rather than explains. → Aglyn Assist\nOrganization (org)\nThe account entity: one subscription, one team roster, one plugin switchboard, one data-isolation boundary. Everything you own in Aglyn — sites, datasets, media, installs — belongs to an organization. In code and APIs this is always org. → Glossary, Teams & roles\nWorkspace\nThe same entity as an organization, in the product\'s user-facing language — "your workspace", including the {slug}.aglyn.com workspace URL. Workspace never names anything in code; it\'s the word the UI uses for your org. → Glossary\nTenant\nThe published-site runtime: the single deployment that takes any incoming domain, resolves it to one of your sites, and renders its published pages. "Tenant" always means this serving side of the platform — it is not another word for organization. → Glossary, Architecture & multi-tenancy\nHost\nOne site, as the data model sees it: its subdomain or custom domain, its pages and layouts, its media'
     },
     {
         path: '/concepts/term-reference',
@@ -5966,7 +6029,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Term reference',
         heading: 'Billing & plans',
         anchor: '#billing--plans',
-        text: 'Plan\nThe subscription tier an organization is on. Entitlements resolve from the plan at read time; workspaces without a plan run dark-launch (ungated). → Billing & plans\nEntitlement\nA capability or limit granted by the plan — feature switches and quotas — optionally overridden per organization by staff. → Billing & plans\nQuota\nA numeric entitlement (sites, datasets, storage) checked at the point of use, with warnings as you approach the limit. → Billing & plans\nSeat\nA team-member allowance. Plans include seats; addon seats can be purchased up to a per-plan maximum. → Teams & roles\nMetered usage\nConsumption billed monthly in arrears (storage, delivery) with a live estimate shown before it lands on an invoice. → Billing & plans\nCredit (AI credit)\nThe unit every AI request is measured in — an assistant answer, a rewrite, a generated section, a whole site — drawn from one monthly pool per workspace rather than a meter per feature. What a request costs varies with how much work it is, and a job estimates itself before you confirm. A plan includes a band each month, the Aglyn AI add-on widens it, and a workspace can stop at the band or set a ceiling on what it will pay past it. → Credits and caps, AI assist overage\nAllotment\nOne member\'s, one site collaborator\'s or one whole site\'s monthly share of the workspace\'s AI credits. Hard stops AI there; soft keeps working and notifies. A share of the pool, never an addition to it. → AI allotments'
+        text: 'Plan\nThe subscription tier an organization is on. Entitlements resolve from the plan at read time; workspaces without a plan run dark-launch (ungated). → Billing & plans\nEntitlement\nA capability or limit granted by the plan — feature switches and quotas — optionally overridden per organization by staff. → Billing & plans\nQuota\nA numeric entitlement (sites, datasets, storage) checked at the point of use, with warnings as you approach the limit. → Billing & plans\nSeat\nA team-member allowance. Plans include seats; addon seats can be purchased up to a per-plan maximum. → Teams & roles\nMetered usage\nConsumption billed monthly in arrears (storage, delivery) with a live estimate shown before it lands on an invoice. → Billing & plans\nCredit (AI credit)\nThe unit every AI request is measured in — an assistant answer, a rewrite, a generated section, a whole site — drawn from one monthly pool per workspace rather than a meter per feature. What a request costs varies with how much work it is, and a job estimates itself before you confirm. A plan includes a band each month, an Aglyn AI tier adds credits on top, and a workspace can stop at the band or set a ceiling on what it will pay past it. → Credits and caps, AI assist overage\nAllotment\nOne member\'s, one site collaborator\'s or one whole site\'s monthly share of the workspace\'s AI credits. Hard stops AI there; soft keeps working and notifies. A share of the pool, never an addition to it. → AI allotments'
     },
     {
         path: '/content-and-data/crm/activities',
@@ -7478,7 +7541,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Datasets & Dynamic Content',
         heading: 'Who a dataset is shared with',
         anchor: '#who-a-dataset-is-shared-with',
-        text: 'Datasets belong to the workspace, not to a single site, so one dataset can drive pages on every site you run. When that isn\'t what you want, the Sharing control on each dataset decides which sites can see it:\n- All sites — everyone in the workspace, on every site.\n- Selected sites… — pick the sites that share it, up to 30.\nWhere a new dataset starts depends on where you create it and on your workspace\'s Default sharing for new datasets, the setting at the top of the organization Data page (new media files have a default of their own, on the workspace Media page):\n- Created on a site\'s Data page — it follows that setting. Set to All sites, the dataset starts on All sites. Set to Only the site they were created in, it starts shared with that site alone, and its control reads Selected sites… with just that site picked.\n- Created on the organization Data page — it starts on All sites whatever the setting says, because there is no site to limit it to.\n- Installed from the Marketplace, or created through the REST API — it starts on All sites too. Both act for the whole organization, not for one site.\nDefault sharing for new datasets {#default-dataset-sharing}\nDefault sharing for new datasets, at the top of the organization Data page, decides what a dataset created on a site\'s Data page starts shared with: All sites, or only that site. Only workspace owners and admins can change it.\nThe setting only decides where a new dataset starts. It changes nothing that already exists, and you can widen or narrow any dataset afterwards.\nA dataset with no sharing stored is visible to no site; its control reads Not shared with any site until you choose one of the two.\nThis matters most for agencies. If you run three internal sites alongside twelve client sites, your rate card can be shared '
+        text: 'Datasets belong to the workspace, not to a single site, so one dataset can drive pages on every site you run. When that isn\'t what you want, the Sharing control on each dataset decides which sites can see it:\n- All sites — everyone in the workspace, on every site.\n- Selected sites… — pick the sites that share it, up to 30.\nWhere a new dataset starts depends on where you create it and on your workspace\'s Default sharing for new datasets, the setting at the top of the organization Data page (new media files have a default of their own, on the workspace Media page):\n- Created on a site\'s Data page — it follows that setting. Set to All sites, the dataset starts on All sites. Set to Only the site they were created in, it starts shared with that site alone, and its control reads Selected sites… with just that site picked.\n- Created on the organization Data page — it starts on All sites whatever the setting says, because there is no site to limit it to.\n- Installed from the Marketplace, or created through the REST API — it starts on All sites too. Both act for the whole organization, not for one site.\n- Made by Aglyn AI for a site — for example the lists a guided start builds, such as your packages or FAQs — it starts shared with that site alone, whatever the setting says, because it was made for that site. Share it with more sites from its Sharing control.\nDefault sharing for new datasets {#default-dataset-sharing}\nDefault sharing for new datasets, at the top of the organization Data page, decides what a dataset created on a site\'s Data page starts shared with: All sites, or only that site. Only workspace owners and admins can change it.\nThe setting only decides where a new dataset starts. It changes nothing that already exists, and you can widen or narrow any dataset afterwa'
     },
     {
         path: '/content-and-data/datasets/overview',
@@ -8887,6 +8950,13 @@ export const DOCS_SECTION_INDEX = [
         anchor: '#media-delivery--media-delivery-provider-server',
         text: 'A slot one plugin holds (core.media-delivery, built on the service contracts above): an object store with its own edge, which serves library video in place of the platform\'s media route. Core keeps every access decision and the copy rules; the provider stores copies and mints URLs. Register it from a serverDeclarations entry, so both apps hold it before the first request.\n| API | Semantics |\n| registerMediaDeliveryProvider(provider, { pluginId? }) | Fills the slot. The same plugin registering again replaces its provider; a second plugin throws naming both. |\n| mediaDeliveryProvider(capability) | The provider when it is configured for \'store\' (copies) or \'deliver\' (URLs), else null. Synchronous and free of I/O, so a hot path asks it first. |\nA provider implements isConfigured(capability), putObject({ key, body, contentLength, contentType }), deleteObject(key), deleteObjectsWithPrefix(prefix) and deliveryUrl({ key, expiresAtMs, claims }). Keys come from core and carry the content hash they were copied from; claims carry the org, site, scope and media id a URL was minted for, and grant nothing. A video is served from the provider only when the releasevideodelivery flag, off by default, is on for its org and a copy of its current bytes exists; everything else serves from the platform exactly as before.'
     },
+    {
+        path: '/developers/plugins/reference/plugin-manager-api',
+        title: 'Plugin-manager API reference',
+        heading: 'Domain search — `plugin-domain-search` (`/server`)',
+        anchor: '#domain-search--plugin-domain-search-server',
+        text: 'A slot one plugin holds (core.domain-search, built on the service contracts above): searching for a domain name to register. Its one caller is the staff console\'s client build, whose Domain step shows the names found with the first-year and renewal price side by side and records the pick for the owner to buy after they subscribe. Core asks through the slot and never imports the plugin that talks to a registrar. Register it from a consoleServerDeclarations entry. Search only: nothing here buys, holds or reserves a name.\n| API | Semantics |\n| registerPluginDomainSearch(impl, { pluginId? }) | Fills the slot. A single-implementation contract: a second plugin\'s implementation throws naming both. |\n| domainSearchRegistered() | Whether a plugin offers search in this process. The Domain step shows Find a domain to buy only when it does; otherwise it offers the free address and a domain the owner already has. |\n| searchDomains(query) | { status: \'ok\', results }, { status: \'unavailable\' } (no plugin, or search answered null) or { status: \'failed\' } (search threw), never thrown. Results missing a name, an availability or a finite, non-negative price are dropped. |\nimpl.search(query) returns the exact name when the query is one plus close alternatives, each { name, available, firstYearUsd, renewalUsd, premium? } in US dollars, or null when no registrar is configured in this deployment. It may throw; the caller reports a failed search, never a partial one. The query is a business name said aloud at a booth, so core never logs it, and the staff route that calls the slot allows each staff account a limited number of searches a minute.'
+    },
     {
         path: '/developers/plugins/reference/plugin-manager-api',
         title: 'Plugin-manager API reference',
@@ -9053,7 +9123,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Plugin-manager API reference',
         heading: 'Billing and access keys — `plugin-entitlements`',
         anchor: '#billing-and-access-keys--plugin-entitlements',
-        text: 'A plugin that sells something, gates something or can be paused in an incident declares the KEYS; the numbers stay where they are checked (PLANPRICING for a price, reconciled by check-pricing-drift).\n| API | Semantics |\n| registerPluginEntitlements(registration) | Idempotent per plugin. A seat add-on, lockdown or catalog permission key another plugin owns refuses the registration. Permissions are forwarded to registerPluginPermissions with the owner filled in. |\n| listPluginOrgPermissions() | The keys plugins add to the org permission catalog, in catalog order, with their owner. ORGPERMISSIONS and ORGPERMISSIONKEYS list them after the core keys and are kept in step in place, so a module that imported them first still reads them. resolveOrgPermissions layers a declared key like a core one — role default, custom role, per-member override — the role editor lists it, and a member, role or collaborator write raises org.permissions.changed once per declared key it moved (pluginPermissionChanges). A declaration naming a core key is refused. |\n| hostRoleDefaults on a catalog key | Makes the key per-site for a site collaborator: resolveCollaboratorHostPermissions and resolveMemberHostPermissions decide it from the host role, refined by the per-site toggle on the member document, and projectHostMemberPermissions stamps the site\'s memberPermissions projection. On the server, memberHasPermissionOnHost, permissionRefusal and setHostPermissions are a door\'s rung, its 403 and the toggle write. |\n| listPluginSeatAddons() / pluginSeatAddon(key) | What resolveOrgEntitlements folds: the quota named gains perUnitByPlan[plan] × units and the features switch on, after the org\'s overrides and before nothing. pluginSeatAddonUnits(org.seatAddons, key) / hasPluginSeatAddon(org, key) in plan-enti'
+        text: 'A plugin that sells something, gates something or can be paused in an incident declares the KEYS; the numbers stay where they are checked (PLANPRICING for a price, reconciled by check-pricing-drift).\n| API | Semantics |\n| registerPluginEntitlements(registration) | Idempotent per plugin. A seat add-on, lockdown or catalog permission key another plugin owns refuses the registration. Permissions are forwarded to registerPluginPermissions with the owner filled in. |\n| listPluginOrgPermissions() | The keys plugins add to the org permission catalog, in catalog order, with their owner. ORGPERMISSIONS and ORGPERMISSIONKEYS list them after the core keys and are kept in step in place, so a module that imported them first still reads them. resolveOrgPermissions layers a declared key like a core one — role default, custom role, per-member override — the role editor lists it, and a member, role or collaborator write raises org.permissions.changed once per declared key it moved (pluginPermissionChanges). A declaration naming a core key is refused. |\n| hostRoleDefaults on a catalog key | Makes the key per-site for a site collaborator: resolveCollaboratorHostPermissions and resolveMemberHostPermissions decide it from the host role, refined by the per-site toggle on the member document, and projectHostMemberPermissions stamps the site\'s memberPermissions projection. On the server, memberHasPermissionOnHost, permissionRefusal and setHostPermissions are a door\'s rung, its 403 and the toggle write. |\n| listPluginSeatAddons() / pluginSeatAddon(key) | What resolveOrgEntitlements folds: the quota named gains perUnit(org, plan) × units (or perUnitByPlan[plan] × units) and the features switch on, after the org\'s overrides and before nothing. pluginSeatAddonSoldOn(addon, plan) answers whether a '
     },
     {
         path: '/developers/plugins/reference/plugin-manager-api',
@@ -9571,7 +9641,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Aglyn Assist',
         heading: 'When it builds instead of answering',
         anchor: '#aglyn-ai',
-        text: 'Everything above is the assistant explaining. With AI generation on your plan — the Aglyn AI add-on, or the AI credits a Free workspace gets — the same assistant also builds: whole pages, layouts, page templates, reusable components, forms, designed emails, campaigns, product copy, your search titles and descriptions, a change to your theme, and a small site from one brief. AI jobs in the panel is where you watch one work and open what it made. It opens on its own while a job is running or waiting for you, the AI chip in the top bar says what your jobs are doing, and the Assist button carries a badge while one runs. See Finding your AI jobs.\nEverything it builds arrives as a draft. It never publishes, never changes a live page in place and never sends anything, so a generated page has no address on your live site until you publish it yourself.\nWhat each door does, what it costs in credits and who can use it is in Aglyn AI. To build several things from one chat message, see Build from Assist chat.'
+        text: 'Everything above is the assistant explaining. On every plan, from the AI credits it includes (and any Aglyn AI tier on top), the same assistant also builds: whole pages, layouts, page templates, reusable components, forms, designed emails, campaigns, product copy, your search titles and descriptions, a change to your theme, and a small site from one brief. AI jobs in the panel is where you watch one work and open what it made. It opens on its own while a job is running or waiting for you, the AI chip in the top bar says what your jobs are doing, and the Assist button carries a badge while one runs. See Finding your AI jobs.\nEverything it builds arrives as a draft. It never publishes, never changes a live page in place and never sends anything, so a generated page has no address on your live site until you publish it yourself.\nWhat each door does, what it costs in credits and who can use it is in Aglyn AI. To build several things from one chat message, see Build from Assist chat.'
     },
     {
         path: '/getting-started/aglyn-assist',
@@ -9592,7 +9662,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Aglyn Assist',
         heading: 'Edits in the Besigner',
         anchor: '#edits-in-the-besigner',
-        text: 'With a page, a reusable component or a layout open in the Besigner, you can ask the assistant for a change: "make this hero darker", "add a testimonial band below", "point this button at the pricing page". When your plan includes AI generation — the Aglyn AI add-on, or the AI credits a Free workspace gets — it answers with a Proposed change card listing what would change: elements added, removed, moved or restyled, settings changed, interactions added, and a page\'s search title or description filled in. Anything it could not match to your canvas is listed under Left out.\n- Interactions on the selected element. Ask "when this is clicked, show the panel below" and the assistant proposes an interaction on the element: something a visitor does to it — a click, a hover, scrolling it into view — and the steps that follow, chosen from the presentational ones every plan runs (show, hide or toggle an element, add or remove a class, scroll to or play an element, open or close a drawer or menu, go to a page, show a message). It is added beside anything the element already does, never in place of it; edit or remove it under Interactions like any other. Ask "what does this do?" and it explains the interactions the element carries.\n- Nothing changes until you apply. Apply as draft puts the changes on the open canvas as unsaved edits, all in one step, so a single Undo takes the whole change back. Nothing is saved or published until you do that yourself. A proposed search title or description is filled into Page Properties, where Save SEO stores it.\n- The live version is never edited in place. When the version open is the one your live site shows, the card offers Make a new version instead — the same New version you would use yourself. Once the new version opens, the card offers Apply '
+        text: 'With a page, a reusable component or a layout open in the Besigner, you can ask the assistant for a change: "make this hero darker", "add a testimonial band below", "point this button at the pricing page". On every plan, from its included AI credits (and any Aglyn AI tier on top), it answers with a Proposed change card listing what would change: elements added, removed, moved or restyled, settings changed, interactions added, and a page\'s search title or description filled in. Anything it could not match to your canvas is listed under Left out.\n- Interactions on the selected element. Ask "when this is clicked, show the panel below" and the assistant proposes an interaction on the element: something a visitor does to it — a click, a hover, scrolling it into view — and the steps that follow, chosen from the presentational ones every plan runs (show, hide or toggle an element, add or remove a class, scroll to or play an element, open or close a drawer or menu, go to a page, show a message). It is added beside anything the element already does, never in place of it; edit or remove it under Interactions like any other. Ask "what does this do?" and it explains the interactions the element carries.\n- Nothing changes until you apply. Apply as draft puts the changes on the open canvas as unsaved edits, all in one step, so a single Undo takes the whole change back. Nothing is saved or published until you do that yourself. A proposed search title or description is filled into Page Properties, where Save SEO stores it.\n- The live version is never edited in place. When the version open is the one your live site shows, the card offers Make a new version instead — the same New version you would use yourself. Once the new version opens, the card offers Apply as draft there.\n- Select th'
     },
     {
         path: '/getting-started/aglyn-assist',
@@ -9725,7 +9795,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'The console tour',
         heading: 'The Sites list',
         anchor: '#the-sites-list',
-        text: 'All Sites is the front door of a workspace: one card per site, for the workspace currently selected in the switcher, in name order. A site you can reach in another organization isn\'t missing — it\'s behind the workspace switcher.\nEach card carries:\n- The site\'s display name as the title, with its hostname underneath as the subheader — the custom domain when the site has one, otherwise its name.aglyn.app address. Both are also listed inside the card, as Aglyn Domain and Custom Domain.\n- A status pill (below).\n- Visit, which opens the live site in a new tab, and Manage, which opens that site\'s dashboard in the console.\nAbove the cards are a Search box and a Filters button — the same controls a table\'s toolbar has, over the cards. Search finds a site by the start of any word of its name, its slug (the name in name.aglyn.app) or its custom domain: harbor, bakery and shop.harbor all find Harbor Bakery at shop.harbor-bakery.com. Filters narrows the cards by Custom domain (Connected or None) and by the day a site was Created — is, after, on or after, before or on or before a day. Each filter in force shows as a chip above the cards; remove a chip to drop it. A filter on the created date lists the cards newest first instead of by name.\nThe search and the filters are answered by the query that reads the cards, across every site you have in the workspace, not only the cards on screen. The cards come twelve at a time; Load more adds the next twelve that match. The site count opposite the heading always counts every site. Status, plan, owner and the last-updated date are not filters: a site\'s status can change with no save at all (a timed suspension ends on its own), and a site doesn\'t store its plan, owner or template. See Filter and search a list.\nA site card {#a-site-card}\nEach c'
+        text: 'All Sites is the front door of a workspace: one card per site, for the workspace currently selected in the switcher, with the sites you pinned first and the rest in name order. A site you can reach in another organization isn\'t missing — it\'s behind the workspace switcher.\nEach card carries:\n- The site\'s display name as the title, with its hostname underneath as the subheader — the custom domain when the site has one, otherwise its name.aglyn.app address. Both are also listed inside the card, as Aglyn Domain and Custom Domain.\n- A status pill (below).\n- A pin, beside the pill. Pinned sites lead the list in the order you pinned them, and the site switcher in the top bar lists them first too. You can pin up to five sites in each workspace; pinning a sixth asks which one it replaces. Your pins are yours alone, and they follow you to every device you sign in on.\n- Visit, which opens the live site in a new tab, and Manage, which opens that site\'s dashboard in the console.\nAbove the cards are a Search box and a Filters button — the same controls a table\'s toolbar has, over the cards. Search finds a site by the start of any word of its name, its slug (the name in name.aglyn.app) or its custom domain: harbor, bakery and shop.harbor all find Harbor Bakery at shop.harbor-bakery.com. Filters narrows the cards by Custom domain (Connected or None) and by the day a site was Created — is, after, on or after, before or on or before a day. Each filter in force shows as a chip above the cards; remove a chip to drop it. A filter on the created date lists the cards newest first instead of by name. While a search or a filter is in force, pinned sites don\'t jump to the top: they sit where the list puts them, with their pin showing.\nThe search and the filters are answered by the query that re'
     },
     {
         path: '/getting-started/console-tour',
@@ -9823,7 +9893,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Publish your first page',
         heading: '3. Preview and publish',
         anchor: '#3-preview-and-publish',
-        text: '1. Use the artboard light/dark toggle to check both color schemes.\n2. Save the canvas. Saving writes your working version — it isn\'t publishing.\n3. Publish. The page\'s slug is registered in the routing map and the page goes live on your site\'s domain.\nKeeping more than one version is a Pro feature Every page is created with one working version, and Save updates that version on every plan — the core loop above needs nothing extra. Keeping more than one — named snapshots you can reopen, publish to roll back to, or schedule — requires Pro or above, and scheduling a version requires Business or above. On Free and Starter the editor answers "Versioning requires a Pro plan — see Billing to upgrade" instead of opening the name dialog. See Versions & scheduled publishing.\nThe Live button The Live button is environment-aware — in production it reflects your published saves so you can jump straight to the real page.'
+        text: '1. Use the artboard light/dark toggle to check both color schemes.\n2. Save the canvas. Saving writes your working version — it isn\'t publishing.\n3. Publish. The page\'s slug is registered in the routing map and the page goes live on your site\'s domain.\nKeeping more than one version is a Pro feature Every page is created with one working version, and Save updates that version on every plan — the core loop above needs nothing extra. Keeping more than one — named snapshots you can reopen, publish to roll back to, or schedule — requires Pro or above, and scheduling a version requires Business or above. On Free and Starter the Versions dialog still shows New version, disabled, with a note naming the plan that includes it and an Upgrade button to the plans on Billing. See Versions & scheduled publishing.\nThe Live button The Live button is environment-aware — in production it reflects your published saves so you can jump straight to the real page.'
     },
     {
         path: '/getting-started/publish-your-first-screen',
@@ -11664,7 +11734,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Add-ons',
         heading: 'Aglyn AI',
         anchor: '#aglyn-ai',
-        text: 'Aglyn AI is the generative add-on: with it on, the assistant builds for you — pages, components, emails, campaigns, products and more — rather than only answering questions about them. It is bought once for the workspace, on any paid plan, and applies to every member who has the permission to generate. What each door does is under Aglyn AI.\n- Everything it builds is a draft. The add-on cannot publish a page, change a live one or send an email. It writes drafts and unpublished versions, which a person reviews and publishes through the buttons that already exist — see the draft rule.\n- One pool, one meter. The add-on adds a band of AI credits to the band your plan already includes, every month. There is no second meter: the AI credits meter on Billing → Usage shows your plan\'s credits and the add-on\'s as one figure, and the same overage rate, stop switch and monthly ceiling apply to the whole band — see AI credits and overage.\n- Priced by plan. The add-on\'s monthly price and the credits it adds both rise with the plan. The figures are on aglyn.com/pricing and in Billing before you confirm; on annual billing it bills yearly with the plan, like every add-on. Enterprise workspaces carry generative building in their agreement instead of buying it.\n- Starter widens a band it already has. Starter includes its own monthly AI credits, and credits past them are sold at the same rate as Pro — so the stop switch and the ceiling are on its billing page with or without the add-on. Adding Aglyn AI increases the band and opens generative building.\n- You can see where it is used before you buy it. On a paid plan without it, Create with AI still shows on the Pages, Templates, Layouts, Forms, Components, Automation, Functions & Variables and email Templates pages, on Products, and on Marke'
+        text: 'Every plan\'s included AI credits pay for all of Aglyn AI: the assistant\'s answers and building for you — pages, components, emails, campaigns, products and more. An Aglyn AI tier adds more credits on top, every month. Choose it in the Aglyn AI row of the Plan add-ons card under Billing → Plan: the Aglyn AI tier field lists every tier with the credits it adds and its price, and marks the one you have as Current. Pick one and choose Apply, or pick No tier and choose Remove; the change is shown with what it costs before you confirm it. What each AI door does is under Aglyn AI.\n- Six tiers, chosen on their own. Spark, Boost, Plus, Max, Ultra and Studio, from 4,000 to 149,000 extra credits a month (see AI credits). Any paid plan can have any tier, at the same price, and changing your plan keeps your tier. Prices are on aglyn.com/pricing and in Billing before you confirm; on annual billing a tier bills yearly with the plan, like every add-on. Enterprise workspaces carry more AI in their agreement instead.\n- Everything it builds is a draft. Aglyn AI cannot publish a page, change a live one or send an email. It writes drafts and unpublished versions, which a person reviews and publishes through the buttons that already exist — see the draft rule.\n- One pool, one meter. A tier adds its credits to the credits your plan already includes. There is no second meter: the AI credits meter on Billing → Usage shows your plan\'s credits and your tier\'s as one figure, and the same overage rate, stop switch and monthly ceiling apply to the whole pool — see AI credits and overage.\n- Moving up to a bigger tier is charged now, prorated for the rest of the period, like a plan upgrade. Moving down or removing the tier takes effect at the end of the period you already paid for, like a plan downgra'
     },
     {
         path: '/workspace-and-billing/billing-and-plans/add-ons',
@@ -11783,7 +11853,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Downgrading, canceling & your data',
         heading: 'Deleting a single site',
         anchor: '#deleting-a-single-site',
-        text: 'To remove just one site (not the whole organization), open the site\'s Admin → Danger zone and use Delete site. A site admin types the site name to confirm, and it\'s deleted immediately — its pages, media, and settings are permanently removed and its address stops resolving. Unlike an organization deletion there\'s no hold, so export a backup first (Setup → Backup & restore) if you might want it back. Your other sites and the organization are unaffected.\nA site in a consent group can\'t be deleted while it\'s in the group, because the group\'s other sites honor the unsubscribes it holds. Remove it from the group first, which copies those opt-outs to the sites that stay, then delete it. The same applies while a consent group change that includes the site is still finishing.'
+        text: 'To remove just one site (not the whole organization), open the site\'s Admin → Danger zone and use Delete site. A site admin types the site name to confirm, and it\'s deleted immediately — its pages, media, and settings are permanently removed and its address stops resolving. Unlike an organization deletion there\'s no hold, so export a backup first (Setup → Backup & restore) if you might want it back. Your other sites and the organization are unaffected.\nDeleting a site also deletes what is the site\'s own:\n- Datasets shared with this site only, with all their records. The Delete site card lists them, with how many records each holds, before you confirm. A dataset the site shares with other sites stays, and the site is removed from its sharing. A dataset shared with All sites isn\'t affected.\n- The site\'s AI jobs, AI insights and Assist conversations.\nTo keep a dataset, share it with another site, or with All sites, from its Sharing control on the Data page before you delete the site.\nA site in a consent group can\'t be deleted while it\'s in the group, because the group\'s other sites honor the unsubscribes it holds. Remove it from the group first, which copies those opt-outs to the sites that stay, then delete it. The same applies while a consent group change that includes the site is still finishing.'
     },
     {
         path: '/workspace-and-billing/billing-and-plans/downgrading-and-canceling',
@@ -11811,7 +11881,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Billing & Plans',
         heading: 'The Billing page',
         anchor: '#billing-page',
-        text: 'Organization → Billing is where your workspace\'s plan, usage, invoices and billing details live, in four tabs: Plan, Usage, Invoices and Settings. Members whose role carries View billing can read every tab; changing anything — the plan, add-ons, caps, cards, the billing address — needs Manage billing. Owners and admins have both.\nCurrent plan {#current-plan}\nThe Current plan card at the top of the Plan tab names your plan, the state of its subscription and its price, with the plan\'s headline limits — sites, team seats and campaign emails a month — beside it. Your full usage against every limit is on the Usage tab.\nWith Manage billing the card also carries the plan\'s controls:\n- Update payment method, in the card\'s header, replaces the card your subscription is charged to in one step, through Stripe\'s own form. It turns solid while a payment is failing, when it is the one thing on the page that matters.\n- Manage payment methods opens the Settings tab, where every card on file is listed — see Payment methods.\n- Cancel subscription opens a short dialog before anything changes — see What the Cancel button actually opens. Once a cancel is scheduled the same button reads Resume subscription.\n- When a move to a lower plan is scheduled, a chip says which plan and on what date, and Keep my current plan undoes it — see Changing your mind.\nA sentence under the limits says when the current period renews or ends, and any add-ons you hold are listed at the bottom.\nBilling links in emails {#billing-link}\nA billing link in an email from Aglyn — a failed-payment notice, say — opens the Billing page of your workspace, asking you to sign in first if you need to. Because the link cannot know which workspace it is about, an account that belongs to one workspace goes straight to its Billing '
+        text: 'Organization → Billing is where your workspace\'s plan, usage, invoices and billing details live, in four tabs: Plan, Usage, Invoices and Settings. Members whose role carries View billing can read every tab; changing anything — the plan, add-ons, caps, cards, the billing address — needs Manage billing. Owners and admins have both.\nCurrent plan {#current-plan}\nThe Current plan card at the top of the Plan tab names your plan, the state of its subscription and its price, with the plan\'s headline limits — sites, team seats and campaign emails a month — beside it. Your full usage against every limit is on the Usage tab.\nWith Manage billing the card also carries the plan\'s controls:\n- Update payment method, in the card\'s header, replaces the card your subscription is charged to in one step, through Stripe\'s own form. It turns solid while a payment is failing, when it is the one thing on the page that matters.\n- Manage payment methods opens the Settings tab, where every card on file is listed — see Payment methods.\n- Cancel subscription opens a short dialog before anything changes — see What the Cancel button actually opens. Once a cancel is scheduled the same button reads Resume subscription.\n- When a move to a lower plan is scheduled, a chip says which plan and on what date, and Keep my current plan undoes it — see Changing your mind.\nA sentence under the limits says when the current period renews or ends, and any add-ons you hold are listed at the bottom.\nLocked features {#locked-features}\nA feature your plan doesn\'t include stays on screen, turned off, with Included from and the plan that has it, and an Upgrade link to the plans on this page; moving to that plan turns it on, with nothing else to set up. A dashboard card from a higher plan shows its name, what it does and th'
     },
     {
         path: '/workspace-and-billing/billing-and-plans/overview',
@@ -11839,7 +11909,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Billing & Plans',
         heading: 'AI assist overage',
         anchor: '#assist-overage',
-        text: 'Paid plans include a monthly band of AI assist credits — the Aglyn Assist credits meter on the billing page shows how much of it this month\'s assistant use has drawn. The Aglyn AI add-on widens that band and opens generative building; it is one pool, so everything below applies to the widened band as a whole. What the credits are spent on, and what each kind of request costs relative to the others, is under Aglyn AI. On a plan that sells credits past the band, reaching it is not a wall:\n- The assistant keeps answering. Nothing stops because you reached your included credits.\n- The extra credits are billed on your monthly invoice, per 1,000 credits over the band, at your plan\'s rate — the exact figure is on the pricing page and in Billing → Usage → AI assist overage.\nIf you would rather the assistant stopped {#stop-ai-assist-at-the-included-band}\nTurn on Stop AI assist at the included band in Billing → Usage → AI assist overage. This is optional and off unless you choose it. Once it is on, the assistant refuses once the included credits are used — the refusal names this switch and where it lives — and you are never billed for AI assist. Turn it off at any time to keep going at your plan\'s rate; either change takes effect on the next message. Changing it needs the Manage billing permission.\nIf you would rather it kept going, up to a figure you choose {#ai-overage-ceiling}\nWith the switch off, the same card offers a monthly ceiling on the extra credits you will pay for: Stop AI when this month\'s overage reaches a dollar figure you type. Once the month\'s overage — the extra credits priced at your plan\'s rate, exactly as the invoice would price them — reaches that figure, the assistant stops for the rest of the month, and the refusal names the ceiling and where to raise or r'
+        text: 'Paid plans include a monthly band of AI assist credits — the Aglyn Assist credits meter on the billing page shows how much of it this month\'s assistant use has drawn. The included credits pay for every AI request, building included, and an Aglyn AI tier adds credits on top; it is one pool, so everything below applies to the widened band as a whole. What the credits are spent on, and what each kind of request costs relative to the others, is under Aglyn AI. On a plan that sells credits past the band, reaching it is not a wall:\n- The assistant keeps answering. Nothing stops because you reached your included credits.\n- The extra credits are billed on your monthly invoice, per 1,000 credits over the band, at your plan\'s rate — the exact figure is on the pricing page and in Billing → Usage → AI assist overage.\nIf you would rather the assistant stopped {#stop-ai-assist-at-the-included-band}\nTurn on Stop AI assist at the included band in Billing → Usage → AI assist overage. This is optional and off unless you choose it. Once it is on, the assistant refuses once the included credits are used — the refusal names this switch and where it lives — and you are never billed for AI assist. Turn it off at any time to keep going at your plan\'s rate; either change takes effect on the next message. Changing it needs the Manage billing permission.\nIf you would rather it kept going, up to a figure you choose {#ai-overage-ceiling}\nWith the switch off, the same card offers a monthly ceiling on the extra credits you will pay for: Stop AI when this month\'s overage reaches a dollar figure you type. Once the month\'s overage — the extra credits priced at your plan\'s rate, exactly as the invoice would price them — reaches that figure, the assistant stops for the rest of the month, and the refusal n'
     },
     {
         path: '/workspace-and-billing/billing-and-plans/overview',