HISTORICAL DIG · JUL—AUG 2026
Can fake data test a sensitive-form tool?
Visa, government, and identity PDFs can look like a few fields, while the real risk is spread across the official entry point, answer storage, network requests, PDF field mapping, and what remains after clearing.
HOW IT RELATES TO WORKFLOW 001
Relation to the current subject
It inspects the path of sensitive input—it does not decide whether you should file.
This historical record shares one principle with the redaction Dig: understand input, storage, network, output, and clearing before sensitive material enters a workflow. The redaction record inspects an existing file; this one asks whether a fictional sample can expose the path before real answers ever reach a form tool.
Record state at the time
- Privacy & documents
- Reversible pre-adoption checks
- Standard record
- Developing
- Historical E3 · one maker-prefilled demo run · no real data or filing outcome
THE GUIDANCE AT THE TIME
Judgment at the time
Use a dummy run to see where answers go. Do not make your passport the test case.
Open full rationale and return rules
Use a dummy run to see where answers go. Do not make your passport the test case. Anchor the check in the current official form and instructions, use only a maker-prefilled fictional demo, and inspect route-specific storage, requests, generated PDF, field mapping, and clearing. If any step remains unclear, stop before real data.
- Who it was for
- People evaluating a visa, government, or other sensitive-form tool who want to understand the data path and output before trusting it
- Why it mattered then
Open note
Once a real name, address, document number, or identity history reaches the wrong route, a shared device, a collaboration service, or a mis-mapped file, the cost is much higher than redoing an ordinary form.
- Where the judgment stops
Open note
The historical E3 applies only to one August 11, 2026 browser run of a maker-prefilled demo: no personal data was entered, no form was filed, and no government acceptance, legal fit, or real service was tested. The current official USCIS G-1145 still shows 09/26/14, so that date alone does not establish that the file is stale. Structural differences between the earlier demo PDF and the current official PDF also do not establish correct or incorrect field mapping. Fillvisa's local-processing description is scoped to the routes it explicitly describes; Plus collaboration and document collection under the same brand cannot be generalized as entirely local.
CHECK BEFORE READING ON
Fit check
Continue only when the official source is available, a fictional demo runs independently, and the clearing boundary is understandable.
This record may help
- The maker provides a public, prefilled fictional demo that requires no sign-in and lets you observe the full flow without touching real data.
- You can obtain the form and instructions from the current official entry and compare fields and values in the generated file item by item.
Do not use it yet when
- The first check requires a real name, document number, account, uploaded file, or professional collaboration.
- The official version, field meaning, generated-PDF mapping, or clearing scope cannot be confirmed.
- You need legal advice, a filing guarantee, an acceptance outcome, or an eligibility judgment for an individual case.
HISTORICAL TRIAL · UNFROZEN, NO REAL CASE
Historical trial
Use ten minutes for one fictional preflight and place the stop line before real data.
- Time needed
- About 10 minutes (earlier trial cap)
- Likely cost
- Use only the public prefilled demo; buy no service and enter no real case workflow
- Permission boundary
- No sign-in, upload, real name, address, document number, or account
- 01
First step
Open this step
Get the current form and instructions from the official page. Run one maker-prefilled fictional sample and record the exact route, browser storage, network requests, generated file, and before-and-after clearing state.
- 02
What should exist
Open this step
A checklist covering official source, exact route, storage, requests, output, and clearing, plus a sample PDF containing fictional data only.
- 03
How to tell it worked
Open this step
The generated file opens, critical fictional values appear in the intended fields, every external request and local-storage item has an understood purpose, and a second check after clearing finds no remaining sample content.
- 04
Stop when
Open this step
Stop if the route becomes an upload, collaboration, or account flow; the official and generated files cannot be compared item by item; the device, backups, or clearing scope are uncontrolled; or the question becomes a legal judgment.
- 05
How to back out
Open this step
Delete the sample PDF and download record, clear site data for that route, and close related tabs. Restart any real filing from the official source.
BITSHOVEL R4 EXPLAINER · NOT A PRODUCT INTERFACE
Method and interfaces
Start from the official source, pass through a fictional demo and path check, then stop before real data.
Open method boundary
The diagram is not an operation result. It is an inspection order: official entry, prefilled fake data, storage and requests, PDF mapping, and clearing. If any step remains unclear, do not continue to real filing.
This diagram separates one reversible preflight into five steps. The red stop line is not permission to file; it keeps real data out until version, route, requests, mapping, and clearing are understood.
About this image and its source
BitShovel R4 explainer created August 15, 2026 from the current official USCIS G-1145 entry and public maker technical, privacy, and demo pages. It is not a USCIS or Fillvisa interface, result, legal opinion, or endorsement.
Open source page ↗SOURCES AND EVIDENCE
Sources and evidence
As of August 15, 2026, one earlier demo record, three current maker pages, and one official form define what to inspect—not that real data is safe or a filing will be accepted.
Open evidence boundary
One earlier demo run records the browser validation, sample-PDF generation, and request-observation process at the time. Current maker pages and the official USCIS source clarify today's routes and scope. They do not establish safety for real data, complete field mapping, filing acceptance, or that the tool should be adopted.
- 01Current maker guidance · Rechecked
Fillvisa technical note: browser generation and local storage
Open source boundary
The maker describes localStorage and pdf-lib for browser-side generation. This is a maker description of a specific implementation, not a BitShovel security audit.
Open original source ↗ - 02Current maker guidance · Rechecked
Fillvisa privacy page: local-processing claim
Open source boundary
The maker says the specific browser tool does not upload answers. The page cannot replace a fresh inspection of the current route, requests, storage, and clearing behavior.
Open original source ↗ - 03Historical run target · Rechecked
Fillvisa maker-prefilled demo
Open source boundary
The earlier E3 used the maker-prefilled fictional sample. This review only confirms that the entry still exists; it was not rerun and is not presented as a real filing outcome.
Open original source ↗ - 04Current official source · Rechecked
Official USCIS G-1145 page and current PDF
Open source boundary
The current official PDF still shows 09/26/14, so the footer date alone cannot establish staleness. Any real use must restart from the official form and instructions.
Open original source ↗ - 05Scope change · Rechecked
Fillvisa Plus: the same brand also has collaboration and document-collection flows
Open source boundary
This is why a local-processing claim must stay attached to a specific product and route rather than being generalized across every service under the brand.
Open original source ↗
REVISION RECORD
Revision record
Revision 4 withdraws the date inference and scopes local processing to an exact route.
Open 3 revisions
- Revision 2
Replaced a free-autofill pitch with a reversible pre-adoption trial using fictional data only.
- Revision 3
Added one browser-validation, request-observation, and sample-PDF record from the maker-prefilled demo, still without real data, filing, or acceptance outcome.
- Revision 4
Rechecked the current official file and product scope: withdrew the inference that 09/26/14 alone established staleness, limited local-processing claims to a specific route, and replaced old product screenshots with unclear reuse rights with a BitShovel explainer.
- What the record said before
- The demo file's footer date differed from the current version, so the route should be stopped.
- What changed
- The current official G-1145 still shows the same footer date. The checks that matter are the official entry, file structure, field-by-field mapping, requests, storage, and clearing; the date cannot stand in for them.
WHAT THIS RECORD LEAVES
What this record leaves
A reversible dummy-data preflight only exposes risk before real material arrives.
If a generated file will later be sent, it needs a separate redaction and disclosure check. If the question becomes one of eligibility, form choice, or legal judgment, return to official guidance or a qualified professional.
Back to the Dig index