Profile Slices
Return only the parts of a user's CanonIQ profile that a product is scoped to receive, such as decision style, values, timing context, preference signals, and consent scope.
CanonIQ API lets approved products adapt around who a user is, what they need, and what they have consented to share.
Use CanonIQ to reduce cold starts, personalize onboarding, improve recommendations, route users to better next steps, and make context-aware experiences feel less generic — without exposing the full user profile.
Currently accepting early API conversations, design partner requests, and integration discovery.
Traditional sign-in tells your product who has access.
CanonIQ helps your product understand how to serve the person.
CanonIQ becomes the context layer between the person and the internet — so users can bring their context with them, and products can adapt around it.
Users should not have to explain themselves from scratch every time they open a new product. CanonIQ gives people a way to carry approved context across products, with control over what is used, where, and why.
Products can request approved CanonIQ profile slices and use them to personalize onboarding, recommendations, next actions, offers, resource routing, explanations, and interface defaults.
Bring your CanonIQ with you.
CanonIQ becomes the context layer between the person and the internet, allowing approved products to adapt around who the user is, what they need, and what they have consented to share.
Most products personalize from local behavior: what someone clicked, watched, bought, searched, or ignored. CanonIQ adds a traceable operating intelligence layer — what a person values, what they avoid, what they are trying to do, how they make decisions, and what kind of help is actually useful.
Most AI products and recommendation systems start with limited context. They ask users to repeat themselves, generate generic outputs, or personalize from shallow demographic and behavioral signals. CanonIQ provides structured identity, values, decision, preference, context, timing, and intent signals that product teams can use to create more relevant experiences.
Start with permissioned identity intelligence instead of making every product interaction begin from zero.
Adapt recommendations, messaging, onboarding, offers, and product flows around how a person actually decides.
Use better context to match the right message, moment, product, or next action to the user.
Give your preferred LLM structured context up front so it spends less effort reconstructing the user.
User builds or connects context
A user creates CanonIQ or builds product-specific profile signals through supported experiences.
Product requests a profile slice
An approved product asks for only the context needed for a specific surface or use case.
CanonIQ applies consent and sensitivity rules
The API filters context based on user permission, product scope, sensitivity, and portability settings.
The product adapts the experience
The product can personalize onboarding, recommendations, resource routing, offers, copy, layout, defaults, or next actions.
Start closer to the user's actual needs instead of asking every question from scratch.
Rank options using approved context, moment signals, preferences, constraints, and feedback.
Show more relevant offers at better moments without exposing the user's full profile.
Surface grants, jobs, providers, public benefits, programs, or tools based on location, need, eligibility, and consented context.
Make preferred LLMs or AI workflows work better with less repeated context.
Adapt tone, layout, CTA priority, explanation depth, filters, and next actions.
A media platform may know what a user watched, but still show irrelevant ads or offers. With CanonIQ, the product could request an approved surface-specific profile slice and learn that this user prefers practical, low-pressure offers, avoids fear-based messaging, and is most receptive to family-friendly or time-saving recommendations in the evening.
Instead of only asking "what did this user watch?", the product can ask "what kind of message, offer, or next action is actually useful for this person right now?"
Products can send structured signals such as saves, dismissals, preferences, feedback, resource interests, and moment context.
Products can request approved profile context for a specific product or surface.
CanonIQ can return personalization instructions such as default filters, tone, layout, CTA priority, relevance tags, and avoid tags.
Users can correct, suppress, or remove signals.
CanonIQ enforces what can be used in-product, across Lumenfolk products, with partners, or not at all.
Signals can be labeled public, low, private, sensitive, or restricted.
{
"surface": "ad_slot",
"personalization": {
"relevance_tags": ["family-friendly", "practical", "low-friction"],
"avoid_tags": ["fear_based", "high_pressure"],
"tone": "clear_practical",
"timing_fit": "good",
"explanation": "Use practical value-first offers and avoid high-pressure messaging."
},
"privacy": {
"scope": "partner_surface_only",
"sensitive_fields_removed": true,
"full_profile_exposed": false
}
}CanonIQ should inform the experience without exposing the full person.
CanonIQ is designed to return only the context a product is allowed to use for a specific purpose. A recommendation surface, resource hub, onboarding flow, ad slot, or AI assistant may each receive different approved context.
Permissioned identity intelligence modules for products that need better personalization, recommendations, onboarding, and conversion.
CanonIQ API is currently in beta. Feature examples use sample data and may not represent final product behavior.
Return only the parts of a user's CanonIQ profile that a product is scoped to receive, such as decision style, values, timing context, preference signals, and consent scope.
Translate identity intelligence into practical guidance for product behavior, messaging, recommendations, onboarding, and user experience.
Let users control which products can access which parts of their CanonIQ profile, with per-app scope and per-field controls.
Give recommendation systems better context so they can suggest content, products, opportunities, resources, or next actions that fit the person.
Help products understand what message, offer, timing, or action is most likely to land with a specific user.
Attach source-backed context to profile claims so products can understand why a signal exists and whether confidence is high enough to use.
Generate plain-language explanations for why a recommendation, route, offer, or next step fits the user.
Allow users to export or carry approved parts of their CanonIQ profile across Lumenfolk products and future partner experiences.
CanonIQ API gives your product context-specific profile intelligence that can be used by your recommendation engine, workflow, UI, ad system, or preferred LLM.
{
"decision_style": "evidence-informed",
"values": ["trust", "quality", "time-saving"],
"preference_signals": ["premium-but-practical", "low-friction"],
"timing_context": "passive_discovery",
"consent_scope": "commerce_recommendations",
"confidence": 0.82
}The API is designed to provide identity-aware personalization across multiple product surfaces, from recommendations and commerce to career positioning and operating intelligence.
CanonIQ is the shared identity intelligence layer behind Lumenfolk's product prototypes. Each surface tests a different use case for the same underlying system: how profile slices, intent signals, values, decision style, context, and timing can make software more useful from the first interaction.
These prototypes are beta learning surfaces. They are examples of where CanonIQ can go once the shared backend and API layer are fully hardened.
Career positioning powered by identity intelligence. Positioned explores how CanonIQ can translate a person's strengths, values, operating style, and goals into clearer professional language and opportunity fit.
View prototypeThe user-facing place to create, understand, and manage a CanonIQ profile. The app shows how people can build self-knowledge and control which products can access each part of their profile.
View prototypeStyle, value, and commerce intelligence. Gingham explores how CanonIQ can help users decide what to buy, when to wait, what to protect, and how personal taste connects to market value.
View prototypeThe operating intelligence layer for traceable, high-value work. The Brain connects decisions, artifacts, workflows, people, initiatives, outcomes, and value signals — so organizations know what happened, why, and what it created. Lumenfolk runs on The Brain.
View prototypeTaste, timing, and recommendation intelligence. Next Up explores how CanonIQ can help users find what to watch, read, listen to, revisit, or discover next based on identity, context, and preference signals.
View prototypeAll prototypes are in beta. Outputs are examples and may not represent final product behavior. The purpose of these surfaces is to test intent signals, personalization patterns, and the shared CanonIQ intelligence layer.
Lumenfolk has already built lightweight product surfaces that demonstrate the breadth of the CanonIQ opportunity. The next phase is hardening the shared backend, profile system, permissions model, and API infrastructure to reliably power consumer products and future partner integrations.
Taste and moment-based recommendations.
Location-aware resource routing based on need, eligibility, and consented context.
Career and positioning experiences that start from approved user context.
Source-backed operating intelligence: traceable context, decisions, and value signals across an organization's work.
More relevant onboarding, recommendations, offers, and next actions.
CanonIQ includes a profile console where users can manage profile slices, personalization directives, app permissions, source evidence, and export settings.
Beta prototype. Example data only. Console behavior and outputs may not represent the final product.
Next: Add a personality framework result
Weighted across personality wallet items and source evidence.
CanonIQ is designed around permissioned context. Products should receive only the context needed for the experience they are improving, and users should have ways to understand, correct, suppress, or remove what CanonIQ thinks it knows.
Apps only see the profile slices a user explicitly approves for that experience.
Signals can be labeled public, low, private, sensitive, or restricted — and filtered accordingly.
Each product receives its own scoped slice. The full profile is never shared by default.
People can correct, suppress, or remove what CanonIQ thinks it knows at any time.
CanonIQ is not identity verification, biometric authentication, or a mental health diagnosis. It is a personal context and surface-personalization layer.
Read more in the Trust & Privacy Center.
CanonIQ gives the blueprint. The Brain Console governs the context. CanonIQ API lets approved products use that context safely.
The blueprint engine for identity, context, preferences, and consented profile signals.
Explore CanonIQThe operating intelligence layer for traceable, high-value work. Source-backed context, decisions, artifacts, workflows, and value signals — connected end to end.
Explore the Brain ConsoleThe permissioned infrastructure layer for approved products that need safer context-aware experiences.
Request API DemoThe Brain keeps the thread between what informed the work, what was decided, what was produced, who or what contributed, and what value was created.
CanonIQ API is currently accepting early API conversations and design partner requests. We are especially interested in products that need better personalization, safer context portability, smarter onboarding, better recommendations, resource routing, or AI workflow context.
We are currently accepting a limited number of early API conversations and design partner requests.
Blueprint. Console. API. One governed context system across CanonIQ, The Brain Console, and CanonIQ API.