Provenance
Inspection

LINEAGE reads a document and reports what it already says about its own origin. Read-only. Nothing is uploaded, nothing is stored, nothing in your file is changed.

ContextWhy this exists

NAVMC 5239.1 puts the labelling duty on you, not on a tool. Labelling a document honestly means knowing what it already declares about its own origin, and none of that is visible in Word, in Acrobat, or in a photo viewer.

The full reasoning

The problem

Paragraph 4.b.(5) requires a label on any document created, in whole or in part, with output from a generative AI tool. Paragraph 4.b.(4) puts responsibility for the product on the person who used one.
Documents carry origin data in structures no ordinary application surfaces. EXIF and XMP in images, C2PA content credentials, Office document properties, tracked changes and comment authors, PDF information dictionaries, and invisible characters sitting inside plain text.
Uploading a document to an online metadata reader to find out what is in it is the wrong trade for anything heading to a record folder.

What this does about it

Reads the file inside this browser tab, on this machine. No upload, no network request, no stored state. The input is re-hashed after the parse and compared to the digest taken at load, so the read-only claim is demonstrated rather than asserted.
Reports what the document declares, next to a named list of everything the parse was unable to read.
Formats the annotation from your inputs and anchors the whole inspection to a SHA-256 of the file.

What it refuses to do

Decide whether AI wrote a passage. No metadata field records it. A tool inferring it would manufacture the very assertion the annotation exists to make. Contribution scope, portion affected, reviewer, and the accuracy confirmation stay yours, and the attestation records that they came from you.
Report a quiet result as a clean one. Zero findings with zero limits means clean. Zero findings with limits recorded means unknown. Unread is not the same as absent, and both the interface and the attestation say which one you got.
Vouch for a content credential. A C2PA manifest is reported as present and never validated, and the attestation states so. A signed manifest is also a provenance signal rather than an AI signal, because Leica, Nikon, Sony, and Canon sign ordinary camera captures with one.

Module 1Inspect

Select a file. It is read into memory in this browser tab, parsed, and discarded when the tab closes. No network request is made at any point.

Drop a file here

Or choose one. Supported for parsing: JPEG, PNG, Word, Excel, PowerPoint, PDF, plain text and markdown.

Module 2Label

This module asserts nothing about AI involvement on its own. It fills what the document declares about itself, names the source of every filled value, and leaves the human judgments empty. It formats a generative AI use annotation under NAVMC 5239.1 of 4 Dec 24, paragraph 4.b.(5).

Read from the file

LINEAGE filled these from data the document carries about itself. Each field names its source. Change any value and the source note switches to operator entered, and the attestation records the change.

Document title or subject line

Document date

Review date

GenAI tool and version used

Only you can supply this 4 fields

LINEAGE has no basis for any of the following. Contribution scope and portion affected are judgments about your own work, not properties of the file. Section 0.3 forbids this tool from deciding whether a passage was written by AI, so it does not guess here.

Contribution scope

Not derivable. LINEAGE never infers AI involvement from file contents.

Portion affected

Not derivable. No metadata field records which passages a tool touched.

Human reviewer, rank and name

Not derivable. An author field names who edited the file, not who reviewed the output.

Operator running this inspection

Not derivable and not verified. Recorded in the attestation as self-asserted.

I confirm the outputs were reviewed for accuracy and suitability prior to use, per NAVMC 5239.1 paragraph 4.b.(4). This is a human act. LINEAGE cannot check it and will not pre-check it.

AuthorityReferences

Paragraph text below is summarised rather than quoted. Confirm every citation against the source document before it goes into anything signed.

NAVMC 5239.1, United States Marine Corps Guidance on Generative Artificial Intelligence, 4 December 2024: 4.a.(2)Users are able to readily determine which systems rely on generative AI, and to accept or reject the output.; 4.a.(7)Provide transparency and explainability for model outputs as required, including data lineage, documentation on model training data, and specification of which components leverage generative AI.; 4.b.(4)Users are responsible for products and decisions made with the assistance of generative AI, and should distrust and verify all outputs prior to use. Module 2 will not pre-check the confirmation of this on your behalf.; 4.b.(5)Users label any document created, in whole or in part, with outputs from generative AI tools. This is the requirement Module 2 formats.
MARADMIN 635/24, Guiding Principles for the Ethical Use of Artificial Intelligence by Communication Strategy and Operations, R 301807Z DEC 24, released 30 December 2024: AnnotationQuoted, because the exact wording is the operative requirement. Products adjusted with AI will annotate that adjustment in both caption and metadata, for example basic correction of color done with AI. The duty reaches metadata, not the caption alone, which is the part LINEAGE reads.; Cite 635/24MARADMIN 602/24 carried the identical title and is marked cancelled at its source. The cancellation carries date-time group R 301748Z DEC 24, nineteen minutes before 635/24 was released. Note that 635/24 declares no supersession of its own, so the reissue relationship rests on the identical title, the nineteen-minute gap, and the carried-forward text rather than on any statement inside the message.; CautionThe cancellation message displays under the identifier MARADMIN 028/24 while carrying a December date-time group, an inconsistency in the source page itself. Confirm the number against the official MARADMIN index before putting it in a signed document.

LINEAGE contains no model, performs no inference, and holds no training data. It is a deterministic byte parser. The position taken here is that the AI tool tracking requirement in paragraph 4.c.(6) does not attach to a tool containing no model, and that determination rests with your command rather than with this page.