Tidy up remaining references to Trillian Tessera (#669)

Author: AlCutter

README.md

@@ -1,19 +1,19 @@
-# Trillian Tessera
+# Tessera
 
 [![Go Report Card](https://goreportcard.com/badge/github.com/transparency-dev/tessera)](https://goreportcard.com/report/github.com/transparency-dev/tessera)
 [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/transparency-dev/tessera/badge)](https://scorecard.dev/viewer/?uri=github.com/transparency-dev/tessera)
 [![Benchmarks](https://img.shields.io/badge/Benchmarks-blue.svg)](https://transparency-dev.github.io/tessera/dev/bench/)
 [![Slack Status](https://img.shields.io/badge/Slack-Chat-blue.svg)](https://transparency-dev.slack.com/)
 
-Trillian Tessera is a Go library for building [tile-based transparency logs (tlogs)](https://c2sp.org/tlog-tiles).
+Tessera is a Go library for building [tile-based transparency logs (tlogs)](https://c2sp.org/tlog-tiles).
 It is the logical successor to the approach [Trillian v1][] takes in building and operating logs.
 
 The implementation and its APIs bake-in
 [current best-practices based on the lessons learned](https://transparency.dev/articles/tile-based-logs/)
 over the past decade of building and operating transparency logs in production environments and at scale.
 
 Tessera was introduced at the Transparency.Dev summit in October 2024.
-Watch [Introducing Trillian Tessera](https://www.youtube.com/watch?v=9j_8FbQ9qSc) for all the details,
+Watch [Introducing Tessera](https://www.youtube.com/watch?v=9j_8FbQ9qSc) for all the details,
 but here's a summary of the high level goals:
 
 *   [tlog-tiles API][] and storage
@@ -53,13 +53,13 @@ Beta in Q2 2025, and production ready around mid 2025.
 |  1  | Drivers for GCP, AWS, MySQL, and POSIX                    |   ✅   |
 |  2  | [tlog-tiles API][] support                                |   ✅   |
 |  3  | Example code and terraform scripts for easy onboarding    |   ✅   |
-|  4  | Stable API                                                |   ⚠️   |
+|  4  | Stable API                                                |   ✅   |
 |  5  | Data migration between releases                           |   ✅   |
 |  6  | Data migration between drivers                            |   ✅   |
 |  7  | Witness support                                           |   ✅   |
 |  8  | Monitoring and metrics                                    |   ✅   |
 |  9  | Production ready                                          |   ✅   |
-|  10 | Mirrored logs (#576)                                      |   ❌   |
+|  10 | Mirrored logs (#576)                                      |   ⚠️   |
 |  11 | Preordered logs (#575)                                    |   ❌   |
 |  12 | Trillian v1 to Tessera migration (#577)                   |   ❌   |
 |  N  | Fancy features (to be expanded upon later)                |   ❌   |

deployment/README.md

@@ -1,6 +1,6 @@
 # Deployment
 
-This directory contains configuration-as-code to deploy Trillian Tessera to supported infrastructure:
+This directory contains configuration-as-code to deploy Tessera to supported infrastructure:
  - `modules`: terraform modules to configure infrastructure for running a Tessera log.
    + `gcp`: a Tessera GCP specific terraform module.
    + `aws`: a Tessera AWS specific terraform module.

deployment/live/aws/codelab/README.md

@@ -1,6 +1,6 @@
 # AWS codelab deployment
 
-This codelab helps you bring a test Trillian Tessera infrastructure on AWS, and
+This codelab helps you bring a test Tessera infrastructure on AWS, and
 to use it by running a test personality server on an EC2 VM. The infrastructure 
 will be comprised of an [Aurora](https://aws.amazon.com/rds/aurora/) MySQL
 database and a private [S3](https://aws.amazon.com/s3/) bucket. 
@@ -20,7 +20,7 @@ with a running EC2 Amazon Linux VM, and the following software installed:
    run the test personality on the VM
  - [terraform](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli)
    and [terragrunt](https://terragrunt.gruntwork.io/docs/getting-started/install/)
-   in order to deploy the Trillian Tessera infrastructure from the VM.
+   in order to deploy the Tessera infrastructure from the VM.
  - `git` to clone the repo
  - a terminal multiplexer of your choice for convenience
 
@@ -83,7 +83,7 @@ the defaults settings, including for the default VPC. Don't forget to run
     cd tessera/
     ```
 
-### Deploy a Trillian Tessera storage infrastructure
+### Deploy a Tessera storage infrastructure
 In this section, we'll bring up a [S3](https://aws.amazon.com/s3/) bucket, an
 [Aurora](https://aws.amazon.com/rds/aurora/) MySQL, and we'll connect them to the
 VM.
@@ -98,7 +98,7 @@ VM.
     terragrunt apply --working-dir=deployment/live/aws/codelab/
     ```
     This brings up the Terraform infrastructure (S3 bucket + DynamoDB table for
-    terraform state locking only) and the Trillian Tessera infrastructure: an
+    terraform state locking only) and the Tessera infrastructure: an
     RDS Aurora instance, a private S3 bucket, and connects this bucket to the
     default VPC that your VM should be connected to.
 
@@ -112,8 +112,8 @@ VM.
 1. Connect the VM and Aurora database following [these instructions](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/tutorial-ec2-rds-option1.html#option1-task3-connect-ec2-instance-to-rds-database),
    it takes a few clicks in the UI.
 
-### Start a Trillian Tessera personality
-A personality is a server that interacts with Trillian Tessera's storage
+### Start a Tessera personality
+A personality is a server that interacts with Tessera's storage
 infrastructure. In this codelab, it accepts POST requests on a `add/` HTTP
 endpoint.
 
@@ -149,7 +149,7 @@ endpoint.
 
  1. 🎉 **Congratulations** 🎉
 
-    You have successfully brought up Trillian Tessera's
+    You have successfully brought up Tessera's
     AWS infrastructure, and started a personality server that can add entries to it.
 
     Use the environment variables from above to interact with the personality in a different terminal.

docs/design/philosophy.md

@@ -2,7 +2,7 @@
 
 ## Objective
 
-This document explains the rationale behind some of the philosophy and design choices underpinning Trillian Tessera.
+This document explains the rationale behind some of the philosophy and design choices underpinning Tessera.
 
 
 ## Simplicity
@@ -17,7 +17,7 @@ we *really need now*?", or otherwise restricting our ability to make large inter
 
 ## Multi-implementation storage
 
-Each storage implementation for Trillian Tessera is independently implemented, and takes the most "native"
+Each storage implementation for Tessera is independently implemented, and takes the most "native"
 approach for the infrastructure it targets.
 
 Trillian v1 defined `LogStorage` and embedded `TreeStorage` interfaces which all storage implementations had
@@ -28,7 +28,7 @@ desired by higher levels in the stack. In turn, this made it hard to:
 1. Support non-single-domain/non-transactional storage implementations, and 
 2. Refactor storage internals to improve performance.
 
-With Trillian Tessera, we are learning from these mistakes, and acknowledging that:
+With Tessera, we are learning from these mistakes, and acknowledging that:
 
 1. The different storage implementations we are building now, and those which will come in the future, have their
    own unique properties which stem from the infrastructure they're built upon - e.g. _some_ infrastructure offers
@@ -51,7 +51,7 @@ caller requesting the addition of the entry was given nothing more than a timest
 would be integrated at some point (note that 24h is the CT _policy_, but there's no specific parameter or deadline
 in Trillian itself - it's _"as soon as possible"_).
 
-With Trillian Tessera, we're tightening the storage contract up so that calls to add entries to the log will
+With Tessera, we're tightening the storage contract up so that calls to add entries to the log will
 return with a durably assigned sequence number, or an error.
 
 It's not a requirement that the Merkle tree has already been extended to cryptographically commit to the new leaf
@@ -82,7 +82,7 @@ This API represents a reasonable set of tradeoffs:
           amortise the long-pole cost over a larger number of sequenced entries.
 2. Limiting the intended window between <sequence> and <integrate> operations to a low
    single-digit-seconds target enables a synchronous add API to be constructed at the layer above (i.e within
-   the "personality" that is built using Trillian Tessera).
+   the "personality" that is built using Tessera).
 
    This approach enables:
      1. synchronous "personalities" to benefit from improved write-throughput (compared with a naive 

storage/mysql/PERFORMANCE.md

@@ -1,7 +1,7 @@
 # MySQL Performance
 
 > [!TIP]
-> The performance test result shows that Trillian Tessera can run on the free tier VM instance on GCP.
+> The performance test result shows that Tessera can run on the free tier VM instance on GCP.
 
 ### GCP Free Tier VM Instance
 
@@ -67,7 +67,7 @@ MiB Swap:      0.0 total,      0.0 free,      0.0 used.     37.3 avail Mem
    git version 2.39.2
    ```
 
-1. Clone the Trillian Tessera repository
+1. Clone the Tessera repository
 
    ```sh
    instance:~$ git clone https://github.com/transparency-dev/tessera.git
@@ -146,7 +146,7 @@ The bottleneck comes from CPU usage of the `cmd/conformance/mysql` binary on the
    git version 2.39.2
    ```
 
-1. Clone the Trillian Tessera repository
+1. Clone the Tessera repository
 
    ```sh
    instance:~$ git clone https://github.com/transparency-dev/tessera.git
@@ -234,7 +234,7 @@ MiB Swap:      0.0 total,      0.0 free,      0.0 used.    403.2 avail Mem
    git version 2.39.2
    ```
 
-1. Clone the Trillian Tessera repository
+1. Clone the Tessera repository
 
    ```sh
    instance:~$ git clone https://github.com/transparency-dev/tessera.git

storage/mysql/README.md

@@ -1,6 +1,6 @@
-# MySQL Storage for Trillian Tessera
+# MySQL Storage for Tessera
 
-This directory contains the implementation of a storage backend for Trillian Tessera using MySQL. This allows Tessera to leverage MySQL as its underlying database for storing checkpoint, entry hashes and data in tiles format.
+This directory contains the implementation of a storage backend for Tessera using MySQL. This allows Tessera to leverage MySQL as its underlying database for storing checkpoint, entry hashes and data in tiles format.
 
 ## Design
 
@@ -14,7 +14,7 @@ See [MySQL storage design documentation](/storage/mysql/DESIGN.md).
 
 ### Constructing the Storage Object
 
-Here is an example code snippet to initialise the MySQL storage in Trillian Tessera.
+Here is an example code snippet to initialise the MySQL storage in Tessera.
 
 ```go
 import (

storage/mysql/mysql_test.go

@@ -374,7 +374,7 @@ func TestTileRoundTrip(t *testing.T) {
 		},
 		{
 			name:  "string entry",
-			entry: []byte("I love Trillian Tessera"),
+			entry: []byte("I love Tessera"),
 		},
 		{
 			name:  "empty byte",
@@ -425,7 +425,7 @@ func TestEntryBundleRoundTrip(t *testing.T) {
 		},
 		{
 			name:  "string entry",
-			entry: []byte("I love Trillian Tessera"),
+			entry: []byte("I love Tessera"),
 		},
 		{
 			name:  "empty byte",

storage/mysql/schema.sql

@@ -12,7 +12,7 @@
 -- See the License for the specific language governing permissions and
 -- limitations under the License.
 
--- MySQL version of the Trillian Tessera database schema.
+-- MySQL version of the Tessera database schema.
 
 -- "Tessera" table stores a single row that is the version of this schema
 -- and the data formats within it. This is read at startup to prevent Tessera

storage/posix/PERFORMANCE.md

@@ -102,7 +102,7 @@ MiB Mem :    970.0 total,     62.2 free,    839.5 used,    227.0 buff/cache
    git version 2.39.2
    ```
 
-1. Clone the Trillian Tessera repository
+1. Clone the Tessera repository
 
    ```sh
    instance:~$ git clone https://github.com/transparency-dev/tessera.git