diff --git a/README.md b/README.md index 5bbf769..49320cc 100644 --- a/README.md +++ b/README.md @@ -126,3 +126,37 @@ To ensure sensitive environments, release archives, or private signing keys are --- *Droid Commander `v1.0.0-RELEASE` — CodePhrex Mobile Security Orchestration Engine* + +## Current UI inventory and implementation status (2026-10-25) + +The UI specification manual defines **14 numbered screens** and the project owner has confirmed **four additional screens** for the working inventory: USB OTG Hardware Inspector, Cellular & Dual-SIM Diagnostics, Wireless & Network Diagnostics, and Automated Remediation Playbooks. This is an inventory of intended screen entries, not a claim that exactly 18 routes are currently registered or that every described capability is production-ready. + +### Current primary navigation + +The current `app/(tabs)/_layout.tsx` declares five visible tabs: + +1. **Command** — operations dashboard / host assessment entry point. +2. **Assess** — local security assessment. +3. **Sessions** — assessment history and privileged-action ledger disclosure. +4. **Threat Intel** — vulnerability/reference catalog. +5. **USB Link** — USB host discovery and service handoff. + +Additional source files may exist outside these primary tabs. A source file's presence does not prove that a screen is reachable from navigation. + +### Evidence and capability boundaries + +The current source audit found several places where UI data must not be described as live device evidence without a verified collector: + +- The vulnerability scanner v3 initializes a sample Galaxy S24 telemetry profile in its screen state. Treat it as illustrative until it is populated from the current host assessment and its provenance is displayed. +- The USB OTG hardware inspector currently passes a hard-coded example USB descriptor and power telemetry into its evaluation engine. This is simulated inspection input, not proof of live USB discovery. +- The SIM diagnostics screen calls a cellular telemetry engine and carrier-token submission method; actual Android/carrier capability and any state-changing effect require separate platform and device verification. +- The wireless diagnostics screen calls a wireless manager; real Wi-Fi/Bluetooth discovery and wireless-debugging control must be verified against Android permissions, OS restrictions, and native implementation. +- The remediation screen calls an engine after a timed UI delay. The delay or success-looking UI is not evidence that a live mitigation or carrier recovery occurred. + +Use explicit evidence states such as **verified**, **reported**, **simulated**, **unavailable**, and **unknown**. Unknown or permission-denied readings must not be silently treated as clean. Include source and collection timestamp where available. CVE correlation indicates potential applicability, not proof that an exploit ran or that a vulnerability is present. + +### Screen audit and release status + +The exhaustive screen audit is in progress. It must distinguish: (1) the specification, (2) active Expo Router routes, (3) legacy/unrouted components, (4) implemented logic, (5) simulated or placeholder behavior, and (6) native/device verification. Several filenames listed in older screen documentation were not found at the exact `app/(tabs)/` paths checked; this is not by itself proof that the feature is absent, because legacy components and replacement implementations may live elsewhere. + +No UI redesign or hardware capability is implied by this documentation update. Browser preview, automated tests, Android build/signing, and physical-device/USB validation are separate gates. Do not describe the app as production-ready or hardware-verified unless the relevant checks have actually passed. diff --git a/TODO.md b/TODO.md index 2013130..253cd82 100644 --- a/TODO.md +++ b/TODO.md @@ -262,3 +262,27 @@ Source evidence (October 21, 2026): native local collector and USB inventory lib - [x] Universal arbitrary shell, arbitrary code/exploit payload, silent lock-screen bypass, silent OEM unlock, unattended flashing, and credential-extraction declarations are rejected by policy. - [x] The contract and native-integration boundary are documented in `VENDOR_CAPABILITY_PROVIDER.md`. - [ ] Connect a real manufacturer/provider SDK, certificate trust-anchor rotation, UI confirmation surface, and native completion callbacks after vendor authorization and lab validation. + +## Exhaustive UI screen audit — documentation update (2026-10-25) + +### Inventory and navigation +- [ ] Maintain a screen-by-screen audit for the 14 numbered manual entries plus the four confirmed additions: USB OTG Hardware Inspector, Cellular & Dual-SIM Diagnostics, Wireless & Network Diagnostics, and Automated Remediation Playbooks. +- [ ] For each entry, record the specification title/purpose, source file, Expo Router route, navigation entry point, implementation status, placeholder/simulated behavior, platform limitations, and acceptance tests. +- [ ] Distinguish active routes from legacy components and non-screen technical routes. The five visible tabs currently declared in `app/(tabs)/_layout.tsx` are Command, Assess, Sessions, Threat Intel, and USB Link. +- [ ] Reconcile legacy filenames in the UI manual with the current source tree; a missing file at an expected path is not sufficient evidence that the feature is absent. + +### Evidence integrity and hardware capability +- [ ] Replace the scanner v3 hard-coded Galaxy S24 example telemetry with the authoritative host assessment source; display source, timestamp, and unknown/unavailable states. +- [ ] Replace or explicitly label the USB hardware inspector's hard-coded Kingston descriptor and sample power values as simulated until live USB discovery and telemetry are wired and tested. +- [ ] Verify cellular telemetry and carrier-token workflow against supported Android APIs and authorized carrier procedures; do not claim an unlock or modem state change without observed confirmation. +- [ ] Verify wireless scanning and wireless-debugging controls against native module implementation, Android permission requirements, and OS restrictions. +- [ ] Verify each remediation playbook's real effect and postcondition; UI delay, action history, or a success message alone is not proof of mitigation. +- [ ] Ensure unavailable, denied, stale, simulated, and inconclusive evidence cannot be rendered as a clean/secure state. + +### Validation gates +- [ ] Complete source/route audit and update the screen matrix. +- [ ] Run static checks, lint, unit tests, and screen-contract tests after documentation and any future implementation changes. +- [ ] Validate browser preview separately from native build/signing. +- [ ] Validate splash-to-home launch on the Galaxy A15 using a newly built APK before diagnosing device behavior as fixed. +- [ ] Test USB OTG and other hardware-dependent flows on supported physical devices; do not infer hardware behavior from web previews or mocks. +- [ ] Obtain approval for proposed visual designs before changing screen UI. diff --git a/ui-style-architecture-guide.md b/ui-style-architecture-guide.md index 323a9ce..75c0a8d 100644 --- a/ui-style-architecture-guide.md +++ b/ui-style-architecture-guide.md @@ -109,3 +109,48 @@ The Droid Commander UI suite comprises **14 complete React Native screens**: | `passkey-break-glass-screen.tsx` | Passkey Break-Glass Override | Countdown timer, 1-tap passkey biometric prompt | | `ledger-inspector-screen-v2.tsx` | Privileged Action Ledger | Hash verification scan line, tamper simulation | | `reports-vault-screen-v2.tsx` | Compliance Reports Vault | Progress-tracked PDF compilation, Studio exporter | + +## 7. Current route and screen audit notes (2026-10-25) + +### 7.1 Inventory rule + +The specification manual documents 14 numbered screens. Four additional confirmed entries expand the working inventory to 18: + +15. USB OTG Hardware Inspector +16. Cellular & Dual-SIM Diagnostics +17. Wireless & Network Diagnostics +18. Automated Remediation Playbooks + +The inventory count is not a route count. The current `app/(tabs)/_layout.tsx` registers five visible tabs: Command, Assess, Sessions, Threat Intel, and USB Link. Other Expo Router files, legacy root-level components, recovery routes, OAuth callbacks, and developer tools must be classified separately. Do not count a component as a reachable screen until route and navigation wiring are verified. + +### 7.2 Evidence-backed source observations + +- `app/(tabs)/vulnerability-scanner-screen-v3.tsx` initializes telemetry with a hard-coded Galaxy S24 example profile. Before presenting it as live, wire it to the authoritative host assessment collector and show evidence source, timestamp, and unavailable/unknown states. +- `app/(tabs)/usb-hardware-inspector-screen.tsx` currently evaluates a hard-coded example Kingston device descriptor and sample VBUS/current readings after a timeout. Label this as simulation until connected to actual USB descriptor and power telemetry. +- `app/(tabs)/sim-diagnostic-screen.tsx` calls `CellularTelemetryEngine` for telemetry and carrier-token submission. Confirm actual platform support and distinguish carrier-authorized workflow from a real modem/carrier state change. +- `app/(tabs)/wireless-diagnostics-screen.tsx` calls `WirelessManager` for Wi-Fi/Bluetooth scans and wireless-debugging actions. Verify native implementation, runtime permissions, Android version behavior, and failure reporting. +- `app/(tabs)/remediation-playbooks-screen.tsx` calls remediation-engine methods after UI delays. Verify each action's actual effect and postcondition; do not infer success from the delay, button state, or history entry alone. +- `app/(tabs)/sessions.tsx` uses local assessment history and verifies the privileged-action ledger. Keep storage/verification errors visible rather than implying an immutable or complete history when verification fails. + +### 7.3 Required UI evidence language + +Use consistent state labels: +- **Verified** — measured or cryptographically checked by a named, functioning collector. +- **Reported** — supplied by an OS/API or remote service but not independently verified. +- **Simulated** — sample, fixture, demo, or test input. +- **Unavailable** — the platform, permission, device, or module cannot provide the reading. +- **Unknown** — evidence is missing, stale, or inconclusive. + +Every live telemetry panel should show source and last-updated time when available. Never convert a denied or unavailable read into a secure/clean result. CVE matches are evidence-qualified potential matches, not proof of exploitability or successful exploitation. + +### 7.4 UI and device validation are separate + +Visual design approval does not certify implementation. The preferred validation sequence is: +1. Static source/route audit and screen contract tests. +2. Browser preview and type/lint/unit checks. +3. Native Android build and signing verification. +4. Install/launch checks on the target handset. +5. Physical USB OTG, SIM, wireless, and other hardware checks on supported devices. +6. Verify state-changing workflows using authorized test fixtures and safe, reversible test conditions. + +Do not claim a stage passed until there is a corresponding result. UI redesign remains subject to owner approval.