@thinkingai/ae-cli 6.1.9 → 6.1.11

package/skills/ae-experiment-design/references/client-experiment-sdk.md

@@ -0,0 +1,147 @@
+# Client Experiment SDK
+
+Read this reference for Android, iOS, or browser JavaScript experiment integration. Read `sdk-index.md` first and verify the current main document before producing production code.
+
+## Shared client model
+
+All three verified client pages describe the same model:
+
+- analytics SDK handles data collection;
+- Remote Config retrieves AE configuration;
+- experiment SDK provides typed Feature getters and exposure;
+- automatic exposure is enabled through `automaticExposureTracking`;
+- manual exposure is available when activation does not coincide with the getter;
+- a custom bucket map can override the default assignment subject;
+- custom fetch parameters can be attached to configuration requests;
+- an explicit fetch can refresh experiment information.
+
+## Android
+
+Verified document state: `TDExperiment` 1.0.1, updated 2026-07-24.
+
+Dependencies:
+
+- `TDAnalytics` >= 3.3.6
+- `TDRemoteConfig` >= 1.3.0
+- automatic package: `cn.thinkingdata.android:TDExperiment:1.0.1`
+
+Initialization order:
+
+```java
+TDAnalytics.init(context, "APP_ID", "https://YOUR_SERVER_URL");
+
+TDExperimentConfig config =
+    new TDExperimentConfig("APP_ID", "https://YOUR_SERVER_URL");
+config.automaticExposureTracking = true;
+TDExperiment.init(context, config);
+```
+
+Verified operations:
+
+```java
+TDExperiment.getValueAsString(key);
+TDExperiment.getValueAsDouble(key);
+TDExperiment.getValueAsBoolean(key);
+TDExperiment.getValueAsJson(key);
+TDExperiment.exposure(key);
+TDExperiment.fetch();
+TDExperiment.setCustomBucketId(bucketId);
+TDExperiment.setCustomFetchParams(params);
+```
+
+Use the initialization callback for first-fetch success or error. `TDExperiment.enableLog(true)` enables experiment logging.
+
+The verified page does not show typed-default overloads for Android getters. Keep an application-owned typed control default and verify whether a newer SDK adds overloads.
+
+## iOS
+
+Verified document state: `TDExperiment` 1.0.2, updated 2026-07-24.
+
+Dependencies:
+
+- `ThinkingSDK` >= 3.1.6
+- `TDRemoteConfig` >= 1.3.1
+- CocoaPods: `pod 'TDExperiment', '1.0.2'`
+- minimum deployment target shown by the experiment page: iOS 9.0
+
+Initialization order:
+
+```objective-c
+[TDAnalytics startAnalyticsWithAppId:@"APP_ID"
+                           serverUrl:@"https://YOUR_SERVER_URL"];
+
+TDExperimentConfig *config =
+    [[TDExperimentConfig alloc] initWithAppId:@"APP_ID"
+                                    serverUrl:@"https://YOUR_SERVER_URL"];
+config.automaticExposureTracking = YES;
+[TDExperiment startWithConfig:config];
+```
+
+Verified getters support no-argument defaults and explicit defaults:
+
+```objective-c
+[TDExperiment getValueAsString:key defaultValue:@"default"];
+[TDExperiment getValueAsNumber:key defaultValue:@0];
+[TDExperiment getValueAsBoolean:key defaultValue:NO];
+[TDExperiment getValueAsJson:key defaultValue:@{}];
+```
+
+Other verified operations:
+
+```objective-c
+[TDExperiment exposure:key];
+[TDExperiment fetch];
+[TDExperiment setCustomBucketId:bucketId];
+[TDExperiment setCustomFetchParams:params];
+```
+
+Use `TDExperimentTask` listeners for startup or fetch success and failure. `[TDExperiment enableLog:YES]` enables experiment logging.
+
+## JavaScript
+
+Verified document state: experiment package 1.0.0, updated 2026-07-24.
+
+Dependencies:
+
+- `TDAnalytics` >= 2.6.0
+- `TDRemoteconfig` >= 1.3.0
+- files shown by the page: `thinkingdata.umd.min.js`, `tdremoteconfig.umd.min.js`, `tdexperiment.umd.min.js`
+
+The page initializes analytics first and then the experiment global with:
+
+- `appId`
+- `serverUrl`
+- `automaticExposureTracking`
+- `customBucketId`
+- `customFetchParams`
+- `enableLog`
+- fetch success and failure callbacks
+
+The page shows typed getters, manual exposure, fetch, custom bucket ID, and custom fetch parameters.
+
+### Spelling gate
+
+The verified page spells the global object `TDExpriment`. Treat this as unresolved until the downloaded 1.0.0 package or a newer verified main document confirms the export. Do not silently change it, and do not publish exact JavaScript code based only on the page.
+
+## Remote Config companion behavior
+
+The verified Remote Config pages show:
+
+- local defaults when no remote value is available;
+- value order: remote, local default, then empty;
+- a successful-fetch update listener;
+- status information for strategies changed to `suspend` or `force_offline`;
+- debug/test mode polling every five seconds for test strategies;
+- test-device selection for client send testing.
+
+These are Remote Config behaviors. Do not imply that the experiment SDK itself polls every five seconds in production.
+
+## Client implementation checklist
+
+- Verify all three SDK versions together.
+- Initialize on the documented thread or lifecycle point.
+- Set assignment identity before first fetch or getter.
+- Use a typed control default.
+- Choose automatic or manual exposure, not both.
+- Freeze behavior when a mid-session update would cause flicker.
+- Test control, treatment, no-network, timeout, account switch, and stale-cache cases.

package/skills/ae-experiment-design/references/experiment-creation.md

@@ -0,0 +1,108 @@
+# Experiment Draft Creation
+
+Use this reference when the user asks to create, save, or reuse an A/B experiment draft.
+
+## Execution boundary
+
+- Perform every platform read or write through `ae-cli`.
+- Discover and inspect the current capability before constructing input.
+- Do not assume Feature, layer, metric, group, targeting, duration, or traffic fields before inspecting the current schema.
+
+## Creation contract gate
+
+Before writing a draft, establish the minimum semantic contract:
+
+1. verified project ID and host;
+2. experiment variable and the user-visible or system behavior that changes;
+3. experiment goal and one primary metric with an exact feasible definition;
+4. target population and material exclusions;
+5. stable assignment unit and identity join path;
+6. one control group and at least one treatment group, with typed Feature values and allocations totaling `1.0`;
+7. experiment traffic, targeting, and a resolved layer or explicit new-layer plan;
+8. Feature ownership, key, type, and typed default;
+9. when the draft requires a duration, a confirmed sample target and
+   formula-derived duration.
+
+Do not create a prose-only shell that leaves the experiment variable, group behavior, primary metric, target population, or assignment identity undefined. Ask one focused question at a time when a missing answer materially changes the draft.
+
+## Design heuristics are not platform facts
+
+Use these only as recommendations and verify that the identity exists and remains stable:
+
+- pre-login experience: usually `#distinct_id` or a stable device identity;
+- authenticated user experience: usually `#user_id`;
+- account-wide B2B behavior: an account identity;
+- device-specific rendering or performance: a device identity.
+
+Do not silently choose an assignment identity. Explain the material identity risk and obtain confirmation when more than one viable identity changes who receives a consistent experience.
+
+## Authorization gate
+
+A draft write is authorized when either condition holds:
+
+- the user reviewed the proposed design and then explicitly asked to create or confirmed creation; or
+- the user's current request explicitly says to create and already provides an exact, complete creation contract.
+
+If the design contains recommended or inferred choices that the user has not reviewed and those choices materially affect assignment, audience, behavior, metrics, or traffic, show a compact plan summary and ask for confirmation before writing.
+
+Do not ask for redundant confirmation when the user has already confirmed the unchanged plan. Design-only language is not authorization to create. Draft authorization never authorizes submit, start, live traffic changes, pause, end, or delete.
+
+## Resolution and idempotency
+
+Before creating assets:
+
+1. resolve the project;
+2. search for exact or likely duplicate experiment drafts;
+3. inspect any likely duplicate before deciding to reuse it;
+4. resolve the exact Feature, layer, and metrics;
+5. verify definitions, types, defaults, ownership, status, and remaining traffic;
+6. identify existing active or draft experiments that may interact with the same Feature, layer, audience, or identity.
+
+Reuse only an exact semantic match. Similar names are not enough. If an exact-match draft already exists, reuse it and report that outcome instead of creating a duplicate.
+
+An empty list is not proof of no conflict. Only a supported conflict check can justify a user-facing "no conflict" result.
+
+## Materialization sequence
+
+Use the inspected schemas and execute only the steps required for this design:
+
+1. create or reuse an exact metric when its definition is complete;
+2. create or reuse an inactive Feature with the correct type and default;
+3. create or reuse a compatible layer with verified assignment identity and sufficient traffic;
+4. assemble experiment name, falsifiable hypothesis, Feature bindings, groups, allocations, traffic, targeting, metrics, and any required schedule fields;
+5. validate or dry-run once when appropriate under `platform-operations.md`;
+6. save the experiment as a draft;
+7. read back the draft and verify its persisted fields;
+8. run supported readiness and conflict checks;
+9. return a concise creation receipt and experiment-detail link.
+
+Do not claim atomic success when supporting assets were created but the experiment save failed. Report created, reused, failed, and unresolved assets separately.
+Immediately before saving, revalidate the creation contract against the inspected schema and ensure no proposed ID is being presented as an existing platform ID.
+
+## Post-save verification
+
+A successful write response is not sufficient by itself. Read back the saved or reused draft and verify, when returned by the platform:
+
+- actual experiment ID and name;
+- project ID;
+- draft status;
+- Feature and layer bindings;
+- group names, values, and allocations;
+- experiment traffic and targeting;
+- primary event metric and calculation code.
+
+Run readiness and conflict checks only when supported. Report each check separately and do not translate "not run" into "passed".
+
+## User-visible completion
+
+Return an operation receipt, not the discovery log. Include:
+
+- created, reused, partially completed, blocked, or failed;
+- experiment name, actual ID, and draft status;
+- control and treatment values and allocations;
+- experiment traffic and primary metric;
+- readiness and conflict results that actually ran;
+- at most three material blockers or semantic risks;
+- the clickable experiment-detail link required by `SKILL.md`.
+
+Do not expose raw candidate lists, capability discovery, request schemas, commands, or internal execution narration unless the user explicitly asks for an audit or debugging view.

package/skills/ae-experiment-design/references/experiment-sdk-contract.md

@@ -0,0 +1,100 @@
+# Experiment SDK Contract
+
+Read this reference when defining Feature retrieval, assignment, defaults, caching, or cross-platform behavior.
+
+## Required sequence
+
+1. Initialize the analytics SDK.
+2. Initialize the Remote Config dependency.
+3. Initialize the experiment SDK with the same verified app and server environment.
+4. Establish the stable assignment identity before the first Feature evaluation.
+5. Fetch or read the Feature using the expected value type.
+6. Apply the assigned behavior.
+7. Record exposure only when the behavior becomes visible or effective.
+8. Report outcome events with an identity that can join to exposure.
+
+The verified Android and iOS experiment documents explicitly require analytics initialization before experiment initialization. Apply the same ordering to JavaScript unless a newer verified main document states otherwise.
+
+## Feature contract
+
+Define the following before implementation:
+
+| Field | Requirement |
+|---|---|
+| Feature key | Stable, environment-correct, and resolved from the real platform asset |
+| Value type | String, number, Boolean, or JSON; match the platform Feature |
+| Default | Typed, safe for control behavior, and owned by the application |
+| Assignment unit | Stable device, account, role, or another verified identifier |
+| Evaluation owner | Client, server, or one side of a hybrid architecture |
+| Exposure owner | Exactly one component |
+| Outcome join | Same stable identity or a verified merge path |
+
+Do not use an empty or null fallback when a safe control behavior is required. A default is product behavior, not only an SDK parameter.
+
+## Assignment identity
+
+Resolve:
+
+- pre-login identity;
+- post-login identity;
+- account switching;
+- multiple roles under one account;
+- device-to-account merge or alias behavior;
+- server/client identity consistency.
+
+If a custom bucket ID is used, set it before fetching or reading the Feature. The verified client SDKs expose a custom bucket map, but the exact key and value semantics must match the experiment configuration. Do not assume that the literal example `bucket_id -> account_id` is the only supported schema.
+
+Do not use custom request parameters as a hidden substitute for assignment identity unless the platform contract explicitly defines that behavior.
+
+## Fetch and cache
+
+Define:
+
+- initial fetch timing;
+- request timeout;
+- retry and backoff;
+- last-known-good cache;
+- cache freshness;
+- whether a stale value may be used;
+- whether a mid-session update can change behavior;
+- control fallback when no value is available.
+
+Avoid UI flicker and treatment changes after the user has already seen control. For a session-scoped experience, freeze the evaluated value for the session unless the product requirement explicitly allows live changes.
+
+Remote Config documentation establishes the general fallback order for configuration keys:
+
+1. remote value;
+2. local default;
+3. empty when neither exists.
+
+For an experiment Feature, prefer an explicit typed application default even when the platform SDK offers an overload or local default store.
+
+## Exposure
+
+Configuration retrieval is not exposure. A getter that automatically reports exposure is valid only if calling the getter coincides with applying the assigned behavior. If the application reads early, preloads, branches later, or may discard the result, disable automatic exposure and use manual exposure at the true activation point.
+
+Read `exposure-contract.md` before finalizing exposure behavior.
+
+## Custom fetch parameters
+
+Use custom fetch parameters only for fields supported by the client configuration channel. Document:
+
+- field name and type;
+- source of truth;
+- whether it affects targeting, diagnostics, or payload enrichment;
+- privacy classification;
+- behavior when absent.
+
+Never place secrets or unstable session values in custom fetch parameters.
+
+## Acceptance checks
+
+- Analytics, Remote Config, and experiment SDK versions are compatible.
+- Initialization uses the intended app and environment.
+- The control default is returned when configuration is unavailable.
+- A test identity receives a stable group across sessions.
+- Client and server agree for the same assignment identity.
+- Exposure occurs once at treatment activation, not at preload.
+- Outcome events join to exposure.
+- Account switching does not leak the previous account’s assignment.
+- Debug logging and test mode are disabled or production-safe before release.

package/skills/ae-experiment-design/references/exposure-contract.md

@@ -0,0 +1,91 @@
+# Experiment Exposure Contract
+
+Read this reference whenever exposure affects assignment, metrics, SDK code, or rollout readiness.
+
+## Exposure definition
+
+Exposure means the assigned behavior was actually rendered or became effective for the analysis unit. It is not:
+
+- SDK initialization;
+- configuration fetch;
+- Feature preload;
+- getter execution when the result may be discarded;
+- assignment calculation without treatment activation.
+
+## Automatic versus manual exposure
+
+The verified Android, iOS, and JavaScript experiment pages state that a typed getter automatically uploads exposure when `automaticExposureTracking` is enabled.
+
+Use automatic exposure only when the getter is called at the same decision point where the value is applied.
+
+Use manual exposure when:
+
+- values are prefetched;
+- a getter is called before eligibility is final;
+- the result may not render;
+- the server assigns but the client activates;
+- one value is read multiple times before a single activation;
+- the product needs a later, explicit effective point.
+
+Do not combine automatic getter exposure and manual exposure for the same activation.
+
+## Exposure owner
+
+Choose exactly one:
+
+- client rendering owner;
+- server behavior owner;
+- another verified activation service.
+
+Document why that component knows the treatment became effective.
+
+## Deduplication contract
+
+Define an application-level deduplication key from stable facts such as:
+
+- project and environment;
+- experiment or Feature;
+- assignment identity;
+- assignment or group;
+- activation scope such as session, page instance, or decision instance.
+
+Do not invent AE event property names. Let the verified SDK emit its supported schema, or resolve the exposure event contract through `ae-cli`.
+
+Retry must be idempotent at the chosen activation scope.
+
+## Identity and join
+
+The identity used for assignment, exposure, and outcome must either be the same or have a verified merge path.
+
+Block launch when:
+
+- anonymous and logged-in identities can cross groups;
+- server and client use different assignment subjects;
+- exposure uses device identity while outcomes use an unlinked account identity;
+- account switching can inherit a cached assignment;
+- the analysis unit cannot be reconstructed from platform evidence.
+
+## Outcome contract
+
+For the confirmed primary event metric, define:
+
+- event or measure;
+- identity;
+- timestamp;
+- attribution window;
+- denominator or eligible population;
+- relation to exposure;
+- duplicate and late-event treatment.
+
+Do not report an exposure merely to force a user into the denominator. Fix the metric or eligibility contract instead.
+
+## Acceptance tests
+
+- Getter without rendering does not produce exposure in manual mode.
+- Rendering produces one exposure.
+- Re-render behavior matches the pre-registered exposure scope.
+- Retry does not create duplicate logical exposure.
+- Control and treatment exposure are both observable.
+- Assignment proportions match configured allocation.
+- Exposure and outcome join for anonymous, login, logout, and account-switch paths.
+- Offline and delayed-upload behavior is understood before launch.

package/skills/ae-experiment-design/references/hybrid-experiment-sdk.md

@@ -0,0 +1,74 @@
+# Hybrid Experiment Architecture
+
+Read this reference when the server assigns or prepares a variant but the client renders or activates the treatment.
+
+## Ownership model
+
+Assign one owner for each responsibility:
+
+| Responsibility | Typical owner |
+|---|---|
+| Stable identity resolution | Server or shared identity service |
+| Assignment or Feature evaluation | Server |
+| Typed default | Both sides, with one canonical value |
+| Rendering or activation | Client |
+| Exposure | Client when it knows rendering succeeded |
+| Outcome events | Side that owns the business action |
+
+These are design defaults, not fixed product requirements.
+
+## Server-to-client envelope
+
+Define an application envelope such as:
+
+```text
+{
+  featureKey,
+  value,
+  valueType,
+  assignmentOrGroupId,
+  configVersion,
+  evaluatedAt,
+  exposureToken?
+}
+```
+
+This is architecture-level pseudocode. Verify any AE-specific schema through `ae-cli`.
+
+## Consistency rules
+
+- Server and client must use the same project, environment, Feature key, and stable identity.
+- The client must validate the value type before applying it.
+- A missing, invalid, or expired envelope falls back to the typed control behavior.
+- Do not re-evaluate independently on the client after a server assignment unless the product explicitly supports that mode.
+- Do not allow account switching to reuse another account’s cached envelope.
+- Include a configuration version or equivalent diagnostic marker when the verified platform provides one.
+
+## Exposure handoff
+
+The server should not report exposure merely because it returned a treatment envelope when the client may never render it. Prefer:
+
+1. server evaluates;
+2. client receives and validates;
+3. client applies behavior;
+4. client reports exposure once.
+
+If exposure must be server-side, define a client acknowledgment or another verified activation signal and make retry idempotent.
+
+## Failure scenarios
+
+- server evaluation succeeds, client render fails: no exposure;
+- server times out: client uses control;
+- client starts offline with cached assignment: use only within the documented stale window;
+- server and client identity disagree: block rollout;
+- both sides report exposure: disable one path before launch;
+- value arrives after control rendered: freeze control for the session or use an explicitly approved transition.
+
+## Acceptance checks
+
+- Server and client return or apply the same value type.
+- Treatment is not visible before identity is stable.
+- Exposure is reported by one owner.
+- Refresh and retry do not duplicate exposure.
+- Cached assignment is isolated by identity and environment.
+- Outcome events remain joinable across client and server.

package/skills/ae-experiment-design/references/metric-readiness.md

@@ -0,0 +1,143 @@
+# Metric Readiness
+
+Use this checklist to decide whether a candidate metric can support an experiment decision.
+
+## Contents
+
+- Supported experiment metric contract
+- Preregistered planning policy
+- Evidence levels
+- Feasibility gates
+- Role selection
+- Common blockers
+- Required output
+
+## Supported experiment metric contract
+
+Use event metrics only. A platform enum or API field is not evidence that
+another metric kind is implemented in the report calculation path.
+
+Use only these event calculation codes:
+
+| Code | Calculation | User-level value | Planning type |
+| --- | --- | --- | --- |
+| `A101` | Triggered users | Whether each user triggered the event; compare group trigger rates | `proportion` |
+| `A100` | Total times | Each user's total event count; compare group user-level means | `continuous` |
+| `A201` | Days | Each user's distinct active-event days; compare group user-level means | `continuous` |
+| `A103` | Sum | Each user's sum of a numeric event property; compare group user-level means | `continuous` |
+| `A104` | Average | Each user's average numeric event-property value; compare group user-level means | `continuous` |
+| `A106` | Maximum | Each user's maximum numeric event-property value; compare group user-level means | `continuous` |
+| `A108` | Distinct count | Each user's distinct count of one event property; compare group user-level means | `continuous` |
+
+Require a numeric event property for `A103`, `A104`, and `A106`, and an exact
+event property for `A108`.
+
+The current report calculation uses a two-sided Z test for both planning
+types, returns p-value, lift, and a 95% confidence interval, and uses
+`p < 0.05` plus confidence-interval direction and goal direction to label a
+positive or negative significant result.
+
+## Preregistered planning policy
+
+Fix the family-wise significance level at `alpha=0.05`, the confidence level
+at `0.95`, and the test direction at two-sided to match current reporting.
+Use `power=0.80` as the explicit planning-policy default when the user does not
+provide power, and label its source as `policy_default`.
+
+Require the MDE before definitive planning. Record whether it is `relative` or
+`absolute` and whether the desired effect is an `increase` or `decrease`; never
+silently substitute a 5% lift. Require observed user-level standard deviation
+for continuous metrics; never substitute an assumed coefficient of variation.
+
+For one control and multiple treatments, treat each treatment-versus-control
+comparison as one member of the same family. Use Bonferroni planning:
+`alpha_per_comparison = 0.05 / number_of_treatments`. Return the family alpha,
+adjusted alpha, method, and comparison count. The current native report still
+labels significance with unadjusted `p < 0.05` and a 95% confidence interval,
+so use raw p-values against the preregistered adjusted threshold for the final
+decision and disclose that native-label mismatch.
+
+Use a minimum runtime of seven days and align recommendations to full weeks by
+default; permit explicit overrides when the decision context justifies them.
+When traffic is not fixed, evaluate absolute experiment-traffic candidates no
+greater than the verified layer capacity and choose the smallest candidate
+that reaches the sample target within the maximum runtime. If none is feasible,
+return the true duration at maximum available traffic and mark it infeasible;
+never truncate the duration to the maximum.
+
+Do not add ad hoc missing-value imputation, winsorization, truncation, or
+post-treatment exclusions. Use the exact platform metric definition and
+preregister any supported filtering or data-quality rule before the run.
+
+Call `calculate_experiment_plan.py` with `metric_type`, `baseline`, `mde`,
+`mde_type`, `effect_direction`, `allocations`, and `daily_eligible_units`.
+Pass `standard_deviation` for a continuous metric. Pass `experiment_traffic`
+when traffic is confirmed; otherwise pass `max_available_traffic` and
+optionally `traffic_candidates` to request a recommendation. `power`,
+`min_runtime_days`, `max_runtime_days`, and `align_to_full_weeks` may override
+their policy defaults. Do not pass `confidence_level` other than `0.95`.
+
+Do not create or recommend a metric outside this contract. If the requested
+business outcome cannot be expressed by one supported event calculation,
+state that it is unavailable and propose the closest valid event metric
+without representing it as equivalent.
+
+## Evidence levels
+
+Label every statement:
+
+- `verified`: supported by current `ae-cli` platform output;
+- `provided`: supplied by the user but not verified on the platform;
+- `assumed`: introduced for design or sensitivity analysis;
+- `missing`: required evidence is unavailable.
+
+Only `verified` or explicitly accepted `provided` evidence can support a final readiness decision.
+
+## Feasibility gates
+
+A metric is feasible only when all applicable gates pass:
+
+1. **Contract**: event, supported calculation code, required property, goal
+   direction, filters, and attribution window are explicit.
+2. **Source**: required events and properties exist or are supplied as a concrete schema.
+3. **Identity**: assignment, exposure, and outcome share a stable join path.
+4. **Ordering**: outcome is attributed after exposure or treatment activation.
+5. **Population**: pre-treatment eligibility and exclusions are reproducible.
+6. **Planning evidence**: baseline, MDE and its type and direction, eligible
+   daily units, verified layer capacity when recommending traffic, and—except
+   for `A101`—user-level standard deviation are available before a definitive
+   sample or duration calculation.
+7. **Stability**: collection and definition are not expected to change during the experiment.
+8. **Sensitivity**: the metric can plausibly respond to the treatment.
+
+Block or mark unverified when any required gate lacks evidence.
+
+## Role selection
+
+### Primary
+
+Choose one supported event metric closest to the hypothesis and decision.
+Confirm its calculation code and direction, then establish its baseline and
+minimum business-relevant effect. Do not calculate a definitive duration
+before the metric contract is confirmed.
+
+## Common blockers
+
+- missing exposure event or treatment-activation marker;
+- assignment uses `user_id` while outcomes only have `device_id`;
+- anonymous-to-login identity cannot be reconciled;
+- cross-device identity is unstable;
+- outcome precedes exposure;
+- denominator is filtered by post-treatment behavior;
+- event volume is too low;
+- metric definition or instrumentation changed during the run;
+- cross-platform events use incompatible identities or semantics.
+
+## Required output
+
+For each candidate, return:
+
+| Metric | Status | Event | Calculation | Property | Direction | Join identity | Window | Evidence | Reason or remediation |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+
+When blocked, give the smallest concrete instrumentation or identity change that would make the metric measurable.