Getting Started
This guide walks through the Jaxon platform's core workflow using screenshots. By the end, you'll understand how documents, rulesets, datasets, and runs fit together to verify text content against formal policies.
Dashboard and the Workspace Menu
After signing in you land on the Dashboard -- a summary of your workspace: headline stats (projects, rulesets, runs this week) and your favorite and recently updated projects.
The left-side workspace menu is always present at this level:
- Dashboard -- the summary described above
- Projects -- browse and enter your projects
- Documents -- every document across your workspace, including ones not yet in a project. A count badge shows the total.
- Rulesets -- every ruleset across your workspace, including ones not yet in a project. A count badge shows the total.
- Activity -- run summaries and the platform activity log across your projects
- Documentation / API Reference -- external references, opened in a new tab
Documents and rulesets are created directly from their workspace pages (see below), so the menu carries no separate Create or Import actions. At the workspace level, a Select a project ▾ picker in the top header bar lets you jump straight into any project.
Projects
A project is a container that groups documents, rulesets, datasets, and runs for one piece of work. Documents and rulesets don't have to live in a project — they can be unaffiliated (created at the workspace level) and added to a project later — but datasets and runs are always project-scoped. The Projects page lists your projects with search, sort, and a card/list view toggle. Click the star on a project to mark it as a favorite; favorites surface on the Dashboard.
- Returning users see their projects with search and sort. Click a project to enter it.
- First-time users (no projects yet) see a welcome screen with a single Create Project action.
Entering a project swaps the left menu to the project menu -- Documents, Rulesets, Datasets, Runs, and Activity -- with the project's name shown at the top and a grid button beside it that returns to the workspace level. The Projects breadcrumb in the top header bar also returns to the workspace, and the project name in the breadcrumb switches directly to another project.
Workspace Documents and Rulesets
The workspace-level Documents and Rulesets pages list assets across every project plus any that are unaffiliated. Each row carries a project chip: a linked asset shows its project (click to open it there), while an unlinked asset shows an Unaffiliated tag with an Add to project control.
A document or ruleset belongs to at most one project. Adding it to a project moves editing into that project — an affiliated asset opened from the workspace page is read-only, with a link to open it in its project. To reuse an asset in another project, Duplicate it from the row's ⋮ menu (the copy defaults to [name]-copy and can target any project or none).
Removing a document from its project is done from within the project's Documents page (Remove from project in the ⋮ menu). Machine-generated (silver) documents, and documents that back a ruleset or dataset in the project, are permanent members of that project and can't be removed. Rulesets can be disassociated directly from the workspace Rulesets page via the chip's × control.
Tip
Create a dedicated project for experimentation so your work doesn't mix with existing data.
Policy Documents
Every ruleset begins with a policy -- the set of requirements you want to enforce. In the platform, policy content is stored as a Document.
The Documents page, accessible from the sidebar, lists all documents in your project.
Documents are organized into Gold and Silver sections. Gold documents have been reviewed and verified by a human. Silver documents are machine-generated and not yet human-reviewed; they are created when synthetic documents are generated to expand the breadth of a Dataset. Once a silver document is reviewed and approved, it can be promoted to gold. All documents are versioned and immutable. Once saved, a version cannot be changed, ensuring that ruleset evaluations are always reproducible.
The Import Documents button opens the import interface, which accepts PDF, DOCX, TXT, MD, and CSV files. Create Document opens an editor to type or paste content directly.
Rulesets
With a policy document uploaded, you can create rulesets that encode its requirements as verifiable rules. A Ruleset is a collection of individual rules that each check one specific compliance requirement.
The Rulesets page, accessible from the sidebar, lists all rulesets in your project.
Click Create Ruleset to open the creation wizard. In the Type step, choose how to build your ruleset:
- From Policy Documents derives rulesets and rules automatically from an existing policy document. This is the recommended starting point when you have a policy to encode.
- Empty Ruleset creates a blank ruleset where rules are defined manually in the Ruleset Studio.
Creating Rulesets From Policy
When you select From Policy Documents, the wizard walks through eight steps:
- Step 1 -- Details
- Enter a name and optional description for the ruleset.
- Step 2 -- Type
- Select From Policy Documents.
- Step 3 -- Models
- Select the Configuration Model (used for extraction and DSAIL generation) and Run Model (used when evaluating content with the ruleset).
- Step 4 -- Select Documents
- Choose the policy document to extract rules from.
- Step 5 -- Set Theme
- Define a theme to guide rule extraction. Enter a title and optional context with extraction guidance. You can also click Suggest to auto-generate a theme from the selected documents.
- Step 6 -- Extract Rules
-
Choose an extraction method:
- Basic -- Direct LLM extraction, suitable for shorter policy documents
- RAG -- Retrieval-augmented extraction for longer, complex documents
Extract Rules kicks off the analysis. The platform extracts individual requirements as rules. This can run in the background.
- Step 7 -- Generate DSAIL
- The platform generates DSAIL Language code and data extraction questions for each rule. Generate DSAIL begins the process (can also run in background).
- Step 8 -- Review & Create
- Review the created ruleset and its rules. From here you can open the ruleset in the Ruleset Studio to view and refine its rules.
Creating an Empty Ruleset
When you select Empty Ruleset in the Type step, the wizard collects a name, description, and model selections, then creates the ruleset immediately.
Once created, the ruleset opens in the Ruleset Studio where you define individual rules manually. This gives you full control over each rule's natural language description and DSAIL code, without deriving them from a policy document.
The Ruleset Studio
After the wizard creates rulesets, opening one takes you to the Ruleset Studio -- the editing environment for viewing, modifying, and refining rules.
The Studio has a three-panel layout:
- Rule list (left) -- Navigate between rules. The "+" button adds new rules.
- Rule editor (center) -- Edit the natural language description and DSAIL code. "Generate DSAIL" creates code from the description, and "Generate Questions" creates claim questions.
- Test panel (right) -- Enter test input, run a test, and see per-assertion results immediately.
The DSAIL Editor
Selecting a rule opens its details, including the DSAIL code editor.
Each rule's DSAIL code contains declarations (variables representing facts about the input text) and assertions (logical expressions that must hold true for compliance). The [pessimistic] annotation tells the solver to treat unknown values as failures -- the recommended setting for compliance checking.
Datasets
With a ruleset configured, test data measures how it performs across a range of inputs. A Dataset groups documents together for batch testing.
The Datasets page, accessible from the sidebar, shows all datasets in your project.
The Create Dataset button creates an empty dataset with a name and optional description.
Once a dataset exists, click on it to open its detail view. From here you can populate the dataset with documents using three methods:
- Import CSV converts each row of a CSV file into a new document in the dataset.
- Generate Records creates new synthetic documents (silver documents) from existing documents in the dataset, using an LLM to expand test coverage.
- Add Documents lets you select documents that have already been uploaded to the Documents section and include them in the dataset.
For meaningful testing, include a mix of compliant and non-compliant examples.
Runs
With a ruleset built and test data prepared, runs execute the ruleset against documents and produce detailed results. A Run is a single evaluation session.
The Runs page, accessible from the sidebar, shows all runs in your project.
The New Run button opens the configuration dialog.
Select a ruleset, then choose a run type:
- Batch -- Select a dataset to run the ruleset against. Two test modes are available:
- Evaluate produces results for each rule against each document in the dataset.
- Variance Test measures the performance of derived questions and claims over a specified number of runs by analyzing variability in the results.
- Interactive -- Run the ruleset against provided input text. The platform evaluates each rule in the ruleset against that content and returns the results immediately.
Understanding Results
After a run completes, the detail view shows per-rule sections for each document:
- Assertions -- Each shows TRUE (compliant), FALSE (violation found), or UNKNOWN (insufficient information)
- Claims -- The questions asked of the document and the LLM's extracted answers
If a variance test was included, the Variance tab shows how consistent results were across iterations, with color-coded variance percentages for each claim. See Runs for a detailed explanation of variance results.
Activity
The Activity page, in the workspace menu, has two subtabs, with a project filter beside them that scopes both:
- Feed -- run summaries from across your projects. Each card shows the run's outcome (pass, fail, or partial), the ruleset and dataset involved, the pass counts, and when it ran. Filter chips narrow the feed to failures & partials or passing runs, and View run jumps straight to the run's detail view inside its project.
- Logs -- system activity across your projects. For general users it displays data-auditing information for projects the user has access to; for auditors, many additional categories are available via the All Categories dropdown.
Inside a project, the project menu's Activity item shows the same two subtabs pre-scoped to that project.
Two additional filters are available in the Logs tab alongside the category dropdown:
- Search -- Filter on any input string across all activity content.
- Time -- Select a preset time window looking back from the present (e.g. last hour, last 24 hours), or specify a custom block of time.
What's Next
That covers the core workflow: policy documents, rulesets created with the wizard, rule refinement in the Studio, test datasets, and evaluation runs.
Deepen your understanding:
- Documents -- Versioning, content management, and the two roles documents play
- Rulesets -- Rulesets, rules, DSAIL code, and the Ruleset Studio
- Datasets -- Organizing test data for batch testing
- Runs -- Batch testing, variance analysis, and interpreting results
- DSAIL Language -- The formal logic language behind the verification engine
Follow a hands-on tutorial:
- SEAD-4 Tutorial -- Build a security clearance adjudication workflow using SEAD-4 alcohol guidelines
- SOX Compliance Tutorial -- Step-by-step tutorial building a SOX compliance verification setup
Optimize your rulesets:
- Best Practices -- Techniques for improving rule accuracy and getting the most from the platform