commit bb503b6caf782c3381827d0391597f66c7960e5e
Author: empiric <info@the-empiric.com>
Date:   Fri Feb 13 06:03:14 2026 +0000

    Add 'README'
    
    Created README file.

diff --git a/README b/README
new file mode 100644
index 0000000..1e99e76
--- /dev/null
+++ b/README
@@ -0,0 +1,74 @@
+# Empiric Issues
+
+Public issue tracker for the Empiric ecosystem.
+
+This repository is used to report bugs, request features, and track development across all Empiric projects, including:
+
+* Server infrastructure
+* AI systems (TTS, STT, LLM services)
+* Web platform and integrations
+* Unity experiences and interactive components
+* Community tools and automation
+* Related services under the Empiric ecosystem
+
+This repository does not contain source code. It exists solely for issue tracking and roadmap visibility.
+
+---
+
+## Before Creating an Issue
+
+Please:
+
+* Search existing issues to avoid duplicates.
+* Provide clear and structured information.
+* Include logs, screenshots, or reproduction steps when applicable.
+
+Incomplete reports may be marked as `needs-info`.
+
+---
+
+## How to Report a Bug
+
+Include:
+
+* A clear description of the problem
+* Steps to reproduce the issue
+* Expected behavior
+* Actual behavior
+* Environment details (OS, browser, device, etc.)
+* Relevant logs or screenshots
+
+The more precise the report, the faster it can be validated.
+
+---
+
+## Feature Requests
+
+When suggesting a feature:
+
+* Explain the problem it solves
+* Describe the expected outcome
+* Clarify whether it affects a specific component (server, AI, web, Unity, etc.)
+
+Not all feature requests will be implemented, but all structured suggestions are reviewed.
+
+---
+
+## Security Issues
+
+Do not post security vulnerabilities publicly.
+
+If you discover a security issue, contact the maintainer directly through private channels.
+
+---
+
+## Scope
+
+This tracker covers all systems developed under the Empiric ecosystem. Third-party software bugs (e.g., external platforms or services) should be reported to their respective maintainers.
+
+---
+
+Maintained by the Empiric development team.
+
+---
+