Document to draft

The document assistant is an example capability running through your local Agent and Worker. It turns a small text document into a proposal you can inspect, test and save as a private capability draft.

It uses the model you configured. Mechanical checks can validate syntax, examples and citations; they do not certify legal, financial or business correctness.

Before you start

• Install and sign in to Rulith.
• Select an enabled Agent and configure its model.
• Install Java 25 for the local checker.
• Prepare a UTF-8 .txt or .md document, at most 256 KiB.
• Choose an Agent whose current work can accommodate configuration changes. An active Case can prevent a new configuration from becoming effective.

1. Prepare the assistant

Open Document assistant in the selected workspace. Start the Worker if prompted.

Choose material delivery permissions and press Prepare local assistant. A remote model needs explicit permission for remote disclosure as well as the local delivery path. Leaving every delivery permission off prevents preparation.

Preparation installs the published authoring capability on the selected Agent, binds its file Source to that profile's material area, and downloads the pinned checker programs once per computer. If Java, the Worker or a Source binding is not ready, resolve the displayed setup error.

2. Add a small document

Attach the file with + → Add files, then ask for a draft. For an initial trial, a short, invented policy is easier to check than a long operational manual.

Demo policy: expense review
An expense has an ID, an amount in USD, and a receipt status.
Amounts from 0 through 100 inclusive qualify only when a receipt is present.
Amounts above 100 do not qualify.
This is test material, not a real reimbursement policy.

A useful request is: “Create a capability draft from this document. Include boundary examples and missing-receipt examples. Ask about ambiguity instead of inventing a rule.”

This is an input example, not an expected-output script. The model may ask questions or need several attempts to pass the checks.

3. Resolve questions and inspect checks

Answer business questions in the conversation. The Agent constructs a proposal and requests the local checks. Review the rule examples and quoted source passages, particularly values at boundaries and cases that should fail.

An attested checker result means the reported mechanical checks ran. It does not raise the truth of every document statement to that tier, or prove that the examples cover every business situation.

If execution is interrupted or its result is unknown, inspect the pending call before continuing. Do not send the same write action again merely to test whether it ran.

4. Review and save

Open Document assistant → Review checked draft. Inspect rules, examples, citations and unresolved questions. Save private draft becomes available only after the matching proposal has a certified completed Case.

Saving stores that selected draft in your private account workspace. Open Workspace → Private drafts in Console to continue editing.

If a save response is lost, reopen the checked draft to look for its saved receipt. An unknown outcome stays unresolved until it can be checked; it is not a reason to create another copy.

5. Publish and install separately

A private draft is not executable configuration. Review it, publish a Release through the separate Console action, then install the chosen Release on an Agent. Check that the installation is effective, configure its Sources and run a small test Case.

Publishing makes the Release content public. Review quotations and source-derived content before publication. The original attachment stays in the Worker material area; Files and permissions explains what else can reach the service or model.

The demo is a starting point for capability authoring. Other workflows should define their own Actions, Sources, tests and acceptance conditions.