Purpose
Track the three written confirmations Anna/Jiao said were still being coordinated on 2026-08-13. These are business/release gates, not implementation blockers for the current draft.
Required written answers
Current evidence
Jiao's email of 2026-08-13 confirms:
- Host-API-only Schema 2 Apps can qualify without a local Executa/runtime;
- developer activation is self-service;
- the handle and slug are first-come-first-served;
- promotional support is prospective rather than guaranteed;
- the remaining Terms/revenue/metrics answers were being coordinated.
The public Developer Hub currently documents the technical publishing lifecycle but does not provide the required commercial calculation or qualified-usage dashboard details. An older public Verified Developer page still describes manual activation and should not be treated as the current operational flow.
Safety / confidentiality
- Do not paste private account tokens, KYC data, tax identifiers, bank details, or confidential contract attachments into this public issue.
- Record only public links, concise confirmed definitions, dates, and release-impact decisions.
- Any non-public agreement must be reviewed outside the public repository; this issue should contain only a sanitized decision summary.
Release impact
PR #30 may continue as a draft and may receive an early technical review once the authenticated core flow works. Public release and business forecasts remain blocked until the owner has reviewed the current Terms and revenue mechanics.
Exit condition
Close only when the owner has received, reviewed, and recorded a privacy-safe decision summary for all three areas: Terms, revenue calculation/payout, and qualified-usage measurement.
Purpose
Track the three written confirmations Anna/Jiao said were still being coordinated on 2026-08-13. These are business/release gates, not implementation blockers for the current draft.
Required written answers
70% of eligible usage profit.Current evidence
Jiao's email of 2026-08-13 confirms:
The public Developer Hub currently documents the technical publishing lifecycle but does not provide the required commercial calculation or qualified-usage dashboard details. An older public Verified Developer page still describes manual activation and should not be treated as the current operational flow.
Safety / confidentiality
Release impact
PR #30 may continue as a draft and may receive an early technical review once the authenticated core flow works. Public release and business forecasts remain blocked until the owner has reviewed the current Terms and revenue mechanics.
Exit condition
Close only when the owner has received, reviewed, and recorded a privacy-safe decision summary for all three areas: Terms, revenue calculation/payout, and qualified-usage measurement.