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.

integration-posthog

PostHog analytics integration with event capture, HogQL, and feature flags

  • Type: feature
  • Version: 1.0.0
  • Stability: experimental
  • Owners: @examples
  • Tags: integration, posthog, analytics, feature-flags
  • field.key.label
    integration-posthog
    field.version.label
    1.0.0
    field.type.label
    feature
    field.title.label
    integration-posthog
    field.description.label

    PostHog analytics integration with event capture, HogQL, and feature flags

  • Type: feature
  • Version: 1.0.0
  • Stability: experimental
  • Owners: @examples
  • Tags: integration, posthog, analytics, feature-flags
  • field.tags.label
    integration,posthog,analytics,feature-flags
    field.owners.label
    @examples
    field.stability.label
    experimental

    PostHog analytics integration with event capture, HogQL, and feature flags

    Source Definition

    import { defineFeature } from '@lssm-tech/lib.contracts-spec';
    
    export const IntegrationPosthogFeature = defineFeature({
    	meta: {
    		key: 'integration-posthog',
    		version: '1.0.0',
    		title: 'PostHog Analytics Integration',
    		description:
    			'PostHog analytics integration with event capture, HogQL, and feature flags',
    		domain: 'integration',
    		owners: ['@examples'],
    		tags: ['integration', 'posthog', 'analytics', 'feature-flags'],
    		stability: 'experimental',
    	},
    
    	integrations: [
    		{ key: 'integration-posthog.integration.posthog', version: '1.0.0' },
    	],
    
    	telemetry: [{ key: 'integration-posthog.telemetry', version: '1.0.0' }],
    
    	docs: [
    		'docs.examples.integration-posthog',
    		'docs.examples.integration-posthog.usage',
    	],
    });