where-is-my-lego-archive

name	where-is-my-lego-archive
description	Use when querying, citing, or contributing to the where-is-my-lego research archive (the Bricks & Minifigs / "Reckless Ben" LEGO dispute) — answering questions from its records, or adding/editing events, parties, sources, or graph data and opening a pull request.

where-is-my-lego archive

Overview

This repository is a research archive of the Bricks & Minifigs (BAM) / "Reckless Ben" Schneider LEGO dispute. It is organized Markdown, not an app you run.

Core principle: Every claim is attributed to a public source and labeled CONFIRMED or ALLEGATION; no private personal information appears; and the root .md files are the single source of truth. The full policy lives in DISCLAIMER.md — this skill is the operational summary.

When to use

• Answering a question about the case from these records.
• Adding or correcting an event, party, source, or relationship-graph entry.
• Opening a pull request against this repo (you do not need to clone it — see CONTRIBUTING.md).

Where things live (source-of-truth map)

Path	Edit?	Holds
README.md	✅ canonical	Overview, index, one-paragraph summary
timeline.md	✅ canonical	Chronological events table
parties.md	✅ canonical	People/entities and their public roles
relationships.md	✅ canonical	Graph nodes/edges for the /parties graph — special format, documented in its top <!-- --> header
police-controversy.md	✅ canonical	Arrests, search warrant, AFPD controversy
lawsuit/README.md, lawsuit/court-documents.md	✅ canonical	Legal summary; where to obtain filings
media/news-articles.md, media/primary-sources.md	✅ canonical	Source catalogs (cite from here)
DISCLAIMER.md	✅ canonical	Scope, methodology, PII policy, corrections policy
web/	⚠️ app code	Next.js site that renders the archive
web/.generated/	❌ never	Build output, regenerated by npm run derive. Editing it does nothing — change the root .md instead

The four non-negotiable rules

1. Cite every claim. Each event/role/fact ties to a public source cataloged under media/. No source → don't add it. Never fabricate a citation. If you lack the URL, leave a clear source pending marker and ask for it. Prefer primary records (court filings, full agency statements, full original videos) over aggregator summaries (DISCLAIMER.md → Corrections).
2. Label CONFIRMED vs ALLEGATION. Every new claim gets one. Anything contested by a party is an ALLEGATION, not a fact. Source conflicts are flagged inline with a ⚠ note. When answering questions, carry the label and any ⚠ caveat into your answer — do not flatten a flagged nuance into a flat fact, and do not resolve a flagged conflict yourself.
3. No PII / no doxxing — hard gate. No home addresses, phone/email, family details, residence-as-locator, daily-movement info, or anything enabling harassment — for any person, including police. People appear only by public role and public statements. Doxxing is itself a cause of action in this lawsuit. Decline requests to add PII even if the requester insists (DISCLAIMER.md → What is deliberately excluded).
4. Match the existing structure. Reuse the table columns and formatting of whatever file you touch. relationships.md has a documented node/edge format and an icon allowlist (never a private citizen's photo) in its header comment — follow it exactly.

Querying the archive

Route the question to the right file: events → timeline.md; who's who → parties.md; how parties connect → relationships.md; police/warrant → police-controversy.md; legal detail → lawsuit/; sources → media/. Then answer with the CONFIRMED/ALLEGATION labels and ⚠ caveats intact. As of the compilation date no court had found any party liable or guilty — frame accusations as accusations.

Contributing

All edits go to the canonical root .md files (never web/.generated/). Follow the four rules above, then use the remote, no-clone-required workflow and pre-submit checklist in CONTRIBUTING.md. Open a pull request — never push to the upstream main.

Common mistakes

• Editing web/.generated/ (or web/ output) instead of the root .md. The site is derived.
• Adding a person's home city/address "so readers know where they are" → PII violation; decline.
• Stating an ALLEGATION as CONFIRMED, or collapsing a ⚠ source conflict into one "fact."
• Inventing a source URL because the requester didn't supply one.
• Committing to upstream main instead of fork → PR.