ParkourSC

Inbound is documented at category level and at scale: signals are ingested from internal and external sources including tiers of suppliers, shippers, storage facilities, warehouses and hospitals, product-level sensor signals are coordinated with carrier and enterprise data, and the twin spans locations, transports, sensors, packaging, contextual data and enterprise systems.

Outbound is asserted without a route: the vendor states it bridges planning and real-time information and can automate decision-making for execution applications, and delivers ground-truth and predictive intelligence into planning applications. No named integration catalog or connector list appears anywhere on the site, no custom tool support is described, and no authenticated action framework is named.

SourceParkourSC, parkoursc.com/platform, /digital-supply-chain-twin and /continuous-realignmentread 2026-09-08

ParkourSC lets customers create automated workflows that function across any entity in the supply chain, structured on business states so that behavior follows where an entity sits in the customer's process lifecycle, with standardized and predictable automated workflows defined in the digital twin and coordinated across the organizations sharing it.

The Developer Studio builds custom workflows alongside a library of pre-built rules, workflows and models, and recipes embed operational rules, AI/ML models, KPIs and thresholds into operations. That is multi-step execution across entities and organizations under a named runtime, with a customer-facing builder. The automation described is rule, recipe and state driven rather than built from named agents.

SourceParkourSC, parkoursc.com/automation-and-collaboration, /platform and /decision-intelligence-developer-studioread 2026-09-08

The digital twin creates a digital model of the customer's end-to-end supply chain, defining the attributes and relationships between every entity involved in delivering product (locations, transports, sensors, packaging, contextual data and enterprise systems), and ParkourSC monitors all of them continuously, with the vendor's patented techniques contextualizing real-time data and the twin extensible through the Developer Studio.

That makes it a maintained, persistent, queryable structure over the customer's own operations that outlives any run. It models entities and relationships over operational and sensor data rather than indexing documents, and no retrieval mechanism is described.

SourceParkourSC, parkoursc.com/digital-supply-chain-twin and /platformread 2026-09-08

The vendor's pages document bounded autonomy under customer-set rules rather than an approval mechanism.

Operational rules are embedded on the twin from the customer's own SOPs, thresholds and business states are defined by the customer, and when the platform highlights a product nearing an acceptable range, operators resolve the excursion online through chat with warehouse operators, distribution managers or logistics providers.

Humans set the bounds and handle exceptions. No review-and-approve step, approval gate or escalation surface between an automated decision and its execution is documented.

SourceParkourSC, parkoursc.com/automation-and-collaboration and /digital-supply-chain-twinread 2026-09-08

When a digital twin is shared across the extended enterprise, each person has visibility into only the information relevant to their role, the twin's owner controls what status other organizations see, and operator dashboards are deployed per entity and per organizational level for executive, planner, supplier, tracer and warehouse-manager roles, including staff at suppliers and logistics firms, with a customer login at prod.parkoursc.com.

That is a role-scoped access model the buyer operates, spanning organizations. No certification, attestation, auditor or report is named anywhere on the site, and the privacy policy was last updated April 2022 and still cites Privacy Shield, invalidated in 2020.

SourceParkourSC, parkoursc.com/automation-and-collaboration, /decision-intelligence-developer-studio and /privacy-policyread 2026-09-08

No run trace, decision log, retention or reconstruction surface is documented. What the vendor's pages document is a different thing: operator dashboards with KPIs, trends, queries and thresholds, excursion identification against acceptable ranges, and process automation where everyone understands the path source material, products or assets have traveled and what happens next. That is chain-of-custody visibility of the goods and live operational monitoring, not a record of what an automation decided or why.

SourceParkourSC, parkoursc.com/platform, /decision-intelligence-developer-studio and /privacy-policyread 2026-09-08

No agent or session state with a stated scope and lifetime is documented, and nothing describes context carried between runs of an automation. The digital twin is a maintained model of the customer's supply chain entities; as an application data model, it is not agent memory.

SourceParkourSC, parkoursc.com estate readread 2026-09-08

Nothing is offered for a buyer with a residency requirement to choose.

The privacy policy, last updated April 2022, describes a SaaS platform run by Parkoursc, Inc. of San Jose and names no hosting provider, no region, no residency commitment and no customer environment option; it still cites Privacy Shield, invalidated in 2020, which dates the document rather than establishing a transfer mechanism.

The platform pages offer nothing selectable either: the line that other organizations may deploy their own ParkourSC instances is about partners running their own tenants to share twins, not about where a customer's data sits.

SourceParkourSC, parkoursc.com/privacy-policy and /continuous-realignmentread 2026-09-08

The Developer Studio page names a library of pre-built rules, workflows and models the customer can apply or extend, alongside recipes spanning demand planning, inventory, cold chain and logistics. The units are components rather than complete working agents, rules, models and workflow fragments assembled inside the customer's own twin, not a named agent a buyer adopts whole. No browsable catalog, marketplace or template gallery is published, and the seven solution pages are a product line rather than a pack.

SourceParkourSC, parkoursc.com/decision-intelligence-developer-studio and /platformread 2026-09-08

Workflows are structured on business states and fire on the data signals received for each entity, so the customer proactively structures state behavior against incoming signals.

The twin identifies potential issues and excursions as conditions approach customer-set thresholds, for example temperature ranges, and surfaces them for immediate response; product-level sensor signals are coordinated with carrier and enterprise data to identify risk earlier; and signals are ingested continuously from internal and external sources including supplier tiers, shippers, storage facilities, warehouses and hospitals. Delivery is to operator dashboards and in-platform chat, with no webhook or external channel surface documented.

SourceParkourSC, parkoursc.com/automation-and-collaboration, /digital-supply-chain-twin and /platformread 2026-09-08

The Decision Intelligence Developer Studio offers a library of pre-built rules, workflows and models or the option to create your own, and states plainly that a customer can seamlessly integrate their existing AI/ML code; the platform page adds that ParkourSC allows you to include custom AI/ML code in the recipes that drive predictive insight.

Customers supplying the models that drive decisions is real control over what runs. The control is over the predictive and decisioning layer rather than over the reasoning model behind the automated agents, no selector, routing surface or provider list is documented anywhere, and the platform's own models are undisclosed.

SourceParkourSC, parkoursc.com/decision-intelligence-developer-studio and /platformread 2026-09-08

Nothing documents an interface by which an outside caller drives this platform: no API reference, SDK, developer portal or MCP server is published, and the only host on the site beyond www is the customer login at prod.parkoursc.com. The Decision Intelligence Developer Studio is not an extensibility surface despite the name: it is a low-code and no-code administrative workbench for extending the customer's own twin, building workflows, writing custom queries and integrating the customer's AI/ML code, which is the customer building inside the platform.

SourceParkourSC, parkoursc.com estate read, probe recordedread 2026-09-08

No harness, scored test cases, holdout, release gate or controlled post-deployment experiment measuring the agents is documented, and no configuration or readiness gate either. Planners modeling and simulating operations to forecast and identify risks tests the customer's supply chain and plan, which is the product's own function, and continuous realignment between plan and execution measures the network, not the automation. Learning from outcomes without a documented loop is absorbed into the model rather than evaluated.

SourceParkourSC, parkoursc.com/continuous-realignment, /platform and /decision-intelligence-developer-studioread 2026-09-08

No browser, desktop or remote control of an interface the vendor does not own is documented anywhere on the site. The platform acts on supply chain data through sensor and system ingestion and pushes intelligence into planning and execution applications; sensor and telemetry ingestion is a data path, not computer use.

SourceParkourSC, parkoursc.com estate readread 2026-09-08