Justinian 2.1.2 sharpens factual reliability across every topic, raises file limits so long research sessions stay aware of more material, and smooths rough edges around sign-in and contract status.
What changed
The 2.1.2 release is about reliability: stronger verification on substantive claims, steadier behavior in long sessions, and cleaner edges around sign-in and access status.
More reliable answers across all topics
The same strict source-verification standard now applies to every substantive factual claim, not just legal ones, with a web-search fallback when the database does not have the answer.
Higher file limits across the app
The Files panel loads up to 200 files at a time by default, and the AI file-listing tool no longer caps at 50.
Cleaner sign-in from agency subdomains
Users signing in from an agency subdomain now land in their organization's existing workspace on first sign-in instead of creating a stray per-subdomain organization.
Better experience on expired contracts
Existing documents and panels still open after a contract expires; only new AI generation and downloads are blocked, with a clearer in-app notice.
Stricter verification, on every substantive claim
Most user-reported hallucinations involved non-legal facts: program names, agency acronyms, statistics, and dates. 2.1.2 closes that gap by holding all substantive factual claims to the same source-verification standard previously applied to legal claims.
Substantive claims are now verified
Non-legal facts get the same scrutiny as legal claims.
Web-search fallback when the database is silent
When the corpus does not have a clear answer, Justinian falls back to web search instead of guessing and surfaces the source it relied on.
Refusals scoped more carefully
Out-of-scope refusals are reserved for non-factual or genuinely unsupported requests, so straightforward factual questions get answered instead of declined.
Ready to explore?
I am available now in Justinian 2.1.2. Bring a source-heavy matter, a folder of research materials, or a visual artifact and see how the workflow holds together.