Who are we styling today? (For demo purposes — in production you'd be recognized automatically.)
Prototype for experience testing. Demo profiles illustrate DCI-informed personalization. Styling responses are provided through the connected runtime service.
For demo purposes, switch between sample personalization profiles to see how recommendations and conversations change.
Switching profiles will start a new conversation and load a different personalization profile.
Sample questions and expected runtime routes.
| Question | Expected Route | Notes | |
|---|---|---|---|
| What does Blemishes do? | KNOWLEDGE_RAG |
Product Feature Explanation is repository-governed through INTENT_FEATURE_001; Scenario is not required. | |
| I need a wedding guest look | KNOWLEDGE_RAG |
Scenario-driven recommendation | |
| Take me to Blemishes | TOOL_NAVIGATION |
Governed action resolution | |
| I have a first date tomorrow night. Give me a complete transformation plan. | PLANNER_REASONING (Controlled Validation) |
Active Validation path: repository-governed Planner eligibility (INTENT_FEATURE_004) permits bounded Planner execution. Validated evidence: Planner Generation = PLAN, Planner Output Validation = Passed, LLM Execution = Completed, fallback_used = false. Limited to this validated intent; other Planner intents are not covered. |
| Question | Expected Behavior | Notes | |
|---|---|---|---|
| How does Brighten Skin work? | Repository Intent Match → INTENT_FEATURE_001 · Knowledge / RAG Route · Scenario optional |
Scenario is optional / not required by the Intent context contract (required_context = NONE). Scenario resolution may still execute and report no active Scenario. |
Reviewer convenience examples for the Worker's Conversation Context Composer stage. These are NOT production-certified expectations — the actual composition_mode/composition_status for any turn is reported only by the Worker's "Conversation Context Composition" runtime_log entry, viewable in the Architecture Runtime Trace above.
| Message | Expected Behavior | |
|---|---|---|
| hair | Broad subject may require governed clarification. | |
| Yes | Meaning depends on active governed clarification context; must not be invented without valid context. | |
| Actually, cancel my subscription. | Explicit independent request should override stale pending clarification context and enter normal routing. |
Validation panel exists to verify runtime routing behavior against the current repository-driven architecture using a POC Runtime Export (Controlled Validation). This is intended for architecture review, demo validation, and regression testing. It does not represent production publication or production approval.