Browse documentation

🧭 Start Here

Blackcap Overview ✨ Blackcap Feature Catalog 🤖 AI Features 🧱 Technology, Administration, and Reliability Installation First Run

📘 User Guides

Administration and Operations Platform Configuration Organization Configuration Email and Consent Management

🚀 Deploy Blackcap

Platform Stacks and Raspberry Pi Hardware Raspberry Pi Deployment Raspberry Pi Client Services GCP Deployment Packaged Blackcap deployment Application Updates After Your First Blackcap Login: Self-Hosted Setup Guide Blackcap Release Notes Environment Variables and Secrets Reverse Proxy and TLS Background Jobs and Schedules

🛠️ Administer Blackcap

Organizations Users, Permissions, and Authentication Configuration Workspace Backups and Restore Database Administration Regression Testing Performance and Job Status Audit, Access Activity, and Logging GeoIP and Access Location Data Retention and Purge Support Chat Administration Support Requests API Tester and Postman Instance Reporting Third-Party Packages and Attribution AI Provider Usage and Billing Portals Microwave Pie licensing for Blackcap Microwave Pie licensing for Blackcap

🍽️ Use Recipes

Recipes and the Recipe Library Recipe Import and Discovery Recipe Editing and Cache Artifacts Recipe Sharing Social Recipe Import AI Recipe Image Generation 🪄 Adapt Recipe and 🎲 Variations

📅 Plan Meals

Meal Planner

🛒 Use Shopping Lists

Shopping Lists and Shop a List External and Household Shopping 🔗 Chrome Extension Shop With

🧺 Manage Kitchen Inventory

🧺 Kitchen Inventory

🖥️ Use Displays

Displays and Connections Assigning and Scheduling Display Content Remote Pi Client E-Ink Rendering Menu Refresh and Rendering Noun Project Footer Images

🧑‍🍳 Cook with Let’s Cook

🧑‍🍳 Let’s Cook 🧑‍🍳 Let’s Cook Controls and Timers

🤖 Use and Administer AI

🤖 AI in Blackcap 🤖 AI Providers and Connections 🤖 AI Seeds and Usage Support Chat

🔗 Use the Chrome Extension

🔗 Blackcap Chrome Extension 🔗 Chrome Extension Recipe Capture 🔗 Chrome Extension Shop With 🔗 Chrome Extension Release and Privacy

🎮 Play Games

Games and trivia Bramble Harvest — Player Guide Flavor Lab — Player Guide

🔌 Integrations

Email Integration Cloud Storage Integrations Voice Assistants Shop With Integrations Authentication Providers

⚙️ Develop Blackcap

Application Architecture Database Service and Data Access SQLite and PostgreSQL Database Migrations Background Job Architecture Testing Games platform — current developer reference Bramble Harvest developer tools API Architecture Security and Organization Scoping UI, Icons, and Documentation Assets Blackcap-Safe Emoji Support Chat Architecture Extending Support Chat Support Chat Model Benchmark Documentation Standards Terminology

⚠️ Troubleshoot Blackcap

⚠️ Troubleshooting Licensing Troubleshooting Deployment Troubleshooting Display Troubleshooting Recipe Import Troubleshooting 🤖 AI Troubleshooting Backup Troubleshooting Database Troubleshooting Diagnostic Organization Clones Support Chat

Games platform — current developer reference

Audience: Developers and administrators
Player guides: Games overview · Bramble Harvest

This page documents maintained behavior and technical integration points. Past implementation reports and abandoned character plans are available in Git history, not in active feature documentation.

Presentation and assets

  • Games use responsive, game-specific UIs with shared navigation, stage and score indicators where applicable. Normal and fullscreen/immersive display modes do not change the authoritative game state.
  • Most arcade and puzzle screens use decorative, original WebP backgrounds such as inky_admin/static/img/games/background_<game-id>.webp. The playable board and interactive controls are separate from the artwork.
  • Card games have their own presentation CSS/JS; Pantry Path uses its own compact layout. Bramble Harvest and Flavor Lab have purpose-built interfaces.
  • Recipe Memory requires accessible cached recipe photographs to start its board; it does not generate substitutes during play.

Persistence, inspection, and cleanup

The shared game-session layer uses game_shared_progress and game_shared_sessions; Recipe Memory and trivia have dedicated progress records. Bramble Harvest uses garden, membership, event, presence, and reward records. All gameplay mutations must pass through authenticated service endpoints with revision/state validation. The global AI Seed allowance is separate from per-garden rewards.

Database Admin offers read-only inspection of Games resources. Game History retention covers eligible finished/shared sessions, Recipe Memory round history, historical garden events, and stale garden presence. It must not delete active game progress, garden state or membership, deletion approvals, or real AI Seed credits.

Bramble Harvest account settings

Character animation, seasonal visitors, ambience, and effects are preferences of the signed-in Blackcap account, not separate per-garden or per-player character equipment. The game reads them via /admin/games/api/cappy-harvest/settings and synchronizes changes on refresh/focus. Fullscreen presentation remains device/browser-local. The garden's Cappy outfit, difficulty, and stamina are shared garden state instead.

Garden export and import

Gardens export as versioned .bh snapshots. The import endpoint creates a new garden with validated, bounded state (including no more than 80 beds); it does not overwrite the original, copy memberships, or duplicate external AI Seed transactions. The importing user chooses Personal or Community visibility. The format preserves the garden difficulty and stamina.

Imported coins are tracked as a subset of the available balance: ordinary spending draws down the imported reserve, while AI Seed purchasing requires eligible, newly earned coins, adequate reputation, and accumulated daily allowance. A portable file is not a cryptographically secure proof of fresh gameplay; external-credit protection requires stronger provenance if policy changes.

Multiplayer events and UI

Garden mutations and revisioned event deltas drive the shared garden display. Viewers replay visual work and sale receipts in event order when possible; when events are missing, the client adopts authoritative state instead of fabricating intermediate actions. The presence/refresh cycle keeps shared state up to date. Shop, Sell, and Growing Now may stay open through remote updates; editing dialogs are protected from interruption. Every physical action and stamina purchase must be transactionally validated against the current shared revision.

Validation

Developer scripts and tests live under tests/ and tools/. Stamina/order balancing simulation scripts are optional and are not required for production. See Bramble developer tools for console-only visual previews, including the first-time player introduction.

On this page