Credibility
Operational credibility
Operational signals only: database counts, tool listing stats, one workflow walkthrough, conceptual layout diagrams, and the public vs verified split. Mission and story: About. Legal defaults: Disclaimers.
How to read this page: counts refresh on each load. Verified members use the same approved=true query as the homepage proof strip. Listing numbers are derived from lib/modules/armory/data.ts — the same statuses you see on /tools.
Do not over-read “available”: it is a listing status, not a promise of a public download. Each tool page states distribution; many listings still have no installer or hosted runner linked from the site.
Public tool counts and verified members
3
Tools listed as available
Same status badges as /tools
2
Listed as in development
May be compute-limited or partial when runnable
3
Listed as coming soon
Roadmap-only listings
8
Total tool listings
Includes pipeline entries, not only shippable binaries
0
Verified members
Users with approved=true in our database
Built from live cases
Several listed tools were iterated against real discovery volume: PDF and message exports that did not match sworn statements, timelines that had to hold up under review, and document metadata that either supported or contradicted claimed origins.
That history does not grant every visitor the same run path today. Listings describe what we ship or intend to ship; some builds stay private, local-only, or verified-gated. This page separates what you can read without an account from what still needs access.
Nora's Law names the public tools layer — a framework and platform, not a statute and not a law firm.
Case-based workflow: checking a document’s digital story
- Party receives a PDF that is supposed to come from an institution (lab, agency, school system).
- They retain the original digital file (not a photo of a printout) and run Document Forensics-style metadata extraction.
- Report shows producer software, author fields, and creation/modification timestamps next to what was claimed in discovery or testimony.
- They hand the report to counsel for authentication strategy; admissibility and next steps are legal decisions, not tool output.
Illustrative metadata excerpt (not from a live case)
File: institution-report-2024.pdf Producer: consumer PDF toolchain / desktop author Created: 2024-02-10 14:22 UTC | Modified: 2024-02-11 09:05 UTC Flag for review: author field inconsistent with stated institutional origin
Full runbook: Document Forensics listing →
Screenshots and visual outputs
Live UI captures are not published here. The diagrams below are conceptual layouts — they illustrate how outputs are structured, not recordings of running software.
What is public vs what requires verification
- The Tools page, /start, /guide, and this proof page — readable without an account.
- Tool detail pages state access mode (public, compute-limited, verified) and distribution honesty (e.g. no public installer linked yet).
- Homepage proof strip: same tool listing counts and verified-member total as the cards below; gift totals are completed donations in our database with a calendar-month reset.
- Approved accounts (`approved` in our user table) for collaboration flows where identity and abuse risk matter.
- Some runs (research, sensitive uploads) may require verification or higher limits — see each tool page and Community.
What remains in development
Snapshot: 3 listed available · 2 in development · 3 coming soon · 8 total listings (same rows as /tools).
Names match the Tools listings. “Available” is a status label, not a guarantee of a public binary — read each tool's distribution note before assuming you can run it tonight.
Available (listed)
- Evidence Organizer
- Timeline Builder
- Document Forensics
In development
- Research Agent
- Filing Builder
Coming soon
- Communication Analyzer
- Metadata Batch Scanner
- Discovery Tracker
Public tools require public support. Fund Public Access →