The organizer's trigger for building a concept graph out of a finished event, or out of a
whole series when it is given a topic.
Shown to administrators only — the endpoint refuses anyone else, and this is the
affordance, not the enforcement. Re-running is the supported way to redo a poor extraction:
it appends a version rather than overwriting, so both attempts stay readable, which is why
the button stays available once a graph exists. On a topic it is also how a series that
predates the feature gets backfilled.
Generation runs in a background job: POST /v1/artifacts/generate only claims the artifact
and enqueues the run, so this component's job is to reflect the artifact prop's real
generationStatus (kept live by the parent via useArtifacts' socket listeners), not the
POST call's own duration. A completion alert is only shown for a run this instance
observed go pending → ready/failed, so an admin who merely opens the page to an
already-finished graph doesn't see a stale "just wrote a version" banner.
The organizer's trigger for building a concept graph out of a finished event, or out of a whole series when it is given a topic.
Shown to administrators only — the endpoint refuses anyone else, and this is the affordance, not the enforcement. Re-running is the supported way to redo a poor extraction: it appends a version rather than overwriting, so both attempts stay readable, which is why the button stays available once a graph exists. On a topic it is also how a series that predates the feature gets backfilled.
Generation runs in a background job: POST /v1/artifacts/generate only claims the artifact and enqueues the run, so this component's job is to reflect the
artifactprop's realgenerationStatus(kept live by the parent via useArtifacts' socket listeners), not the POST call's own duration. A completion alert is only shown for a run this instance observed go pending → ready/failed, so an admin who merely opens the page to an already-finished graph doesn't see a stale "just wrote a version" banner.