Phase 4 partner services

Jurisdiction-aware operations review

Review province-aware workflow posture through the jurisdiction layer while keeping legal, tax, accounting, and financial advice outside the product.

Service tracks

Providers

Jurisdiction

Marketplace

closed

Target outcome

Teams can identify jurisdiction-sensitive workflows and route them through templates, rules, and review boundaries instead of product forks.

Review checklist

1Confirm province and jurisdiction metadata is present.
2Review template and notice dependencies by jurisdiction.
3Keep service guidance framed as product operation, not legal advice.

Open source workspace Back to partner services

Service boundary

Partner services must package reviewed operational help, not self-serve marketplace discovery.
Every service track must remain source-linked to an existing Blocora workspace and permission boundary.
Jurisdiction-sensitive services must route through the province-aware rules layer and stay outside legal, tax, accounting, or financial advice.

Still closed

Self-serve partner marketplace
External partner billing or revenue-share engine
Provider-owned application, lease, payment, or notice decisions
Autonomous cross-system workflow execution
Legal, tax, accounting, or financial advisory services

Next controlled step

Keep partner services governed, source-linked, and hardened; onboarding and migration packs plus deeper intelligence are hardened, while community and membership remain deferred optional.