OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

AI index

health.activities.sync

Synchronize activity entries from the configured health provider.

  • Type: operation (command)
  • Version: 1.0.0
  • Stability: experimental
  • Owners: @platform.integrations
  • Tags: health, activities, wearables
    • field.key.label
    health.activities.sync
    field.version.label
    1.0.0
    field.type.label
    operation (command)
    field.title.label
    health.activities.sync
    field.description.label

    Synchronize activity entries from the configured health provider.

  • Type: operation (command)
  • Version: 1.0.0
  • Stability: experimental
  • Owners: @platform.integrations
  • Tags: health, activities, wearables
    • field.tags.label
    health,activities,wearables
    field.owners.label
    @platform.integrations
    field.stability.label
    experimental

    Synchronize activity entries from the configured health provider.

    Goal

    Keep canonical activity records aligned with upstream provider sources.

    Context

    Triggered by scheduled jobs or manual refresh actions to maintain incremental sync state.

    Source Definition

    import {
	type AnyOperationSpec,
	defineCommand,
	defineQuery,
} from '@lssm-tech/lib.contracts-spec/operations';
import type { OperationSpecRegistry } from '@lssm-tech/lib.contracts-spec/operations/registry';
import { ScalarTypeEnum, SchemaModel } from '@lssm-tech/lib.schema';
import { HealthActivityRecord } from '../models';
import { HEALTH_TELEMETRY_EVENTS } from '../telemetry';

export const HealthSyncActivities = defineCommand({
	meta: {
		key: 'health.activities.sync',
		version: '1.0.0',
		description:
			'Synchronize activity entries from the configured health provider.',
		goal: 'Keep canonical activity records aligned with upstream provider sources.',
		context:
			'Triggered by scheduled jobs or manual refresh actions to maintain incremental sync state.',
		owners: ['@platform.integrations'],
		tags: ['health', 'activities', 'wearables'],
		stability: 'experimental',
	},
	io: {
		input: HealthSyncActivitiesInput,
		output: HealthSyncActivitiesOutput,
	},
	policy: {
		auth: 'admin',
	},
	telemetry: {
		success: {
			event: { key: HEALTH_TELEMETRY_EVENTS.activitiesSynced },
		},
		failure: {
			event: { key: HEALTH_TELEMETRY_EVENTS.activitiesSyncFailed },
		},
	},
});