Step 0: Discovery and generation proof

Complete live discovery and prove generation with the local probe

Goal

Add the permanent local probe. Complete live discovery through the approved VPN path. Prove generation against a version-matched fixture, QA, and production without deployed artifacts.

Scope

Create the initial private, ESM, Node-only @concourse/rsdb package with reusable discovery and generation logic. Do not add the runtime registry, database factory, or connection pools in this step. The runtime package document defines the ./probe entry boundary.

Add:

A root pnpm rackspace:probe command.
A pnpm rackspace:probe --record-platform evidence mode.
Interactive, masked, paste-enabled credential prompts.
QA and production discovery modes.
Protected temporary output and persistent evidence reports.
A safe local report-cleanup mode.
A disposable, version-matched MySQL fixture.
Focused tests for prompts, paths, permissions, redaction, manifests, and cleanup.
The completed status record.

The probe command must satisfy the complete command contract. Do not commit generated live snapshots, raw evidence, account names, database names, hostnames, or credentials.

The fixture includes tables, views, triggers, procedures, functions, events, mixed-case names, denied grants, and two unrelated schemas. Use the pinned pull() export from drizzle-kit/cli. Do not use pull --init, a child process, or custom introspection.

Procedure

Implement the probe, package boundary, local fixture, and tests.
Connect the laptop to the approved VPN.
Run the probe against QA with the operator, snapshot, and runtime accounts.
Use the operator account only for authoritative inventory, server facts, and grant inspection.
Use the snapshot account only for metadata and SHOW CREATE proof.
Use the runtime account only for connection and grant inspection.
Prompt for one QA representative database.
Run two programmatic pulls without a database change.
Review the temporary output and approve its removal.
Store the persistent QA report outside the repository.
Resolve every unexplained QA result before production starts.
Repeat the probe against production with separate prompts.
Prompt for one production representative database from the same schema family. Require the operator to confirm that both databases represent the same schema family. Do not commit either name.
Run two programmatic pulls without a database change.
Review the temporary output and approve its removal.
Store the persistent production report outside the repository.
Run the same generation proof against the version-matched local fixture. Compare all output bytes except the exact unstable fields that the local fixture proves.
Record only safe conclusions and evidence IDs in the status record.
Configure the GitHub main ruleset defined by the publication document.
Disable GitHub's automatic head-branch deletion setting.
Create a private Blob store for the Production environment.
Make sure that no Blob lifecycle or scheduled cleanup removes review artifacts.
Create the Connect installation for conveyal/concourse only.
Record Workflow availability for the concourse project.
Record the read-only external inspection results with --record-platform.
Put only its safe evidence ID in the status record.
Record human approval to start Step 1.

The probe never creates accounts or changes grants. It never issues an application-data write or a DDL statement. The operator creates the final accounts through a separate manual procedure.

Completion gate

Step 0 is complete only when:

No required status record value remains unknown or pending.
The QA and production reports exist outside the repository with recorded evidence IDs and hashes.
The QA run completed before the production run.
The prompted databases represent the same approved schema family.
The fixture, QA, and production pulls define the exact normalization list.
The generated TypeScript compiles.
The fixture, QA, and production sources contain no new migration ledger.
The probe stored no credential value or complete generated DDL in a persistent report.
All temporary plaintext workspaces are absent after operator confirmation.
The GitHub ruleset is active.
GitHub automatic head-branch deletion is disabled.
Workflow, private Blob, and Connect are ready.
No Blob lifecycle or schedule removes review artifacts.
A human approved Step 1.

Stop conditions

Stop and revise the architecture if:

The server version invalidates the grant model.
Public certificate validation fails.
The two accounts cannot remain separate.
The snapshot account cannot prove complete object visibility.
QA and production have an unexplained compatibility difference.
The programmatic API does not produce every required output class.
The pull writes to the source database.
The generated TypeScript does not compile.
The command stores a secret or complete generated DDL in a persistent report.
The command cannot restore terminal echo or protect its output paths.

Step 0: Discovery and generation proof

Complete live discovery and prove generation with the local probe

Goal

Add the permanent local probe. Complete live discovery through the approved VPN path. Prove generation against a version-matched fixture, QA, and production without deployed artifacts.

Scope

Add:

A root pnpm rackspace:probe command.
A pnpm rackspace:probe --record-platform evidence mode.
Interactive, masked, paste-enabled credential prompts.
QA and production discovery modes.
Protected temporary output and persistent evidence reports.
A safe local report-cleanup mode.
A disposable, version-matched MySQL fixture.
Focused tests for prompts, paths, permissions, redaction, manifests, and cleanup.
The completed status record.

The probe command must satisfy the complete command contract. Do not commit generated live snapshots, raw evidence, account names, database names, hostnames, or credentials.

Procedure

Implement the probe, package boundary, local fixture, and tests.
Connect the laptop to the approved VPN.
Run the probe against QA with the operator, snapshot, and runtime accounts.
Use the operator account only for authoritative inventory, server facts, and grant inspection.
Use the snapshot account only for metadata and SHOW CREATE proof.
Use the runtime account only for connection and grant inspection.
Prompt for one QA representative database.
Run two programmatic pulls without a database change.
Review the temporary output and approve its removal.
Store the persistent QA report outside the repository.
Resolve every unexplained QA result before production starts.
Repeat the probe against production with separate prompts.
Prompt for one production representative database from the same schema family. Require the operator to confirm that both databases represent the same schema family. Do not commit either name.
Run two programmatic pulls without a database change.
Review the temporary output and approve its removal.
Store the persistent production report outside the repository.
Run the same generation proof against the version-matched local fixture. Compare all output bytes except the exact unstable fields that the local fixture proves.
Record only safe conclusions and evidence IDs in the status record.
Configure the GitHub main ruleset defined by the publication document.
Disable GitHub's automatic head-branch deletion setting.
Create a private Blob store for the Production environment.
Make sure that no Blob lifecycle or scheduled cleanup removes review artifacts.
Create the Connect installation for conveyal/concourse only.
Record Workflow availability for the concourse project.
Record the read-only external inspection results with --record-platform.
Put only its safe evidence ID in the status record.
Record human approval to start Step 1.

The probe never creates accounts or changes grants. It never issues an application-data write or a DDL statement. The operator creates the final accounts through a separate manual procedure.

Completion gate

Step 0 is complete only when:

No required status record value remains unknown or pending.
The QA and production reports exist outside the repository with recorded evidence IDs and hashes.
The QA run completed before the production run.
The prompted databases represent the same approved schema family.
The fixture, QA, and production pulls define the exact normalization list.
The generated TypeScript compiles.
The fixture, QA, and production sources contain no new migration ledger.
The probe stored no credential value or complete generated DDL in a persistent report.
All temporary plaintext workspaces are absent after operator confirmation.
The GitHub ruleset is active.
GitHub automatic head-branch deletion is disabled.
Workflow, private Blob, and Connect are ready.
No Blob lifecycle or schedule removes review artifacts.
A human approved Step 1.

Stop conditions

Stop and revise the architecture if:

The server version invalidates the grant model.
Public certificate validation fails.
The two accounts cannot remain separate.
The snapshot account cannot prove complete object visibility.
QA and production have an unexplained compatibility difference.
The programmatic API does not produce every required output class.
The pull writes to the source database.
The generated TypeScript does not compile.
The command stores a secret or complete generated DDL in a persistent report.
The command cannot restore terminal echo or protect its output paths.

Step 0: Discovery and generation proof

Complete live discovery and prove generation with the local probe

Goal

Add the permanent local probe. Complete live discovery through the approved VPN path. Prove generation against a version-matched fixture, QA, and production without deployed artifacts.

Scope

Add:

A root pnpm rackspace:probe command.
A pnpm rackspace:probe --record-platform evidence mode.
Interactive, masked, paste-enabled credential prompts.
QA and production discovery modes.
Protected temporary output and persistent evidence reports.
A safe local report-cleanup mode.
A disposable, version-matched MySQL fixture.
Focused tests for prompts, paths, permissions, redaction, manifests, and cleanup.
The completed status record.

The probe command must satisfy the complete command contract. Do not commit generated live snapshots, raw evidence, account names, database names, hostnames, or credentials.

Procedure

Implement the probe, package boundary, local fixture, and tests.
Connect the laptop to the approved VPN.
Run the probe against QA with the operator, snapshot, and runtime accounts.
Use the operator account only for authoritative inventory, server facts, and grant inspection.
Use the snapshot account only for metadata and SHOW CREATE proof.
Use the runtime account only for connection and grant inspection.
Prompt for one QA representative database.
Run two programmatic pulls without a database change.
Review the temporary output and approve its removal.
Store the persistent QA report outside the repository.
Resolve every unexplained QA result before production starts.
Repeat the probe against production with separate prompts.
Prompt for one production representative database from the same schema family. Require the operator to confirm that both databases represent the same schema family. Do not commit either name.
Run two programmatic pulls without a database change.
Review the temporary output and approve its removal.
Store the persistent production report outside the repository.
Run the same generation proof against the version-matched local fixture. Compare all output bytes except the exact unstable fields that the local fixture proves.
Record only safe conclusions and evidence IDs in the status record.
Configure the GitHub main ruleset defined by the publication document.
Disable GitHub's automatic head-branch deletion setting.
Create a private Blob store for the Production environment.
Make sure that no Blob lifecycle or scheduled cleanup removes review artifacts.
Create the Connect installation for conveyal/concourse only.
Record Workflow availability for the concourse project.
Record the read-only external inspection results with --record-platform.
Put only its safe evidence ID in the status record.
Record human approval to start Step 1.

The probe never creates accounts or changes grants. It never issues an application-data write or a DDL statement. The operator creates the final accounts through a separate manual procedure.

Completion gate

Step 0 is complete only when:

No required status record value remains unknown or pending.
The QA and production reports exist outside the repository with recorded evidence IDs and hashes.
The QA run completed before the production run.
The prompted databases represent the same approved schema family.
The fixture, QA, and production pulls define the exact normalization list.
The generated TypeScript compiles.
The fixture, QA, and production sources contain no new migration ledger.
The probe stored no credential value or complete generated DDL in a persistent report.
All temporary plaintext workspaces are absent after operator confirmation.
The GitHub ruleset is active.
GitHub automatic head-branch deletion is disabled.
Workflow, private Blob, and Connect are ready.
No Blob lifecycle or schedule removes review artifacts.
A human approved Step 1.

Stop conditions

Stop and revise the architecture if:

The server version invalidates the grant model.
Public certificate validation fails.
The two accounts cannot remain separate.
The snapshot account cannot prove complete object visibility.
QA and production have an unexplained compatibility difference.
The programmatic API does not produce every required output class.
The pull writes to the source database.
The generated TypeScript does not compile.
The command stores a secret or complete generated DDL in a persistent report.
The command cannot restore terminal echo or protect its output paths.

Step 0: Discovery and generation proof

Complete live discovery and prove generation with the local probe

Goal

Add the permanent local probe. Complete live discovery through the approved VPN path. Prove generation against a version-matched fixture, QA, and production without deployed artifacts.

Scope

Add:

A root pnpm rackspace:probe command.
A pnpm rackspace:probe --record-platform evidence mode.
Interactive, masked, paste-enabled credential prompts.
QA and production discovery modes.
Protected temporary output and persistent evidence reports.
A safe local report-cleanup mode.
A disposable, version-matched MySQL fixture.
Focused tests for prompts, paths, permissions, redaction, manifests, and cleanup.
The completed status record.

The probe command must satisfy the complete command contract. Do not commit generated live snapshots, raw evidence, account names, database names, hostnames, or credentials.

Procedure

Implement the probe, package boundary, local fixture, and tests.
Connect the laptop to the approved VPN.
Run the probe against QA with the operator, snapshot, and runtime accounts.
Use the operator account only for authoritative inventory, server facts, and grant inspection.
Use the snapshot account only for metadata and SHOW CREATE proof.
Use the runtime account only for connection and grant inspection.
Prompt for one QA representative database.
Run two programmatic pulls without a database change.
Review the temporary output and approve its removal.
Store the persistent QA report outside the repository.
Resolve every unexplained QA result before production starts.
Repeat the probe against production with separate prompts.
Prompt for one production representative database from the same schema family. Require the operator to confirm that both databases represent the same schema family. Do not commit either name.
Run two programmatic pulls without a database change.
Review the temporary output and approve its removal.
Store the persistent production report outside the repository.
Run the same generation proof against the version-matched local fixture. Compare all output bytes except the exact unstable fields that the local fixture proves.
Record only safe conclusions and evidence IDs in the status record.
Configure the GitHub main ruleset defined by the publication document.
Disable GitHub's automatic head-branch deletion setting.
Create a private Blob store for the Production environment.
Make sure that no Blob lifecycle or scheduled cleanup removes review artifacts.
Create the Connect installation for conveyal/concourse only.
Record Workflow availability for the concourse project.
Record the read-only external inspection results with --record-platform.
Put only its safe evidence ID in the status record.
Record human approval to start Step 1.

The probe never creates accounts or changes grants. It never issues an application-data write or a DDL statement. The operator creates the final accounts through a separate manual procedure.

Completion gate

Step 0 is complete only when:

No required status record value remains unknown or pending.
The QA and production reports exist outside the repository with recorded evidence IDs and hashes.
The QA run completed before the production run.
The prompted databases represent the same approved schema family.
The fixture, QA, and production pulls define the exact normalization list.
The generated TypeScript compiles.
The fixture, QA, and production sources contain no new migration ledger.
The probe stored no credential value or complete generated DDL in a persistent report.
All temporary plaintext workspaces are absent after operator confirmation.
The GitHub ruleset is active.
GitHub automatic head-branch deletion is disabled.
Workflow, private Blob, and Connect are ready.
No Blob lifecycle or schedule removes review artifacts.
A human approved Step 1.

Stop conditions

Stop and revise the architecture if:

The server version invalidates the grant model.
Public certificate validation fails.
The two accounts cannot remain separate.
The snapshot account cannot prove complete object visibility.
QA and production have an unexplained compatibility difference.
The programmatic API does not produce every required output class.
The pull writes to the source database.
The generated TypeScript does not compile.
The command stores a secret or complete generated DDL in a persistent report.
The command cannot restore terminal echo or protect its output paths.

Search documentation

Search documentation

Search documentation

Goal

Scope

Procedure

Completion gate

Stop conditions

Search documentation

Goal

Scope

Procedure

Completion gate

Stop conditions

Search documentation

Search documentation

Goal

Scope

Procedure

Completion gate

Stop conditions

Search documentation

Goal

Scope

Procedure

Completion gate

Stop conditions