Metadata-Version: 2.4
Name: optivibe-reference
Version: 0.2.0
Summary: OptiVibe reference layer: lookup tables + RAG + intent->ZOS-API grounding
License: Apache-2.0
Project-URL: Homepage, https://github.com/chuang44-tiff/optivibe-mcp
Project-URL: Issues, https://github.com/chuang44-tiff/optivibe-mcp/issues
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3.11
Requires-Python: >=3.11
Description-Content-Type: text/markdown
Provides-Extra: manual
Requires-Dist: pymupdf; extra == "manual"
Provides-Extra: probe
Requires-Dist: pythonnet; extra == "probe"
Provides-Extra: dev
Requires-Dist: pytest; extra == "dev"

# optivibe-reference

The grounding layer for optivibe-mcp: deterministic lookup tables, a SQLite
**FTS5** full-text store over the OpticStudio manual, and an intent→operand
grounding index. It lets the agent consult operand meanings, glass properties,
and manual passages so its choices are grounded rather than guessed.

It is composed **in-process** by `optivibe-mcp` (not a standalone server) and
exposes five tools: `lookup_operand`, `search_reference`, `lookup_glass`,
`find_glasses`, and `find_glass_pair`.

## Data is built locally

No vendor data is committed. The glass catalog (recomputed from your install's
`.agf` files), the manual FTS5 corpus (indexed from your manual PDF), and the
description-bearing operand/tolerance catalogs are all **built on your machine
from your own licensed OpticStudio install** and are gitignored. Only the
author's own sources ship — the `*_synonyms.json` intent vocabularies and
`operand_semantics.json`. Build the data with the `optivibe-build-data` command that
comes with the package; the [repository README](https://github.com/chuang44-tiff/optivibe-mcp#readme) has the
steps and `PROVENANCE.md` the data-source ledger.

Any tool whose data has not been built degrades to a typed "unavailable" result
instead of failing — the rest of the server keeps working.

See `AGENTS.md` for more detail. Python 3.11.
