INTELLIGENCE WORKSPACE · V1.9

Dashboard

Manage credit reporting investigations with evidence-first workflows.

FCRA WAR ROOM · V2.0 / INVESTIGATION OPERATIONS

Investigate the facts.
Challenge the errors.

A guided, evidence-first command center for personal and enterprise credit reporting investigations. Start with a profile, connect a tradeline, build a case, and review the dispute before sending.

HUMAN APPROVAL REQUIRED

Mission Control · Guided actions

01
Identify the consumerFirst name · middle initial · last name · authorization
02
Verify reporting fieldsLink the bureau, creditor, balance, status and supporting report
03
Build the investigationIdentify exact errors and missing evidence
04
Prepare a defensible disputeReview a draft before sending it yourself

Operations snapshot

🔒 Security status: Local legacy records are not encrypted. Cloud modules require configuration and independent access-control testing. Do not enter unredacted SSNs, complete account numbers, or sensitive client documents into local storage.

Quick Launch

Consumer rights intelligence / Private & Enterprise

Investigate. Document. Challenge.

Cross-examine reporting inconsistencies, assemble evidence-backed cases, and prepare disputes with precision. No manufactured allegations. No automatic submissions.

● LOCAL WORKSPACE● HUMAN-APPROVED DISPUTES● AUDIT-READY CASES
NEW IN v1.5 / DOCUMENT INTELLIGENCE

From source document to investigation.

Extract locally, scan for review candidates, and verify the facts before opening disputes. A smarter workflow without invented violations.

Case activity

System safeguards

✓ Separate personal and enterprise workspaces

✓ Client authorization tracking

✓ Evidence-based dispute templates

✓ Local backup and restore

⚠ No automated sending or unverified legal allegations

Forensic radar

Clients & profiles

Tradeline registry

Dispute case management

Evidence vault

Evidence metadata and notes are saved locally. For safety and browser storage limits, v1.0 does not store uploaded document contents. Keep originals securely outside this app.

Dispute document studio

Select a case and generate a letter. Verify all facts before sending.

Investigation tracking

Calendar-day estimates based on bureau receipt date. Actual statutory extensions and notice periods depend on the facts.

Report Intake Lab

CSV / TSV / JSON / Text
Local report import parses structured text records only. PDF extraction, OCR, direct bureau connections, and automated legal conclusions are not implemented. Review all imported data before creating cases. Do not upload reports containing SSNs or full account numbers.

Guided report intake & accuracy review

Paste structured CSV rows, inspect potential duplicates and missing fields, and selectively import verified entries.

LOCAL RULES · NO AI CONNECTION

Import safeguards

✓ Field-by-field validation

✓ Existing-record duplicate detection

✓ Per-row review and selection

✓ Suspicious date and balance checks

✓ Explicit confirmation before saving

⚠ Report discrepancies are not proven FCRA violations

Paste a CSV or TSV export to begin. Avoid SSNs, full account numbers, and unredacted reports.

Import structured tradelines

Columns: creditor, last4, bureau, status, balance, delinquency, notes. CSV/TSV headers required. JSON: array of account objects or {accounts:[...]}. Text: comma-separated header + rows.

Nothing selected.

Manual forensic intake

Have a report you can't export as structured text? Add each tradeline manually, then compare bureau versions in the Forensic Lab.

Supported format example

creditor,last4,bureau,status,balance,delinquency,notes
Example Bank,1234,Equifax,Closed,0,2022-01-01,Verify against statement

Imported records remain in browser localStorage and are not encrypted.

Cross-Bureau Forensic Lab

RULE-BASED ANALYSIS
Flags identify differences and review opportunities—not confirmed violations. Differences may be legitimate due to reporting dates, account updates, or bureau-specific formatting.

Account investigation

SOURCE-FIRST INVESTIGATION

Document Intelligence Studio

Extract text from a local PDF or TXT file, inspect the source, then explicitly select what to investigate.

LOCAL REVIEW · NO AI API
PDF text extraction requires a browser connection to load the PDF.js reader library. The selected PDF is processed in your browser; this app does not upload the file. Scanned/image-only PDFs require OCR, which is not included. Never assume extracted text is correct.

01 / Capture source

No document selected.

02 / Investigation candidates

Local pattern matching highlights possible account details. It does not determine account ownership, accuracy, or legal violations.

Extract text and run the scan to see review candidates.

03 / Analyst handoff

For a real case, confirm the facts against the source, then use guided intake to create a tradeline or dispute. No automatic case creation from uncertain text.

V1.6 • SECURE FOUNDATION

Cloud Operations & Evidence Vault

Separate Supabase-backed workspace. Existing local records are NOT automatically uploaded. Never paste a service-role key here. Deploy over HTTPS, configure the SQL migration, and verify RLS before using real client data.

01 / Connect securely

Not connected

02 / Private workspaces

New users receive a private personal workspace automatically. Enterprise access is granted only through server-side membership policies; changing the dropdown cannot grant permissions.

Cloud records

Sign in to view records.

03 / Cloud case entry

The server verifies membership and only permits approved case fields.

04 / Protected evidence files

Private Supabase Storage bucket; access checked by storage policies. Evidence file access is authenticated and time-limited.

Cloud safety and migration

Local v1.5 records stay in their original browser storage. Cloud cases are created separately to prevent accidental disclosure. Migration requires an explicit, reviewed import in a later build.

Set up Supabase using the included migration and deployment guide before connecting.

V1.7 • UNIFIED CLIENT INTELLIGENCE

Cloud Client & Tradeline Registry

Cloud records are separated by authorized workspace. Sign in through Cloud Operations first. Import is preview-only until you explicitly approve individual records. Legacy local data remains unchanged.

01 / Guided cloud client intake

For enterprise workspaces, a self-declared status does not substitute for written authorization. No SSN is requested.

Sign in and select a cloud workspace.

02 / Cloud clients

No cloud records loaded.

New cloud tradeline

03 / Legacy-to-cloud migration preview

Review a local JSON backup before uploading. This preview supports profiles and tradelines only, never disputes, documents, passwords, or evidence files. Select an authorized cloud workspace and approve each import.

Profiles imported with authorization state not recorded. Tradelines are not automatically migrated: inspect and enter them through the cloud form after confirming account ownership.

V2.1 / AUTHENTICATED CLOUD INTELLIGENCE

Secure Intelligence Operations

Workspace-scoped case review, source-grounded AI recommendations and an explicit human approval gate. Requires configured Supabase and deployed Edge Function.

01 / Cloud case selector

Sign in through Cloud Operations first. This selector only displays cases visible through your Supabase access policies.

Not connected

No AI request has been made.

02 / Security boundaries

Only case title and issue text are sent to the configured AI provider. Client names, account numbers, evidence files, and full credit reports are not included. Do not put those identifiers in the case title or issue.

Every request requires a signed-in session, workspace membership, explicit consent, and server-side authorization.

AI results are suggestions, not verified legal conclusions. Review before using a draft.

For production: review privacy agreements, retention, breach response, audit logging, CROA/state compliance and provider data-handling terms.

03 / Intelligence findings

Select an authorized case and request analysis.
V2.3 / CLOUD CASEWORK

One client. One connected investigation.

Workspace-scoped clients, tradelines, cases, and evidence. Every link is validated by the database. Local records remain separate until individually reviewed.

CLOUD PILOT · Run migration 004 in a disposable Supabase project after migrations 001–003. Never upload sensitive records before access-control testing.

Sign in through Cloud Operations to begin.

01 / Choose a cloud client

Authorization must be independently verified before acting for an enterprise client.

Linked tradelines

Select a client.

02 / Create linked case

No automatic allegation, dispute, or legal conclusion is created.

03 / Connected casework & evidence

Case record

Choose a case.

Evidence inventory

Choose a case.

Upload actual files in Cloud Operations. This view references only evidence metadata and does not download files automatically.

04 / Cloud consistency checkpoint

Refresh to verify case links, authorization flags, and evidence relationships.

Data & privacy controls

Data stays in this browser's localStorage. It is not encrypted and does not synchronize between devices. Do not store SSNs, full account numbers, identity documents, or sensitive medical information.

Backups are unencrypted JSON. Store them only in a secure location. Importing a backup replaces current local data.

Legal and product boundaries

Not a law firm, legal advice, credit bureau interface, or guaranteed credit-score improvement service. Verify all legal conclusions. Enterprise use with paying clients requires independent CROA, state-law, privacy, contract, and fee-compliance review before launch.

V1.8 / FORENSIC CASE INTELLIGENCE

Case dossiers. Evidence before allegations.

Investigate documented discrepancies, prioritize review, and prepare defensible dispute drafts. Rule-based intelligence; no AI service is connected.

Investigation selector

HUMAN REVIEW REQUIRED

The analysis uses local case, account, and evidence metadata. It does not read external evidence files or determine whether a legal violation occurred.

Select a case and run the evidence review.

Investigation timeline

Select a case to inspect its milestones.
V1.9 / INVESTIGATION COPILOT

Draft with evidence. Escalate with precision.

Generate factual dispute drafts locally or connect a secure, owner-managed AI proxy. No auto-submission or unsupported legal conclusions.

01 / Select investigation

Review account details and evidence in Case Intelligence before drafting. No credit report or evidence file is transmitted by the local template generator.

02 / Optional secure AI connection

Not connected by default. Do not use a raw OpenAI API key in the browser. Configure a separately deployed authenticated proxy with strict access controls, data minimization, and audit logging.

AI not connected. Local draft mode is ready.

Choose a case to prepare an evidence-grounded dispute.
V2.2 / UNIFIED CLOUD OPERATIONS

Security & synchronization control room

Inspect workspace-scoped cloud records, authorization status and server-generated audit events. This is not an automatic migration or full sync engine.

TEST ENVIRONMENT FIRST. Apply migration 003 after 001 and 002. Keep client data out of local modules; cloud permission checks require live verification.

Sign in through Cloud Operations before loading.

Data integrity & migration readiness

No cloud data loaded.

The earlier selective profile import remains available in Cloud Registry. Never import without authorization and review.

Read-only audit timeline

Apply migration 003 and refresh.

New record