Implemented application controls

• The public beta guest flow requires no account and does not persist public guest questions as MERENVAY legal matters; protected matter, evidence, document, review and release APIs remain authenticated.
• The public beta does not accept client-document upload, does not write public guest questions to Notion and does not use Hermes for guest analysis. The preliminary guest issue map is generated in the browser and its question/decision text is not sent to the MERENVAY backend or an AI provider. The separate public Quick Chat records minimised anonymous operational metrics by default; raw question text is retained only after explicit visitor opt-in and identifying-information screening. Quick Chat analytics do not create email, Human Consultation, a legal matter or a legal opinion.
• Matter ownership is checked before matter-specific records or signed document links are returned.
• Stored document paths are namespaced by authenticated user and matter.
• Supported file types are checked against declared type and file signature; DOCX archives have bounded entry, expansion and compression-ratio checks.
• Embedded-text PDF extraction runs with JavaScript evaluation disabled and is exercised by a synthetic runtime self-test; scanned PDFs without meaningful embedded text fail closed for OCR/review instead of being treated as read.
• Extracted and retrieved source state is bound into material fingerprints; stale analysis and stale Human Legal Review are invalidated.
• Official-source verification requires consumed source content rather than a citation label alone.
• A separate adversarial AI Red Team and reconciliation step fail closed before release-eligible synthesis.
• The conditional-probability calculator runs in the browser using caller-supplied assumptions and attestations. MERENVAY does not verify its source metadata or likelihood ratios. Its ranges are hypothetical scenarios, not confidence intervals, calibrated case-success probabilities or legal conclusions; incomplete or conflicting inputs block the numeric result.
• The Jordan research path no longer constructs public search query URLs from matter text. It uses fixed official hubs and host-validated configured source URLs. This closes the identified query-link disclosure path; it does not make the protected workspace offline. Configured private AI processing, source retrieval and cloud storage still apply.
• Human Legal Review remains mandatory, but final release commit is intentionally held in the live private beta while release atomicity and production-assurance gates remain open.
• Automatic official-source research is currently configured for Jordan matters. Retrieved sources still require human verification. This research scope does not enable final release: final release commit remains on hold for every matter in the live beta.
• Authenticated matter deletion removes app-held matter records and stored matter artifacts when the deletion completes successfully.
• New client-document upload is currently disabled in the live beta while the production data-governance gate remains open.

Explicitly not claimed yet

• No SOC 2, ISO 27001/27701/42001 or equivalent certification is claimed.
• No independent penetration-test report or external audit opinion is claimed.
• The adversarial AI Red Team is procedurally separated from draft composition; independent model/provider identity or external-reviewer independence is not claimed.
• No guaranteed hosting region or data-residency commitment is claimed without deployment-specific documentation.
• No public claim is made that scanned multi-page PDFs are fully OCR-processed; scanned PDFs that lack meaningful embedded text fail closed as needing OCR/review.
• The configured upload-path limit is 3 MB per document, but new client-document upload is currently disabled. Larger-document production transport is not claimed until a separately verified upload architecture is available.
• A fully generated dependency lockfile/SBOM and independent software-supply-chain attestation remain external release-evidence items; core runtime/build dependencies are pinned where verified to reduce drift.

Design principle

MERENVAY does not treat visual confidence, model confidence or marketing language as a security or legal guarantee. Trust-relevant state is intended to remain inspectable and block release when required evidence, document coverage, applicability, Red Team reconciliation or human approval is incomplete.