# Ask and push: context

Copy this file to CONTEXT.md next to SKILL.md and fill in every blank. The agent asks you for any blank it needs. Never put passwords, access keys or card numbers here.

## Decider
(Who answers the questions: a role or first name, and how they prefer to be asked.)
Example: The studio owner. Prefers multiple choice, one line per option.

## Where to search before asking
(Every place a fact might already live. The agent works through all of them before asking.)
Example: notes/ folder, the issue tracker, the project README, the shared drive "Ops" folder, the analytics dashboard.

## Credential stores
(Where credentials are kept, so the agent looks there instead of asking. Name the store, never the value.)
Example: the 1Password vault "agent-keys" (service account) or a separate Bitwarden account; the project's .env file, listed in .gitignore.

## Decision ledger
(Where unanswered questions are filed: a tracker project, a label, or the path to DECISIONS.md.)
Example: DECISIONS.md in the repository root. Or: GitHub Issues in the repository "your-org/ops", label "decide".

## Stable key format
(How keys are built so the same question is never filed twice.)
Example: ask:<area>:<short-question-slug>, e.g. ask:billing:annual-plan-discount

## Areas
(The areas an item can belong to, used for spreading the daily block.)
Example: product, billing, marketing, hiring, personal

## Critical incident marker
(What makes an item a critical incident that bypasses the age ladder.)
Example: severity = critical and label = incident

## Daily surfaces
(When the morning and evening summaries run, and where they appear.)
Example: Morning at 08:00 in the daily standup note; evening at 18:00 in the end-of-day note.

## Cap per surface
(Maximum decision items per surface. Default 3.)
Example: 3

## Standing decisions
(Answers the decider has already given that sub-agents' questions can be settled against.)
Example: Always use the existing email provider; never discount below the listed floor price without asking.

## Source of truth per item type
(Override or extend the verification table in SKILL.md with your real sources.)
Example: Client follow-ups: the contact record in the customer database. Deploys: the release list in the repository.