VerisyntaxEvidence-oriented language
In developmentVerisyntax is a local prototype. Features, syntax, and documentation may change.

Verisyntax — User Manual (prototype 0.1)

Current prototype boundaries

  • CSV, flat JSON, line text, XLSX, SQLite, PostgreSQL, datasets, C++ generation, native execution, run audit, deterministic logic, exact Boolean probability, and initial continuous Bayesian inference are implemented. The standalone desktop composer builds compiler-validated ordered joins across two to eight same-database sources; the VS Code composer remains limited to two sources.
  • Source columns support category, quoted units on numeric columns, and day/week/month/quarter/year period grain. Joins and column comparisons require compatible type, unit, and period. Program-level stratification rejects direct and indirect recursion through negation.
  • Continuous inference supports normal, robust student_t, uniform, beta, and observed binomial. A deterministic temporal evaluator reports Brier score, clipped log loss, calibration bins, and expected calibration error; more likelihoods, posterior predictive checks, and broader model calibration suites remain.
  • Database rows can be queried as datasets. Approved claims and active rules are available together through the hash-bound approved-logic JSON/C++ API and are included as read-only local-AI project context. Structured claim JSON is not automatically converted into a specialized executable predicate; that still requires a separately reviewed program projection.
  • The standalone desktop app exposes the main imported-cell mention and local claim-to-fact review flow plus explicit compiler-validated multi-source join drafting. Its History & provenance panel provides bounded read-only import, inference, execution, and mention history plus exact-run imported record/cell inspection, all bound to the unchanged saved program. The VS Code client still has richer structured comparisons, text-range snapshots, optional join-key profiling, and detailed inference views.
  • Bounded local PDF/DOCX text extraction and controlled HTTPS allowlist, immutable-snapshot, content-hash, and exact-quote primitives are implemented in C++. They are not yet connected to the source/claim UI, and Verisyntax does not fetch a retrieval plan automatically.
  • Metadata schema v8 stores review plans, before/after snapshots, reversible tombstones, and forward/rollback schema steps. The mutation and restore executor/UI is not implemented, so replacement/deletion remains unavailable and missing import rows still never imply deletion. Cross-database joins are also not implemented.
  • The local .app is development-signed. Public distribution still requires Apple Developer ID signing and notarization.

For exact technical contracts, see ARCHITECTURE.md, DATABASE_SCHEMA.md, IDE_PLAN.md, LANGUAGE_SERVER.md, and LLM_EVALUATION.md in the same documentation folder.