Academy
8. The Marketplace: Install, Derive and Publish
Browse the marketplace of OUPI and organization artifacts, install one, derive a custom version, and understand ratings and governance.
The Live Artifacts Marketplace is a curated catalog accessible at the marketplace route. It lists two categories of artifacts: those published by OUPI (platform-provided templates covering common professional workflows) and those published by members of your organization. When you browse the marketplace, each listing shows what the artifact does, the inputs it expects, and community ratings. Installing an artifact gives you your own instance — your inputs, your run history, and your runs billed to your own account. The original author's workflow is preserved as a reference, but your usage is entirely independent.
Installing a marketplace artifact is not the same as deriving one. Installing gives you a ready-to-run copy: fill the declared inputs and launch. Deriving means you take an existing artifact — one you installed or one shared within your team — and fork it into a new artifact on the forge page. The derived version inherits the original's workflow structure, but you can rename inputs, add or remove parameters, change schedules or triggers, and reshape the logic by describing changes in plain language. @oupi rebuilds the workflow from your modifications, just as it would when forging from scratch. The derived artifact is yours to publish back to the marketplace or keep private.
Governance in the marketplace relies on three pillars. First, per-member billing: when you install and run an artifact, credits are debited from your balance, not the publisher's, so cost accountability is clear (each run's cost appears in history). Second, ratings let the organization surface the most reliable artifacts and flag those that underperform. Third, every run carries a verification verdict — verified, failed, or could not be verified — so you and your team can audit quality over time before deciding to adopt or derive an artifact.
Before publishing a derived artifact to your organization's marketplace, run it at least three times with varied inputs and review the verification verdicts. A consistent 'verified' track record builds trust and earns better ratings from colleagues who install it later.
When deriving, focus on what varies between runs. Rename inputs to match your team's vocabulary, mark truly optional fields as optional, and use allowed-choice lists to prevent input errors. Well-declared inputs are the difference between an artifact people adopt and one they abandon.
Open the marketplace (dashboard.user.live-artifacts.marketplace). Browse the OUPI artifacts, pick one relevant to your work, and install it. Run it once with real inputs. Then go to the forge page, derive a custom version — change at least one input or add a new one — and run the derived version. Compare both runs in your history.
The marketplace is where reusable workflows circulate — published by OUPI or your organization. Install to get your own independent instance; derive to fork and customize on the forge page. Ratings and per-run verification verdicts provide quality signals, while per-member billing keeps cost governance transparent. Master the install → derive → publish loop and you turn proven workflows into organizational assets.