A personal project. A traceable reference.

Federal Judicial Process is a personal research and engineering project by Jason93. It makes a structured federal criminal-process knowledge system browsable: procedural modules, atomic claims, authority records, conditional process relationships, circuit overlays, and district court source locations.

It is not a law firm, a government service, a court filing tool, an outcome predictor, or legal representation. No affiliation with a court or government body is claimed. Do not rely on this reference to calculate a filing deadline or choose a remedy without checking the actual record and current governing authority.

What the dates mean

Each module and authority page shows two dates, and each one means only what it says.

Legal review is the date the record's statements were last checked against their sources. It changes only when a reviewer re-checks the record. It never moves because a build ran or a link opened.

Links checked is the date an automated run last requested every recorded source URL. "Opened" means the server returned the page in full. It shows that the link works on that day. It does not show that the text or the law is unchanged, and it does not replace a citator check of later history and treatment. The run and its evidence are recorded in data/link_check.json.

The inherited research baseline is August 26, 2026. Individual claims and records retain their own verification dates and qualifications. A label such as verified_current is the original research classification as of its recorded date; it is not a representation that publication or a successful website build freshly verified the law.

This publication preparation does not perform a new proposition-level legal review, a full subsequent-treatment search, or district-rule semantic review. The original archive records 1,080 claims, including three partially verified and four historical claims. Those distinctions remain in the records.

Uncertainty is public

The public register retains 468 unresolved items: 369 inherited legacy formulations, five circuit/posture comparisons, and 94 district-rule text reviews. None of the unverified legacy formulations is adopted as canonical law. Discovery of a court's rules page does not establish the current legal effect of every linked document.

The court catalog covers 94 district-level courts and 1,466 source entries recorded during the baseline work; it is not a guarantee that every rule, amendment, judge-specific practice or newly issued order has been discovered. Nine catalog entries carried technical fetch limitations at that time. Check the live issuing court before use.

Publication boundary and provenance

Canonical modules, claims and authority records were imported without changing their legal text. Original migration evidence, company-specific materials, local-machine paths, raw execution logs and historical repository internals remain in a separate private archive.

Original legacy filenames in the public uncertainty register are represented by stable private-source IDs. Six company-specific legacy text fields are explicitly withheld, with hashes of the original wording; they are not rewritten or attributed to this personal project. Their issue IDs, not-verified status, review dependencies and replacement-module routing remain visible.

Some preserved module prose refers to the private coverage matrix or historical workflow statuses. The public uncertainty register and coverage summary explain the final inventory. A disposition records what happened to an item; it does not turn an unsupported proposition into verified law.

Updates require review

Automated checks may identify changed source bytes, access failures and overdue review dates. Those checks do not determine legal effect. A reviewer must inspect the actual authority, jurisdiction, posture, dates and affected claims before changing canonical content. Publication follows validation of an approved release. No unattended legal promotion is enabled.

Engineering and portability

Small canonical source files control the generated site, master compilation, structured downloads and process explorer. The public build can run independently of the private archive. Each release has a content identity and file hashes. The personal site consumes a validated static release, not the working research directory.

The visual process explorer is a navigation aid over recorded conditional relationships. The court directory is a source map, not a geographic boundary map or a venue determination. Plain-language navigation labels do not replace the source-backed qualifications within modules.

Corrections

Report a suspected issue through the repository with the page or stable claim ID, the specific statement, jurisdiction and procedural posture, and a primary source if available. Do not include confidential records or sensitive personal information in public issues. Corrections must preserve traceability and cannot silently change historical verification dates.

License

The content and data of the Federal Judicial Process reference are licensed under CC BY 4.0 (see LICENSE-CONTENT.md). The code is licensed under the MIT License (see LICENSE).

Anyone may use, share and adapt the reference, including commercially, with credit to "Federal Judicial Process by Jason93" and a link to the license. Statutes, rules, court opinions and other U.S. government works are in the public domain and are not covered by these licenses. Third-party material keeps its own terms.

Contributions are accepted under the same licenses.

This reference is general legal information, not legal advice, and is provided without warranty.