[ 00. ACCESS LAYER ]
HANDLE PHRASE: To post or append entries, enter a HANDLE_PHRASE with a minimum length of 8 characters. This is not an account — it generates your anonymous handle.
CONSISTENT HANDLE: The same phrase will always generate the same handle. If you reuse your phrase, you will appear as the same contributor again. If you want a new anonymous identity, use a different phrase.
ACCESS LEVEL & LIMITS: Handles earn an ACCESS_LEVEL over time through legitimate activity. Higher levels unlock higher hourly limits (posts/entries) up to a fixed cap. Current limits and reset time are shown in the status line.
CHALLENGE VERIFY: After entering the phrase, complete the short verification code. Once verified, the interface unlocks and your EVENT_REF becomes active for actions on the current event.
[ 01. PURPOSE ]
AGGREGATE. CROSS-CHECK. ARCHIVE. ICESS is an event hub. One EVENT_ID collects sources, artifacts, and discussion so the public can compare narratives in one place.
NO EDITORIAL LAYER. We do not curate opinions or write conclusions. The record is built from submitted evidence, linked reporting, and timestamped contributions.
[ 02. WHAT BELONGS IN AN EVENT ]
- SOURCES: URLs to reporting, official statements, documents, livestreams, datasets.
- ARTIFACTS: Photos, video, audio, PDFs. (Max 75MB each.)
- DISCUSSION: Context, timelines, corrections, and analysis (no link drops here).
[ 03. INDEXING ]
TAG IT. Use #tags to make events searchable (e.g., #NYStorm, #Earthquake, #Election, #MarketCrash). Keep summaries factual: What / Where / When.
[ 04. HARD LIMITS ]
ILLEGAL CONTENT IS REMOVED. No CSAM. No doxxing. No credible threats. No malware. No instructions for wrongdoing. No stolen personal data. This is not “censorship” — it is legal compliance and user safety.
ABUSE IS RATE-LIMITED. Spam and automated flooding are blocked. Repeated abuse results in an access ban for the offending identity/key.