Skip to content

docs(spec): §8 counsel items record their now-existing drafts (HT-5) #101

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zaridan merged 1 commit into from
Jul 20, 2026
Merged

docs(spec): §8 counsel items record their now-existing drafts (HT-5) #101

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions specs/modules/marketplace-v1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -909,10 +909,10 @@ dependencies" quietly become a catch-all label for anything pre-launch.

| Item | Nature | Gate | Not gating |
|---|---|---|---|
| Commercial module license text (replaces the current placeholder) | Counsel-drafted | Before Stripe flips to live mode / before the marketplace takes real money | Does **not** gate HT-82's test-mode dogfood — Resonant IQ as its own test-mode customer needs no finished license text, only a placeholder |
| Terms of sale — including the refund policy (§2's `refunded` state, §5.3's decommission-after-refund), the refund window (**14 days**) and config-export grace period (**7 days**) (§5.3; the day figures are confirmed, §10.11 — only the customer-facing policy *wording* remains on this gate), and the dispute-handling policy (§2's `frozen` state): this spec pins the entitlement and hosting-lifecycle *mechanics* and the exact windows; the customer-facing policy language is counsel's/TJ's call | Counsel-drafted (the window figures are decided; policy wording remains) | Before Stripe flips to live mode / before the marketplace takes real money | Same — pre-revenue, not pre-dogfood (test-mode dogfood uses the confirmed figures) |
| Privacy policy for the store | Counsel-drafted | Same gate (real customer PII starts flowing at first live charge) | Same |
| **Managed-hosting terms & data-handling disclosure** (new in v1.1) — because a Resonant IQ-hosted module reads the operator's conversation data on Resonant IQ infrastructure to do its job, managed hosting is the charter's "hosted convenience services" (§3) made real, and it needs its own disclosure/DPA-style terms the operator consents to at enrollment (§3e). This is distinct from the store privacy policy, which covers *purchaser* PII; this covers the *operator's end-customers'* conversation data flowing through a hosted module | Counsel-drafted | Same gate — real operator data starts flowing through a hosted module at first live managed install | Not pre-dogfood — Resonant IQ hosting its own module for its own desk raises no third-party data question. **The charter §2 own-your-data reconciliation flagged at §10.13 is now RESOLVED — charter §2 was amended the same day (HT-5/HT-82); the managed-hosting data-handling terms/disclosure themselves remain on this gate** |
| Commercial module license text (replaces the `All rights reserved` placeholder in module repos) — **DRAFTED 2026-07-19**: `legal/module-commercial-license.md` (this repo), pending TJ counsel sign-off + adoption into each module repo | Drafted; adoption pending | Before Stripe flips to live mode / before the marketplace takes real money | Does **not** gate HT-82's test-mode dogfood — Resonant IQ as its own test-mode customer needs no finished license text, only a placeholder |
| Terms of sale — including the refund policy (§2's `refunded` state, §5.3's decommission-after-refund), the refund window (**14 days**) and config-export grace period (**7 days**) (§5.3; the day figures are confirmed, §10.11 — only the customer-facing policy *wording* remains on this gate), and the dispute-handling policy (§2's `frozen` state): this spec pins the entitlement and hosting-lifecycle *mechanics* and the exact windows; the customer-facing policy language is counsel's/TJ's call — **DRAFTED 2026-07-19**: `legal/terms-of-sale.md` in the marketplace repo, pending TJ counsel sign-off + publication on the store | Drafted; sign-off + publication pending | Before Stripe flips to live mode / before the marketplace takes real money | Same — pre-revenue, not pre-dogfood (test-mode dogfood uses the confirmed figures) |
| Privacy policy for the store — **DRAFTED 2026-07-19**: `legal/privacy-policy.md` in the marketplace repo (purchaser-PII scope, subprocessors incl. Resend, category retention), pending sign-off + publication | Drafted; sign-off + publication pending | Same gate (real customer PII starts flowing at first live charge) | Same |
| **Managed-hosting terms & data-handling disclosure** (new in v1.1) — because a Resonant IQ-hosted module reads the operator's conversation data on Resonant IQ infrastructure to do its job, managed hosting is the charter's "hosted convenience services" (§3) made real, and it needs its own disclosure/DPA-style terms the operator consents to at enrollment (§3e). This is distinct from the store privacy policy, which covers *purchaser* PII; this covers the *operator's end-customers'* conversation data flowing through a hosted module — **DRAFTED 2026-07-19**: `legal/managed-hosting-terms.md` in the marketplace repo (incl. Article-28-shaped Data Processing Terms and the model-provider conduit clause), pending sign-off; consented at enrollment when managed hosting ships | Drafted; sign-off pending | Same gate — real operator data starts flowing through a hosted module at first live managed install | Not pre-dogfood — Resonant IQ hosting its own module for its own desk raises no third-party data question. **The charter §2 own-your-data reconciliation flagged at §10.13 is now RESOLVED — charter §2 was amended the same day (HT-5/HT-82); the managed-hosting data-handling terms/disclosure themselves remain on this gate** |
| **Stripe Tax enabled** (automated EU VAT / US sales-tax calculation and remittance on Checkout Sessions) | Compliance/finance configuration, not counsel-drafted | Same gate — charging real customers across jurisdictions without correct tax handling is its own launch blocker | Not pre-dogfood — Stripe test mode carries no real tax obligation. Which jurisdictions to register in first is decision point §10.9 |

The plugin exception's counsel deadline — set in CHARTER.md §3's module boundary,
Expand Down