Chanora — Proofs of Concept
This directory holds non-product technical spikes. They exist to retire risk before the Flutter/Rust product scaffold is created.
Authority: docs/architecture/proof-of-concept-plan.md.
Rule (PoC plan §4): A PoC is not product code unless explicitly promoted. Nothing here should be imported by the future
apps/chanora_flutterorcrates/chanora_*trees.
Status
| Spike | Required by PoC plan | Status |
|---|---|---|
tsclientlib-connect-spike |
yes | PASS — see tsclientlib-connect-spike/VERIFICATION.md |
flutter_rust_bridge_hello |
yes (flutter-rust-bridge-hello in plan) |
PASS — see flutter_rust_bridge_hello/VERIFICATION.md |
secure-storage-spike |
yes | PASS (Linux only) — see secure-storage-spike/VERIFICATION.md |
sqlite-storage-spike |
yes | PASS — see sqlite-storage-spike/VERIFICATION.md |
diagnostics-redaction-spike |
yes | PASS — see diagnostics-redaction-spike/VERIFICATION.md |
audio-capture-playback-spike (desktop half) |
yes | PASS — see audio-capture-playback-spike/VERIFICATION.md |
audio-capture-playback-android-spike (mobile half) |
yes | PASS — see audio-capture-playback-android-spike/VERIFICATION.md |
linux_voice_test |
no (extra Linux backend spike) | PASS — see linux_voice_test/VERIFICATION.md |
ts3-manual-research |
no (extra TS3 protocol research spike) | PASS — see ts3-manual-research/VERIFICATION.md |
tsclientlib-query-spike |
no (extra TS3 protocol research spike) | PASS — see tsclientlib-query-spike/VERIFICATION.md |
tsclientlib-channel-query-spike |
no (extra TS3 protocol research spike) | PASS — see tsclientlib-channel-query-spike/VERIFICATION.md |
tsclientlib-filetransfer-spike |
no (extra TS3 protocol research spike) | PASS — see tsclientlib-filetransfer-spike/VERIFICATION.md |
tsidentity-import-spike |
no (extra TS3 protocol research spike) | PASS — see tsidentity-import-spike/VERIFICATION.md |
Naming note
flutter_rust_bridge_hello is listed in the PoC plan as
flutter-rust-bridge-hello. The directory on disk uses underscores
because the Dart pubspec.yaml package-name grammar forbids hyphens.
This is a naming convention, not a scope change.
What "verified" means here
Each verified spike contains:
- a
README.mddescribing scope, exit criterion, and reproduction; - a
VERIFICATION.mdrecording the exact toolchain versions, command, observed output, and an honest list of things the spike does not validate.
Spikes are intentionally narrow. They do not approximate Chanora architecture layering, they do not implement the documented DTO catalogue, and they do not stand in for the product Rust crates or Flutter modules.