An offline-first diagnostic atlas for programming languages, infrastructure, and GPU runtimes.
**Why a buyer cares:** LexiconError packages transferable product IP — source, docs, in-repo brand assets, and a diligence room under `docs/acquisition/` — under a clear proprietary posture so diligence can proceed without mistaking the repo for open source. --- ## 2. Product snapshot | Item | Detail | |------|--------| | Product | LexiconError | | Repo | `theworker02/lexicon-error` | | Language | Python | | Open source? | **No** — proprietary | | Rightsholder | theworker02 | | Diligence pack | `docs/acquisition/` | ### Capability highlights (from current materials) - Official diagnostic identifiers are kept separate from human-readable titles. - Severity, frequency, and taxonomy tier are independent fields rather than one vague priority score. - Curated entries and generated registry imports expose different verification states. - Source provenance remains attached to the diagnostic instead of being discarded during ingestion. - Triggering code and hardened code are stored side by side. - Related diagnostics can connect comparable concepts across languages without pretending their runtime semantics are identical. - The desktop application, portable SQLite index, Hugging Face dataset, and routing models are separate outputs built from the same normalized knowledge layer. - **Curated experience likelihood** is an ordinal classification: `Common`, `Uncommon`, `Rare`, or `Situational`. - **Catalog distribution** is computed from the local SQLite database and shows how many indexed records in the selected ecosystem belong to each frequency or failure-domain bucket. - Node.js 20 or newer - Rust stable - Python 3.11 or newer --- ## 3. Problem / opportunity Teams evaluating LexiconError typically need either (a) a commercial right to run or embed it, or (b) outright ownership of the Product IP for strategic build-out. Public GitHub visibility without a proprietary license creates false assumptions about free production use. This brief and the linked data room make the commercial path explicit. --- ## 4. What ships today Honest maturity: treat repository contents, README claims, tests, and release tags as the source of truth. Do not assume production customers, ARR, filed patents, or SLAs unless separately evidenced in diligence. Typical transferable surfaces: - Source tree and build/test scripts present in-repo - Documentation and design notes - Acquisition / diligence markdown under `docs/acquisition/` - Branding assets committed to the repository (if any) --- ## 5. Demo / evaluation path (buyer) Minimal path (no secrets required unless README says otherwise): ``` bash git clone https://github.com/theworker02/lexicon-error.git cd lexicon-error # Follow README for language-specific install / run steps ``` Extended evaluation: `docs/acquisition/BUYER_EVALUATION.md`. Written NDA / evaluation grants may be required for private materials. --- ## 6. What a transaction typically includes Subject to definitive schedules: | Included (typical) | Excluded (typical) | |--------------------|--------------------| | Repo materials + asserted original IP | Seller personal accounts / unrelated repos | | Docs + diligence room at closing | Third-party dependency source under separate licenses | | In-repo brand marks as assigned | Secrets without rotation plan | | Know-how captured in docs | Fabricated revenue, user, or adoption metrics | --- ## 7. Suggested deal structures | Structure | When it fits | |-----------|--------------| | Non-exclusive commercial license | Deploy/run under seat or environment terms | | Exclusive field-of-use license | Buyer wants exclusivity; seller may retain entity | | Asset / IP assignment | Buyer wants ownership of Materials outright | | OEM / redistribution | Separate agreement — not implied here | Commercial terms (price, earnouts, escrow) are negotiated under NDA with counsel. --- ## 8. Buyer diligence checklist - [ ] Confirm Rightsholder identity and authority to sell/license - [ ] Inventory Materials (`docs/acquisition/ASSET_INVENTORY.md`) - [ ] Review IP posture (`IP_PROVENANCE.md`) and dependencies (`DEPENDENCY_INVENTORY.md`) - [ ] Run evaluation script (`BUYER_EVALUATION.md`) - [ ] Review risks (`RISK_REGISTER.md`) - [ ] Agree transfer scope (`TRANSFER_MANIFEST.md`) and handoff (`HANDOFF_CHECKLIST.md`) - [ ] Supersede root `LICENSE` at closing via definitive agreement --- ## 9. Related documents | Document | Purpose | |----------|---------| | `LICENSE` | Proprietary — no default grant | | `docs/acquisition/README.md` | Data-room index | | `docs/acquisition/EXECUTIVE_SUMMARY.md` | One-page thesis | | `README.md` | Product overview | | `SECURITY.md` | Vulnerability reporting | | `COMMERCIAL.md` | Licensing contact path | | `.github/FUNDING.yml` | Sponsors / thanks.dev | --- ## 10. Disclaimer This package is informational and **does not** create a binding offer, grant of rights, or investment advice. Engage counsel for any transaction. --- *Document version: 2.0.0 / 2026-09-22 · Classification: acquisition briefing*