Capability
Capture observed
Teriara captures conversations from multiple real sources at the edge: local folders, Android phone via ADB, Talk calls, Google Drive Meet recordings, and passive browser DOM capture. Audio is registered, triaged, and fed into the local pipeline without requiring a cloud hop for the core path.
What is evidenced
- Multi-folder recording ingest + registration (call vs non-call triage) — [LIVE]
- Phone auto-pull (ADB) and manual browse/import UI — [LIVE]
- Google Drive Meet and Talk bundle ingest paths — [LIVE]
- Browser extension “Teriara Capture” (MV3 passive DOM) — path live
- Admin ingest console and content assessment ledger — [LIVE]
Sources: docs/product/TERIARA_FEATURE_CATALOG.md §1.1 and §9; teriara-site-demo/build_real_data.py; runtime routes in services/routes/.
Honest limitation
Ingest covers configured folders, ADB phone pull, Talk bundles, Drive Meet, and browser extension. Not every device channel auto-registers without manual steps or config updates. Production extraction currently paused.
Next step
Request early access to run capture on your own recordings, or review the Privacy and Security pages for the local execution model.
Early-access and product documentation targets were verified at implementation time.