DOCUMENT REVIEW · BUILT WITH OVERLIFT

Vellucent Studio

Review the writing. Protect the meaning.

Vellucent is a document workspace for reviewing PDF language while keeping proposed changes tied to the original text. This case study shows how meaning checks and human review distinguish a useful correction from a change that should be refused.

See the document review workflow See project screenshots
Vellucent Studio browser qualification laboratory with local capability checks and proof gates
Browser qualification laboratory Vellucent measures isolation, shared memory, local storage, WebGPU, document engines, and proof gates before trusting the browser with a sensitive document workflow.

Recorded project scope

Implemented

Browser qualification and local capability evidence

More in this category (2)
  • Proof Truth corpus and deterministic grammar-proposal admission
  • Private-first document workflow with visible fallbacks and review gates

Demonstrated

Local PDF and fixture processing without document content in the qualification report

More in this category (2)
  • Separation of required corrections, preserved writing, ambiguity, and meaning risk
  • Sentence reconstruction and failure-directed evaluation surfaces

Planned

Owner-qualified learned 384-dimensional MiniLM Semantic Bridge

More in this category (2)
  • Broader large-PDF editing, retrieval, and reversible transformation workflows
  • Dedicated GPU training and distillation workflow on the RTX 5090 system

Research

A selected grammar winner—or explicit no-winner result—from ProofTagger, BERT Tiny, and DistilBERT campaigns

More in this category (2)
  • Meaning-preserving multimodal document revision
  • Semantic and causal evidence for complex document changes
PROJECT SCREENSHOTS

Explore the interface, workflow, and results shown in the project screenshots.

MARKETING

Who it helps and why.

Large or sensitive documents are difficult to review, and ordinary AI editing can make a sentence sound smoother while quietly changing what it means. Sending every page to a cloud model also creates a privacy problem before the user has even decided whether outside processing is necessary.

What makes it useful: Generic PDF copilots flatten structure and treat fluent output as success. Vellucent retains page/object anchors, separates exact evidence from learned interpretation, measures required corrections and KEEP cases, protects consequential meaning, refuses unsafe changes, and preserves a reversible proof of every decision.

BUSINESS / EXECUTIVE

Business value.

Vellucent is designed to help a reviewer improve a document while retaining control over disclosure, protected facts, and accepted changes. The intended benefit is more accountable review; time savings and suitability for a particular document workflow need their own evaluation.

Explore the business outcomes
  • Lower document exposure and cloud dependency
  • Traceable, reversible corrections for government and regulated review
  • Faster review without silent source mutation
ARCHITECTURE

How the system fits together.

Deterministic Proof Core and JavaScript/C17-WebAssembly Meaning Lock are active. A pinned same-origin MiniLM runtime is acquired and recovered automatically, executes in an isolated worker, and remains behind native learned-output admission. The current Semantic Bridge still uses its deterministic projection until the learned 384-dimensional path is owner-qualified; ProofTagger, BERT Tiny, and DistilBERT remain candidate grammar systems rather than a claimed production winner.

A representative workflow

  1. 01

    Check the browser capabilities and open the local document workflow with the original preserved.

  2. 02

    Review a proposed correction alongside the source and the Meaning Lock checks on protected content.

  3. 03

    Accept, reject, or revise the proposal, retaining the original and the record of the accepted operation.

Explore the architecture details

I built Vellucent Studio as a private-first document workstation. The browser qualifies its own capabilities, processes local document fixtures, measures proofreading truth, separates required corrections from writing that must remain untouched, and admits only structured proposals that pass deterministic policy and meaning checks.

ENGINEERING

Engineering choices.

I kept the original document immutable and made corrections reviewable proposals. Meaning Lock checks protected content before acceptance. This adds an explicit review step, while preserving the distinction between a suggested improvement and an authorized document revision.

Explore the technology and engineering details
Technology stack.NET 10, C17/WebAssembly, OPFS, WebGPU, ONNX Runtime Web, local RAG, optional multimodal model routing
  • Page-aware PDF evidence with source, object, geometry, revision, and uncertainty anchors
  • Correct, preserve, review, or refuse through Proof Core and Meaning Lock
  • Local-first semantic proposals with explicit capability, approval, verification, and receipt boundaries
OVERLIFT METHOD

How this product applies the OverLift method.

OverLift gives agents room to inspect, retrieve, and propose while denying ambient document authority. Exact source identity, explicit capabilities, Meaning Lock, approval, deterministic operations, verification, receipts, replay, and recovery decide what may become an official derived revision.

Explore the shared OverLift architecture

The method is reusable. Each product supplies its own facts, rules, execution, and validation. These tiers describe the shared architecture; the project scope above records which capabilities are implemented here.

Why determinism matters here: Government and regulated documents cannot accept a fluent but untraceable mutation. Determinism binds source identity, protected meaning, policy, approval, operation, and verification to one reproducible decision chain.

  1. T0
    Exact baseline

    Define the authoritative result before adding acceleration, semantics, or agents.

  2. T1
    Measured evidence

    Instrument state, latency, quality, and failure so improvement is observable.

  3. T2
    Bounded ownership

    Move expensive or high-frequency work behind clear worker and memory boundaries.

  4. T3
    Deterministic transport

    Version messages, snapshots, identities, deadlines, and replay inputs.

  5. T4
    Semantic assistance

    Let local retrieval and models propose meaning only inside admitted evidence.

  6. T5
    Candidate paths

    Compare several allowed next actions with explicit risk, cost, fit, and uncertainty.

  7. T6
    Shadow verification

    Challenge the production route without giving the challenger authority.

  8. T7
    Governed production

    Promote only measured, replayable paths with fallback and operational receipts.

  9. Tier-S
    Experimental challenger

    Run advanced evaluators in shadow, compare them with the control, and graduate only repeatable gains.

CATS

Context-Aware Tier Selection

CATS chooses a qualified execution tier for the evidence, device, latency, permissions, and failure conditions of the task.

SEMANTIC BRIDGE

Meaning becomes typed product state

The Semantic Bridge maps a goal to explicit entities, evidence, uncertainty, tools, and permissions. Missing or contradictory information remains visible.

DETERMINISM

Validate the action and retain the result

Models may retrieve, compare, or propose. Exact software checks facts, permissions, state changes, and execution, then records what happened.

OverLift securityAgentic AI Glossary

Read the OverLift MethodOverLift.ai See other products
PROOF

Evidence and limits.

The Browser Qualification Laboratory exposes available local capabilities and fallbacks. The Proof Truth Laboratory records correction, preservation, abstention, and false-positive checks. These are evidence for specific tested capabilities; they do not qualify every browser, document, or candidate grammar model.

Explore the meaning-preservation lab View project screenshots

Back to the project overview ↑

GOVERNMENT AND REGULATED DOCUMENTS

Proofread the language. Preserve the record. Prove the decision.

Vellucent is built for PDFs where a polished sentence is not enough: policy, procurement, reports, grants, regulations, forms, contracts, technical publications, and records whose facts, defined terms, citations, obligations, and revision history must remain defensible.

Explore document safeguards, workflow, and delivery limits
01
Immutable PDF source

Bind every operation to document identity, revision, page, object, text span, geometry, and uncertainty.

02
Page-aware evidence graph

Reconstruct logical sentences without discarding reading order, headings, tables, forms, annotations, or source anchors.

03
Local semantic proposal

Use exact terms, same-origin MiniLM context, Proof rules, terminology, policy, and bounded grammar candidates to propose—not commit.

04
Meaning and capability gates

Protect names, numbers, dates, money, citations, negation, modality, comparison direction, defined terms, permissions, and lifecycle state.

05
Reviewable derived revision

Preview the operation, require the proper reviewer, verify the result, preserve the original, and issue a replayable receipt.

MISSION VALUE

Controlled language without a cloud-first dependency

Agency terminology, acronyms, form labels, policy clauses, prior decisions, and hard-negative examples can support review inside the controlled application boundary.

SECURITY

Untrusted documents never inherit ambient authority

Workers, WebAssembly, hash-pinned local assets, explicit capabilities, server-side credentials, source-span checks, permission checks, and fail-closed admission reduce the blast radius of malformed content and unsafe output.

SAFETY

Correct, preserve, review, or refuse

Meaning Lock can block a grammatical proposal that changes a protected fact, obligation, certainty, negation, comparison, identifier, quotation, citation, or defined term.

PRIVACY

Keep the private first pass local

Core parsing, retrieval, proof analysis, and proposal handling can remain local or within an agency-controlled deployment. Optional providers receive only an approved passage and declared capability.

AUDITABILITY

Bind the source, proposal, authority, decision, and result

A receipt can retain document and revision hashes, page and object anchors, rule/model identity, evidence, Meaning Lock verdict, policy, reviewer, output hash, and verification result.

RECORD INTEGRITY

The original remains the original

Accepted changes create labeled derived revisions. Structural edits do not pretend that a prior digital signature remains valid, and automatic PDF grammar writes stay disabled until preservation and rollback gates pass together.

ACTIVE

Deterministic Proof Core, JavaScript and C17/WebAssembly Meaning Lock, page-aware source anchors, local proposal receipts, and same-origin MiniLM acquisition/admission architecture.

QUALIFICATION-GATED

The learned 384-dimensional Semantic Bridge, a selected production grammar model, image-only OCR correction, and verified automatic PDF writes remain behind explicit owner, quality, preservation, and recovery gates.