# Proof-of-Concept Plan

**Document type:** Architecture / Proof-of-Concept Plan  
**Version:** 0.1.0  
**Status:** Draft  
**Language:** English  
**Product:** Chanora  
**Repo path:** `docs/architecture/proof-of-concept-plan.md`

---

## 1. Purpose

This document defines technical proof-of-concept work that should be completed before heavy product implementation.

## 2. Required PoCs

| PoC | Purpose | Exit criteria |
|---|---|---|
| Flutter/Rust bridge hello | Prove command/result/event DTO boundary | Flutter can call Rust and receive event stream data |
| `tsclientlib` connect spike | Prove protocol feasibility | Rust can connect to a compatible server/test double |
| Audio capture/playback spike | Prove platform audio behavior | Capture/playback works on at least one desktop and one mobile target |
| Secure storage spike | Prove secret storage behavior | Secret write/read/delete works through platform secure storage |
| SQLite storage spike | Prove local non-secret persistence | Schema, migration, and repository pattern are demonstrated |
| Diagnostics redaction spike | Prove redaction before export | Password and identity-secret samples are redacted |

## 3. PoC Directory

Recommended future location:

```text
poc/
  flutter-rust-bridge-hello/
  tsclientlib-connect-spike/
  audio-capture-playback-spike/
  secure-storage-spike/
  sqlite-storage-spike/
  diagnostics-redaction-spike/
```

## 4. Rule

A PoC is not product code unless explicitly promoted.

## 5. Change History

| Version | Date | Description |
|---|---|---|
| 0.1.0 | 2026-05-14 | Initial proof-of-concept plan. |