[{"data":1,"prerenderedAt":887},["ShallowReactive",2],{"navigation_docs":3,"-docs-deployment-upgrade":364,"-docs-deployment-upgrade-surround":882},[4,8,34,64,90,139,157,171,193,227,241,266,312,342],{"title":5,"path":6,"stem":7},"Documentation","\u002Fdocs","docs\u002Findex",{"title":9,"path":10,"stem":11,"children":12},"Getting started","\u002Fdocs\u002Fgetting-started","docs\u002F01.getting-started\u002Findex",[13,14,18,22,26,30],{"title":9,"path":10,"stem":11},{"title":15,"path":16,"stem":17},"Introduction","\u002Fdocs\u002Fgetting-started\u002Fintroduction","docs\u002F01.getting-started\u002F01.introduction",{"title":19,"path":20,"stem":21},"Concepts","\u002Fdocs\u002Fgetting-started\u002Fconcepts","docs\u002F01.getting-started\u002F02.concepts",{"title":23,"path":24,"stem":25},"Quickstart (5 minutes)","\u002Fdocs\u002Fgetting-started\u002Fquickstart","docs\u002F01.getting-started\u002F03.quickstart",{"title":27,"path":28,"stem":29},"Local development","\u002Fdocs\u002Fgetting-started\u002Flocal-development","docs\u002F01.getting-started\u002F04.local-development",{"title":31,"path":32,"stem":33},"FAQ","\u002Fdocs\u002Fgetting-started\u002Ffaq","docs\u002F01.getting-started\u002F05.faq",{"title":35,"path":36,"stem":37,"children":38},"Architecture","\u002Fdocs\u002Farchitecture","docs\u002F02.architecture\u002Findex",[39,40,44,48,52,56,60],{"title":35,"path":36,"stem":37},{"title":41,"path":42,"stem":43},"Architecture overview","\u002Fdocs\u002Farchitecture\u002Foverview","docs\u002F02.architecture\u002F01.overview",{"title":45,"path":46,"stem":47},"Services","\u002Fdocs\u002Farchitecture\u002Fservices","docs\u002F02.architecture\u002F02.services",{"title":49,"path":50,"stem":51},"Request lifecycle","\u002Fdocs\u002Farchitecture\u002Frequest-lifecycle","docs\u002F02.architecture\u002F03.request-lifecycle",{"title":53,"path":54,"stem":55},"Data model","\u002Fdocs\u002Farchitecture\u002Fdata-model","docs\u002F02.architecture\u002F04.data-model",{"title":57,"path":58,"stem":59},"Status and evidence","\u002Fdocs\u002Farchitecture\u002Fstatus-and-evidence","docs\u002F02.architecture\u002F05.status-and-evidence",{"title":61,"path":62,"stem":63},"Target architecture and authority","\u002Fdocs\u002Farchitecture\u002Ftarget-architecture","docs\u002F02.architecture\u002F06.target-architecture",{"title":65,"path":66,"stem":67,"children":68},"Auth","\u002Fdocs\u002Fauth","docs\u002F03.auth\u002Findex",[69,70,74,78,82,86],{"title":65,"path":66,"stem":67},{"title":71,"path":72,"stem":73},"Overview","\u002Fdocs\u002Fauth\u002Foverview","docs\u002F03.auth\u002F01.overview",{"title":75,"path":76,"stem":77},"Organization and agent model","\u002Fdocs\u002Fauth\u002Forg-project-model","docs\u002F03.auth\u002F02.org-project-model",{"title":79,"path":80,"stem":81},"Issuing API keys","\u002Fdocs\u002Fauth\u002Fissuing-api-keys","docs\u002F03.auth\u002F03.issuing-api-keys",{"title":83,"path":84,"stem":85},"Multi-tenant RLS","\u002Fdocs\u002Fauth\u002Fmulti-tenant-rls","docs\u002F03.auth\u002F04.multi-tenant-rls",{"title":87,"path":88,"stem":89},"Operator sessions and step-up","\u002Fdocs\u002Fauth\u002Foperator-sessions","docs\u002F03.auth\u002F05.operator-sessions",{"title":91,"path":92,"stem":93,"children":94},"Proxy","\u002Fdocs\u002Fproxy","docs\u002F04.proxy\u002Findex",[95,96,99,103,107,111,115,119,123,127,131,135],{"title":91,"path":92,"stem":93},{"title":71,"path":97,"stem":98},"\u002Fdocs\u002Fproxy\u002Foverview","docs\u002F04.proxy\u002F01.overview",{"title":100,"path":101,"stem":102},"Authentication","\u002Fdocs\u002Fproxy\u002Fauthentication","docs\u002F04.proxy\u002F02.authentication",{"title":104,"path":105,"stem":106},"Request routing","\u002Fdocs\u002Fproxy\u002Frequest-routing","docs\u002F04.proxy\u002F03.request-routing",{"title":108,"path":109,"stem":110},"Sessions","\u002Fdocs\u002Fproxy\u002Fsessions","docs\u002F04.proxy\u002F04.sessions",{"title":112,"path":113,"stem":114},"Directives","\u002Fdocs\u002Fproxy\u002Fdirectives","docs\u002F04.proxy\u002F05.directives",{"title":116,"path":117,"stem":118},"Idempotency and budgets","\u002Fdocs\u002Fproxy\u002Fidempotency-and-budgets","docs\u002F04.proxy\u002F06.idempotency-and-budgets",{"title":120,"path":121,"stem":122},"Rate limiting","\u002Fdocs\u002Fproxy\u002Frate-limiting","docs\u002F04.proxy\u002F07.rate-limiting",{"title":124,"path":125,"stem":126},"Provider adapters","\u002Fdocs\u002Fproxy\u002Fprovider-adapters","docs\u002F04.proxy\u002F08.provider-adapters",{"title":128,"path":129,"stem":130},"Auth caching","\u002Fdocs\u002Fproxy\u002Fauth-caching","docs\u002F04.proxy\u002F09.auth-caching",{"title":132,"path":133,"stem":134},"Configuration","\u002Fdocs\u002Fproxy\u002Fconfiguration","docs\u002F04.proxy\u002F10.configuration",{"title":136,"path":137,"stem":138},"Provider routing and resilience","\u002Fdocs\u002Fproxy\u002Fprovider-routing-and-resilience","docs\u002F04.proxy\u002F11.provider-routing-and-resilience",{"title":140,"path":141,"stem":142,"children":143},"Memory","\u002Fdocs\u002Fmemory","docs\u002F05.memory\u002Findex",[144,145,149,153],{"title":140,"path":141,"stem":142},{"title":146,"path":147,"stem":148},"Memory overview","\u002Fdocs\u002Fmemory\u002Foverview","docs\u002F05.memory\u002F01.overview",{"title":150,"path":151,"stem":152},"Write path","\u002Fdocs\u002Fmemory\u002Fwrite-path","docs\u002F05.memory\u002F02.write-path",{"title":154,"path":155,"stem":156},"Search and lifecycle","\u002Fdocs\u002Fmemory\u002Fsearch-and-lifecycle","docs\u002F05.memory\u002F03.search-and-lifecycle",{"title":158,"path":159,"stem":160,"children":161},"Context","\u002Fdocs\u002Fcontext","docs\u002F06.context\u002Findex",[162,163,167],{"title":158,"path":159,"stem":160},{"title":164,"path":165,"stem":166},"Assembly pipeline","\u002Fdocs\u002Fcontext\u002Foverview","docs\u002F06.context\u002F01.overview",{"title":168,"path":169,"stem":170},"Ranking and packing","\u002Fdocs\u002Fcontext\u002Franking-and-packing","docs\u002F06.context\u002F02.ranking-and-packing",{"title":172,"path":173,"stem":174,"children":175},"Intelligence","\u002Fdocs\u002Fintelligence","docs\u002F07.intelligence\u002Findex",[176,177,181,185,189],{"title":172,"path":173,"stem":174},{"title":178,"path":179,"stem":180},"Workers","\u002Fdocs\u002Fintelligence\u002Fworkers","docs\u002F07.intelligence\u002F01.workers",{"title":182,"path":183,"stem":184},"Extraction","\u002Fdocs\u002Fintelligence\u002Fextraction","docs\u002F07.intelligence\u002F02.extraction",{"title":186,"path":187,"stem":188},"Embedder","\u002Fdocs\u002Fintelligence\u002Fembedder","docs\u002F07.intelligence\u002F03.embedder",{"title":190,"path":191,"stem":192},"Extraction evaluation","\u002Fdocs\u002Fintelligence\u002Fevaluation","docs\u002F07.intelligence\u002F04.evaluation",{"title":194,"path":195,"stem":196,"children":197},"API reference","\u002Fdocs\u002Fapi-reference","docs\u002F08.api-reference\u002Findex",[198,199,203,207,211,215,219,223],{"title":194,"path":195,"stem":196},{"title":200,"path":201,"stem":202},"Chat completions","\u002Fdocs\u002Fapi-reference\u002Fchat-completions","docs\u002F08.api-reference\u002F01.chat-completions",{"title":204,"path":205,"stem":206},"Responses","\u002Fdocs\u002Fapi-reference\u002Fresponses","docs\u002F08.api-reference\u002F02.responses",{"title":208,"path":209,"stem":210},"Errors","\u002Fdocs\u002Fapi-reference\u002Ferrors","docs\u002F08.api-reference\u002F03.errors",{"title":212,"path":213,"stem":214},"Health and metrics","\u002Fdocs\u002Fapi-reference\u002Fproxy-health","docs\u002F08.api-reference\u002F04.proxy-health",{"title":216,"path":217,"stem":218},"HTTP route inventory","\u002Fdocs\u002Fapi-reference\u002Fhttp-routes","docs\u002F08.api-reference\u002F05.http-routes",{"title":220,"path":221,"stem":222},"Management API","\u002Fdocs\u002Fapi-reference\u002Fmanagement-api","docs\u002F08.api-reference\u002F06.management-api",{"title":224,"path":225,"stem":226},"Auth gRPC (ValidateToken, ValidateAgent)","\u002Fdocs\u002Fapi-reference\u002Fauth-grpc","docs\u002F08.api-reference\u002F07.auth-grpc",{"title":228,"path":229,"stem":230,"children":231},"MCP","\u002Fdocs\u002Fmcp","docs\u002F09.mcp\u002Findex",[232,233,237],{"title":228,"path":229,"stem":230},{"title":234,"path":235,"stem":236},"Memory server","\u002Fdocs\u002Fmcp\u002Fmemory-server","docs\u002F09.mcp\u002F01.memory-server",{"title":238,"path":239,"stem":240},"Operator gateway","\u002Fdocs\u002Fmcp\u002Foperator-gateway","docs\u002F09.mcp\u002F02.operator-gateway",{"title":242,"path":243,"stem":244,"children":245},"Security","\u002Fdocs\u002Fsecurity","docs\u002F10.security\u002Findex",[246,247,251,254,258,262],{"title":242,"path":243,"stem":244},{"title":248,"path":249,"stem":250},"Security overview","\u002Fdocs\u002Fsecurity\u002Foverview","docs\u002F10.security\u002F01.overview",{"title":100,"path":252,"stem":253},"\u002Fdocs\u002Fsecurity\u002Fauthentication","docs\u002F10.security\u002F02.authentication",{"title":255,"path":256,"stem":257},"Tenant isolation","\u002Fdocs\u002Fsecurity\u002Ftenant-isolation","docs\u002F10.security\u002F03.tenant-isolation",{"title":259,"path":260,"stem":261},"Secrets and keys","\u002Fdocs\u002Fsecurity\u002Fsecrets-and-keys","docs\u002F10.security\u002F04.secrets-and-keys",{"title":263,"path":264,"stem":265},"Prompt injection","\u002Fdocs\u002Fsecurity\u002Fprompt-injection","docs\u002F10.security\u002F05.prompt-injection",{"title":267,"path":268,"stem":269,"children":270},"Operations","\u002Fdocs\u002Foperations","docs\u002F11.operations\u002Findex",[271,272,276,280,284,288,292,296,300,304,308],{"title":267,"path":268,"stem":269},{"title":273,"path":274,"stem":275},"Observability","\u002Fdocs\u002Foperations\u002Fobservability","docs\u002F11.operations\u002F01.observability",{"title":277,"path":278,"stem":279},"Traces and ClickHouse","\u002Fdocs\u002Foperations\u002Ftraces-and-clickhouse","docs\u002F11.operations\u002F02.traces-and-clickhouse",{"title":281,"path":282,"stem":283},"Health checks","\u002Fdocs\u002Foperations\u002Fhealth-checks","docs\u002F11.operations\u002F03.health-checks",{"title":285,"path":286,"stem":287},"Incident response","\u002Fdocs\u002Foperations\u002Fincident-response","docs\u002F11.operations\u002F04.incident-response",{"title":289,"path":290,"stem":291},"Troubleshooting","\u002Fdocs\u002Foperations\u002Ftroubleshooting","docs\u002F11.operations\u002F05.troubleshooting",{"title":293,"path":294,"stem":295},"Billing and budgets","\u002Fdocs\u002Foperations\u002Fbilling-and-budgets","docs\u002F11.operations\u002F06.billing-and-budgets",{"title":297,"path":298,"stem":299},"Evidence and relay","\u002Fdocs\u002Foperations\u002Fevidence-and-relay","docs\u002F11.operations\u002F07.evidence-and-relay",{"title":301,"path":302,"stem":303},"Console","\u002Fdocs\u002Foperations\u002Fconsole","docs\u002F11.operations\u002F08.console",{"title":305,"path":306,"stem":307},"Failure modes and recovery","\u002Fdocs\u002Foperations\u002Ffailure-and-recovery","docs\u002F11.operations\u002F09.failure-and-recovery",{"title":309,"path":310,"stem":311},"Data lifecycle and deletion","\u002Fdocs\u002Foperations\u002Fdata-lifecycle-and-deletion","docs\u002F11.operations\u002F10.data-lifecycle-and-deletion",{"title":313,"path":314,"stem":315,"children":316},"Deployment","\u002Fdocs\u002Fdeployment","docs\u002F12.deployment\u002Findex",[317,318,322,326,330,334,338],{"title":313,"path":314,"stem":315},{"title":319,"path":320,"stem":321},"Docker Compose (dev)","\u002Fdocs\u002Fdeployment\u002Fdocker-compose","docs\u002F12.deployment\u002F01.docker-compose",{"title":323,"path":324,"stem":325},"Environment variables","\u002Fdocs\u002Fdeployment\u002Fenvironment-variables","docs\u002F12.deployment\u002F02.environment-variables",{"title":327,"path":328,"stem":329},"Kubernetes","\u002Fdocs\u002Fdeployment\u002Fkubernetes","docs\u002F12.deployment\u002F03.kubernetes",{"title":331,"path":332,"stem":333},"Production readiness","\u002Fdocs\u002Fdeployment\u002Fproduction-readiness","docs\u002F12.deployment\u002F04.production-readiness",{"title":335,"path":336,"stem":337},"v1-single-node profile","\u002Fdocs\u002Fdeployment\u002Fv1-single-node","docs\u002F12.deployment\u002F05.v1-single-node",{"title":339,"path":340,"stem":341},"Upgrade and support window","\u002Fdocs\u002Fdeployment\u002Fupgrade","docs\u002F12.deployment\u002F06.upgrade",{"title":343,"path":344,"stem":345,"children":346},"Reference","\u002Fdocs\u002Freference","docs\u002F13.reference\u002Findex",[347,348,352,356,360],{"title":343,"path":344,"stem":345},{"title":349,"path":350,"stem":351},"Glossary","\u002Fdocs\u002Freference\u002Fglossary","docs\u002F13.reference\u002F01.glossary",{"title":353,"path":354,"stem":355},"Roadmap and gates","\u002Fdocs\u002Freference\u002Froadmap","docs\u002F13.reference\u002F02.roadmap",{"title":357,"path":358,"stem":359},"Architecture decisions","\u002Fdocs\u002Freference\u002Fadr","docs\u002F13.reference\u002F03.adr",{"title":361,"path":362,"stem":363},"Compatibility and versioning","\u002Fdocs\u002Freference\u002Fcompatibility","docs\u002F13.reference\u002F04.compatibility",{"id":365,"title":339,"audience":366,"author":367,"authorUrl":367,"body":368,"coverIndex":367,"coverLabel":367,"coverTone":367,"date":367,"decisionStatus":367,"description":873,"excerpt":367,"extension":874,"featured":875,"historical":875,"meta":876,"navigation":877,"path":340,"readingTime":367,"scope":878,"seo":879,"sourceOfTruth":880,"status":375,"stem":341,"tags":367,"verifiedDate":376,"__hash__":881},"docs\u002Fdocs\u002F12.deployment\u002F06.upgrade.md","operator",null,{"type":369,"value":370,"toc":863},"minimark",[371,377,387,392,418,480,494,508,512,515,532,643,647,662,699,702,706,709,759,782,786,792,823,842,846],[372,373],"page-status",{"note":374,"status":375,"verified":376},"Migration counts and rollback limits are verified from the tree; no version support window is signed","PROVISIONAL","2026-11-17",[378,379,380,381,386],"p",{},"This page is the release-level upgrade reference. The step-by-step procedure — drain, stop, snapshot, migrate,\nprovision, start, and the digest-based rollback — is on the\n",[382,383,385],"a",{"href":384},"\u002Fdocs\u002Fdeployment\u002Fv1-single-node#upgrade-and-rollback","v1-single-node profile page",". This page adds what that procedure\ndepends on: how many migrations you are applying, which ones cannot be undone, what must exist before you start, and\nwhat a rollback cannot recover.",[388,389,391],"h2",{"id":390},"versions-and-migrations","Versions and migrations",[378,393,394,395,399,400,403,404,407,408,411,412,407,414,417],{},"The proposed reference path is ",[396,397,398],"code",{},"v0.1.9"," → current ",[396,401,402],{},"main"," head. The PostgreSQL counts below are ",[396,405,406],{},".up.sql"," files under\n",[396,409,410],{},"infra\u002Fmigrations\u002Fpostgres\u002F",", applied in order by the migration runner; the ClickHouse counts are ",[396,413,406],{},[396,415,416],{},"infra\u002Fmigrations\u002Fclickhouse\u002F",", and only a deployment that runs ClickHouse applies them.",[419,420,421,437],"table",{},[422,423,424],"thead",{},[425,426,427,431,434],"tr",{},[428,429,430],"th",{},"Point",[428,432,433],{},"PostgreSQL migrations",[428,435,436],{},"ClickHouse migrations",[438,439,440,453,467],"tbody",{},[425,441,442,447,450],{},[443,444,445],"td",{},[396,446,398],{},[443,448,449],{},"39",[443,451,452],{},"5",[425,454,455,461,464],{},[443,456,457,460],{},[396,458,459],{},"6f12c96c"," (2026-11-10)",[443,462,463],{},"58",[443,465,466],{},"6",[425,468,469,475,478],{},[443,470,471,472,474],{},"current ",[396,473,402],{}," head",[443,476,477],{},"76",[443,479,466],{},[378,481,482,483,485,486,489,490,493],{},"An upgrade from ",[396,484,398],{}," therefore applies 37 PostgreSQL migrations. The ",[396,487,488],{},"v1-single-node"," profile runs PostgreSQL\nmigrations only; the one additional ClickHouse migration applies only to a deployment that runs ClickHouse separately.\nThe counts are a property of the checkout you build from, not of the tag you are leaving: the ",[396,491,492],{},"migrate"," one-shot is\nbuilt from the target checkout, so build and migrate from the same commit.",[378,495,496,497,499,500,503,504,507],{},"The ",[396,498,398],{}," row is checkable rather than remembered: ",[396,501,502],{},"infra\u002Fmigrations\u002Fpostgres\u002Ftestdata\u002Freleased\u002Fv0.1.9.sha256"," pins\nthe digest of all 78 migration files (39 up, 39 down) as they stood at the tag, and\n",[396,505,506],{},"TestUnit_ReleasedMigrationSetImmutable"," fails if any of them changes.",[388,509,511],{"id":510},"precondition-a-snapshot-and-a-restore-you-have-run","Precondition: a snapshot and a restore you have run",[378,513,514],{},"The upgrade and the rollback both rest on one database snapshot, so the snapshot is not optional and neither is the\nproof that it restores.",[516,517,518,522,529],"ul",{},[519,520,521],"li",{},"Take the snapshot after draining and stopping, as the profile page's procedure states.",[519,523,524,525,528],{},"Rehearse the restore before the change window. ",[396,526,527],{},"05.v1-single-node.md"," requires both directions to be rehearsed from a\nreal snapshot of the previous release, with the commands, image IDs, and row counts recorded.",[519,530,531],{},"Keep the window between snapshot and rollback short, and keep token revocations, deletion requests, and legal-hold\nrecords outside the database so they can be re-applied.",[378,533,534,535,538,539,542,543,546,547,550,551,554,555,558,559,562,563,566,567,570,571,574,575,578,579,582,583,586,587,590,591,594,595,598,599,546,602,605,606,609,610,613,614,617,618,621,622,630,631,634,635,638,639,642],{},"The command surface exists, and it fails closed rather than pretending. ",[396,536,537],{},"make v1-backup"," (",[396,540,541],{},"TYPE=full|diff|incr","),\n",[396,544,545],{},"make v1-restore"," and ",[396,548,549],{},"make v1-pitr TARGET=\u003CISO8601>"," wrap pgBackRest (",[396,552,553],{},"Makefile",":232-242 →\n",[396,556,557],{},"infra\u002Fscripts\u002Fdev-tool.sh",":709-731), and before any of them reaches pgBackRest they require a real\n",[396,560,561],{},"infra\u002Fbackup\u002Fpgbackrest\u002Fpgbackrest.conf",": the shipped ",[396,564,565],{},".example"," is refused by path identity and a missing file is\nrefused too (",[396,568,569],{},"dev-tool.sh",":556-580). A restore is destructive and verified, not fire-and-forget: it stops Postgres,\nrestores with ",[396,572,573],{},"--delta",", checks ",[396,576,577],{},"PG_VERSION"," before the server starts, and prints ",[396,580,581],{},"ok"," only once\n",[396,584,585],{},"pg_is_in_recovery()"," is false — then leaves the cluster running and verified\n(",[396,588,589],{},"infra\u002Fscripts\u002Fplatform\u002Fpgbackrest-restore.sh",":276-281,314-319,330-344,401). ",[396,592,593],{},"make v1-pitr"," is supported: it restores\nto the timestamp with ",[396,596,597],{},"--type=time --target-action=promote"," and rewrites the ISO-8601 ",[396,600,601],{},"T",[396,603,604],{},"Z"," forms that\npgBackRest's parser rejects (",[396,607,608],{},"pgbackrest-restore.sh",":157-181). Rehearse a target on a scratch volume first —\n",[396,611,612],{},"make v1-pitr TARGET=… SCRATCH_VOLUME=\u003Cname>"," restores beside the live cluster, stops nothing, and leaves the restored\ncopy stopped for inspection (",[396,615,616],{},":241-274","). The restore runbook exists — ",[396,619,620],{},"engineering\u002Frunbooks\u002FRUNBOOK-restore.md",",\nlinked from ",[382,623,627],{"href":624,"rel":625},"https:\u002F\u002Fgithub.com\u002FRick1330\u002Fibex-harness\u002Fblob\u002Fmain\u002Fengineering\u002Frunbooks\u002FRUNBOOKS.md",[626],"nofollow",[396,628,629],{},"RUNBOOKS.md"," — and\nit requires you to establish what should be absent from a source outside the restored database, because a receipt\ninside that database is a row of the database being restored (",[396,632,633],{},"RUNBOOK-restore.md",":274-294). The committed drill\nevidence is still a ",[396,636,637],{},"pg_dump"," fallback report that records ",[396,640,641],{},"rpo_pass: false",", and no restore has been rehearsed end to\nend for this release. So the precondition is reachable only with an operator-built repository configuration, and the\nrehearsal is an operator step the upgrade depends on rather than one it performs.",[388,644,646],{"id":645},"irreversible-migration-families","Irreversible migration families",[378,648,649,650,657,658,661],{},"Migrations are forward-only in production: starting an older image against the migrated schema is not a supported\nrollback (",[382,651,654],{"href":652,"rel":653},"https:\u002F\u002Fgithub.com\u002FRick1330\u002Fibex-harness\u002Fblob\u002Fmain\u002Fengineering\u002FDEPLOYMENT.md",[626],[396,655,656],{},"DEPLOYMENT.md"," §7.2). Two\nfamilies cannot be undone by a ",[396,659,660],{},"down"," migration even in development:",[663,664,665,680],"ol",{},[519,666,667,675,676,679],{},[668,669,670,671,674],"strong",{},"Memory lifecycle (",[396,672,673],{},"000045_memory_lifecycle",")."," The down migration is safe only before lifecycle events have been\nconsumed or used as authority. Once published, lifecycle history is not reconstructible\n(",[396,677,678],{},"infra\u002Fmigrations\u002Fpostgres\u002F000045_memory_lifecycle.down.sql",":1-3). A rollback after a consumer has acted on outbox\nrows needs an explicit recovery plan, not the down file.",[519,681,682,687,688,691,692,694,695,698],{},[668,683,684,685,674],{},"ClickHouse analytics migrations (",[396,686,416],{}," ClickHouse has no transactional rollback for\nmost DDL, and the down files drop the tables they created. Applying a destructive ",[396,689,690],{},"up",", or running a ",[396,693,660],{}," against a\nlive database, destroys analytics rows with no recovery path — which is why the migration suite gates destructive\nDDL before it can be applied (",[396,696,697],{},"infra\u002Fmigrations\u002Fclickhouse\u002Fdestructive_ddl_unit_test.go",":11-13).",[378,700,701],{},"Both families make the snapshot the only recovery path. Neither is repaired by re-running a migration.",[388,703,705],{"id":704},"rollback-limits","Rollback limits",[378,707,708],{},"Rollback restores the snapshot and starts the previous image digests; it is not a schema downgrade. The limits that\nmatter:",[516,710,711,720,730,736,742],{},[519,712,713,716,717,719],{},[668,714,715],{},"Forward-only schema."," An older image against the migrated schema is unsupported. The rollback unit is the\nsnapshot, not the ",[396,718,660],{}," file.",[519,721,722,725,726,729],{},[668,723,724],{},"Stop the stack; do not rebuild."," A rebuild replaces the images you are trying to recover. Retag each recorded\nimage ID onto its Compose name and start with ",[396,727,728],{},"--no-build",".",[519,731,732,735],{},[668,733,734],{},"Transient Redis state is lost."," Reset the extraction queue, the result backend, and the caches; re-submit\nextraction work accepted after the snapshot.",[519,737,738,741],{},[668,739,740],{},"Database state moves back in time."," Re-apply token and PAT revocations, user suspensions, legal-hold creations and\nclearances, accepted deletion requests, and completed forgets, in that order, before reopening traffic. A hold must be\nreplayed before the deletion it blocks is judged. The profile page lists the full sequence.",[519,743,744,747,748,751,752,755,756,758],{},[668,745,746],{},"Capability-login verifiers revert."," They live in ",[396,749,750],{},"pg_authid",". The recreated one-shots rewrite them from the\ncurrent ",[396,753,754],{},".env",", so a credential rotated after the snapshot must still be in ",[396,757,754],{}," when the stack starts.",[378,760,761,762,765,766,768,769,771,772,775,776,779,780,729],{},"A rollback that has never been executed is not evidence. Rehearse both directions and record both. The migration span\nnow has an executed rehearsal — ",[396,763,764],{},"TestUpgradeRehearsal_V019ToHead"," runs ",[396,767,398],{}," → head → ",[396,770,398],{}," → head against seeded\ntenant rows in the ",[396,773,774],{},"db-migrate"," CI job, removing the tombstoned memory before it rewinds because ",[396,777,778],{},"000045","'s down guard\nrefuses to roll past one. That is a test database, not a deployment: it starts no application, restores no snapshot,\nexercises no concurrency, and rewinds no further than ",[396,781,398],{},[388,783,785],{"id":784},"support-window","Support window",[378,787,788,791],{},[668,789,790],{},"No version support window or support matrix is signed."," What is true today:",[516,793,794,806,809],{},[519,795,796,797,799,800,805],{},"There is exactly one supported deployment profile, ",[396,798,488],{},", selected by\n",[382,801,804],{"href":802,"rel":803},"https:\u002F\u002Fgithub.com\u002FRick1330\u002Fibex-harness\u002Fblob\u002Fmain\u002Fengineering\u002Fadr\u002F0097-v1-supported-profile.md",[626],"ADR-0097",". Kubernetes,\nHelm, and HA topologies are outside it.",[519,807,808],{},"There is no hosted offering and no hosted support claim.",[519,810,811,812,814,815,818,819,822],{},"No document states how long a released version receives fixes, or which version-to-version skips are supported. The\nonly upgrade path this page proposes is the ",[396,813,398],{}," → head ",[668,816,817],{},"reference path","; its migration counts are read from the\ntree. That one skip is exercised at migration level with data present (see ",[382,820,705],{"href":821},"#rollback-limits",") and no\nother is: no upgrade has been rehearsed end to end — no deployment, no application start, no concurrency, and no\nClickHouse.",[378,824,825,826,829,830,833,834,841],{},"A support window and support matrix are therefore an ",[668,827,828],{},"open owner decision",", not a policy this page can state. The\nremaining v1 gaps record the item as ",[396,831,832],{},"P1-46"," in\n",[382,835,838],{"href":836,"rel":837},"https:\u002F\u002Fgithub.com\u002FRick1330\u002Fibex-harness\u002Fblob\u002Fmain\u002Fengineering\u002Farchitecture-v2\u002F35-v1-remaining-gaps-staged-2026-11-13.md",[626],[396,839,840],{},"35-v1-remaining-gaps-staged-2026-11-13.md","\n§3, and the open owner questions are §9 of the same document. Until the owner signs a window, treat every release as\nsupported only at the version you are running, upgrade one rehearsal at a time, and do not promise a customer a\nmaintenance or upgrade window from this page.",[388,843,845],{"id":844},"related","Related",[516,847,848,853,858],{},[519,849,850,852],{},[382,851,335],{"href":336}," — start, upgrade, and rollback procedure.",[519,854,855,857],{},[382,856,331],{"href":332}," — the promotion checklist and open gates.",[519,859,860,862],{},[382,861,323],{"href":324}," — the configuration registry.",{"title":864,"searchDepth":865,"depth":865,"links":866},"",2,[867,868,869,870,871,872],{"id":390,"depth":865,"text":391},{"id":510,"depth":865,"text":511},{"id":645,"depth":865,"text":646},{"id":704,"depth":865,"text":705},{"id":784,"depth":865,"text":785},{"id":844,"depth":865,"text":845},"The v0.1.9 → head upgrade reference — migration counts, the irreversible migration families, the backup precondition, rollback limits, and what is and is not supported today.","md",false,{},true,"provisional",{"title":339,"description":873},"infra\u002Fmigrations; infra\u002Fmigrations\u002Fpostgres\u002Ftestdata\u002Freleased\u002Fv0.1.9.sha256; engineering\u002FDEPLOYMENT.md; engineering\u002Farchitecture-v2\u002F35-v1-remaining-gaps-staged-2026-11-13.md","vYFvI06eNSgxlNPpj-G8sOgZPrSUYIBH9bo_fqs6rY4",[883,885],{"title":335,"path":336,"stem":337,"description":884,"children":-1},"The supported single-node Docker Compose profile — one published HTTPS port, pinned dependencies, safe bootstrap, and recorded readiness.",{"title":343,"path":344,"stem":345,"description":886,"children":-1},"Glossary, roadmap, compatibility policy, and decision-record index.",1795256626364]