At a glance
| Input | Current action | Output | Boundary |
|---|---|---|---|
| .pdf and application/pdf | Validate the exact allow-listed pair | Accepted PDF input | A mismatched extension or MIME type is rejected. |
| PDF source bytes | Check the opening %PDF-x.y and trailing %%EOF marker | pdfVersion and parsedByteLength | This is an outer-structure check, not full PDF validation. |
| Parsed result | Record semanticContentStatus: not_checked and unavailable extracted text | Explicit content boundary | No PDF text, page count, layout, image, table, form, attachment, or signature meaning is extracted. |
| Source bytes | Calculate SHA-256 and append a content-addressed frozen-content object | Immutable content object and revision reference | SQL evidence stores hashes and the Object Store key, not raw bytes. |
| Approved term catalog | Receive no extracted PDF text | Zero content-derived usage observations | No OCR or term matching runs on PDF content. |
| Retention class and Retention until | Validate an allowed class and future timestamp | Upload admission | The artifact persists the class. The current upload runtime does not persist the selected date. |
| File up to 350 KiB | Send one direct resolver request | Persisted or duplicate result | Base64 transport remains bounded below Forge request limits. |
| File above 350 KiB and up to 25 MiB | Stage verified 256 KiB chunks | Final persisted object after assembly and whole-file hash verification | Chunk cleanup is attempted and reported after finalization. Maximum: 100 chunks. |
How it works
- Open Enterprise evidence workspace.
- Find Upload controlled evidence.
- Under Evidence file, select the PDF file.
- Select a Retention class.
- Set Retention until.
- Select Upload evidence.
- Review the returned Artifact and Revision. Expect Usages: 0 for PDF content.
- Record the approved retention date in another controlled system until durable date persistence is implemented.
Example
A team uploads Audit-report.pdf. Its bytes begin with %PDF-1.7 and end with %%EOF. The app stores the bytes in Object Store. It records the version, byte length, hash, provenance, object reference, and immutable revision. Visible terms do not become usage evidence because PDF text is not extracted.
What this does not mean
PDF ingestion provides structure metadata and byte integrity only. It does not establish that the PDF is complete, readable, authentic, signed, or legally valid. It does not assess meaning or certify claims. The retention date is required for admission but is not durably attached to current evidence records. Use a supported text format when content-level terminology evidence is required.
Related questions
Next step
Upload a PDF when structure metadata, byte integrity, and provenance are sufficient. Use text evidence for terminology checks.
View on Atlassian Marketplace