Tierline Contact

Roadmap

Roadmap and local setup

What exists today, what is running with communities, and what comes next.

Source code

Source and local setup

Software version 1.5.0.dev0.

Tierline’s code is licensed Apache-2.0. The repository is not public yet and will be linked here when it is. The browser search this site runs can be read now: js/audio-worker.js, served exactly as it runs.

The source includes docs/LOCAL_SETUP.md and a setup helper for running the reference engine on your own computer.

Roadmap

Where each part stands

From the tools you can use on this site to the community pilots. Progress shows where each part stands today.

01

Available now

Interactive experience

A browser workspace for your own recordings (import, describe, search, review, access settings, export and re-import), example recordings of real public-domain speech, review notes with JSON, CSV and TextGrid export, a clickable architecture explorer, and a governance simulator.

02

Implemented and tested

Local browser workspace

A loopback-only, token-protected API serving authorized archive intervals, cropped playback, saved human-authored context, and stored-segment search through the reference engine. Reference-engine search needs the model staged and its PCA and quantizer fitted on the machine that runs it, as the recorded run on the example recordings did.

03

Held-out evaluation reported; public-data protocol next

Measure the full engine

Tierline's held-out evaluation measured retrieval quality and robustness under six degradations; separate benchmarks measured latency, approximate-search recall and memory (see Evaluation). Next: run the public-data MSWC-v1 protocol from a clean commit, so a result on public data can be reproduced from its own record.

04

Implemented and tested

Stewardship

Fail-closed private readiness, explicit action-by-action consent, encrypted backups, withdrawal tombstones that survive stale restores, retention checks and a record of physical-artifact cleanup. In the operating pilots, community-side administrators direct each collection under a written deployment agreement.

05

Four operating, two in co-design

Community pilots

Each collaboration works under a signed agreement (see Partners & archives); a comparative study measured whether search saved time (see Impact). A new collaboration starts with an agreement.

06

Next

Sustainable preservation

Keep recovery drills, format migration and administrator succession documented, each with a named responsible operator, as the pilots' preservation and recovery procedures are. A partner-led grant proposal includes a budgeted Tierline role (see Funding & stewardship).

Running it yourself

Two ways to run Tierline

Preview the public site and demo

From a copy of the Tierline source (see About):

python3 scripts/serve_site.py

Open the loopback URL it prints. The example search and the Workspace need no model weights and no network access. For deployment, publish only the contents of site/dist/.

Use your own authorized archive

With the web extras installed and a workspace initialized:

PYTHONPATH=src python -m tierline.web \
  --workspace /path/to/workspace \
  --user language-worker \
  --role language_worker

Enter the printed token under Archive → Local workspace. For reference-engine search, also pass --feature-set and --quantizer once artifacts are staged and indexed.

The local adapter serves a single operator and is bound to loopback. It is not an Internet-facing service: there is no reverse proxy, no public binding, and no multi-user login. It should not be exposed to a network or used for a sensitive pilot without a security review.