Compliance & Troubleshooting

The Beacon runs on a 24-hour Guard Lambda cycle — a scheduled function in your own AWS account:

1. Guard Lambda pings api.sirsluginston.com/beacon daily
2. Beacon returns an Ed25519-signed token with your active publisher ID and cap status
3. Token is stored in your DynamoDB with a 36-hour expiry (12-hour buffer beyond the 24-hour cycle)
4. Your Beacon component reads from /api/beacon-local and passes the token to each AdSlot
5. AdSlot verifies the Ed25519 signature — no valid signature, no publisher ID

The daily cap check means traffic spikes are handled gracefully: if your site crosses the solvency threshold during a big day, your publisher ID stays active until the next Guard Lambda renewal.

For full technical documentation: sirsluginston.com/docs

Two different situations — with very different implications:

Guard Lambda unreachable / API temporarily down:

• The stored token remains valid for up to 36 hours from its last renewal
• AdSlots continue serving your publisher ID normally during the window
• No escalation, no banners, no admin notices
• Resolves automatically when the Guard Lambda runs on its next cycle

Token lapsed (Guard Lambda stopped, or Beacon component removed):

• After the 36-hour token expiry, AdSlots serve internal SirSluginston promotions
• A restoration timeline begins (see below)
• Run sirsluginston repair to restore everything immediately

The vast majority of issues are the first case — a temporary network hiccup that the 36-hour window absorbs without you ever noticing.

Run from your app directory:

npx sirsluginston repair

This re-verifies and restores:

1. app/globals.css — Beacon integrity block
2. app/api/beacon-health/route.ts — Ed25519-signed health endpoint
3. app/lib/admin-actions.ts — checkBeaconLock gate
4. app/[...slug]/page.tsx — Shell inclusion

Every restoration effect reverses immediately when a valid token is issued. No cooldown, no appeal, no manual step on SirSluginston Co's side.

If repair does not fix it: sirsluginston.com/support

If a token goes unrenewed, effects activate on this graduated timeline:

Time without valid renewal	Effect	Who sees it	Reversed when
0–36h	Token valid. Normal ad serving.	Nobody	—
36h+	AdSlots serve internal SirSluginston promotions	Silent	Next Guard Lambda renewal
72h	Restoration notice in /admin. Saves fully functional.	Admin only	Next Guard Lambda renewal
1 week	Admin panel saves locked	Admin only	Next Guard Lambda renewal
2 weeks	Public notice banner for all visitors	Everyone	Next Guard Lambda renewal

Every effect is fully reversible the instant a valid token is issued — no grace period or cooldown after restoration.

SirSluginston runs under the SirSluginston License for Infrastructure and Monetization across Environments (SLIME).

SLIME is source-available — published so you can verify exactly how the ad publisher ID is resolved and how the solvency cap is calculated. Ownership and direction remain with SirSluginston Co.

Required: Guard Lambda running and Beacon functional in the Shell, AdSlot publisher ID logic intact, "Powered by SirSluginston: Core" footer visible on all public pages, ads.txt intact.

Not required: Sharing your app code, any upfront payment to SirSluginston Co, manual cost reporting.

Full license text → · Technical docs →

Material breaches — active tampering with the revenue-share mechanism:

• Modifying the publisher ID resolution logic (hardcoding an ID, intercepting or forging the signed token)
• Blocking or rerouting Guard Lambda pings to the central beacon
• Removing the "Powered by SirSluginston: Core" attribution footer
• Redistributing Core as a competing site platform

Not a breach:

• Temporary network outages that the 36-hour window absorbs
• Customizing content, styling, and page layout
• Building any features on top of Core for your own site
• Accidentally deleting the Beacon component — run repair

Note: Ed25519 asymmetric signing means token forgery is cryptographically infeasible even with full source access.

sirsluginston.com/support