From 02210ba44bd6a1a7117423bc3f2de83cdb36e430 Mon Sep 17 00:00:00 2001 From: purushpsm147 Date: Thu, 16 Apr 2026 01:16:19 +0530 Subject: [PATCH 1/2] feat: implement browser-ready intent factory and initialize project documentation and landing pages --- Generate blueprint json/BaselineBluePrint.md | 15 ++++++ PRICING.md | 51 ++++++++++++++++--- landing/cheatsheet.html | 11 ++-- landing/ecommerce/index.html | 7 +-- landing/index.html | 26 ++++++---- landing/licensing.html | 42 ++++++++++----- landing/llms-full.txt | 16 ++++-- landing/llms.txt | 15 ++++-- landing/marketing-cheatsheet.html | 15 ++++-- landing/solutions.html | 10 ++-- marketing-cheatsheet.md | 29 ++++++++++- package-lock.json | 2 +- packages/core/CHANGELOG.md | 10 ++++ packages/core/README.md | 23 ++++++--- packages/core/docs/architecture.md | 32 ++++++------ packages/core/package.json | 2 +- packages/core/sandbox/amazon/app.ts | 3 +- packages/core/sandbox/app.ts | 2 + packages/core/src/engine/intent-manager.ts | 4 +- packages/core/src/factory.ts | 9 ++++ packages/core/src/types/events.ts | 23 +++++++-- .../core/tests/compatibility-matrix.test.mjs | 40 +++++++++++++++ .../core/tests/integration-contract.test.mjs | 14 ++++- packages/core/tests/microkernel.test.mjs | 31 +++++++++++ packages/react/README.md | 5 ++ packages/remix/README.md | 12 +++-- 26 files changed, 356 insertions(+), 93 deletions(-) diff --git a/Generate blueprint json/BaselineBluePrint.md b/Generate blueprint json/BaselineBluePrint.md index e9b692c..c9c43d8 100644 --- a/Generate blueprint json/BaselineBluePrint.md +++ b/Generate blueprint json/BaselineBluePrint.md @@ -8,6 +8,21 @@ Because the engine evaluates strictly on the client side without cross-session e **Blueprints** solve this cold-start problem. By injecting a pre-calculated mathematical topography into the engine on Day 1, developers can achieve instant, zero-latency intent detection from the very first user session. +## When to Use Blueprints vs. Custom Consolidation + +**Blueprints are the right starting point** when a team has short sessions but a +fairly standard journey. A startup or mid-market ecommerce team can inject +`ecommerce-strict-funnel.json`, start with mature prior transition counts, and +get usable confidence immediately while the engine continues adapting to its own +traffic. + +**Custom consolidation becomes valuable** when the customer journey is highly +specialized. Enterprise teams with bespoke B2B checkout, approval, onboarding, +or regulated intake flows often need a baseline that reflects their exact path, +not a generic template. In those cases, a customer-specific blueprint plus the +Persistent Graph Consolidator lets the engine preserve learning across short +sessions and keep improving without depending on a single long visit. + --- ## The Blueprints diff --git a/PRICING.md b/PRICING.md index f51fea1..226945a 100644 --- a/PRICING.md +++ b/PRICING.md @@ -13,12 +13,45 @@ PassiveIntent is **free and open-source** under AGPLv3 for open-source projects, ## Tiers -| Tier | Annual Fee | Target Audience | What You Get (Support & Features) | -| ---------- | ---------- | ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Free | $0 | Open-source projects, students | AGPLv3 copyleft license. Full SDK. **Support:** Community Forum / GitHub Issues only. | -| Startup | $599/yr | Small teams (5–50 employees) | Up to 3 Commercial Projects, AGPL exemption. **Support:** Priority Email Support — async, business days only. | -| Growth | $1,999/yr | Scaling companies (50–200 employees) | Unlimited Internal Projects (1 org). **Support:** Direct Founder Access — async email/chat, business days only. | -| Enterprise | Custom | Multi-org deployments, highly regulated industries (Fintech/Healthcare), and massive retail operations. | Unlimited scope. Includes AGPL commercial exemption, OEM wrapping rights, and white-labeling. **Premium Intent Catalog:** Access the private `@passiveintent/enterprise` NPM package (Fraud, VIP Whale, Rage-Quit detection — subject to request). **Custom Integration Sprints:** We build domain-specific kinematic adapters for your exact UI. **Zero-Trust BYOC:** Custom telemetry egress adapters routed directly to your private AWS/Azure/GCP VPC, bypassing third-party analytics. **Support:** Dedicated private Slack Connect channel — direct line to the engineer who built this. Priority issue triage before all other tiers. Quarterly roadmap review call included. Weekend/24-7 coverage available upon request at additional cost. | +### Free + +Annual Fee: **$0** + +Target Audience: Open-source projects and students. + +What You Get: AGPLv3 copyleft license and the full SDK. Support is limited to the Community Forum and GitHub Issues. + +### Startup + +Annual Fee: **$599/yr** + +Target Audience: Small teams with roughly 5 to 50 employees. + +What You Get: Up to 3 commercial projects, AGPL exemption, and priority email support during business days. + +### Growth + +Annual Fee: **$1,999/yr** + +Target Audience: Scaling companies with roughly 50 to 200 employees. + +What You Get: Unlimited internal projects within one organization and direct founder access over async email and chat during business days. + +### Enterprise + +Annual Fee: **Custom** + +Target Audience: Multi-org deployments, highly regulated industries such as fintech and healthcare, and massive retail operations. + +What You Get: Unlimited scope, AGPL commercial exemption, OEM rights, white-labeling, premium enterprise modules, custom integration sprints, Persistent Graph Consolidator access, BYOC egress options, and dedicated support. + +Enterprise packages can additionally include: + +- Premium Intent Catalog access via the private `@passiveintent/enterprise` package. +- Customer-specific kinematic adapters and integration sprints for your exact UI. +- Persistent Graph Consolidator engagements for cross-session learning in short-session, high-consideration funnels. +- Zero-Trust BYOC telemetry routing directly into your private AWS, Azure, or GCP environment. +- Dedicated Slack Connect support, priority triage, roadmap reviews, and optional expanded coverage. ## What "commercial use" means @@ -53,6 +86,12 @@ A single deployable web application or npm package that ships PassiveIntent. Mic **Is there a trial period?** The Free (AGPLv3) tier has no time limit and no feature restrictions — it is the full SDK. Commercial tiers add a support channel, AGPL exemption, and (for Growth/Enterprise) premium features as they ship. +**We have short user sessions. Should we start with a Blueprint or an Enterprise engagement?** +If your flow broadly matches a standard ecommerce or content journey, start with a Blueprint JSON. It seeds the engine with mature prior transition counts on day one and is usually the fastest way to bypass cold start for startup and growth-stage teams. If your journey is highly customized and users only generate a small number of events per session, a generic blueprint can be too coarse. In that case, we recommend an Enterprise engagement with the Persistent Graph Consolidator so the model can preserve learning across sessions and tune itself to your exact funnel. Engagements start at **$50,000**. + +**What changes when we outgrow the generic Blueprint?** +The open-source path is designed to deliver immediate value with synthetic baselines and live-session memory. That is often enough to catch hesitation and recover abandoned carts quickly. Teams typically move up when they want the engine to stop resetting to a generic prior and start retaining the organic behavior of their own customers over a longer window. That is the role of the Enterprise package: Persistent Graph Consolidator preserves customer-specific learning across sessions, supports long-horizon calibration, and keeps the model compounding instead of restarting. + --- ## Support Boundaries diff --git a/landing/cheatsheet.html b/landing/cheatsheet.html index 001e841..9d06431 100644 --- a/landing/cheatsheet.html +++ b/landing/cheatsheet.html @@ -177,13 +177,14 @@

One page that connects the math to the marketing move.

Important note on thresholds

Propensity thresholds are not universal constants.

- A 3-page checkout funnel and a 40-page discovery catalog have entirely different - structural probabilities. + A 3-page checkout funnel and a 40-page discovery catalog have different structural + probabilities, and organic learning depends on your privacy and storage mode.

- The thresholds below assume a calibrated baseline tuned to your site's traffic patterns. - For best accuracy, ensure your integration includes a calibration step before you apply - hard intervention rules in production. + The engine starts from raw Markov probabilities. In zero-consent, ephemeral deployments, + it resets with the tab, so Blueprint JSON is the practical path to instant, + high-sensitivity funnel enforcement. Teams that want cross-session organic learning can + enable compliant persistent storage or move to Enterprise Persistent Graph Consolidator.

diff --git a/landing/ecommerce/index.html b/landing/ecommerce/index.html index 472413e..a85b3ee 100644 --- a/landing/ecommerce/index.html +++ b/landing/ecommerce/index.html @@ -140,7 +140,7 @@ "name": "Does PassiveIntent require cookie banners to work?", "acceptedAnswer": { "@type": "Answer", - "text": "No. PassiveIntent calculates intent locally in the browser without exporting behavioral payloads to PassiveIntent servers." + "text": "For the default zero-egress, in-memory deployment, no. If you enable persistent browser storage or export graph data to your own infrastructure, your consent and privacy obligations depend on your implementation and legal review." } }, { @@ -894,8 +894,9 @@

What eCommerce teams ask before they install.

Does PassiveIntent require cookie banners to work?

- No. PassiveIntent runs locally in the browser and does not export behavioral payloads - to our servers. + For the default zero-egress, in-memory deployment, no.* If you enable persistent + browser storage or export graph data to your own infrastructure, your consent and + privacy obligations depend on your implementation and legal review.

diff --git a/landing/index.html b/landing/index.html index 8c8df9d..61bd27f 100644 --- a/landing/index.html +++ b/landing/index.html @@ -163,7 +163,7 @@ "name": "Do we need a cookie banner for PassiveIntent to work?", "acceptedAnswer": { "@type": "Answer", - "text": "No. PassiveIntent itself does not require analytics cookies or server-side behavioral tracking." + "text": "For the default zero-egress, in-memory deployment, no. If you enable persistent browser storage or export graph data to your own infrastructure, your consent and privacy obligations depend on your implementation and legal review." } }, { @@ -694,9 +694,10 @@

Calibration guide

Open-source core vs enterprise

Start with the pure core. Expand when the journey gets bigger.

- The AGPL core is built for one live session on one site in one tab. Enterprise is for + The AGPL core is built for one live session on one site in one tab. Start with a + Blueprint when the journey is standard and sessions are short. Enterprise is for brands that need continuity across repeat visits, connected properties, - comparison-heavy journeys, and high-volatility campaigns. + customer-specific funnels, and high-volatility campaigns.

@@ -743,8 +744,9 @@

Start with the pure core. Expand when the journey gets bigger.

- Same privacy promise. Enterprise keeps the zero-egress posture of the - core while widening the kinds of journeys you can understand. + Same privacy promise. Start with a Blueprint when the journey is + standard. Move to enterprise when the model needs to retain organic customer learning + across visits, tabs, or properties.

Growth

Enterprise

Custom

- Built for repeat visits, connected properties, comparison-heavy journeys, and - enterprise rollout needs. + Built for repeat visits, connected properties, and custom short-session journeys that + need cross-session continuity and long-term customer-specific calibration.

What teams usually need answered before they adopt.
Do we need a cookie banner for PassiveIntent to work?

- No. PassiveIntent itself does not require analytics cookies or server-side behavioral - tracking. + For the default zero-egress, in-memory deployment, no.* If you enable persistent + browser storage or export graph data to your own infrastructure, your consent and + privacy obligations depend on your implementation and legal review.

@@ -879,8 +882,9 @@

What teams usually need answered before they adopt.

PassiveIntent Core is the AGPL open-source engine for one live session on one site in - one tab. Enterprise expands that same privacy-first model for repeat visits, connected - properties, tab-heavy research, and fast-changing traffic conditions. + one tab. If a standard journey only needs a faster start, use a Blueprint. Enterprise + expands that same privacy-first model for repeat visits, connected properties, + customer-specific short-session funnels, and fast-changing traffic conditions.

diff --git a/landing/licensing.html b/landing/licensing.html index d614602..020f7b2 100644 --- a/landing/licensing.html +++ b/landing/licensing.html @@ -154,8 +154,8 @@

Growth

Enterprise

Custom

- Advanced modules, custom engineering support, and Zero-Trust BYOC for enterprise - rollout. + Blueprint launch paths, Persistent Graph Consolidator, and Zero-Trust BYOC for + enterprise rollout.

Enterprise

Open-source core vs enterprise

Choose based on how complex the buyer journey really is.

- The AGPL core is deliberately narrow: one live session, one site, one tab. Enterprise - widens that model for repeat visits, connected properties, comparison-heavy research, - and campaign volatility, while keeping the same privacy-first posture. + The AGPL core is deliberately narrow: one live session, one site, one tab. Start with + a Blueprint when the journey is standard and sessions are short. Move to enterprise + for repeat visits, connected properties, custom funnels, and campaign volatility while + keeping the same privacy-first posture.

@@ -263,18 +264,25 @@

Best for proving the loop inside one active decision window.

Built for revenue journeys that stretch across time, sites, and tabs.

- Choose enterprise when a single isolated session is no longer enough to explain the - customer’s real buying journey. + Choose enterprise when a single isolated session is no longer enough, or when a + custom short-session funnel needs learning that survives the visit.