Review & Content Quality Intelligence · Documentation
How to Use This Demo
Driving Review & Content Quality Intelligence in the host, the Cloud/OSS inspector, and the operator console — with honest labels.
← Review & Content Quality Intelligence- 1
Signing in
The ecosystem is gated. Open the live demo and sign in as the universal owner (admin / admin@123) to run classification and make moderation decisions, or as the read-only viewer to observe the queue and the published wall. The owner-only configuration (the Layer-2 overlay) is never sent to the browser for an unauthorized session.
- 2
Driving the queue
Open app 05 from the launcher. The operator console opens on the moderation queue — every pending review with a status pill. Pick a review and press Classify: the one metered stage runs and the detail panel fills with the category (clean / spam / abuse / pii / off-topic), a toxicity reading, a 0–100 quality score, the rule hits, and a suggestion. Then approve, hold, or reject. Approving publishes the review to the property detail wall shown lower on the surface.
Open the dark "Behind the scenes" inspector to see the honesty layer: the Cloud/OSS mode toggle, the per-stage pipeline trace (Intake → Layer 1 → Layer 2 → Classify), and the cost meter. This instrumentation lives only in the inspector — the moderation surface itself shows none of it.
- 3
Configuring the rules
The owner-only CONFIGURE section holds the Layer-2 overlay: the blocked-phrase list and the hold-below-quality threshold. Layer 1 is shown read-only — it can be extended in code but not weakened from the console. Viewers see the queue and verdicts but not the configuration; the owner-only controls are absent from the DOM for a viewer session, not merely hidden.