rubydb 0.1.4 → 0.1.6

data/CHANGELOG.md

@@ -1,28 +1,58 @@
-# Changelog
-
-All notable changes to RubyDB are documented here. Versions follow
-[Semantic Versioning](https://semver.org/).
-
+# Changelog
+
+All notable changes to RubyDB are documented here. Versions follow
+[Semantic Versioning](https://semver.org/).
+
 ## Unreleased
-
-- Added full developer, troubleshooting, debugging, production operations,
-  Rails compatibility, and SQL compatibility guides with repository maps,
-  incident evidence procedures, safe recovery guidance, and deployment
-  checklists.
-- Added RubyDB connection URLs (`rubydb://` and TLS-enabled `rubydbs://`) for
-  regular Ruby clients and Rails `database.yml`, including percent-encoded
-  credentials and documented TLS/query options.
-- Added a beginner-friendly local-to-production guide covering local RubyDB,
-  PostgreSQL migration, RubyDB server deployment, environment URLs, Render-style
-  hosting, data transfer, smoke tests, and production checklists.
-- Added a documentation index and lessons-learned guide covering durability,
-  ownership, replication fencing, cancellation, deadlocks, Rails adapters,
-  operations, evidence, and security review boundaries.
-- Added a full CLI guide and cheat sheet covering lifecycle, server operation,
-  shell, migrations, backup/restore, snapshots, branches, inspection, doctor,
-  vacuum, maintenance, and release workflows.
+
+- Added full developer, troubleshooting, debugging, production operations,
+  Rails compatibility, and SQL compatibility guides with repository maps,
+  incident evidence procedures, safe recovery guidance, and deployment
+  checklists.
+- Added RubyDB connection URLs (`rubydb://` and TLS-enabled `rubydbs://`) for
+  regular Ruby clients and Rails `database.yml`, including percent-encoded
+  credentials and documented TLS/query options.
+- Added a beginner-friendly local-to-production guide covering local RubyDB,
+  PostgreSQL migration, RubyDB server deployment, environment URLs, Render-style
+  hosting, data transfer, smoke tests, and production checklists.
+- Added a documentation index and lessons-learned guide covering durability,
+  ownership, replication fencing, cancellation, deadlocks, Rails adapters,
+  operations, evidence, and security review boundaries.
+- Added a full CLI guide and cheat sheet covering lifecycle, server operation,
+  shell, migrations, backup/restore, snapshots, branches, inspection, doctor,
+  vacuum, maintenance, and release workflows.
 - Clarified the tested common SQLite-style profile and production limits.
 
+## 0.1.6 - 2026-09-18
+
+- Bundled the Go accelerator binaries and Ruby bridge for release installs;
+  developers do not need Go installed to use the packaged core gem.
+- Added lock-protected direct storage snapshots, worker lifecycle recovery,
+  multiplexed requests, cancellation, bounded execution, and adaptive Ruby/Go
+  selection with a safe Ruby fallback.
+- Added accelerator CLI diagnostics, environment-mode handling, checksums,
+  extracted-gem verification, and release packaging for the runtime binaries.
+- Added the Rails ecommerce pressure example and expanded production guidance
+  for embedded development, managed RubyDB services, PostgreSQL-backed large
+  applications, and ActiveRecord adapter deployment.
+- Prepared `rubydb-activerecord` 0.1.3 for the RubyDB 0.1.x release line.
+
+## 0.1.5 - 2026-09-10
+
+- Applied network query and prepared-statement parameters through the server
+  protocol before SQL parsing, using shared safe literal binding rules.
+- Added the initial Python DB-API adapter and live protocol validation under
+  `adapters/python`.
+- Added a ten-lesson guided journey with copy-and-paste development,
+  PostgreSQL, RubyDB server, Rails, microservice, recovery, security, and
+  release examples.
+- Expanded the lesson journey with a direct RubyDB-to-production deployment
+  path covering persistent storage, TLS, secrets, migrations, smoke tests,
+  backup/restore, canary traffic, and rollback evidence.
+- Added the initial `rubydb-python` DB-API 2.0 adapter under
+  `adapters/python`, including TLS URLs, prepared statements, transactions,
+  pooling, timeouts, cancellation, tests, and PyPI build instructions.
+
 ## 0.1.4 - 2026-09-09
 
 - Returned logical generated primary-key values to ActiveRecord separately
@@ -53,8 +83,8 @@ All notable changes to RubyDB are documented here. Versions follow
   range.
 
 ## 0.1.0 - 2026-09-07
-
-- Initial public release candidate.
-- Includes the embedded engine, ActiveRecord adapter, backup/recovery, WAL,
-  TLS, authentication, and validated production-hardening checkpoints.
-- See `docs/production_validation.md` for tested scope and operational limits.
+
+- Initial public release candidate.
+- Includes the embedded engine, ActiveRecord adapter, backup/recovery, WAL,
+  TLS, authentication, and validated production-hardening checkpoints.
+- See `docs/production_validation.md` for tested scope and operational limits.

data/CODE_OF_CONDUCT.md

@@ -1,13 +1,13 @@
-# Contributor Code of Conduct
-
-RubyDB contributors are expected to make participation respectful, practical,
-and safe. Harassment, discrimination, threats, personal attacks, doxxing,
-deliberate disruption, and unwanted sexual attention are not acceptable.
-
-Project maintainers may moderate comments, discussions, issues, and pull
-requests when conduct violates this standard. They should explain the reason,
-apply the rule consistently, and protect people who report concerns.
-
-Report a conduct concern privately to the repository maintainers through a
-GitHub private security/contact channel. Do not include production secrets or
-customer data. Reports are handled confidentially as far as practical.
+# Contributor Code of Conduct
+
+RubyDB contributors are expected to make participation respectful, practical,
+and safe. Harassment, discrimination, threats, personal attacks, doxxing,
+deliberate disruption, and unwanted sexual attention are not acceptable.
+
+Project maintainers may moderate comments, discussions, issues, and pull
+requests when conduct violates this standard. They should explain the reason,
+apply the rule consistently, and protect people who report concerns.
+
+Report a conduct concern privately to the repository maintainers through a
+GitHub private security/contact channel. Do not include production secrets or
+customer data. Reports are handled confidentially as far as practical.

data/CONTRIBUTING.md

@@ -1,29 +1,29 @@
-# Contributing to RubyDB
-
-RubyDB is a correctness-first database project. Small, reviewable changes with
-tests and documentation are preferred over broad changes with unverified
-claims.
-
-## Development
-
-```sh
-bundle install
-bundle exec rspec
-bundle exec rubocop
-```
-
-Use a temporary database for tests. Do not commit database files, credentials,
-generated private keys, coverage output, or release artifacts. Follow the
-architecture and testing guides in `docs/`.
-
-## Pull requests
-
-Explain the invariant being changed, the failure mode it prevents, and the
-rollback or compatibility impact. Add regression coverage for parser,
-execution, storage, transaction, protocol, adapter, or operational changes.
-Run the relevant workload, crash, backup/restore, and security checks. Update
-the compatibility contract when behavior changes.
-
-Never describe a simulated fault test as proof of physical power-loss,
-multi-host, or independent security-review results. See the
-[lessons learned](docs/lessons-learned.md) guide.
+# Contributing to RubyDB
+
+RubyDB is a correctness-first database project. Small, reviewable changes with
+tests and documentation are preferred over broad changes with unverified
+claims.
+
+## Development
+
+```sh
+bundle install
+bundle exec rspec
+bundle exec rubocop
+```
+
+Use a temporary database for tests. Do not commit database files, credentials,
+generated private keys, coverage output, or release artifacts. Follow the
+architecture and testing guides in `docs/`.
+
+## Pull requests
+
+Explain the invariant being changed, the failure mode it prevents, and the
+rollback or compatibility impact. Add regression coverage for parser,
+execution, storage, transaction, protocol, adapter, or operational changes.
+Run the relevant workload, crash, backup/restore, and security checks. Update
+the compatibility contract when behavior changes.
+
+Never describe a simulated fault test as proof of physical power-loss,
+multi-host, or independent security-review results. See the
+[lessons learned](docs/lessons-learned.md) guide.

data/GOVERNANCE.md

@@ -1,16 +1,16 @@
-# RubyDB governance
-
-RubyDB is maintained through reviewed changes in the public repository. The
-maintainers are responsible for release decisions, security coordination,
-compatibility claims, and accepting changes that affect data safety.
-
-Changes to storage format, WAL, recovery, transaction isolation, replication,
-authentication, protocol framing, or release automation require focused tests,
-documentation, and an explicit operational-impact review.
-
-Security vulnerabilities should be reported privately as described in
-`SECURITY.md`. Public issues are appropriate for reproducible bugs that do not
-expose an unpatched vulnerability.
-
-The project follows semantic versioning while compatibility is still evolving.
-Release tags must pass the protected CI and RubyGems release checks.
+# RubyDB governance
+
+RubyDB is maintained through reviewed changes in the public repository. The
+maintainers are responsible for release decisions, security coordination,
+compatibility claims, and accepting changes that affect data safety.
+
+Changes to storage format, WAL, recovery, transaction isolation, replication,
+authentication, protocol framing, or release automation require focused tests,
+documentation, and an explicit operational-impact review.
+
+Security vulnerabilities should be reported privately as described in
+`SECURITY.md`. Public issues are appropriate for reproducible bugs that do not
+expose an unpatched vulnerability.
+
+The project follows semantic versioning while compatibility is still evolving.
+Release tags must pass the protected CI and RubyGems release checks.

data/Gemfile

@@ -1,17 +1,18 @@
-# frozen_string_literal: true
-
-source 'https://rubygems.org'
-
-gemspec
-
-gem 'rake', '~> 13.2'
-gem 'rspec', '~> 3.13'
-gem 'rubocop', '~> 1.65', require: false
-gem 'rubocop-performance', '~> 1.21', require: false
-gem 'standard', '~> 1.39', require: false
-gem 'simplecov', '~> 0.22', require: false
-
-# Optional development dependencies
-gem 'pry', '~> 0.14', group: :development
-gem 'pry-byebug', '~> 3.10', group: :development
-gem 'memory_profiler', '~> 1.0', group: :development
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+gemspec
+
+gem "rake", "~> 13.2"
+gem "rspec", "~> 3.13"
+gem "rubocop", "~> 1.64", require: false
+gem "rubocop-performance", "~> 1.21", require: false
+gem "standard", "~> 1.39.0", require: false
+gem "simplecov", "~> 0.22", require: false
+gem "benchmark", "~> 0.4", require: false
+
+# Optional development dependencies
+gem "pry", "~> 0.14", group: :development
+gem "pry-byebug", "~> 3.10", group: :development
+gem "memory_profiler", "~> 1.0", group: :development

data/Gemfile.lock

@@ -1,71 +1,125 @@
-PATH
-  remote: .
-  specs:
-    rubydb (0.1.0)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    ast (2.4.2)
-    base64 (0.2.0)
-    json (2.7.2)
-    language_server-protocol (3.17.0.3)
-    parallel (1.24.0)
-    parser (3.3.1.0)
-      ast (~> 2.4.1)
-      racc
-    racc (1.8.0)
-    rainbow (3.1.1)
-    rake (13.2.1)
-    regexp_parser (2.9.2)
-    rexml (3.2.6)
-    rspec (3.13.0)
-      rspec-core (~> 3.13.0)
-      rspec-expectations (~> 3.13.0)
-      rspec-mocks (~> 3.13.0)
-    rspec-core (3.13.0)
-      rspec-support (~> 3.13.0)
-    rspec-expectations (3.13.0)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.13.0)
-    rspec-mocks (3.13.0)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.13.0)
-    rspec-support (3.13.1)
-    rubocop (1.63.4)
-      json (~> 2.3)
-      language_server-protocol (>= 3.17.0)
-      parallel (~> 1.10)
-      parser (>= 3.3.0.2)
-      rainbow (>= 2.2.2, < 4.0)
-      regexp_parser (>= 1.8, < 3.0)
-      rexml (>= 3.2.5, < 4.0)
-      rubocop-ast (>= 1.31.1, < 2.0)
-      ruby-progressbar (~> 1.7)
-      unicode-display_width (>= 2.4.0, < 3.0)
-    rubocop-ast (1.31.3)
-      parser (>= 3.3.0.2)
-    rubocop-performance (1.21.0)
-      rubocop (>= 1.48.1, < 2.0)
-      rubocop-ast (>= 1.31.1, < 2.0)
-    ruby-progressbar (1.13.0)
-    standard (1.35.1)
-      language_server-protocol (~> 3.17.0.2)
-      rubocop (~> 1.63.0)
-      rubocop-performance (~> 1.21.0)
-    unicode-display_width (2.5.0)
-
-PLATFORMS
-  arm64-darwin-23
-  ruby
-
-DEPENDENCIES
-  rake (~> 13.2)
-  rspec (~> 3.13)
-  rubocop (~> 1.60)
-  rubocop-performance (~> 1.20)
-  rubydb!
-  standard (~> 1.35)
-
-BUNDLED WITH
-   2.5.9
+PATH
+  remote: .
+  specs:
+    rubydb (0.1.6)
+      base64 (>= 0.2)
+      bigdecimal (>= 3.1)
+      concurrent-ruby (>= 1.2)
+      date (~> 3.3)
+      digest (~> 3.1)
+      json (~> 2.7)
+      time (~> 0.4)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    ast (2.4.3)
+    base64 (0.3.0)
+    benchmark (0.5.0)
+    bigdecimal (4.1.2)
+    byebug (13.0.0)
+      reline (>= 0.6.0)
+    coderay (1.1.3)
+    concurrent-ruby (1.3.8)
+    date (3.5.1)
+    diff-lcs (1.6.2)
+    digest (3.2.1)
+    docile (1.4.1)
+    io-console (0.9.2)
+    json (2.21.2)
+    language_server-protocol (3.17.0.6)
+    lint_roller (1.1.0)
+    memory_profiler (1.1.0)
+    method_source (1.1.0)
+    parallel (1.28.0)
+    parser (3.3.12.0)
+      ast (~> 2.4.1)
+      racc
+    prism (1.9.0)
+    pry (0.16.0)
+      coderay (~> 1.1)
+      method_source (~> 1.0)
+      reline (>= 0.6.0)
+    pry-byebug (3.12.0)
+      byebug (~> 13.0)
+      pry (>= 0.13, < 0.17)
+    racc (1.8.1)
+    rainbow (3.1.1)
+    rake (13.2.1)
+    regexp_parser (2.12.0)
+    reline (0.7.0)
+      io-console (~> 0.5)
+    rexml (3.4.4)
+    rspec (3.13.0)
+      rspec-core (~> 3.13.0)
+      rspec-expectations (~> 3.13.0)
+      rspec-mocks (~> 3.13.0)
+    rspec-core (3.13.0)
+      rspec-support (~> 3.13.0)
+    rspec-expectations (3.13.5)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.13.0)
+    rspec-mocks (3.13.8)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.13.0)
+    rspec-support (3.13.1)
+    rubocop (1.64.1)
+      json (~> 2.3)
+      language_server-protocol (>= 3.17.0)
+      parallel (~> 1.10)
+      parser (>= 3.3.0.2)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 1.8, < 3.0)
+      rexml (>= 3.2.5, < 4.0)
+      rubocop-ast (>= 1.31.1, < 2.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 2.4.0, < 3.0)
+    rubocop-ast (1.50.0)
+      parser (>= 3.3.7.2)
+      prism (~> 1.7)
+    rubocop-performance (1.23.1)
+      rubocop (>= 1.48.1, < 2.0)
+      rubocop-ast (>= 1.31.1, < 2.0)
+    ruby-progressbar (1.13.0)
+    simplecov (0.22.0)
+      docile (~> 1.1)
+      simplecov-html (~> 0.11)
+      simplecov_json_formatter (~> 0.1)
+    simplecov-html (0.13.2)
+    simplecov_json_formatter (0.1.4)
+    standard (1.39.2)
+      language_server-protocol (~> 3.17.0.2)
+      lint_roller (~> 1.0)
+      rubocop (~> 1.64.0)
+      standard-custom (~> 1.0.0)
+      standard-performance (~> 1.4)
+    standard-custom (1.0.2)
+      lint_roller (~> 1.0)
+      rubocop (~> 1.50)
+    standard-performance (1.6.0)
+      lint_roller (~> 1.1)
+      rubocop-performance (~> 1.23.0)
+    time (0.4.2)
+      date
+    unicode-display_width (2.6.0)
+
+PLATFORMS
+  arm64-darwin-23
+  ruby
+  x64-mingw-ucrt
+
+DEPENDENCIES
+  benchmark (~> 0.4)
+  memory_profiler (~> 1.0)
+  pry (~> 0.14)
+  pry-byebug (~> 3.10)
+  rake (~> 13.2)
+  rspec (~> 3.13)
+  rubocop (~> 1.64)
+  rubocop-performance (~> 1.21)
+  rubydb!
+  simplecov (~> 0.22)
+  standard (~> 1.39.0)
+
+BUNDLED WITH
+   2.5.9

data/README.md

@@ -3,10 +3,61 @@
 RubyDB is a Ruby-native relational database with an embedded engine, a
 client/server mode, a Ruby client, and an ActiveRecord adapter.
 
+**Author:** Aldane Hutchinson
+
 > **Status: alpha.** RubyDB is suitable for experimentation, development,
-> controlled embedded workloads, and applications that stay within the
-> documented and tested feature set. It provides a tested common SQLite-style
-> profile, but is not a drop-in replacement for PostgreSQL, MySQL, or SQLite.
+> controlled embedded workloads, and production microservices that stay within
+> the documented and tested feature set. RubyDB can be used in both development
+> and production, but each production workload must pass its own query,
+> concurrency, backup, restore, security, and operational validation. It
+> provides a tested common SQLite-style profile, but is not a drop-in
+> replacement for PostgreSQL, MySQL, or SQLite.
+
+## Recommended database roles
+
+Use RubyDB when you want a Ruby-native database for local development, tests,
+internal tools, or an independently owned microservice with a bounded workload.
+Use embedded mode when one Ruby process owns the database file. Use RubyDB
+server/client mode when multiple application processes connect to one service.
+
+Use PostgreSQL as the default system of record for massive applications,
+high-concurrency public products, large shared Rails applications, advanced
+PostgreSQL SQL/extensions, and workloads requiring a mature managed database
+ecosystem. A common production architecture is PostgreSQL for the main app and
+RubyDB for smaller, independently operated microservices.
+
+## Ecosystem and community adapters
+
+RubyDB's ecosystem is built around a clear boundary: application code connects
+to a RubyDB server through the documented client/server protocol. The embedded
+`.rdb` file format is an internal storage implementation, not a public API for
+third-party drivers. This lets RubyDB evolve its storage safely while language
+and framework communities build clients that share the same server behavior.
+
+Official integration surfaces include:
+
+- Ruby's direct API and the `rubydb` client/server client
+- `rubydb-activerecord` for Rails applications
+- `rubydb-python` for Python DB-API 2.0 applications
+- `rubydb-node` for Node.js and TypeScript applications
+- Sequel and other Ruby integrations documented under `adapters/`
+
+Community developers can create adapters for another language, framework,
+ORM, query builder, migration tool, observability system, or job framework.
+Every adapter should begin with the [server protocol](docs/server/protocol.md)
+and the executable protocol tests, then provide an idiomatic API for its
+community. A production adapter must preserve parameter binding, transaction
+ownership, deadlines and wire cancellation, TLS verification, bounded frames,
+error details, and clean connection shutdown. A wrapper that only sends a
+string of SQL is not a production adapter.
+
+Use a distinct package name such as `rubydb-go`, `rubydb-django`, or
+`@your-scope/rubydb` and make its ownership clear. Do not present a community
+package as an official RubyDB release. Add the adapter to the ecosystem list
+only after it has live integration tests against a real RubyDB server and its
+supported RubyDB versions are documented. The complete build, test, security,
+and publishing workflow is in
+[Lesson 11: Build a community adapter](lessons/11-community-adapter.md).
 
 ## What works today
 
@@ -51,18 +102,54 @@ unsupported or unverified dialect features must not be assumed to work.
 
 ## Quick start
 
-Install the prerelease gem:
-
-```sh
-gem install rubydb --pre
-```
-
-For local development from this repository:
+Install the core release gem:
+
+```sh
+gem install rubydb -v 0.1.6
+```
+
+For Rails, install the core and ActiveRecord adapter together:
+
+```ruby
+# Gemfile
+gem "rubydb", "~> 0.1.6"
+gem "rubydb-activerecord", "~> 0.1.3"
+```
+
+RubyDB ships the Go accelerator binaries inside the core gem. Developers and
+deployments do not install Go. The default `accelerator.mode: auto` starts Go
+for eligible workloads and keeps it only when the result is equivalent and
+the measured latency wins; use `RUBYDB_ACCELERATOR=required` for a readiness
+check that must exercise Go, or `RUBYDB_ACCELERATOR=off` for Ruby-only
+diagnostics.
+
+For local development from this repository:
 
 ```sh
 bundle install
-bundle exec rspec
-```
+bundle exec rspec
+```
+
+### Bundled Go acceleration
+
+RubyDB keeps the Ruby engine as its correctness authority and automatically
+starts a bundled, CGO-free Go worker for proven read-only pipelines, checksums,
+and compression. The release gem contains platform binaries; end users do not
+install or configure Go. From a source checkout, build and verify the worker
+with:
+
+```sh
+ruby scripts/build_accelerator
+ruby -Ilib exe/rubydb accelerator --ping --json
+```
+
+Use `accelerator.mode: off` or `RUBYDB_ACCELERATOR=off` for Ruby-only
+diagnostics. `mode: auto` calibrates eligible scans, aggregates, and inner
+hash joins against Ruby and keeps Go only when it wins without changing the
+result. Use `required` only for differential validation and readiness checks.
+See [the accelerator architecture](docs/architecture/go-accelerator.md)
+for the protocol boundary, fallback behavior, differential testing, and
+release rules.
 
 ## Ruby usage
 
@@ -92,6 +179,73 @@ client.disconnect
 Use the `rubydb://` or TLS-enabled `rubydbs://` format documented in the Rails
 configuration guide. RubyDB URLs are not PostgreSQL URLs.
 
+## Copy-and-paste examples
+
+### RubyDB for local development
+
+This creates a durable local database in one owning Ruby process:
+
+```ruby
+require "rubydb"
+
+engine = RubyDB::Storage::Engine.new("tmp/development.rdb")
+begin
+  engine.execute("CREATE TABLE IF NOT EXISTS notes (id INTEGER PRIMARY KEY, body TEXT NOT NULL)")
+  engine.execute("INSERT INTO notes (body) VALUES ('First note')")
+  puts engine.execute("SELECT id, body FROM notes ORDER BY id").inspect
+ensure
+  engine.close
+end
+```
+
+Do not open the same embedded path from separate web and worker processes.
+
+### RubyDB for a production microservice
+
+Run one RubyDB server on persistent storage and inject a TLS URL into the
+service:
+
+```sh
+gem install rubydb -v 0.1.6
+rubydb --config /etc/rubydb/production.yml --env production start
+```
+
+```ruby
+require "rubydb"
+
+client = RubyDB::Client::Client.new(url: ENV.fetch("RUBYDB_URL"))
+begin
+  puts client.query("SELECT 1").to_hash
+ensure
+  client.disconnect
+end
+```
+
+Use a URL such as `rubydbs://user:URL_ENCODED_PASSWORD@db.internal:7432/app`
+with TLS verification enabled. Store the complete URL in a secret manager and
+keep the database service on a private network.
+
+### PostgreSQL for a massive Rails application
+
+Use the `pg` gem and a managed PostgreSQL connection string for the main
+application:
+
+```ruby
+# Gemfile
+gem "pg"
+```
+
+```yaml
+# config/database.yml
+production:
+  url: <%= ENV.fetch("DATABASE_URL") %>
+  pool: <%= ENV.fetch("RAILS_MAX_THREADS", "5") %>
+```
+
+Set `DATABASE_URL` through the hosting provider’s secret settings, run
+migrations once from a release job, and validate the application against the
+same PostgreSQL major version used in production.
+
 ## Rails example
 
 The small Rails 7.2 application in
@@ -133,6 +287,7 @@ by the presence of an adapter.
 ## Documentation
 
 - [Documentation index](docs/README.md)
+- [Production journey](lessons/01-foundations.md)
 - [Developer guide](docs/developer-guide.md)
 - [Troubleshooting guide](docs/troubleshooting.md)
 - [Debugging playbook](docs/debugging.md)
@@ -147,6 +302,7 @@ by the presence of an adapter.
 - [Rails installation](docs/rails/installation.md)
 - [Rails production guidance](docs/rails/production.md)
 - [Rails compatibility guide](docs/rails/compatibility-guide.md)
+- [Python adapter](adapters/python/README.md)
 - [Production readiness](docs/production-readiness.md)
 - [Operations and workload testing](docs/operations/workload-testing.md)
 - [Production runbook](docs/operations/production-runbook.md)