Developer & partner overview

A soft, high-level overview of how jdwin thinks about integration: public discovery stays open, decisions stay behind authenticated accounts, and approved partners receive dedicated materials through institutional channels, never through an exhaustive public dump.

Integration philosophy

jdwin is a decision product first. Any integration conversation should preserve that order: a confirmed place and sector remain the human input; a certified report with a binary verdict remains the human output; Free → Pro → Max depth remains the commercial language of value. Public documentation therefore describes capabilities in product terms, analysis inside an account, packages and Polar checkout, report export and share, without publishing route inventories, request contracts, or operational verification samples. If a capability exists for consumers in the product, partners may discuss it conceptually; the exact binding materials arrive privately after engagement.

Access

Visitors reach marketing, packages, documentation, support, and sign-in without a session. Consumer registration and sign-in, including approved identity providers such as Google and X in the browser experience, open the authenticated journey where map, reports, and vault live. Incomplete sessions are not treated as full access. What a report reveals follows the account package. Partner portals, when available, use independent authentication after joining and are never assumed for ordinary consumers. Staff and governance experiences, if any, are outside this public overview entirely.

Partners

Institutional partners and Enterprise engagements receive materials matched to their agreement. Public support for ordinary users remains at /support. Commercial package truth for consumers lives on /packages and in Entitlements. This overview exists so technical readers understand the boundary: jdwin documents product strength publicly, and reserves binding integration detail for channels that can protect it.