The Cloud

00 · What Button Is — Engagement Context

🔘
Button
—:—/—:—

00 · What Button Is — Engagement Context

🔘

The anchor doc. Every downstream page and every dispatched agent reads this first. Kept living. Correct it the moment reality diverges.

The company

Button (usebutton.com) operates in commerce / retail-media / affiliate infrastructure. Their core motion: connect retailers, publishers, creators, and advertisers into a tracked commerce network, then drive traffic quickly toward products in that network via collaborative / co-branded ads with attribution layered on top.

  • Creator portal: creators drop in their own Amazon affiliate link; Button layers trackable, attributed links on top of it, tying downstream sales back to the creator and the network.

  • Traffic engine: collaborative ads move traffic fast toward network products, tracked end-to-end.

  • Active partners (per Daniel, to be verified by research pass): Walmart, and "Reece / sports research" (exact entity TBD — flagged for the market-research dispatch to confirm).

⚠️

Everything above is founder-briefed, not yet independently verified. The first research dispatch's job #1 is to confirm/correct this section against public sources. Do not treat as canonical until vetted.

The business problem (their pain — our wedge)

The operations layer is manual and painful:

  • Onboarding retailers.

  • Sourcing creative and creators.

  • Getting deals set up and live.

Every one of those is human glue today. The stated goal: less manual, more powerful, more effective, more innovative.

🔥

The mandate — read this twice. Updated per Daniel, higher scope. Teka is not consulting Button on the margins. Teka is rebuilding Button's entire stack end-to-end on The Cloud substrate, improving it, and expanding it past what Button can do today. The website, the creator portal, the retailer onboarding, the deal pipeline, the tracking/attribution layer — all of it gets rebuilt on The Cloud, made better, and extended with capability Button doesn't currently have. The Cloud is the substrate the whole rebuilt stack runs on; Teka is the Lab that builds and expands it. This is a full-stack rebuild-and-expand engagement, not a back-office cleanup. Every downstream doc, audit, and dispatch inherits this scope.

The engagement — what Teka is delivering

  1. The Cloud as WorkSpace — end-to-end business substrate for Button's internal ops (onboarding, sourcing, deal pipeline, docs, task pipelines).

  2. Teka as their Lab — Button's R&D / build partner; the dispatch fleet runs their research, builds, and automation.

  3. Website rebuild — full modern rebuild at Fable-level design with SEO + GEO rigor. Decision locked: GitHub repo + Vercel for scale (not Studio). Studio is skipped for this build per Daniel's call.

  4. Ops automation — progressively replace manual onboarding/sourcing/setup with powerful, effective, automated flows.

Working rules for this Space (same as Cloud + Kindo)

  • Docs pattern mirrors Kindo: Identity → What It Is → Mission/Positioning → Architecture → Tech Stack → Delivery Pipeline → Gate Board → Access (Private) → numbered Audits + BuildDocs.

  • BuildDoc routing: dev blockers/fixes/features → BuildDocs (phased) or tasks (single fixes), cross-linked via Portable References, slotted into this Space's own pipeline page.

  • Dispatch discipline: repo-bound spawns clone fresh on new ora/agent-* branches. Ora vets + sequences; Daniel taps merge — never auto-merge.

  • Model routing: mechanical wedges → cheapest tier that holds the bar (Alpaca/native). Novel logic + synthesis → frontier tier. Gate suite is the quality bar.

  • Access & credentials live on the private Access page — never inline in working docs.

Open questions (resolve early)

  • Confirm the exact identity of "Reece / sports research" partner.

  • Confirm scope of the Walmart relationship (live? pilot? which surface?).

  • Where does Amazon affiliate fit vs. Button's own link-layering — is there overlap/tension with Teka's own teka000-20 Amazon work, or is it clean?

  • Who on Button's side is the executive sponsor and who are the day-to-day users of the WorkSpace? (Onboarding design depends on this.)

  • Website rebuild: is there an existing brand system to honor, or is this a from-scratch identity?


The Cloud