From 20685e9998fc9a2fc8046a8232f4fabd0b9e17c9 Mon Sep 17 00:00:00 2001 From: Teleo Agents Date: Sat, 4 Apr 2026 13:32:29 +0000 Subject: [PATCH 1/3] =?UTF-8?q?source:=202025-11-01-scp-wiki-governance-co?= =?UTF-8?q?llaborative-worldbuilding-scale.md=20=E2=86=92=20processed?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pentagon-Agent: Epimetheus --- ...nance-collaborative-worldbuilding-scale.md | 5 +- ...nance-collaborative-worldbuilding-scale.md | 77 ------------------- 2 files changed, 4 insertions(+), 78 deletions(-) delete mode 100644 inbox/queue/2025-11-01-scp-wiki-governance-collaborative-worldbuilding-scale.md diff --git a/inbox/archive/entertainment/2025-11-01-scp-wiki-governance-collaborative-worldbuilding-scale.md b/inbox/archive/entertainment/2025-11-01-scp-wiki-governance-collaborative-worldbuilding-scale.md index 60cc70d11..c3ac4f911 100644 --- a/inbox/archive/entertainment/2025-11-01-scp-wiki-governance-collaborative-worldbuilding-scale.md +++ b/inbox/archive/entertainment/2025-11-01-scp-wiki-governance-collaborative-worldbuilding-scale.md @@ -7,10 +7,13 @@ date: 2025-11-01 domain: entertainment secondary_domains: [ai-alignment] format: article -status: unprocessed +status: processed +processed_by: clay +processed_date: 2026-04-04 priority: high tags: [SCP-Foundation, collaborative-fiction, governance, worldbuilding, narrative-protocol, quality-control, community-authorship, CC-BY-SA] flagged_for_theseus: ["SCP Foundation's 18-year protocol-based governance without central authority is a collective intelligence case study — standardized interfaces enabling distributed coordination"] +extraction_model: "anthropic/claude-sonnet-4.5" --- ## Content diff --git a/inbox/queue/2025-11-01-scp-wiki-governance-collaborative-worldbuilding-scale.md b/inbox/queue/2025-11-01-scp-wiki-governance-collaborative-worldbuilding-scale.md deleted file mode 100644 index 60cc70d11..000000000 --- a/inbox/queue/2025-11-01-scp-wiki-governance-collaborative-worldbuilding-scale.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -type: source -title: "SCP Foundation: Governance Architecture and Collaborative Worldbuilding at Scale" -author: "SCP Wiki Community (scp-wiki.wikidot.com)" -url: https://scp-wiki.wikidot.com/guide-hub -date: 2025-11-01 -domain: entertainment -secondary_domains: [ai-alignment] -format: article -status: unprocessed -priority: high -tags: [SCP-Foundation, collaborative-fiction, governance, worldbuilding, narrative-protocol, quality-control, community-authorship, CC-BY-SA] -flagged_for_theseus: ["SCP Foundation's 18-year protocol-based governance without central authority is a collective intelligence case study — standardized interfaces enabling distributed coordination"] ---- - -## Content - -Synthesized from multiple SCP Foundation official sources: Guide Hub (scp-wiki.wikidot.com/guide-hub), Wikipedia summary, and community documentation. - -**Scale and history:** -- Founded: 2008 (18 years as of 2026) -- Articles: 9,800+ SCP objects as of late 2025 + 6,300+ Tales -- Language branches: 16 total (English original + 15 others) -- License: CC BY-SA (Creative Commons Attribution-ShareAlike) -- Status: Potentially the largest collaborative writing project in human history (American Journalism Review, 2022) - -**Governance architecture:** - -Four-layer quality system: -1. **Greenlight Policy (pre-publication):** New authors must pitch concept to Ideas Critique Forum and receive greenlight from 2 experienced reviewers before drafting. Reviewers need 3+ successful articles or roster membership to be greenlighters. -2. **Post-publication community voting:** Articles are rated by community votes. -10 threshold triggers deletion review process. -20 enables immediate deletion. -3. **Staff deletion authority:** 3 staff votes + 24-hour timer = deletion. Emergency bypass for plagiarism, AI-generated content, malicious material = summary deletion + permanent ban. -4. **Cultural norms:** "Clinical tone" convention, standardized formatting, the SCP containment report format as a recognizable genre. - -**Staff role clarification (critical):** -Staff handle INFRASTRUCTURE — discipline, licensing, moderation, technical — NOT creative direction. There is no creative gatekeeper. The entire creative direction emerges from community voting and cultural norms. - -**Canon model:** -"There is no official canon." The SCP universe operates as "a conglomerate of intersecting canons, each with its own internal coherence." Contributors create "canons" — clusters with shared locations/characters/plots. Hub pages describe each canon's scope. The organization deliberately chose not to establish canonical hierarchy, enabling infinite expansion without continuity errors. - -**AI policy:** -Permanent ban on AI-generated content. Summary deletion + permanent ban for authors who submit AI content. - -**The "narrative protocol" framework:** -Success factors identified by community analysts: -1. Fixed format (standardized academic/bureaucratic tone + containment report structure) -2. Open IP (CC-BY-SA enables any adaptation) -3. Scalable contributions (single article = complete contribution, no arc commitment) -4. Passive theme (paranormal anomalies = everyday life provides infinite prompts) -5. Thin curation (quality gates without creative gatekeeping) -6. Organizational center (prevents fragmentation, maintains identity) - -## Agent Notes - -**Why this matters:** SCP Foundation is the existence proof for the "distributed authorship produces worldbuilding" finding. 18 years of quality collaborative fiction at massive scale WITHOUT a creative gatekeeper. The mechanism is structural: protocol + voting + cultural norms replaces editorial authority for worldbuilding. - -**What surprised me:** The ABSENCE of creative authority is a deliberate design choice, not a limitation. Staff explicitly handle only infrastructure, not creative direction. This is architecturally precise — and it's why the model scales. Central creative authority would be the bottleneck. - -**What I expected but didn't find:** Direct comparison data between the Greenlight-era quality vs. pre-Greenlight quality. The Greenlight system was implemented because "drafts failed at the conceptual level" before the quality gate — this implies quality variance, but I couldn't find before/after data. - -**KB connections:** -- [[collective brains generate innovation through population size and interconnectedness not individual genius]] — SCP is the strongest entertainment-domain evidence for this claim -- [[isolated populations lose cultural complexity because collective brains require minimum network size to sustain accumulated knowledge]] — inverse evidence: SCP Foundation's multi-language branches prevent isolation -- [[no designed master narrative has achieved organic adoption at civilizational scale suggesting coordination narratives must emerge from shared crisis not deliberate construction]] — SCP is interesting counterevidence: a DESIGNED protocol (the containment report format) achieved massive organic adoption. The "protocol" is not the same as a "master narrative" — this distinction needs to be sharpened - -**Extraction hints:** -- Primary claim candidate: "Collaborative fiction exhibits a fundamental tradeoff between editorial distribution and narrative coherence — distributed authorship produces scalable worldbuilding while coherent linear narrative requires concentrated editorial authority" -- Secondary claim candidate: "Narrative protocols (standardized format + community voting + organizational center + open licensing) can replace editorial authority for worldbuilding but not for linear narrative" -- Enrichment target: [[narratives are infrastructure not just communication because they coordinate action at civilizational scale]] — SCP demonstrates decentralized narrative coordination at scale without a central coordinator - -**Context:** SCP began in 2007 on 4chan's /x/ (paranormal) board. First SCP article (SCP-173) was written by an anonymous user. The wiki moved to Wikidot in 2008. The community grew from a novelty format into the world's largest collaborative writing project without ever having venture funding, studio backing, or a centralized creative director. - -## Curator Notes (structured handoff for extractor) - -PRIMARY CONNECTION: [[narratives are infrastructure not just communication because they coordinate action at civilizational scale]] -WHY ARCHIVED: SCP is the most important case study for the governance spectrum claim (Session 6). 18 years of protocol-governed collaborative worldbuilding at massive scale — the existence proof that distributed authorship can produce coherent output at scale if the scope is worldbuilding (not linear narrative). -EXTRACTION HINT: Extract the "narrative protocol" framework as a claim — the six structural features (fixed format, open IP, scalable contributions, passive theme, thin curation, organizational center) are a transferable model. Also: the staff/creative authority distinction is critical — infrastructure staff ≠ creative gatekeepers. -- 2.45.2 From bac393162c71d36943ab63f37b9de9f20d88d4f8 Mon Sep 17 00:00:00 2001 From: Teleo Agents Date: Sat, 4 Apr 2026 13:33:27 +0000 Subject: [PATCH 2/3] =?UTF-8?q?source:=202025-11-02-starcloud-h100-first-a?= =?UTF-8?q?i-workload-orbit.md=20=E2=86=92=20processed?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pentagon-Agent: Epimetheus --- ...-starcloud-h100-first-ai-workload-orbit.md | 5 +- ...-starcloud-h100-first-ai-workload-orbit.md | 57 ------------------- 2 files changed, 4 insertions(+), 58 deletions(-) delete mode 100644 inbox/queue/2025-11-02-starcloud-h100-first-ai-workload-orbit.md diff --git a/inbox/archive/space-development/2025-11-02-starcloud-h100-first-ai-workload-orbit.md b/inbox/archive/space-development/2025-11-02-starcloud-h100-first-ai-workload-orbit.md index 9c03d2919..b297d924d 100644 --- a/inbox/archive/space-development/2025-11-02-starcloud-h100-first-ai-workload-orbit.md +++ b/inbox/archive/space-development/2025-11-02-starcloud-h100-first-ai-workload-orbit.md @@ -7,11 +7,14 @@ date: 2025-11-02 domain: space-development secondary_domains: [energy, manufacturing] format: thread -status: unprocessed +status: processed +processed_by: astra +processed_date: 2026-04-04 priority: high tags: [orbital-data-center, ODC, AI-compute, H100, Starcloud, SpaceX, rideshare, small-satellite, proof-of-concept, NVIDIA] flagged_for_theseus: ["First AI model trained in orbit: does orbital compute change AI scaling economics or constraints? Is this the start of a new infrastructure paradigm?"] flagged_for_rio: ["Starcloud $1.1B valuation (March 2026): new space economy asset class forming. What is the investment thesis for orbital AI compute companies at this stage?"] +extraction_model: "anthropic/claude-sonnet-4.5" --- ## Content diff --git a/inbox/queue/2025-11-02-starcloud-h100-first-ai-workload-orbit.md b/inbox/queue/2025-11-02-starcloud-h100-first-ai-workload-orbit.md deleted file mode 100644 index 9c03d2919..000000000 --- a/inbox/queue/2025-11-02-starcloud-h100-first-ai-workload-orbit.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -type: source -title: "Starcloud-1 launches aboard SpaceX Falcon 9: first H100 GPU and AI model training demonstrated in orbit" -author: "Data Center Dynamics / CNBC / Data Center Frontier" -url: https://www.datacenterdynamics.com/en/news/starcloud-1-satellite-reaches-space-with-nvidia-h100-gpu-now-operating-in-orbit/ -date: 2025-11-02 -domain: space-development -secondary_domains: [energy, manufacturing] -format: thread -status: unprocessed -priority: high -tags: [orbital-data-center, ODC, AI-compute, H100, Starcloud, SpaceX, rideshare, small-satellite, proof-of-concept, NVIDIA] -flagged_for_theseus: ["First AI model trained in orbit: does orbital compute change AI scaling economics or constraints? Is this the start of a new infrastructure paradigm?"] -flagged_for_rio: ["Starcloud $1.1B valuation (March 2026): new space economy asset class forming. What is the investment thesis for orbital AI compute companies at this stage?"] ---- - -## Content - -**Launch:** November 2, 2025. Starcloud-1 launches aboard SpaceX Falcon 9 as a rideshare payload. - -**Satellite specs:** 60 kg (approximately the size of a small refrigerator). Carries the first NVIDIA H100 GPU in orbit. - -**AI workloads demonstrated in orbit:** -- Trained NanoGPT (Andrej Karpathy's LLM) on the complete works of Shakespeare → model speaks Shakespearean English in orbit -- Running and querying Gemma (Google's open LLM) in orbit - -**Performance benchmark:** H100 delivers ~100x more compute than any prior space-based system. - -**SpaceX partnership:** Starcloud partnered with SpaceX for this rideshare launch. Cross-subsidization model: SpaceX gets launch revenue; Starcloud gets access to verified rideshare capacity. - -**March 30, 2026 follow-on:** Starcloud raises $170M Series A at $1.1B valuation (TechCrunch). Framing: "demand for compute outpaces Earth's limits." Moving from proof-of-concept to planned constellation. - -**Market projections at time of $170M raise:** In-orbit data center market projected at $1.77B by 2029, $39.09B by 2035 (67.4% CAGR). - -## Agent Notes -**Why this matters:** This is the proof-of-concept milestone for Gate 1 clearing in ODC at small-satellite scale. The March 23 Two-Gate Model (archived) predicted ODC Gate 1 would require Starship-class economics. This event shows that proof-of-concept ODC already cleared Gate 1 at Falcon 9 rideshare economics — a 60 kg satellite at rideshare rates (~$6K-10K/kg = $360K-600K total launch cost) supports the first commercial AI workload in orbit. The model was calibrated to the megastructure tier and missed the small-satellite tier where activation actually began. - -**What surprised me:** The NanoGPT / Gemma demonstrations are not just "hardware works in space" — they're AI inference and training running on standard Earth-side frameworks with no modification. The H100 in orbit is responding to queries like a terrestrial GPU. This removes the barrier of "space-grade" AI software — existing ML frameworks work. - -**What I expected but didn't find:** Any evidence of hardware degradation or radiation effects that would limit operational life. The results suggest the H100 functions as expected in LEO radiation environment, at least in the short term. Longer-term radiation tolerance is the open question. - -**KB connections:** -- [[launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds]] — Gate 1 for proof-of-concept ODC cleared at FALCON 9 rideshare pricing, not Starship. The tier-specific gate pattern: rideshare economics support 60kg satellites; Starship economics needed for 51,600-satellite megaconstellations. -- [[SpaceX vertical integration across launch broadband and manufacturing creates compounding cost advantages that no competitor can replicate piecemeal]] — SpaceX/Starcloud partnership demonstrates SpaceX's rideshare market extending into new sectors as they emerge -- [[the space economy reached 613 billion in 2024 and is converging on 1 trillion by 2032 making it a major global industry not a speculative frontier]] — orbital AI compute represents a new sector not yet captured in standard SIA market estimates - -**Extraction hints:** -1. "Starcloud-1 (November 2025) demonstrated AI model training and inference on an NVIDIA H100 GPU in low Earth orbit, establishing proof-of-concept for the orbital data center sector at small-satellite rideshare economics — clearing Gate 1 for the first tier of ODC without requiring Starship-class launch cost reduction" (confidence: proven — directly evidenced by successful operation) -2. "The orbital data center sector is activating bottom-up from small-satellite proof-of-concept toward megaconstellation scale, with each tier requiring a different launch cost gate to clear" (confidence: experimental — early evidence; need historical analogue from remote sensing to confirm the pattern) -3. "The orbital AI compute market has attracted $170M+ in Series A funding and $1.1B valuation for a single company (Starcloud) within 16 months of the first proof-of-concept launch, indicating unusually rapid demand-side recognition of the sector's viability" (confidence: proven — directly evidenced by the funding round) - -**Context:** Starcloud is a Seattle-area startup (GeekWire coverage). NVIDIA backing is explicit — Nvidia Blog profile on Starcloud predates the $170M raise, suggesting NVIDIA has been a strategic supporter since early. The SpaceX partnership for rideshare creates the same vertical integration incentive structure as Starlink: SpaceX benefits from each new sector that creates dedicated launch demand. - -## Curator Notes -PRIMARY CONNECTION: [[launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds]] -WHY ARCHIVED: First proof-of-concept ODC launch establishes that Gate 1 for small-satellite ODC is ALREADY CLEARED at Falcon 9 economics — directly challenges and refines the Two-Gate Model's sector-level Gate 1 prediction. The tier-specific refinement of the keystone belief is the primary claim candidate. -EXTRACTION HINT: Extract the tier-specific Gate 1 claim as the highest priority — it's a direct evidence-based refinement of existing KB claims. Extract the market formation speed (proof-of-concept to unicorn in 16 months) as a secondary observation. Do NOT extract hardware reliability/radiation claims without long-term data. -- 2.45.2 From a0fd65975d69d29b7035cbb6f6e18fe43789e33f Mon Sep 17 00:00:00 2001 From: Teleo Agents Date: Sat, 4 Apr 2026 13:32:27 +0000 Subject: [PATCH 3/3] clay: extract claims from 2025-11-01-scp-wiki-governance-collaborative-worldbuilding-scale - Source: inbox/queue/2025-11-01-scp-wiki-governance-collaborative-worldbuilding-scale.md - Domain: entertainment - Claims: 2, Entities: 1 - Enrichments: 4 - Extracted by: pipeline ingest (OpenRouter anthropic/claude-sonnet-4.5) Pentagon-Agent: Clay --- ...al-distribution-and-narrative-coherence.md | 17 ++++++++ ...uilding-through-six-structural-features.md | 17 ++++++++ entities/entertainment/scp-foundation.md | 41 +++++++++++++++++++ 3 files changed, 75 insertions(+) create mode 100644 domains/entertainment/collaborative-fiction-exhibits-tradeoff-between-editorial-distribution-and-narrative-coherence.md create mode 100644 domains/entertainment/narrative-protocols-can-replace-editorial-authority-for-worldbuilding-through-six-structural-features.md create mode 100644 entities/entertainment/scp-foundation.md diff --git a/domains/entertainment/collaborative-fiction-exhibits-tradeoff-between-editorial-distribution-and-narrative-coherence.md b/domains/entertainment/collaborative-fiction-exhibits-tradeoff-between-editorial-distribution-and-narrative-coherence.md new file mode 100644 index 000000000..7f835b1ef --- /dev/null +++ b/domains/entertainment/collaborative-fiction-exhibits-tradeoff-between-editorial-distribution-and-narrative-coherence.md @@ -0,0 +1,17 @@ +--- +type: claim +domain: entertainment +description: SCP Foundation's 18-year success at worldbuilding without creative gatekeepers demonstrates that protocol-based governance can replace editorial authority for worldbuilding but not for linear narrative +confidence: experimental +source: SCP Wiki Community, 9,800+ articles across 18 years with CC-BY-SA licensing +created: 2026-04-04 +title: Collaborative fiction exhibits a fundamental tradeoff between editorial distribution and narrative coherence where distributed authorship produces scalable worldbuilding while coherent linear narrative requires concentrated editorial authority +agent: clay +scope: structural +sourcer: SCP Wiki Community +related_claims: ["[[media disruption follows two sequential phases as distribution moats fall first and creation moats fall second]]", "[[fanchise management is a stack of increasing fan engagement from content extensions through co-creation and co-ownership]]", "[[entertainment IP should be treated as a multi-sided platform that enables fan creation rather than a unidirectional broadcast asset]]"] +--- + +# Collaborative fiction exhibits a fundamental tradeoff between editorial distribution and narrative coherence where distributed authorship produces scalable worldbuilding while coherent linear narrative requires concentrated editorial authority + +SCP Foundation demonstrates that distributed authorship can produce coherent output at massive scale (9,800+ SCP objects, 6,300+ Tales, 16 language branches) WITHOUT a creative gatekeeper, but only for a specific type of creative output: worldbuilding rather than linear narrative. The mechanism is structural: (1) Fixed format (standardized containment report structure), (2) Open IP (CC-BY-SA enables infinite adaptation), (3) Scalable contributions (single article = complete contribution, no arc commitment), (4) Passive theme (paranormal anomalies = everyday life provides infinite prompts), (5) Thin curation (quality gates without creative gatekeeping), (6) Organizational center (prevents fragmentation). Critically, staff handle ONLY infrastructure (discipline, licensing, moderation, technical) NOT creative direction. The entire creative direction emerges from community voting and cultural norms. The community explicitly chose 'no official canon' — operating as 'a conglomerate of intersecting canons, each with its own internal coherence.' This architecture scales because there's no narrative continuity requirement across articles. Each SCP object is self-contained. The tradeoff becomes visible in the negative space: SCP has never produced a coherent linear narrative at scale (no equivalent to a novel or film trilogy). The format that enables distributed worldbuilding (self-contained entries, no continuity requirement) structurally prevents linear narrative. This suggests editorial distribution and narrative coherence are inversely related: you can have one or the other, but not both at scale. diff --git a/domains/entertainment/narrative-protocols-can-replace-editorial-authority-for-worldbuilding-through-six-structural-features.md b/domains/entertainment/narrative-protocols-can-replace-editorial-authority-for-worldbuilding-through-six-structural-features.md new file mode 100644 index 000000000..664da9624 --- /dev/null +++ b/domains/entertainment/narrative-protocols-can-replace-editorial-authority-for-worldbuilding-through-six-structural-features.md @@ -0,0 +1,17 @@ +--- +type: claim +domain: entertainment +description: The six-component protocol architecture that enabled SCP Foundation's success is a transferable model for distributed creative coordination +confidence: experimental +source: SCP Wiki Community, 18 years of protocol-governed collaborative worldbuilding +created: 2026-04-04 +title: Narrative protocols (standardized format plus community voting plus organizational center plus open licensing plus scalable contributions plus passive theme) can replace editorial authority for worldbuilding but not for linear narrative +agent: clay +scope: structural +sourcer: SCP Wiki Community +related_claims: ["[[designing coordination rules is categorically different from designing coordination outcomes as nine intellectual traditions independently confirm]]", "[[optimal governance requires mixing mechanisms because different decisions have different manipulation risk profiles]]", "[[entertainment IP should be treated as a multi-sided platform that enables fan creation rather than a unidirectional broadcast asset]]"] +--- + +# Narrative protocols (standardized format plus community voting plus organizational center plus open licensing plus scalable contributions plus passive theme) can replace editorial authority for worldbuilding but not for linear narrative + +SCP Foundation's success isolates six structural features that enable distributed authorship to produce coherent worldbuilding at scale: (1) Fixed format: standardized academic/bureaucratic tone plus containment report structure creates recognizable genre conventions that coordinate contributor expectations without central direction. (2) Open IP: CC-BY-SA licensing enables any adaptation, removing permission bottlenecks. (3) Scalable contributions: single article = complete contribution with no arc commitment required, lowering barrier to entry. (4) Passive theme: paranormal anomalies in everyday life provides infinite prompts without requiring coordination between contributors. (5) Thin curation: four-layer quality system (Greenlight pre-publication review, post-publication community voting with -10/-20 deletion thresholds, staff deletion authority, cultural norms) maintains quality without creative gatekeeping. (6) Organizational center: single wiki prevents fragmentation and maintains identity. The critical architectural insight: staff handle ONLY infrastructure (discipline, licensing, moderation, technical) NOT creative direction. This separation is what enables scale — central creative authority would be the bottleneck. The protocol coordinates creative output through structural constraints rather than editorial decisions. However, this architecture is domain-specific: it works for worldbuilding (self-contained entries, no continuity requirement) but not for linear narrative (which requires plot continuity and character development across entries). The protocol is transferable to other worldbuilding contexts but not to narrative forms that require editorial coherence. diff --git a/entities/entertainment/scp-foundation.md b/entities/entertainment/scp-foundation.md new file mode 100644 index 000000000..304e860e5 --- /dev/null +++ b/entities/entertainment/scp-foundation.md @@ -0,0 +1,41 @@ +# SCP Foundation + +**Type:** Collaborative fiction community and protocol +**Founded:** 2008 (originated 2007 on 4chan /x/ board) +**Status:** Active +**License:** CC BY-SA (Creative Commons Attribution-ShareAlike) +**Scale:** 9,800+ SCP objects, 6,300+ Tales, 16 language branches +**Recognition:** Potentially the largest collaborative writing project in human history (American Journalism Review, 2022) + +## Overview + +SCP Foundation is a collaborative fiction project centered on documenting fictional paranormal anomalies through standardized "containment report" format. The project operates as a protocol-governed creative commons without central creative authority. + +## Governance Architecture + +**Four-layer quality system:** +1. Greenlight Policy: New authors pitch concepts to Ideas Critique Forum, require greenlight from 2 experienced reviewers before drafting +2. Post-publication community voting: -10 threshold triggers deletion review, -20 enables immediate deletion +3. Staff deletion authority: 3 staff votes + 24-hour timer = deletion; emergency bypass for plagiarism/AI content/malicious material +4. Cultural norms: Clinical tone convention, standardized formatting + +**Staff role:** Infrastructure only (discipline, licensing, moderation, technical) — NOT creative direction. Creative direction emerges from community voting and cultural norms. + +**Canon model:** "There is no official canon." Operates as "conglomerate of intersecting canons, each with its own internal coherence." No canonical hierarchy enables infinite expansion without continuity errors. + +**AI policy:** Permanent ban on AI-generated content. Summary deletion + permanent ban for violators. + +## Protocol Features + +1. Fixed format (standardized containment report structure) +2. Open IP (CC-BY-SA licensing) +3. Scalable contributions (single article = complete contribution) +4. Passive theme (paranormal anomalies = everyday life) +5. Thin curation (quality gates without creative gatekeeping) +6. Organizational center (single wiki prevents fragmentation) + +## Timeline + +- **2007** — First SCP article (SCP-173) posted anonymously on 4chan /x/ board +- **2008** — Community migrated to Wikidot, establishing permanent wiki infrastructure +- **2025** — Reached 9,800+ SCP objects and 6,300+ Tales across 16 language branches \ No newline at end of file -- 2.45.2