LazyingArtLocal Knowledge Terminal

Project-owned sample · reference snapshot 2026-08-31

A fit report
you can inspect.

This concrete example applies the USD 250 sprint format to Local Knowledge Terminal's own documented reference collection. It shows the three deliverables before you share any customer material.

Evidence boundary: this is not a customer result, testimonial, benchmark, sale, or claim of a paid engagement.

Start the free fit check Inspect the source report

Decision summary

GO, with a bounded scope.

The existing structured records fit LKT's local exact and lexical retrieval plus cited-card workflow on the current Raspberry Pi 5 8 GB target. The useful first proof is a browser card backed by one retrieved record and its stored provenance.

Do not expand this decision to image-only PDFs, custom OCR, unreviewed rights, hardware supply, or production operations. Those require a separate scope.

19,119structured records
5reviewed collection exports
5.8 MBapproximate runtime indexes
Localsource files and retrieval

Deliverable 01

Collection, privacy, and citation map.

The public proof uses five reviewed exports. Full books, images, model weights, generated indexes, and editorial queues remain outside the public repository.

Documented reference snapshot
Collection exportRecordsRuntime treatment
Word Origins6,994Exact headword and lexical FTS5
Book of Answers318Deterministic query-seeded draw
Book of Questions291Multilingual FTS5 and deterministic fallback
English Root Dictionary6,327Exact headword and morphology FTS5
English Affix Dictionary5,189Exact headword and morphology FTS5
Total19,119Five local indexes, approximately 5.8 MB
owned source files reviewed export local SQLite index retrieved record + source ID bounded composition browser card

What remains local

  • Private source files and generated indexes.
  • Model weights and runtime state.
  • Editorial workspaces and review queues.

What a citation retains

  • Corpus and record identifiers.
  • Source title, excerpt, and page when present.
  • The indexed-file hash used for retrieval.

Deliverable 02

Representative browser proof.

These reviewable captures use the current card contract. A paid sprint would instead use only a small, customer-approved sample after rights, format, privacy, readers, language goal, and existing hardware pass the free fit check.

Local Knowledge Terminal multilingual Word Card interface
Multilingual Word Card with bounded language fields.
Local Knowledge Terminal cited Word Origin graph interface
Word Origin graph separating retrieved evidence from model context.

Deliverable 03

A written go/no-go boundary.

Go when

  • You control the bounded source and have the right to use it.
  • Text is already extractable or structured.
  • A representative sample can be reviewed.
  • The goal is a small cited browser proof on an existing machine.
  • One language goal and reader group can be stated clearly.

No-go or separate scope

  • Source rights are unclear.
  • The material is mainly scanned images requiring custom OCR.
  • The request is an unbounded migration or production platform.
  • Shipped hardware, uptime commitments, or a production SLA are required.
  • The sample needs an unapproved handling environment.

The fixed paid scope

One collection. Three bounded artifacts. USD 250.

After a positive free fit check, the sprint delivers a written data, citation, and privacy map; a small browser proof from a usable representative sample; and a written go/no-go decision. Hardware, shipping, custom OCR, and production deployment are excluded.

Start the free fit check The fit-check page stores and sends nothing automatically.

Reproduce the public checks

python -m unittest discover -s tests -v
python -m compileall -q lkt tests

The tests cover indexing, retrieval, provenance, preparation, model boundaries, storage, outputs, and the browser service. They demonstrate the public implementation; they do not substitute for checking a customer's actual sample.

Read the source report and corpus ledger →