Deliver Rackspace schema snapshots through gated production steps
This outline orders the implementation of the Rackspace schema architecture. Each step has its own document with a goal, scope, tests, a completion gate, and stop conditions.
Do not start Step 1 until every applicable Step 0 gate in the status record is complete. Record the merge commit for this documentation revision as the implementation base before Step 1 starts.
This revision was reviewed from clean main commit 85dcb64. Do not use that review commit as
the Step 1 base. Replace it with the documentation merge commit after this revision merges.
| Step | Deliverable | Production effect | Status |
|---|---|---|---|
| 0 | Local discovery and generation proof | None, local probe only | TODO |
| 1 | Foundation and confined tracer | Read-only probe, no Git reference | TODO |
| 2 | @concourse/rsdb runtime | Empty registry, no Rackspace data | TODO |
| 3 | Candidate pipeline | Ephemeral candidates only | TODO |
| 4 | Inventory and selection | Read-only inventory | TODO |
| 5 | Review artifacts and safe publication | First reviewed pull request | TODO |
| 6 | Sequential multi-database refresh | Multi-database pull request | TODO |
| 7 | Deployed verification | Read-only production verification | TODO |
| 8 | Production rollout | Full registered database coverage | TODO |
The steps run in numeric order. Merge each step before the next step starts. Update the status column after each accepted gate.
@concourse/db owns the Turso application schema and migrations.requireSystemAdmin() enforces fresh sessions and rejects impersonation.apps/concourse/proxy.ts does not yet exclude Workflow routes.drizzle-kit@1.0.0-rc.4.@concourse/rsdb package or local Rackspace probe.CI / verify job and has no MySQL service.concourse with root apps/concourse.iad1, Fluid Compute, and Static IPs.main branch has no protection or ruleset.Use one branch and pull request for each numbered step. Merge each step before the next step starts.
Use the normal staging and production process. Get operator approval before a push, deployment, or pull request. Do not use an ad hoc production deployment.
Record these values in each pull request:
After each implementation step, run:
pnpm format:fix
pnpm verifyStop all local servers and test services after each step.
Update the architecture and topic documents before an implementation changes a fixed decision. Update the status record when an external fact, owner, limit, account, or key changes.
Keep the step documents focused on implementation order and completion gates. Keep raw operational evidence out of Git under the evidence rules.
Deliver Rackspace schema snapshots through gated production steps
This outline orders the implementation of the Rackspace schema architecture. Each step has its own document with a goal, scope, tests, a completion gate, and stop conditions.
Do not start Step 1 until every applicable Step 0 gate in the status record is complete. Record the merge commit for this documentation revision as the implementation base before Step 1 starts.
This revision was reviewed from clean main commit 85dcb64. Do not use that review commit as
the Step 1 base. Replace it with the documentation merge commit after this revision merges.
| Step | Deliverable | Production effect | Status |
|---|---|---|---|
| 0 | Local discovery and generation proof | None, local probe only | TODO |
| 1 | Foundation and confined tracer | Read-only probe, no Git reference | TODO |
| 2 | @concourse/rsdb runtime | Empty registry, no Rackspace data | TODO |
| 3 | Candidate pipeline | Ephemeral candidates only | TODO |
| 4 | Inventory and selection | Read-only inventory | TODO |
| 5 | Review artifacts and safe publication | First reviewed pull request | TODO |
| 6 | Sequential multi-database refresh | Multi-database pull request | TODO |
| 7 | Deployed verification | Read-only production verification | TODO |
| 8 | Production rollout | Full registered database coverage | TODO |
The steps run in numeric order. Merge each step before the next step starts. Update the status column after each accepted gate.
@concourse/db owns the Turso application schema and migrations.requireSystemAdmin() enforces fresh sessions and rejects impersonation.apps/concourse/proxy.ts does not yet exclude Workflow routes.drizzle-kit@1.0.0-rc.4.@concourse/rsdb package or local Rackspace probe.CI / verify job and has no MySQL service.concourse with root apps/concourse.iad1, Fluid Compute, and Static IPs.main branch has no protection or ruleset.Use one branch and pull request for each numbered step. Merge each step before the next step starts.
Use the normal staging and production process. Get operator approval before a push, deployment, or pull request. Do not use an ad hoc production deployment.
Record these values in each pull request:
After each implementation step, run:
pnpm format:fix
pnpm verifyStop all local servers and test services after each step.
Update the architecture and topic documents before an implementation changes a fixed decision. Update the status record when an external fact, owner, limit, account, or key changes.
Keep the step documents focused on implementation order and completion gates. Keep raw operational evidence out of Git under the evidence rules.