diff --git a/README.md b/README.md
index ef4dca2..3bd5c9b 100644
--- a/README.md
+++ b/README.md
@@ -1 +1,53 @@
-# CS35L27-firmware-analysis
\ No newline at end of file
+# CS35L27 Firmware and Runtime Forensic Analysis
+
+This repository documents the ground-truth results of forensic analysis of the CS35L27 amplifier firmware, configuration, and runtime behavior.  
+**All observed behaviors, features, and command usage are described strictly as documented in device binaries and operational logs, without speculation or narrative interpretation.**
+
+---
+
+## Unexplained or Undocumented Capabilities
+
+During analysis, several **unknown or undocumented technical behaviors and capabilities** were observed, including but not limited to:
+- Use of extended/undocumented I2C commands
+- Code paths enabling uncommon hardware features (e.g., bidirectional I2S)
+- High-frequency toggling of specific GPIO bits
+
+**These cannot be fully explained based solely on available public documentation and the data present on the device.**
+
+---
+
+### Vendor Review Required
+
+- The presence of these capabilities and their extensive use at runtime **require clarification from the chip or device vendor** to determine whether they represent intended behavior or pose security/privacy risks.
+- **No claims of confirmed vulnerabilities are made in this repository:** rather, there is a strong recommendation that the vendor or a qualified third party review these technical findings to rule out potential backdoors or misuse.
+
+---
+
+## Repository Structure
+
+```
+CS35L27-firmware-analysis/
+├── docs/
+│   └── analysis-methods.md            # Data sources and analytic procedures
+├── report/
+│   ├── findings.md                    # Core observed technical findings
+│   ├── technical-details.md           # Assembly, register, and bit-level details
+│   ├── runtime-trace-analysis.md      # Objective TraceV3 runtime evidence
+│   └── comparison-and-correlation.md  # Firmware <-> runtime cross-reference table
+```
+---
+
+**Each file reports only measured, observable facts from the corresponding source(s). No speculation or narrative is included.**
+
+---
+
+*Continue with your “Unexplained or Undocumented Capabilities” and “Vendor Review Required” sections…*
+
+## Scope Statement
+
+- All findings are based strictly on direct binary and trace analysis—no assumptions or attack scenarios are included.
+- This repository is intended as an evidence-based platform for deeper review, vendor clarification, and possible reference device comparison.
+
+---
+
+**If you are a vendor, developer, or security professional with access to reference documentation or source code, analysis contributions and clarifications are welcome to aid in definitive assessment.**