What shipped
Product updates
Every Izuran Legal release, newest first: what shipped in research, drafting, the matter file, sources, and the account.
Every Izuran Legal release, newest first: what shipped in research, drafting, the matter file, sources, and the account. Each entry is left as published on its date.
Tighter permissions in matters and offices
- Matter viewers are read-only
- Office member changes are saved
The matter viewer role is now read-only in the matter's chats: viewers cannot send, edit, regenerate, or stop someone else's answer. Queued follow-up messages are visible to and sent by their author only. Changing a member's role or removing them from the office portal is now saved, and two-factor authentication is required for every account holding console permissions.
Finish research and open the latest messages
- Final synthesis uses the same selected model
- Latest message shown when returning or reloading
A final answer step is reserved before research steps run out, with unproductive repetition stopped and evidence gaps explained. Existing chats open at the latest message and respect your position when you scroll up to read older messages.
Completing answers after research
- Distinct reasons for missing answers, output limits and research step limits
- Retry older replies that stopped at a skill announcement
Chat recovers answer text delivered at the end of a stream and asks the same model to continue when it stops at a progress announcement. If no final answer arrives, a clear reason and retry are available.
Analysis summaries in your question’s language
- Translated summary headings and paragraphs
- Answers remain available if summary translation fails
Answers and analysis summaries follow your requested language or question language, falling back to the website language. The translated summary appears after the answer, uses the same model and counts toward request usage.
Message actions and clearer chat failures
- Provider credit, token limits and timeouts distinguished from plan allowances
- Failure details survive reloads
- Rejected text remains available to copy and edit
Copy or remove messages while keeping editing available. Failed replies show the provider, model and support reference, with a retry that reuses the question.
Clearer chat model controls
- Route and model state update together
- Accurate message when the legal tool is unavailable
Operators can hide or disable a model used by a chat route, choosing a ready replacement when it is the default. Chat identifies an unavailable legal analysis tool instead of incorrectly blaming question length.
Answer path restored and archive status clarified
- Legal Skill reconnected for the selected model
- Source gaps shown separately from download failures
The selected OpenAI model has been reconnected to its legal Skill after the previous identifier became invalid. Operations now separates publisher-unavailable files from actual archive download failures.
A dedicated Website Studio
- A separate workspace for website design
- Clearer live-page and draft states
Website pages now have a dedicated studio with clear navigation, using your existing account and permissions. Old links open the studio, and signing in returns you to the requested page.
An institutional website and visual content editor
- Izuran templates in seven languages
- Drag-and-drop editing, mobile preview and an image library
- Separate editing and publishing permissions with version history
Clear paths for the platform, solutions, resources and contact, with plans on a dedicated page. Website staff can design pages, save and preview drafts, publish and restore versions from Content.
Explore workflows from the homepage
- Four workflows linked to their guides
- Keyboard navigation and a responsive mobile layout
The homepage explains matters, research, drafting, and saved versions through an interactive overview, with a guide link for each workflow and Izuran’s identity in light and dark modes.
Quote-match state and matter-file re-checks
- Quote-match badge only when evidence exists
- Matter files denied after membership revoke mid-run
The source card now shows whether text is an excerpt, unreviewed OCR, or verbatim from human-reviewed text when the evidence exists. Matter-file tools re-check membership during the run.
Packages, routing, and office AI policy on one path
- Routing tiers shown next to each plan’s models
- Office AI policy from the organization settings console
- Cancel requested on matter-member removal
- Clearer no-training copy without a ZDR claim
Plan eligibility for routing models now matches what plan economics uses, and operators can set an office AI policy from the organization record. Removing a matter member requests cancel of their active runs, and the no-training wording is clearer on pricing and account privacy.
The processing register in the trust centre is readable again
- Every register card sets its own ink instead of inheriting the band behind it.
- The security badge in the homepage product frame is readable in dark mode.
- Journal, chamber and careers footers are now full-width bands instead of a floating slab.
Operation titles and company names in the processing register were rendering in a light ink on a white card and were nearly unreadable. The cards now follow the page paper with clear ink, and the file-journey section is back to its calm layout.
QR code for two-factor setup
- The code is drawn in your browser; the secret never leaves the platform.
- Available to every account from the Settings page.
Enabling two-factor authentication from Settings now shows a QR code to scan with your authenticator app, with the text key still available for manual entry.
Official Gazette references
- Gazette references use the correct source name.
- The law stays linked to its table and pages in the original issue.
Texts linked to a Parliament Gazette issue open their verified original PDF, with file and printed page numbers preserved in the reference.
Stable site navigation
- Pricing, team and careers links no longer disappear briefly during navigation.
- Homepage section links work without reloading the entire page.
Navigation links and the account button stay visible when moving between the guide, blog and other site pages, even on a slow connection.
More reliable sign-in to chat
- Sign-in opens `/chat` with a clean load.
- Frontend updates no longer leave the user on a white application-error page.
- No change to accounts, conversations, or data.
After sign-in, the browser opens chat with a full load of the current version and recovers automatically if an old bundle is left behind after a platform update.
The mix is for the public site; the signed-in app is unchanged
- The visitor site keeps the mix on the bar and sections.
- The signed-in workspace has no inverted rail or page headings.
- Sign-in remains part of the public site.
The navy-in-light and cream-in-dark islands stay on the public site: homepage, docs, trust centre and sign-in. After you sign in, the rail, page headings and chat look as they did before.
The mix now runs through the rail and every page heading
- The icon rail and mobile bars reverse with the theme; the conversation list stays page paper.
- Matter, document, settings and chat headings follow the mix without inverting the whole page.
- The homepage, docs and trust centre place islands across successive sections.
The opposite-colour island is no longer limited to a few bands: it now appears in the app rail, page headings, chat welcome, the public site bar, and more homepage and docs surfaces. Paper stays paper beside the island.
Blue in light mode, cream in dark
- Heroes, bands and the identity pane reverse with the theme instead of staying navy in dark mode.
- Cards on an island follow the page paper; the gold action stays brand gold.
- The emblem on an island switches: silver on navy, blue on cream.
The page follows the theme and keeps an opposite-colour island: navy inside light mode, cream inside dark mode. That mix appears on the trust centre, homepage, sign-in, pricing, careers, journal, chamber and docs, and in the figures bar and chat messages.
Chat routing and cost review
- Token-cost preview without an AI call, with tier and plan eligibility context.
- Input, output and cached-input prices share a calculation source, with dated history and finance permissions.
- Review changes before saving; outdated settings and admin-restricted defaults are rejected.
Administrators can compare models and recorded costs for each analysis tier before saving routes, and review provider rates and effective dates on the same page. Customer subscription prices remain separate.
Processing and privacy by tool
- Anthropic and OpenAI by implemented operation
- Training, retention and processing-location policies
- Permission-controlled editing with an audit trail
The trust center and account privacy show the company, service and data scope for each operation. Administrators can register future providers and document a separate policy for each provider and tool, with a reference and review date before publication. Registration or policy edits do not change where files are sent.
A clearer trust center
- Three entry points to the details
- File journey with external processing identified
- Responsive design in seven languages
A new design explains file access, the document journey, and answer sources. The page describes external processing and retention limits, with an educational source-card example, expandable questions, and direct guide links.
An account-deletion tool on the user record
- Delete from the user record
- Includes administration accounts
- Identifier confirmation
From the user record you can delete an account after typing its identifier. That includes administration-console accounts, which previously had no delete action. Your own account and the owner stay protected. The financial usage ledger is kept without a user link.
Where accounts are deleted
The deletion tool sits at the bottom of the user record and in the directory menu. It is not the browser prompt that used to be hidden for administration accounts.
- Type the email or username exactly as shown to confirm.
- Private conversations and files are removed with the account. Financial usage rows remain.
- The owner account is not deleted, and you cannot delete your own account.
A trust center, workspace bounds, and a source card
- Public trust center
- Workspace privacy
- Clearer source card
The platform now states who can see a file, what is sent to an AI provider, and what appears under an answer. Public copy follows what was tested: office membership does not open a matter, an organization workspace without a matter is shared, a lawyer’s scan goes through Anthropic, and the validity badge is not proof of the applicable version.
Who sees the file
The user guide said no other user sees your files. That was broader than the product. The correction: a personal workspace is yours, a matter is for its members, and an organization workspace without a matter is shared inside the office.
- A public trust center in seven languages, without ISO seals or a residency map.
- In settings: the bounds and the AI path as the server enforces them.
- A control register in the console for those who can read the audit log.
What appears under the answer
The source card shows validity evidence level, issuing body, and page when they are present. No legal-probability percentage is invented. The validity badge is read with its limit.
- Open the source before relying on the badge.
- A lawyer’s scanned file is sent to Anthropic vision; that is stated, not hidden.
A product version and a public changelog
- Version number
- Public history
- Seven languages
The platform now publishes a clear version number and records what reached the user on each date. This is the first public history; earlier versions were reconstructed from what was already running on those dates.
Where the number is read
The number is the same in the guide and in account settings. It is not the npm package number, and not a repository hash.
- The current version appears in account settings, with a link to this page.
- Each entry below stays as published on its date; a correction is added in a later release.
- This history describes user-facing behaviour. Internal operations notes are not here.
Complete rulings, archived originals, and fixed draft versions
- Complete ruling
- Archived original
- Evidence grade
- Fixed version
A Supreme Court principle opens the archived complete ruling when identities agree. The international-law lane starts with the stored official file. The validity badge is read with its evidence grade. Draft export is rendered from a stored, checksummed version, not from the live browser editor.
Supreme Court principles and the archived ruling
The principle remains a principle. The complete ruling opens from the archived original when article identities agree across the principle, the relationship, and the ruling.
- When identities agree, the structured text and the archived PDF open in the same viewer.
- A correct session date overrides a malformed date in the ruling payload if they conflict.
- The principle is not replaced by the ruling text, and the ruling is not copied into the principle record.
The treaty original before the source card
In the international-law lane inside Judgments, the stored official file is the first surface.
- The archived CTC or PDF opens inside the viewer, not an organisation homepage as the original.
- Text extracted from the file is labelled as extracted, and is not citation-ready on its own.
- The external source page stays a separate link; it is not presented as the stored file.
Grades of validity evidence
The badge is not proof of the applicable version. Evidence is linked, named, or source-badge only.
- Linked: the repealing or amending text is a corpus document you can open.
- Named: the successor is named from stored text, without a file link.
- Badge only: the status comes from the source, without identifying what repealed or amended it.
- A successor is not invented to fill a gap. A visible gap is safer than an invented authority.
Fixed drafting versions
- A named version receives a draft-scoped number, an identifier, a SHA-256 digest, and a stored preflight result.
- PDF or Word export creates or reuses a content-identical version, then renders only that stored row.
- Two named versions of the same draft can be compared after both digests are recomputed.
- Citation markers in a draft address ordered stored sources, not a decorative list.
Conversation links and the follow-up queue
- Each conversation has a stable address that can be reopened and shared inside the account.
- During a turn the composer stays open; each send adds an item to an ordered queue instead of replacing the text.
- A queued item can be edited or cancelled before it is taken.
Agenda, memory, and one lawyer workspace
- Agenda
- Memory
- Unified chrome
- Frozen price
Agenda and memory became first-class lawyer workspaces. Application pages and public sign-in share one header. Usage reports freeze the price that applied at the time of the call.
Workspaces
- Agenda gathers hearings and procedural deadlines on one surface.
- Memory stores what you asked the counsel to remember about you, separate from the legal corpus.
- The matter file and the remaining lawyer pages share one visual system with the application sidebar.
Usage at the price of its time
- The cost report freezes the price and request context; the past is not recalculated from today’s list.
- Intelligence tools pass through one credit reservation before they run.
- The public sign-in screen now uses the same site header.
Answer language, judgment scope, and the lawyer’s desk
- Answer language
- Judicial scope
- Badge with evidence
- Workspaces
The answer follows the interface language; the source language stays visible. Judicial research has an explicit scope, separate from private office precedents. The validity badge is not read as a ruling. Chat, matters, drafting and tools were rebuilt as workspaces.
Answer language and source language
- The answer is written in the selected interface language.
- The source reader shows the original language and the display language, and does not call a secondary copy official unless the source says so.
- The count of legal works is shown separately from the count of language representations.
Judgments with three scopes
- The domestic corpus first, then judgments and principles as a separate judicial scope, then private office precedents.
- Judicial scope is explicit in count and identity; a missing source year stays unknown and is not filled with an import date.
- Index-quality measurement in the administration console describes database and search parity, not legal-answer accuracy.
The lawyer’s desk
- Chat was rebuilt as a consultation desk: question, answer and sources on one path.
- The matter file, drafting, tools and the document library became workspaces with a clear sidebar.
- The validity badge is shown with a warning that it is not proof of the applicable version.
Commercial launch
- Libyan corpus
- Matter file
- Subscription plans
- Arabic and English
A Libyan legal research platform for counsel: a question with an answer whose source opens, a matter file, drafting, and subscription plans. Arabic and English are product languages. An administration console for organisations, billing, and corpus operations.
Reading the text
- Counsel searches Libyan legislation, Supreme Court judgments and the Official Gazette.
- An answer is a door to the page, not a summary that closes the file.
- The corpus is a public original; client uploads stay in the matter file.
The matter file and tools
- A file per matter: parties, deadlines, documents, and conversations bound to the file.
- Drafting of a brief, petition or contract, with export.
- Tools: contract review, comparing two texts, a deadline calculation, an inheritance division.
Account and administration
- Subscription plans with seats and a usage allowance.
- Arabic and English as interface languages.
- An administration console for organisations, billing, corpus source operations, and the audit log.
These pages describe the platform as it works today. Verifying the text and its application remains the professional’s responsibility.