Write a Feature Contract From a Messy Request
Draft a concise feature contract from an ambiguous model requirement.
A churn model owner asks for recent support activity as a feature, but the phrase hides event filters, entity grain, timestamp semantics, freshness, and ownership. Contract fields: purpose, entity, definition, timestamp, source, schema, freshness, quality rule, owner, limits The common shortcut is registering a feature with a friendly name and a source table while leaving bot tickets, edited tickets, null behavior, and freshness for later. Before recent_support_activity: count from support tickets table. Used for churn model. After support_human_ticket_count_7d: count of human-agent support tickets opened in the seven days before prediction time, entity customer_id, event timestamp ticket_created_at, excludes bot-only tickets and…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in