Spaces:
Sleeping
Sleeping
metadata
title: README
emoji: 🚀
colorFrom: blue
colorTo: purple
sdk: gradio
pinned: false
short_description: A simple Gradio app
StrategyStack Recovery, Enrichment & Outreach Platform
Granular UI Features (Nov 2025)
New Compliance, Audit, Branching & Diagnostics Widgets
1. Consent/Event Audit Panel
Shows all consent events, opt-outs, and compliance flags per contact and batch.
- Backend mapping: Receives list of consent events (JSON, e.g. {contact_id, event_type, opt_out, compliance_flag}) per contact or batch.
- UI mapping: Gradio panel renders event history per contact, batch aggregation, flags out-of-policy events.
- State schema: See /docs/configs/compliance_schema.json.
2. Dynamic Cadence Branching Composer
Visual builder for editing & previewing cadence sequences (multi-step outreach flows with conditional logic)
- Backend mapping: Mirrored to cadence state JSON (see cadence_agent.py / docs/configs/cadence_tree.json)
- UI mapping: Interactive tabular/tree UI shows each step, transition, and condition (see new app.py logic).
- Inline code: Each logic widget/function takes the backend structure as argument.
3. Live Diagnostics Panel (Incidents/Health)
Shows real-time and historical such as error, warning, info events for cadence or batch operations.
- Backend mapping: List of incidents/events from backend diagnostics state (event objects: {timestamp, type, message, level})
- UI mapping: Gradio Markdown log renders type/level/message per event.
- Config: Event/incident schema in docs/configs/diagnostics_schema.json
4. Exportable Audit Trail (Compliance/Debug)
CSV/text export of event history (compliance and debug records)
- Backend mapping: Batch history as list of per-event dicts, same as consent_audit schema.
- UI mapping: Text/csv box (downloadable) shows organized history—maps to regulatory & support request export needs.
Usage & API Mapping
- All widgets assume backend compliance/cadence events via standardized JSON from respective APIs (see /api/diagnostics, /api/cadence, /api/compliance, etc).
- See app.py for inline documentation on each panel/component; argument signatures require the backend state JSON (typically list[dict]).
Inline Documentation Examples (app.py)
- Each widget (audit, diagnostics, branching, export) is documented inline for both UI and state/JSON structure.
- You can customize backend structure via docs/configs/ files and panel logic will adopt new schemas as format evolves.
Example Panel Usage
Example construction is provided in app.py showing default data structures and rendering each widget in a Gradio tab.
(legacy platform and API docs retained below)