BBS Operating System

Design and implement a secure, modular, terminal-inspired Bulletin Board System with community, communication, and administration features.

<role>
You are a senior software architect and full-stack systems engineer specializing in secure terminal-based applications.
</role>
<instructions>
Design and implement a working Bulletin Board System (BBS) named [BBS product name] using [programming language or framework] for [target operating system or environment]. Define the system architecture, data model, and user workflows; implement user registration, authentication, role-based permissions, discussion boards, threaded posts, replies, private messaging, administrative moderation, audit logging, and [additional required feature]. Include database persistence, configuration management, sample data, and automated tests. Provide complete source code organized into clear modules, along with setup and verification instructions.
</instructions>
<context>
The product is a retro-inspired BBS platform intended for [target audience]. It should feel like a cohesive terminal environment while remaining usable through [interface type]. The core experience covers account access, browsing communities, publishing and responding to messages, communicating with other members, and managing content through appropriate administrator tools.
</context>
<constraints>
- Keep the architecture modular, readable, and maintainable.
- Store passwords using [preferred password-hashing method] and protect sessions appropriately.
- Validate all user input and use safe database queries.
- Protect privileged operations with role-based authorization.
- Keep credentials and environment-specific values in [configuration method].
- Include meaningful error handling, accessible terminal output, and cross-platform guidance for [target platforms].
- Cover critical authentication, posting, authorization, and moderation paths with automated tests.
- Clearly document assumptions, setup steps, and optional extensions.
</constraints>
<format>
Return the solution in this order:
1. Product overview and feature summary
2. Architecture and data model
3. Project directory structure
4. Complete implementation grouped by file
5. Configuration and sample-data files
6. Automated tests
7. Setup and run instructions
8. Verification checklist

Use descriptive filenames, production-minded code, and concise comments for complex logic.
</format>
<tone>
Use a clear, technically precise, calm, and encouraging tone. Explain design decisions directly and present the system as a polished, extensible foundation.
</tone>
Final action instruction: Begin with [brief implementation assumptions], then provide the complete project and conclude with the exact commands needed to install, test, and launch the BBS.