docs: truth-audit cleanup — correct customer/adoption claims + delete stale infra-contradicting decks

README.md

@@ -285,6 +285,6 @@ See design documentation:
 
 ---
 
-**Documentation Last Updated:** 2026-02-17
+**Documentation Last Updated:** 2026-06-11
 **Documentation Version:** 2.4 (Added Multi-Modal Authentication Module)
 **Project Version:** 1.0.0-SNAPSHOT

adr/0001-hosted-first-oidc.md

@@ -6,7 +6,7 @@
 
 ## Context
 
-FIVUCSAS originally shipped as an embeddable iframe widget that tenants dropped into their site, with the user typing credentials and completing MFA inside the iframe. The widget proved brittle across the surfaces that real customers need to cover:
+FIVUCSAS originally shipped as an embeddable iframe widget that tenants dropped into their site, with the user typing credentials and completing MFA inside the iframe. The widget proved brittle across the surfaces that real-world integrations need to cover:
 
 - **Web NFC** cannot be used inside a cross-origin iframe — the spec restricts the API to top-level browsing contexts. NFC-driven authentication (Turkish e-ID, MRZ-bearing documents) was effectively dead in-iframe.
 - **WebAuthn / passkeys** suffer cross-origin edge cases. Cross-origin iframes carry restrictive Permissions Policy defaults, and even with `publickey-credentials-get` delegated, Safari and several embedded webviews refuse the request.

plans/BAAS_RENTAL_MODEL.md

@@ -28,7 +28,7 @@
 
 ## 1. Executive Summary
 
-FIVUCSAS has evolved from a university project into a production-grade biometric platform with 10 authentication methods, identity verification, and an embeddable auth widget. The next commercial step is offering individual biometric capabilities as rentable APIs -- Biometrics as a Service (BaaS). Developers should be able to sign up, get an API key, and call `POST /v1/face/verify` without deploying any infrastructure. This document defines the pricing tiers (Free/Developer/Enterprise), API gateway architecture with per-key rate limiting, feature isolation model, usage metering pipeline, SDK distribution strategy (npm, Maven Central, CocoaPods), and developer portal experience. The target is to make FIVUCSAS as easy to integrate as Stripe is for payments.
+FIVUCSAS, a university capstone biometric platform with 10 authentication methods, identity verification, and an embeddable auth widget, could be extended commercially by offering individual biometric capabilities as rentable APIs -- Biometrics as a Service (BaaS). Developers should be able to sign up, get an API key, and call `POST /v1/face/verify` without deploying any infrastructure. This document defines the pricing tiers (Free/Developer/Enterprise), API gateway architecture with per-key rate limiting, feature isolation model, usage metering pipeline, SDK distribution strategy (npm, Maven Central, CocoaPods), and developer portal experience. The target is to make FIVUCSAS as easy to integrate as Stripe is for payments.
 
 ---