Implemented application controls

• Authentication is required for matter, evidence, document, analysis, review and release APIs.
• 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.
• Final release requires a current Human Legal Review and all backend blockers to clear.
• Final release is jurisdiction-gated; current automated official-source final-release coverage is Jordan.
• 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.
• 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 current secure upload cap is 3 MB per document in this private-beta transport path; 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.