LYNDA remains the approved intelligence identity across the public site and authenticated customer experience.
CENTRAL OXS INTELLIGENCE
One LYNDA identity.
Strict knowledge boundaries.
This milestone defines how LYNDA separates public guidance from authenticated tenant intelligence without silently increasing what a person may see or do.Public questions use approved AdamaIQ knowledge. Tenant-private retrieval remains locked until identity, membership and authority are verified.
An authenticated request must carry one exact OXS tenant and active membership; portfolio visibility never becomes tenant authority.
One approved voice and pronunciation profile is requested from OXS, with only one audio session allowed per browser.
Public use has a defined rate-limit contract and is not an unlimited general-purpose AI service.
Live customer knowledge stays off until gateway, denial tests, provenance, monitoring and explicit production approval pass.
LYNDA OBJECT HANDOFF
Prepared for the approved master.
The existing governed fallback remains public while the final object is completed. No draft or partially approved media can replace it.- 01 · face masterAwaiting asset, integrity hash and separate owner approval.
- 02 · sphere motionAwaiting asset, integrity hash and separate owner approval.
- 03 · voice masterAwaiting asset, integrity hash and separate owner approval.
- 04 · combined masterAwaiting asset, integrity hash and separate owner approval.
- 05 · reduced motion fallbackAwaiting asset, integrity hash and separate owner approval.
ACTIVATION GATES
Private knowledge requires proof.
- IdentityVerify the person through the approved customer identity provider.
- MembershipResolve one active OXS membership for the requested tenant.
- PermissionApply role, record, location and purpose boundaries server-side.
- ProvenanceAttach sources, tenant, policy decision and response trace.
- AcceptancePass denial, isolation, rate-limit and monitoring tests before activation.