U.S. patent agent practice · Registration No. 82,283
About the practiceResources
LAYNEINTELLECTUAL PROPERTY

Systems / Browser-based utility

Evidence Manifest

Build a reviewable source index. Entries and file bytes stay in your browser; nothing is uploaded by this tool.

Research utilities · v1.3Export your work before leaving this page. A checksum identifies bytes; it does not prove authenticity or a legal conclusion.
Add an evidence source

Your source index (0)

Evidence sources in this manifest
SourceLocatorReview stateChecksumAction

Add your first source or load an illustrative example.

What an export contains

Source identifier, title, type, locator, review state, notes, filename, size, checksum, and capture time. Treat any notes and source details according to your own information-handling obligations.

Return to the evidence

Verify a saved manifest

Open a JSON export from this utility, choose the corresponding local files, and compare their sizes and SHA-256 checksums. Resolve duplicate filenames explicitly. No files or source URLs are uploaded or fetched.

Compare manifest files

Choose a version 1 manifest with up to 200 sources.

Manifest file comparison
Recorded sourceSelected local fileComparison result

A match confirms the recorded bytes. It does not authenticate the source or provide a trusted timestamp. Your original capture dates and manual review states remain unchanged. The comparison report is a separate download.

Prepare your source list

Clean a URL list

Extract HTTP(S) links from pasted text, normalize hosts and default ports, remove fragments and exact duplicates, and preserve query strings. Review the output before using it; links are never visited.

Clean pasted URLs

Up to 500 candidate URLs. Embedded username/password URLs are excluded.

Keep the source. Prepare a readable copy.

Convert local HTML to text or Markdown

Choose a saved UTF-8 HTML file or paste its source. This utility reads the markup as text, removes active content, and prepares a basic text or Markdown projection. It does not open a webpage, fetch links, load images, or upload your input.

Convert HTML locally

Supports explicitly closed basic HTML. Unsaved inputs remain only in this page.

Supported content and conversion limits

Headings, paragraphs, lists, blockquotes, links, emphasis, and code are supported. This is a lossy basic-HTML conversion. Correct missing or mismatched closing tags before converting. CSS layout and visibility are not evaluated; CSS-only hidden text can remain. Tables flatten and require review. Unsupported entities, numbering, and wrappers receive warnings. JavaScript, styles, frames, forms, and active containers are omitted. No output is rendered as HTML or Markdown here.

Maximum input: 1 MiB. Each derived output: 2 MiB. Processing also has bounded nodes, depth, steps, and tag sizes. File receipts cover the exact chosen bytes; pasted receipts cover the pasted text encoded as UTF-8. A checksum establishes matching bytes, without establishing authorship or a trusted capture time.

Reference review / Local processing

Citation & identifier workbench

Review a reference-manager export, compare explicit identifiers, and keep source disagreements visible. Files and pasted text stay in this page’s memory. The tool does not look up references, verify publications, or merge records.

Review citation metadata locally

Limits: 1 MiB of UTF-8 input; 200 records; 10,000 characters per text field; 100 authors; 256 observations per record; 64 distinct variants per field and 64 possible RIS page combinations; 20,000 JSON values; BibTeX nesting depth 32. Oversized or unsupported structures are rejected.

Choose a format and review local text or a file.

Supported subset and a worked example

RIS needs explicit TY/ER record boundaries and keeps author names literal. Its ambiguous SN field is preserved without guessing ISBN versus ISSN. CSL JSON preserves supported structured names and date precision; duplicate object keys are rejected. BibTeX accepts article, book, and misc entries with balanced fields. Macros, concatenation, inherited crossrefs, duplicate fields, and preambles are rejected; TeX text is never evaluated.

The worked example contains two synthetic sources with the same DOI spelling under conservative comparison, but different titles and years. Keep both sources separate, build the exports, and compare the warnings and source mapping. The example does not refer to a verified real publication.

To connect this review to the Evidence Manifest, add the original bibliography, a selected projection, and the review JSON as three separate local file sources. Record which source observations support a statement, preserve the originals, and use the checksum verifier for a later comparison.

For an actual research question, export the manifest and use Verify a saved manifest to compare the local copies you plan to cite. Keep unresolved title, date, identifier, and passage questions in your notes. A matched file and a reviewed citation do not determine what a reference discloses. Prior-art research can develop the search and a comparison supported by the sources. Start with a nonconfidential inquiry; agree the engagement and an appropriate exchange method before sharing detailed invention or client materials.

Compare an explicit identifier

No identifier has been processed.

DOI comparison folds Basic Latin case only. Exact doi.org/dx.doi.org paths are decoded once; ambiguous URL queries or fragments are rejected. Patent publication kind codes and application namespaces remain distinct. This comparison does not establish a publication’s existence, status, or ownership.

Search Layne IP