What does the source citation validator produce?
Check exact local file references, PDF page ranges and HTTP or HTTPS citation syntax without contacting external sources.
Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.
What do you need before you start?
- Define the authorized source population and your review rules.
- Keep the unchanged original files and record the snapshot and exclusions.
- Review missing and invalid inputs before preparing the finalized pack.
What information do you enter?
Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.
- Up to 20 local evidence files, 10 MB each and 25 MB total. Files receive stable browser file IDs.
- Document or review reference. Customer-controlled reference.
- Document or review version. Customer-controlled version label.
- Responsible owner. Named customer owner. This does not authenticate authority.
- Preparation date. Your declared calendar date.
- Review scope. State the population, period and purpose. No completeness is inferred.
- Source citation rows. JSON array, at most 200 rows. Exact keys. citationId, fileId, pageStart, pageEnd, locator, url. Use the file IDs displayed below.
| Field | What to enter | Fictional example |
|---|---|---|
| Document or review referenceRequired | Customer-controlled reference. | FICTIONAL-REVIEW-1 |
| Document or review versionRequired | Customer-controlled version label. | fictional-v1 |
| Responsible ownerRequired | Named customer owner. This does not authenticate authority. | Fictional records owner |
| Preparation dateRequired | Your declared calendar date. | 2026-10-08 |
| Review scopeRequired | State the population, period and purpose. No completeness is inferred. | Fictional evidence population. Replace every fact before use. |
| Source citation rowsRequired | JSON array, at most 200 rows. Exact keys. citationId, fileId, pageStart, pageEnd, locator, url. Use the file IDs displayed below. | [{"citationId":"C1","fileId":"f1","pageStart":"","pageEnd":"","locator":"Fictional paragraph 1","url":"https://example.com/source"},{"citationId":"C2","fileId":"f2","pageStart":"","pageEnd":"","locator":"Fictional paragraph 2","url":""}] |
What you can download
Every result must identify its supplied facts, assumptions and unresolved items.
| Free result | Included downloads |
|---|---|
Enter your information, inspect the on-screen result and keep a browser backup. Editing and direct copies of your entered information stay free. |
These supported outputs are free. No checkout is required. |
Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.
How does the source citation validator work?
- 1Select the actual sources
Up to 20 local evidence files, 10 MB each and 25 MB total. Files receive stable browser file IDs.
- 2Freeze the review rules
Resolve exact file IDs. Count actual readable PDF pages locally and check requested inclusive page ranges. Non-PDF page or section locators remain declared by you. Check URL syntax only, never destination availability or source authority.
- 3Inspect complete findings
Review all source-linked results and unresolved items. Free JSON and CSV preserve complete results.
- 4Keep recoverable work
Browser inputs, exact file bytes and retained local event history survive reload. Restore a validated exact-byte workspace backup or explicitly approved private cloud revision. A pre-restore checkpoint and earlier generic work remain separately preserved.
- 5Prepare the finalized pack
Prepare seven core files and the exact selected attachments, then download them free. Review the fictional sample below.
Method and sources
Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.
Common questions
What information does the source citation validator need?
Enter up to 20 local evidence files, 10 MB each and 25 MB total. Files receive stable browser file IDs; document or review reference. Customer-controlled reference; document or review version. Customer-controlled version label; responsible owner. Named customer owner. This does not authenticate authority; preparation date. Your declared calendar date. Define the authorized source population and your review rules.
What does the source citation validator produce?
Seven core files. Formal PDF and Word report, complete Excel index, CSV findings, frozen source/result JSON, delivered-file SHA-256 manifest and instructions. Exact selected local attachments. Disclosure tools include only eligible approved copies or section attachments. Reports retain source filenames, hashes and declared review metadata, which require customer review before disclosure. Complete local result and browser backup. Earlier stored work and purchases remain separate. Review unresolved findings and limitations before use.
Who makes the final decision?
A responsible person reviews the result. Customer facts, source bytes, file metadata, approvals and declared dates stay in this browser. Mechanical findings do not authenticate provenance, approval authority, source correctness, legal applicability, redaction completeness or unrecorded events. No remote source is fetched, file is deleted or external provider is called.
Is this tool free?
Yes. The on-screen result and listed downloads are free. No checkout is required. Keep local backups and review the stated method and limits.
Can I use the source citation validator for this task?
Check referenced files, pages and links. Customer facts, source bytes, file metadata, approvals and declared dates stay in this browser. Mechanical findings do not authenticate provenance, approval authority, source correctness, legal applicability, redaction completeness or unrecorded events. No remote source is fetched, file is deleted or external provider is called.
What still needs review?
Customer facts, source bytes, file metadata, approvals and declared dates stay in this browser. Mechanical findings do not authenticate provenance, approval authority, source correctness, legal applicability, redaction completeness or unrecorded events. No remote source is fetched, file is deleted or external provider is called.
JSON input tables support 200 rows per field and 20000 characters per answer. Complete findings support at most 5000 rows. The formal report displays the first 100 findings, 1000 characters per displayed finding. Confirmed tables and approved section content are rendered completely. Excel/JSON preserve complete accepted values.
PDF page ranges are checked only for readable PDFs. Non-PDF section locators and all external URLs remain unverified. No remote content is requested.
Backup integrity checks support only evidence-control-workspace-v1 archives. Local event history is bounded to 500 recorded events with an explicit retained-chain starting point. No trusted timestamp or external audit authority.