Public community overview · updated 28 October 2026

PABC: structured debate, philosophy, and cosmology

PABC is a community space for philosophy, formal logic, evidence-based character matchups, cosmology analysis, wiki-style profiles, collaborative research, and community discussion. Members can make arguments and challenge interpretations, but claims should remain proportionate to the evidence and counterevidence.

Core standard: identify the source, explain what it directly establishes, show the bridge premise that connects it to the conclusion, and record limitations or plausible alternative readings.

Explore PABC

Open the community Discussions Community wiki Cosmology dossiers Live channels Member directory Publishing tutorials Sandbox & Studio

Topic areas

Philosophy and formal logic. Define terms, state premises, identify inference rules, and address objections.
Battleboarding and source analysis. Separate attack potency, destructive capacity, durability, speed, range, resistance, and special abilities instead of treating one statistic as a universal verdict.
Cosmology and worldbuilding. Map universes, timelines, abstract structures, modal spaces, narrative levels, and their proposed relations. A diagram records a claim; it does not prove the claim on its own.
Community wiki. Draft character profiles, articles, evidence ledgers, scan analyses, and revision proposals.
Media and documents. Share source links, supported video embeds, and public Google Docs or Drive previews where provider settings allow embedding.

Public publishing and embeds

Public Google documents can be shared with link-viewing access or published to the web, where appropriate. Do not share private documents. Providers may block iframe embedding; if a preview does not load, provide a direct link and check the provider's sharing settings. Use the in-site Channel tutorials for detailed steps.

Channels and projects

The community includes general conversation, philosophy, battleboarding, scaling and cosmology work, content revision review, wiki workshops, project activities, media room, argument arena, document showcase, and publishing tutorials. Channel availability is managed by the live community system and may change.

Step-by-step: publish a cosmology dossier

Open Cosmology blog and select Publish cosmology dossier.
Give the dossier a specific title and a short summary explaining the cosmology and the claim being assessed.
Paste the original source, scan archive, or public cosmology-blog URL into the external-source field. Do not treat a tier label as a substitute for the evidence.
Link the related CRT/debate thread if one exists. Record system family, method, axioms, definitions, proposed tier, ontology tags, and logic tags separately.
In the long explanation, include the primary source, exact passage or scan, bridge premises, counter-readings, limitations, and a conclusion calibrated to the evidence.
Use Preview before publishing. After publishing, open the dossier and verify every external link and any optional embed.

Google Docs, Sheets, Slides and Drive: safe embed workflow

Open the document in Google Docs, Sheets, or Slides. Use a test document with no personal or confidential information.
Choose File → Share → Publish to web, then choose Embed when the file type supports it, and publish.
Copy the generated embed URL or iframe source. PABC's supported document fields accept provider URLs, not arbitrary HTML pasted into a post.
Return to the cosmology dossier, discussion, wiki, or #document-showcase and paste the public URL in its optional source/embed field or body.
Save, open the post, and confirm the preview is scrollable on desktop and mobile. Keep the direct document link next to the viewer as a fallback.
If the viewer says access denied or remains blank, check Google sharing/publishing permissions and whether the provider allows embedding. Do not disable browser security to force it.

Privacy warning: “Anyone with the link” or “Publish to web” can expose content beyond PABC. Recheck the document's sharing settings before posting. Never paste an iframe with scripts or an unknown host into a community post.

Long-form posts, TikZ and source-preserving diagrams

Discussion, wiki and cosmology content supports up to 500,000 characters per body at the application layer. Channel chat messages support up to 150,000 characters, and replies up to 300,000. Actual practical capacity depends on UTF-8 size, the D1 row limit, browser memory, and the complexity of the document. D1 does not compile TeX.

Write TikZ as a fenced code block using ```tikz and the matching closing fence. PABC attempts browser-side rendering for diagrams up to 20,000 characters. Larger or unsupported diagrams are kept as expandable raw source instead of being discarded. Split very large diagrams into separate figures, or compile a trusted SVG/PDF outside the browser and attach it alongside the source. Do not expect the serverless D1 database to compile TikZ.

For safe document embeds, paste a supported provider URL on its own line. The site converts supported Google Docs/Drive, YouTube, Vimeo, TikTok and Spotify links into sandboxed responsive frames across discussions, wiki pages, cosmology dossiers, replies and chat. Arbitrary iframe HTML and JavaScript are intentionally not accepted. If a provider blocks embedding, use the direct link.

Image attachment in a private message

Upload the image to a host that provides a direct HTTPS image URL, such as an Imgur direct image link.
Make sure the link ends in a supported image file or actually returns an image, and that it does not contain private material.
In Inbox → Direct messages, enter your message and paste the image URL into the optional image field. You can also include a supported video or Google Docs URL.
Send the message and open the conversation again to confirm the image renders. If the host blocks embedding, send a regular link instead.

Edit and delete private messages

Use the Edit control on a message you sent. Editing is limited to the first 15 minutes. Delete removes the message from your own inbox view only; it does not silently erase the recipient's copy. Channel-message edit/delete controls remain subject to the existing author and staff permissions.

Channel badges, pinned messages and themes

Staff can assign a channel badge such as NEW, GUIDE, STAFF, OFFICIAL, EVENT, BETA, HOT or READ-ONLY from Moderation Desk → Channels. Clear the badge to remove it. Staff can reorder pinned discussions with the up/down controls in the discussion detail view. In live channels, use the single 📌 Pins control in the channel header to browse pinned messages. Staff can pin messages with /pin MESSAGE_ID where supported by the chat command parser. The public member directory never exposes email addresses. Only administrator and owner-level staff can view member emails in the protected moderation member search. Moderators do not receive email fields.

Appearance offers Classic PABC, Early-2000s Reddit, Retro Imageboard and Battle Wiki Classic layout presets. Staff can also configure an Advent or Christmas overlay in Moderation Desk → Visual designer, set its start/end dates, or switch it off. The holiday treatment is deliberately light and can be disabled without changing the underlying theme.

Privacy and safety

Private messages, account email addresses, moderation reports, and private account details are not public content. Never post passwords, session tokens, keys, private correspondence, or personal documents. User-submitted text is rendered as Markdown with sanitization; supported embeds are limited to recognized HTTPS provider URLs.

This is a public, crawlable overview. Community threads, private inbox content, and dynamic client-side pages may not be indexed by every crawler. See robots.txt and llms.txt. Allowing a crawler does not guarantee indexing or display in an AI answer.