Refund window
policies/refunds.md
“Is this purchase eligible for a refund?”
State the window, the exceptions, and the escalation path in one customer-safe page.
- Owner
- customer-success
- Audience
- external
Example library
A dependable source is not a dump of every file. It is a handful of focused pages, each with a clear owner, a stated audience, and a current approved version.
policies/refunds.md
“Is this purchase eligible for a refund?”
State the window, the exceptions, and the escalation path in one customer-safe page.
metrics/active-user.md
“What counts as an active user?”
Pin down the exact time window, the qualifying event, the exclusions, and the source-of-truth table.
operations/lost-device.md
“What do I do when a company laptop is lost?”
Name the first action, the deadline, the escalation contact, and what the employee must not do.
sales/discount-policy.md
“Which discount can a rep offer without approval?”
Set the thresholds, the term rules, the exceptions, and who signs off above the threshold.
product/audit-export.md
“Which plans include audit-log export?”
List the eligible plans, the rollout state, the export format, and any region-specific limit.
systems/orders.md
“Which system owns order status?”
Identify the owning service, the canonical table, the status meaning, and the downstream copies.
Copy the pattern
The editor gives your team a normal writing surface with a few structured fields. Underneath, each page stays portable markdown and YAML.
--- title: Active user type: metric owner: product-analytics classification: internal status: approved --- A user with at least one qualifying session in the trailing 28 days. Signups without a qualifying session are excluded. The source event is events/session.md.
Pick one example, adapt it to your business, approve it, and connect the AI assistants your team already uses.
Start freeCurated Data
Loading application code and preparing your workspace…