| index b0f556eb6..1512984b7 100644 |
| --- a/implementation/carloku-paid-launch/AGENT_HANDOFF.md |
| +++ b/implementation/carloku-paid-launch/AGENT_HANDOFF.md |
| @@ -6,7 +6,7 @@ This file is context and instructions for the next coding agent. The branch is a |
| |
| ## Objective and current boundary |
| |
| -Paul asked to get carloku.com paid pricing live by morning and asked whether Stripe Tax can handle tax. Yes for calculation and collection. The VAT/OSS registrations are active, and Paul approved Stripe's PaaS classification and the plan-specific codes below. He then explicitly requested this branch handoff so another agent can pick up the work. |
| +Paul asked to get carloku.com paid pricing live by morning and asked whether Stripe Tax can handle tax. Yes for calculation and collection. The VAT/OSS registrations are active, and Paul approved Stripe's PaaS classification and the plan-specific codes below. He requires the complete metered model at launch; annual subscriptions with temporarily waived overages are not an acceptable launch scope. Object-storage overages count only transfer that AWS charges Team Tito for, so delivered-byte access logs alone are not billing authority. He then explicitly requested this branch handoff so another agent can pick up the work. |
| |
| Billing remains OFF. Read-only live Stripe requests verified the account on 2026-09-21; no charges, catalog mutations, production infrastructure changes, or deployments were made. The platform changes are being checkpointed on `feat/carloku-paid-launch-20260916` at `https://amadan.net/carlos/platform`. Nothing is being merged to main. |
| |
| @@ -73,8 +73,8 @@ make test |
| - Billing copy review: http://docs-t1.tail5fd3ba.ts.net:34185 |
| - Postal/location copy review: http://docs-t1.tail5fd3ba.ts.net:46235 |
| - Review data lives in `writing/{pricing-launch,billing-launch,billing-location}` in scratch. All three servers last responded HTTP200; no result.json was present. No pricing page or billing UI copy has been applied. Apply submitted source strings verbatim; use the writing/copy-review skills for new user-facing copy. |
| -- Object-store transfer contract question is pending: all bytes served directly to customers/apps (including AWS), excluding Carloku's traffic, or only AWS-chargeable external transfer? AWS IP-feed complement is not proof of chargeable traffic; it omits BYOIP/some services. |
| -- Optional annual-only launch/waived-overage question was asked and unanswered. No waiver or reduced launch scope is authorized by silence. |
| +- Object-store transfer contract is settled: count only transfer that AWS charges Team Tito for. AWS access logs show delivered bytes but cannot reliably identify every free-transfer case, so they are not sufficient billing authority by themselves. The collector needs billing-grade AWS evidence, durable customer attribution and a hold when that evidence is incomplete. |
| +- Launch scope is settled: the complete metered model is required. Do not launch annual subscriptions with overages waived or defer any meter as a post-launch follow-up. |
| |
| ## Infrastructure and artifact cautions |
| |
| @@ -88,6 +88,6 @@ A scratch SQLite experiment was also found replacing local root main.go. It was |
| |
| 1. Read Amadan CI for the final durability-fix commit and inspect the complete branch diff as WIP. The local gate is green, but that does not make the launch ready. |
| 2. Review host wiring: `bindingFailed` is set on unmetered fallbacks but currently only the permanently false attestation prevents billing. Finish per-route move/checkpoint tests and client inventory, source completeness folding, scoped external-client exclusion, crash/late-callback/restart proof, bounded ledger retention and real-disk latency measurement. Keep unattested usage unbillable until proved. |
| -3. Implement P5 collector with durable deduplication, immutable historical bucket ownership and a settled transfer contract. Prepare exact scoped logging activation before seeking production approval. |
| +3. Implement P5 collector with durable deduplication, immutable historical bucket ownership and AWS billing-grade classification so only transfer AWS charges Team Tito for reaches overage billing. Prepare exact scoped logging activation before seeking production approval. |
| 4. Complete partial-month billing, quantity/proration collection, operator review/house doors, Free enrollment/caps/idle/flush-only, dormancy warnings/archive and revenue-pool accounting required by the spec. Use the requirements audit rather than treating these as optional follow-ups. |
| 5. After copy approvals, provision and verify the Stripe catalog with the approved per-plan PaaS codes, run the real sandbox purchase/webhook/portal flow, obtain independent reviews, pass Amadan CI and release gates, then land/deploy through the required reviewed path and verify live behaviour. No main merge or deployment is part of this handoff. |
amadan