Core Platform — SirSluginston

Core is the foundation of every SirSluginston site. It gives you:

• A server-driven page system — pages and their content are stored in your database, rendered on the server, and served instantly. No rebuild required to change content.
• A visual admin panel — non-technical team members can create, edit, and publish pages without touching code.
• Multi-tenant support — run multiple brands from a single deployment.
• Ad revenue with a built-in cost model — the Beacon activates your ad slots and tracks your impression count against your solvency cap. You earn ad revenue first, up to your infrastructure cost threshold. There is no monthly SirSluginston fee.

Example: Ma's Bakery runs their entire public site on Core — a homepage, a menu page, an about page, and a seasonal specials blog. Ma updates the specials herself from the admin panel every Friday morning. No developer involvement.

Every page is made up of blocks. Each block is a self-contained section of content that you add, reorder, and configure from the admin panel.

Available blocks:

• Callout — Hero section with title, description, and action buttons
• Rich Text — Markdown content with full formatting
• Card Grid — A grid of cards with title, description, icon, and link
• Media Split — Image and text side-by-side
• Pricing Table — Tiers with feature lists and a CTA
• Accordion — Collapsible FAQ-style sections
• Form — Contact forms with configurable fields
• Docs — Structured documentation with sidebar navigation (this page is a Docs block)

Example: Ma's 'Menu' page uses a Callout block at the top, then a Card Grid of categories (Pastries, Breads, Seasonal), then a Rich Text block with the week's specials. She built it in 20 minutes from the admin panel.

Visit /admin to access your admin panel. It gives you:

• Page Manager — create, edit, and delete pages
• Page Builder — add blocks to a page and configure each one
• Brand Config — set your site name, colors, navigation, and logo
• Multi-Brand View — switch between tenants if you run more than one brand
• Solvency Cap Status — see your current ad impression count and cap position

In production (this deployment), access is protected by Cognito and the SLIME acceptance gate. On first admin login, you'll be shown the SLIME acceptance modal before the panel opens.

Example: When the Family Foods group wanted to add Pa's Donuts as a second brand, Ma opened the admin panel, created a new brand called 'pas-donuts', and it was immediately available at the same domain under a different tenant route. No new deployment.

Every SirSluginston deployment is multi-tenant by default. A brand is a namespace — it gets its own pages, its own config, its own colors and navigation. Multiple brands share one infrastructure deployment.

Brands can be independent or hierarchical. Independent brands have completely separate content and configuration. Parent/child brands share a content pool, useful for larger organizations managing many sub-sites under one operator.

The solvency cap belongs to the hub entity, not to individual brands. Infrastructure is shared, so the cap is calculated once against the total deployment cost. Adding a new brand introduces minimal incremental cost — a Route 53 hosted zone entry at roughly $0.50 per month, which the Cost Explorer Lambda picks up automatically.

Example: The Family Foods group runs Ma's Bakery, Pa's Donuts, and Cousin's Coffeehouse from one deployment. Each brand has its own branding and page content. One solvency cap covers the whole group.

Tenant routing happens at the middleware layer. Each incoming request is tagged with a tenant ID based on the hostname.

The Beacon is a persistent background component that does three things, all of which work in your favor.

1. Activates your ad slots. The Beacon receives a signed token from the platform on each page load. That token tells your AdSlots which publisher ID to serve. Without it, slots fall back to internal promotions instead of your ad revenue.
2. Runs your solvency cap. The Beacon tracks your impression count against your monthly infrastructure cost. While you are below the cap, your AdSense publisher ID runs. Once you exceed it, the platform's publisher ID takes over until the monthly reset. You never pay a flat fee. Your traffic covers your costs before SirSluginston Co earns a cent above that threshold.
3. Keeps your account in good standing. The platform monitors Beacon health. A missing or broken Beacon is treated as an infrastructure issue, not an immediate breach. You are notified with time to diagnose and restore it, and every effect reverses the moment it is back.

On a live deployment, restoration is immediate.

Core handles everything for a content-driven site. The add-ons extend it for specific needs:

• Ocean — if you receive data from external sources that visitors need to see. Includes Sonar alerting.
• Intellect — if visitors would genuinely benefit from a live AI assistant
• Commerce — if you are selling something

Each add-on increases your infrastructure footprint and your solvency cap. Add what you actually need, not what sounds useful.

---

More detail at sirsluginston.com/docs — architecture walkthroughs, SLIME reference, and audit-level documentation.