1
WandGx builds or understands the app
The app context manifest keeps workflows, roles, screens, and privacy labels visible so the app is understandable after launch.
Adaptive Business OS product lane
Build the app, spot the struggle, and ship the training beside the workflow.
WandGx is the AI app factory. SET is the living training layer. Together they help business apps teach the team how to use them, detect where people struggle, and keep the app, SOPs, quizzes, and lessons aligned as the business changes.
Early access beta scope: the local proof shows the WandGx to SET loop, published artifacts, and manual-review guardrails. Production hardening, customer-specific rollout, and any compliance certification stay separate.
Demo app
PainterQuote Pro
Workflow
quote-create
Role
estimator
Detected struggle
surface prep / pricing confusion
Fix type
training_gap with reviewable app guidance
SET artifacts
learning_path, quiz, sop, micro_lesson
Closed loop
The loop customers can understand in one pass
The demo is intentionally concrete: one app, one workflow, one role, one struggle, one signed handoff, and four published SET artifact types mapped back into WandGx.
2
Hosted apps emit privacy-safe telemetry
Generated and hosted apps can report adoption patterns and workflow friction without sending raw customer field values or secrets.
3
WandGx detects user struggle
Repeated estimator friction in quote-create becomes a reviewable insight tied to the exact workflow, role, and app surface.
4
WandGx prepares the fix and handoff
The system creates a fix proposal and a signed SET training handoff instead of silently changing behavior or publishing training.
5
SET publishes role-based training
SET turns the handoff into approved learning artifacts for the estimator role: a path, quiz, SOP, and micro-lesson.
6
WandGx shows the training beside the workflow
The Adaptive OS control view maps published artifacts back to the app, workflow, role, insight, and proposed fix.
7
Sensitive handoffs stay guarded
Confidential, regulated, phi_possible, and cjis_possible labels remain manual-review only and are not auto-synced in the demo loop.
Why this is different
Not just an app builder. Not just an LMS.
The value is the connection between software, adoption evidence, fixes, and training. Each part makes the others more useful.
App builders
Usually stop after generating or shipping the first version of the software.
LMS tools
Usually publish training separately from the live app workflow where people are struggling.
Adaptive Business OS
Keeps the app, adoption signal, fix proposal, training package, and review proof connected in one operating loop.
Workspace link
One customer workspace, one command center, one training layer.
The customer should not feel like they bought two disconnected apps. WandGx is where the business app is built and managed. SET powers the training behind it. The link is the app workflow, role, and version, so training points back to the exact place the team is struggling.
One company workspace
The customer gets one company workspace, one WandGx workspace, and one linked SET training workspace. They do not manage two unrelated products.
Training Layer Connection
The Adaptive OS Workspace Link stores the SET tenant, base URL, handoff endpoint, status endpoint, connection mode, health, sync state, and manual-review policy without storing raw secrets.
App linkage
Each generated app is mapped to SET by tenant, app id, app version, workflow id, role id, handoffId, proposalId, trainingManifestId, artifactId, and artifact type.
User roles
Operators use WandGx as the command center, trainers open SET Adaptive Training, and team members use the app with training support tied to the workflow they are using.
Early access path
What early access includes
Early access is for operators who want to demo the WandGx plus SET loop, choose one real workflow, and move through manual review before anything sensitive is synced. The first demo shows the app context, detected workflow struggle, reviewable fix proposal, SET handoff, published artifacts, and WandGx proof beside the workflow.
Included in early access
- A guided demo of the PainterQuote Pro loop with app context, workspace link, workflow struggle, SET handoff, and published training artifacts.
- A discovery call to choose the first company workspace, WandGx app, SET training workspace, workflow, role, privacy label, and training source documents.
- Operator-run setup using manual review for confidential, regulated, phi_possible, and cjis_possible handoffs.
- A safe first build or app-understanding path through the existing WandGx build flow when the prospect is ready.
What is not included yet
- No HIPAA, CJIS, SOC2, or compliance certification claim.
- No automatic sync of confidential, regulated, phi_possible, or cjis_possible data without explicit operator approval.
- No promise that SET training status equals WandGx app hosting status.
- No full production enterprise rollout before customer-specific hardening, legal review, and deployment decisions.
PainterQuote Pro story
A simple demo story with exact artifacts
PainterQuote Pro gives the Adaptive Business OS loop a concrete business scenario. It is easier to trust because the page names the app, workflow, role, struggle, handoff, and published outputs.
App
PainterQuote Pro, a WandGx-built painting quote app
Workflow
quote-create
Role
estimator
Struggle
Estimators need clearer help with surface prep and pricing decisions while creating a quote.
WandGx output
A workflow-level struggle insight, a reviewable fix proposal, and a signed SET handoff.
SET output
learning_path, quiz, sop, and micro_lesson artifacts for the estimator role.
Private, local, and regulated workflows
Sensitive data stays guarded by default
The Adaptive Business OS story is strongest when the guardrails are explicit. Local and private routing can demonstrate the loop without turning sensitive labels into automatic syncs.
Confidential, regulated, phi_possible, and cjis_possible handoffs stay manual-review only. They do not auto-sync in the local demo path.
Private or local routing matters for hospitals, police stations, government teams, legal offices, finance teams, and other sensitive businesses.
The local demo proves the handoff loop, published status, and guardrail behavior. It is not a HIPAA, CJIS, or compliance certification claim.
SET availability is reported as training-sync status. It must not imply that WandGx app hosting is blocked when an eligible app is otherwise ready.
Admin proof
What the Adaptive OS admin should prove
- Published SET artifacts are shown only when the demo report or status endpoint has evidence of published artifacts.
- Manual-review messaging stays visible for sensitive labels so operators understand why a handoff did not auto-sync.
- Unavailable SET status should be shown as unavailable or blocked, not as a fake success state.
Customer talk track
The one-minute explanation
WandGx does not stop at generating a business app. It keeps the app understandable, watches for privacy-safe signs of user struggle, proposes the right app or training fix, hands training work to SET for approval and publishing, then shows the resulting learning artifacts back beside the exact workflow where the struggle happened.
Show the loop live
Use the public story to explain the promise, then open the admin proof page to show the live Adaptive OS loop, status, guardrails, and published SET artifacts when the demo smoke has produced them.