Tau Translator — Product Whitepaper (Public Alpha)

This page summarizes the value, approach, and safeguards behind Tau Translator. It is a readable HTML version of our whitepaper; no proprietary assets are embedded and no internal code details are disclosed.

Try Translator Intent Lattices (FDL)

Executive Summary

Tau Translator turns natural‑language intent into clear, testable specifications and back. It provides English → Controlled English → Formal Spec, deterministic validation, and assisted authoring with governance.

Trust & Licensing

No raw licensed Tau grammar is embedded or shipped. We operate at the semantics level and keep Tau printing as a user‑installed adapter. Knowledge packs contain only derivative summaries and examples.

Operating Modes

Assist‑Only: draft & refine; humans approve.
Generate Spec: propose controlled spec; deterministic validation gates acceptance and repair.

Architecture (High‑Level)

Presentation: modern web app and optional desktop client.
Services: prompt analysis, specification synthesis, validation.
Semantics: clean‑room GS/NSO intermediate representation (license‑safe).
Providers: configurable; user‑managed keys supported.

Intent Detection & Analysis (What’s New)

We model ambiguity as a finite distributive lattice (FDL) over facets (intent, guards, quantifiers, temporal). We compute a “certain core” and ask targeted questions to resolve the rest. A clean‑room GS/NSO semantic layer synthesizes unambiguous controlled English. See the explainer: Distributive Intent Lattices.

Deterministic projection to a “certain core.”
Information‑theoretic clarifications to minimize questions.
License‑clean semantic synthesis to controlled English.

Security & Privacy

Deterministic validation before acceptance; transparent reasons.
Data minimization and redaction; user‑managed keys where applicable.
Defense‑in‑depth for the public alpha (rate limits, CSP/CORS, auditability).

Public API (PoC)

Use the public endpoints to explore the translator and build prototypes. Responses are structured and include reasons and validation signals.

POST /llm/prompt-to-spec — English → controlled spec (assist or generate)
POST /llm/spec-to-prompt — Formal/controlled spec → plain English explanation
POST /validate/tce — Validate a controlled‑spec statement
POST /translate/tce-to-tau — Controlled spec → formal target (when available)

Intended for evaluation and early integrations during the public alpha.

Roadmap

Version‑space clarifications and counterexample‑guided queries.
Operator‑aware normalization for canonical controlled English.
Expanded knowledge packs and provenance UI.

Contact

Feedback & issues: GitHub Issues