Contextual Multimodal Frame Injection Brief

Role: Lead Android Client Architect for Generative Experiences

Context

• Minimum supported Android API: {{target_android_api}}
• Primary visual input stream: {{source_camera_feed}}
• Orchestration layer framework: {{prompt_orchestration_layer}}
• Multimodal token context budget: {{token_budget_limit}}
• Target user interaction modality: {{user_interaction_mode}}
• User data protection protocol: {{privacy_redaction_policy}}

Task

Author a comprehensive multimodal prompting system brief that defines how client-side visual context from {{source_camera_feed}} and UI state within {{target_android_api}} is captured, sanitized, token-optimized, and dispatched via {{prompt_orchestration_layer}}.

Method

1. Establish the window and view sampling strategy for capturing spatial coordinates and visual state without interrupting {{user_interaction_mode}}.
2. Construct the transformation pipeline converting {{source_camera_feed}} bitmap streams into quantized image patches matched with dynamic token limits in {{token_budget_limit}}.
3. Implement the client-side redaction interceptor enforcing {{privacy_redaction_policy}} before any prompt payload serialization.
4. Design the structured system prompt template containing dynamic slots for device orientation, localized UI context, and visual frame tokens.
5. Detail the state machine governing prompt assembly, dispatch via {{prompt_orchestration_layer}}, and UI response rendering.
6. Specify error handling for partial frame ingestion, prompt token overflow, and network-level retries.
7. Define telemetry hooks to evaluate multimodal prompt accuracy and visual grounding fidelity on client devices.

Constraints

• MUST enforce strict PII scrubbing and on-device masking according to {{privacy_redaction_policy}} before serialization.
• MUST NOT retain raw unredacted image buffers in unencrypted persistent storage or heap memory.
• Keep client payload overhead minimized to ensure low-bandwidth operability.
• Maintain complete architectural alignment with Android Jetpack Compose and Modern Android Architecture guidelines.

Output format

1. System Context & Data Flow Architecture (200 words)
2. Frame Capture & Redaction Pipeline (Step-by-step technical contract)
3. Multimodal Prompt Token Allocation Map (Exact budget breakdown table)
4. Client-Side Orchestration State Machine (State transitions and error branches)
5. Security & Compliance Implementation Guidelines (Enforcement checklist)

Self-review

• Ensure the prompt payload structure respects the limitations of {{token_budget_limit}}.
• Confirm that {{privacy_redaction_policy}} is enforced prior to passing data to {{prompt_orchestration_layer}}.
• Validate that all lifecycle-aware components handle Android configuration changes seamlessly.