Free fit check · one collection · existing hardware

Turn one private collection into cited local cards.

Tell me what you have, who will use it, and the machine it must stay on. If it fits, the fixed USD 250 sprint maps the data, evaluates up to 12 agreed source units against 20 questions, builds up to two cited browser cards, and gives you a written go/no-go.

No account or source upload. Nothing is sent while you fill in or review the fit check. After review, send the encrypted request here, open it in your email app, or copy it. Inspect the code and tests →

One collection, one language goal, and one existing machine. Hardware, shipping, custom OCR, bulk conversion, production deployment, and ongoing support are excluded.

Private Document Collection-Fit Sprint: USD 250, free fit check first, software service, hardware not included
A software service on your existing machine. Read the project-owned sample before deciding whether to enquire.
LOCALPrivate corpora and model inference
CITEDSources come from retrieved records
EN · 日 · 中Multilingual cards with reading aids
PI 5A tested reference build, not included hardware

A terminal, not another chat tab

Built around durable cards.

The browser interface is the first display. E-paper, microphone, and audio remain separate adapters, so the knowledge core does not depend on one piece of hardware.

01

Ground the answer

Retrieve from a private book or reviewed dictionary first. Citations are attached from those records, not invented by the language model.

02

Compose one card

Question, Answer, Word Card, Word Origin, Root, and Affix remain distinct modes with one clear teaching point per screen.

03

Keep it local

SQLite stores accepted knowledge. A local Qwen model prepares bounded artifacts; private books, indexes, and model files stay outside the public repository.

Local Knowledge Terminal word origin graph interface

Words with a memory

See where a word came from.

Word Origin uses a directed ancestry graph rather than a paragraph pretending to be one. Nodes can distinguish book evidence from model context, while the primary card stays readable.

  • English meaning remains primary.
  • Japanese and Chinese can add pronunciation guides.
  • Root and affix views reuse accepted atomic evidence.

Read-only MCP bridge

Let an agent ask—and show its sources.

A compatible MCP client can search the accepted part of an LKT collection and trace a returned claim to its source evidence. The bridge is deliberately small: it reads the local knowledge ledger, never invokes a model, and cannot change the collection.

01

Ask the collection

Search accepted multilingual records with bounded results instead of handing an agent unrestricted access to your files.

02

Open the evidence

Trace a returned claim to an accepted source excerpt, safe locator, and validated content hash.

03

Keep the boundary

The public bridge has two read-only tools and no file, shell, ingestion, generation, review, or write access. Network mode stays on loopback by default.

Inspect the MCP contract Open-source implementation and tests. Remote access needs a separate authenticated boundary.

A graph you can inspect

From books and dictionaries to one connected atlas.

Lexicon Atlas is a public, read-only example of what LKT can build from a collection. Its first downloadable snapshot connects 15,925 entities through 15,197 typed edges and keeps 13,431 evidence records alongside roots, affixes, historical forms, meanings, pronunciations, and translations.

  • Search a word, then follow one-, two-, or three-hop relationships.
  • Filter by language, node type, evidence basis, and review state.
  • Explore locally after downloading the fixed SQLite snapshot.

This public snapshot demonstrates the graph and its provenance; it is not a finished etymological dictionary.

Actual Lexicon Atlas desktop view showing a local three-dimensional lexical knowledge graph

See the deliverable before you enquire

Read a real, bounded fit report.

The public sample applies the sprint format to LKT's own documented reference collection: 16,800 current-code structured records across five local indexes, with raw source material and derived indexes kept outside Git. It is project-owned evidence, not a customer result or testimonial.

01

Data and privacy map

See what becomes a reviewed local record, what stays outside the repository, and where stored provenance enters the card.

02

Representative proof

Inspect up to two cited browser cards backed by the current card contract, with clear boundaries around customer-approved sample material.

03

Go/no-go boundary

Read the conditions for a useful sprint and the separate-scope cases: image-only PDFs, custom OCR, shipped hardware, or production operations.

Related work you can inspect

The collection work is already public.

The fit sprint is new, but it is grounded in years of organizing technical, multilingual, and book-length material into durable reading tools. These projects show the relevant craft without pretending that they are paid LKT client engagements.

Physics archive

Susskind lectures

A maintained collection of transcripts, subtitles, notes, TeX, course PDFs, and a public web reader.

Inspect the archive →

Reproducible editions

PocketPolyglot

A Studio, CLI, and TeX pipeline for aligned multilingual books with pinyin, furigana, and reusable source data.

Inspect the pipeline →

Public output shelf

LinguaLeaf

A browsable shelf of multilingual reading editions, including Chinese classics and history in several formats.

Browse the shelf →

Related public work is evidence of collection handling and publishing experience, not a claim that those projects were produced through this paid sprint.

Who the pilot may fit

A small, private place for a serious collection.

Terminology and language study

Test a rights-cleared glossary, dictionary, or reading collection. When the source supports it, cards can preserve citations while tracing roots, affixes, and word history.

Libraries and exhibits

Explore a bounded collection through an ambient display without exposing the source books to a cloud service.

Working terms

Know the boundary before work starts.

The free fit check comes first. If the collection fits, the written scope uses these same terms so timing, corrections, privacy, and cancellation are clear before payment.

10 DAYS

One sprint at a time

Delivery is ten business days after the scope is accepted, payment is confirmed, and the complete agreed sample and machine-access path are ready. The clock pauses while a required input is missing.

7 DAYS

One correction window

Send one consolidated list of up to ten factual corrections within seven calendar days after delivery. New sources, questions, languages, formats, interfaces, or deployment work need a new scope.

CLEAR EXIT

Pay only for delivered work

Cancel before source transfer or processing begins for a full refund. After work starts, only completed, delivered items are retained: USD 75 for the map, USD 125 for the evaluation and cards, and USD 50 for the report and correction pass.

Customer material is not published or reused without separate written permission. Working source copies are deleted within fourteen calendar days after acceptance, cancellation, or refund unless the written scope requires earlier deletion or limited records must be retained by applicable rules. Written clarification is available during the seven-day correction window; hosting, maintenance, hardware support, and ongoing operation are excluded.

Founding collection-fit sprint · USD 250

Bring one collection and one real use case.

A deliberately small first engagement: one private collection, one language goal, and one existing machine. After a free fit check, the paid sprint produces a written data, citation, and privacy map; evaluates an agreed sample capped at 12 source units and 20 test questions; builds up to two cited browser cards when the source is usable; and gives a clear go/no-go recommendation for a larger deployment. One factual correction pass is included.

  • Customer-provided material only; you must have the right to use it.
  • The written scope defines one source unit—for example, a passage, record, or representative page—before payment.
  • Hardware, shipping, custom OCR, bulk conversion, production deployment, and ongoing support are not included.
  • A supplied device is a separate, quote-only product.
  • Payment is requested by Stripe only after the fit and scope are accepted.