Public Documentation

Lawie Docs

Releases

The canonical record of verified product and documentation changes, deprecations, behavior changes, security notes, and known issues.

Release cadence is event-driven: material changes are published when verified, with periodic digests when enough changes accumulate. No release is invented to satisfy a calendar.

Release-note standard

Each applicable note distinguishes New, Improved, Fixed, Security, Behavior or Breaking Changes, Known Issues, and migration action. AI changes describe user-visible impact on citations, evidence scoring, confidence behavior, or default workflow behavior without publishing sensitive internal prompts.

Deprecation Center

No deprecations scheduled.

major

2026-07-14

Canonical Lawie Docs Portal

New

Added first-class Help Centre, Developers, Trust Centre, and Legal and Policies sections.

Added article feedback and full-body documentation search.

Improved

Consolidated product help, developer documentation, releases, status, support, security, trust, and legal policy navigation under docs.lawielabs.com.

Expanded generated Help articles with expected results, security notes, limits, failure recovery, related content, and escalation guidance.

Security

Restricted the interactive API explorer to the Lawie sandbox and to operations published in the sanitized public API reference.

Removed internal and retired Help or Support routes from the public OpenAPI catalogue and shared SDK surface.

Behavior changes

Product Help URLs now use /help/{article}; legacy generated guide URLs redirect to the canonical article.

Status no longer infers availability from synthetic or stale fallback data.

AI impact

Added explicit documentation for AI boundaries, citation verification, confidence and evidence-strength interpretation, and safe feedback.

No model, scoring algorithm, default prompt, or product inference behavior changed in this release.

Known issues

The production subprocessor register and formal contracting identity remain unpublished until supported by executed legal and vendor records.

Fixed

Service status now uses direct live production probes when no external status feed is configured; it does not infer availability from cached or synthetic data.