Skene
Product
Pricing
Docs
Blog
About
Log In
ProductPricingDocsBlogAbout
Log In
Resources / Glossary

Baseline manifest

The recorded state of an instrumentation surface at a point in time, used as the comparison point for future PRs.

Concepts

About this term

This page is part of the Skene analytics instrumentation glossary. Use it as a reference when writing specs, dashboards, or playbooks.

Canonical glossary index: /resources/glossary

Glossary

Glossary

Analytics callEvent namePayload (event properties)Identify callEvent taxonomyInstrumentation surfaceBaseline manifestInstrumentation driftSemantic diffRemoved eventRenamed eventMoved eventAltered payloadConditional firing changeCustomer Data Platform (CDP)Schema registryMCP (Model Context Protocol)Coding agentSide effectFunnelConversion eventActivation eventCohort

Definition

When Skene indexes a repo, the output is a structured manifest: every analytics call with its library, event name, payload shape, file path, line number, and control-flow context. That manifest is the baseline. On the next PR, Skene rebuilds the manifest for the new state and diffs against the baseline.

How the baseline updates

When a PR with intentional changes merges, the baseline updates to reflect the new state. Changes you accepted are now the truth; future PRs only flag drift from there.

Related terms

  • Instrumentation surface
  • Semantic diff
Skene

Product

How it worksFeaturesArchitectureIntegrationsSecurityPricing

Resources

DocumentationGlossaryPlaybooksBlog

Company

AboutOpen sourceContactPrivacyTerms
© 2026 Skene. All rights reserved.
Privacy PolicyTerms of Service
Skene