Verisyntax — User Manual (prototype 0.1)

Start Center: begin with what you already have

The IDE opens Start Center, so a beginner does not need to write a script first:

  • Blank model opens an empty, unsaved untitled.vsx so you can write the model from scratch. It does not delete a saved file, project folder, imported data, or database.
  • Local data file selects CSV, JSON, TXT, or XLSX. For Excel, the IDE lists the workbook's worksheets so the sheet name does not need to be typed manually. The C++ runtime inspects the file read-only, displays fields, inferred types, and optional values, then generates an editable SQLite or PostgreSQL starter. When an ID-like column is complete and unique across every inspected row, the wizard displays it as an explained primary-key proposal. The proposal is off by default and is added to the .vsx draft only when the user selects it; the original file is never rewritten. The wizard does not import rows. The generated draft switches the left sidebar to the data file's folder, and the first Save proposes that same folder. If the folder does not yet have a configured Verisyntax project, the saved .vsx is automatically registered as the analysis project's start program; an existing project is never silently rebound. Click Check, select the generated source, then use Import files… for a reviewed preview and separate commit. If Verisyntax import metadata is missing, the app explains why the tables are required and asks for separate approval to create them before continuing to the file picker and import preview.
  • Existing database table selects an existing SQLite file or names the environment variable containing a PostgreSQL connection. Click Check, choose the database, then Schema. Select a table or view in the read-only dialog, review columns, nullability, and primary key, and click Add reviewed source draft. This workflow does not change the database.
  • Saved project folder opens a project folder. Start Center keeps the five most recent folders locally for one-click reopening in later sessions. A saved .vsx file therefore provides the simple path back to tables used previously. Open one standalone .vsx file through More tools… → Open file.
  • New article evidence project selects an empty folder and creates article_analysis.vsx, <article-storage>/, and data/. The starter uses a local SQLite file and supports repeated imports of ordinary raw TXT articles. A local LLM can then propose the logic-bearing passages, so the user does not have to divide the article line by line. It never overwrites an existing .vsx project.
  • Question for local AI provides focused task templates. Add your question. Add project facts, code & schema to Request validates every registered .vsx file and adds its declarations plus every active database-approved fact and rule. Each database record includes its exact version, hash, and approval provenance. Other project files and libraries are read-only context; the model must return one complete proposal for the current file. Ordinary domain-table rows are not fetched. Read the complete Request field and review the local model, 64K/128K context, and loopback endpoint before approval. The C++ parser validates the proposal, and it can be applied only when all existing facts, rules, and data declarations are preserved. Apply preservation-safe draft is undoable and does not import, approve, or execute anything.

The default toolbar shows Start → Save → Check → Compile & build → Run plus Clear model. Compile & build checks, generates C++, and links the local executable as one automatic action without confirmation dialogs; any failed stage stops the chain and opens the exact error in a dialog as well as Diagnostics. Clear requires confirmation and empties the current editor while resetting the Diagnostics tab, issue count, and editor markers; the editor change is undoable. A saved .vsx changes only if you subsequently click Save, and Clear never deletes project folders, imported data, databases, or review history. More tools… reveals single-file open, formatting, IR, metadata initialization, database audit, and result-file controls; Fewer tools hides them again. Help: from start to result and the Current data, Local AI, Claim review, and Rule review panels can each be opened and closed as needed.

Preview IR means *Preview Intermediate Representation*. It displays the machine-readable JSON understood by the C++ compiler between .vsx source and generated C++. Advanced users can inspect types, sources, datasets, rules, queries, and hashes. It does not execute the program or change data, so beginners can normally ignore it.