True Cost Group. Built Oct 28, 2026, 10:20 PM AST.

Two Tasks For Thursday, Oct 29

Two developers, two projects, one day each. Both due Thursday Oct 29 at 6 PM AST. Each one ends with a list of what is left before production and the developer's own time estimate for it. Nobody touches the sales dashboard.

1. Member App

Developer 2Due Thu Oct 29, 6 PM AST

What it is

The members area for True Cost Group clients. A member signs in with a code and their date of birth, and sees their plan, their doctors, their prescriptions and prices, their ID card, guides for their state, and a way to ask the team a question. It is a read-only window into what we already know about them. Goal: a member never has to call to find out what they have.

Where it runs

Tomorrow's task

  1. Design check. Open every page on an iPhone and on a desktop browser. Anything that looks wrong, is cut off, overlaps, is misspelled, or a member would not understand: screenshot it and write one line.
  2. Click everything. Every button, link, tab and form. Anything that does nothing, errors, or goes to the wrong place: screenshot it and write one line.
  3. Spot check 15 real members. On the preview, open 15 members (we give the list). For each one confirm the plan name, the monthly amount, the doctors, the prescriptions and the ID card match the source record we hand over with the list. Write a row per member: matches, or what is off.
  4. Production-ready list. After the above, write everything that still has to happen before real members are told about this app: every defect to fix, anything missing, anything risky. Next to each item, your own time estimate in hours or days, and a total.

What to send back by 6 PM

One document: the defect list (page, what you did, what happened, screenshot, P0 / P1 / P2), the 15-member table, and the production-ready list with a time estimate per item and a total. Every page named, even the clean ones, with "no defect" next to it. Fixes start the next day.

What they need

  • Nothing for steps 1 and 2.
  • For step 3: an admin account on the preview plus the 15-member list with the source records. Xavi prepares the list once Victor names the tester.
  • Full code: GitHub invite to testedmedia/tcg-member-app (see Code Access below).

Other options for the same day

  • Code audit instead of a spot check: read the sign-in and the "view as member" code and write up every place a member could see another member's data. Two to three hours, needs the repo on GitHub.
  • Both: design and clicks in the morning, code audit in the afternoon, skip the spot check until the list is ready.

2. Affiliate Portal (TrueCost Rx)

GabrielDue Thu Oct 29, 6 PM AST

What it is

The affiliate program for TrueCost Rx, the prescription discount membership. An affiliate (an agent, a clinic, anyone with an audience) signs up, gets a personal link and a typed code, and sends people to join TrueCost Rx. Every join that comes through that link or code is credited to the affiliate, the affiliate earns a commission on each paying member every month, and the portal shows their members, their commissions and their statements. Goal: other people sell TrueCost Rx for us and we only pay when a member pays.

Where it runs

Tomorrow's task

  1. Sign up as an affiliate three times: once with email and password, once with Google, once through the "Become an affiliate" tab. Confirm each one lands on its own dashboard with its own link and code.
  2. Make a sale through each affiliate. In a private browser window, join TrueCost Rx as a member once through the affiliate's link, once by typing the affiliate's code, once with no link or code at all. Then check the affiliate dashboard: the first two show as that affiliate's member with a commission, the third shows nowhere.
  3. Walk every view on phone and desktop: dashboard, links, codes, members, commissions, statements, settings, and the admin view. Compare each to the approved design. Anything different, broken or confusing: screenshot and one line.
  4. Audit everything, then the production-ready list. Wrong password, expired link, the same code twice, a member joining twice, signing out and back in, the emails that go out, the numbers on the commission and statement screens adding up. Then write everything that still has to happen before a real affiliate is given a link: every defect, anything missing, anything risky. Next to each item, your own time estimate in hours or days, and a total.

What to send back by 6 PM

One document: the three affiliate accounts, the three test members and what each affiliate dashboard shows for them, the defect list per view (screenshot, P0 / P1 / P2), and the production-ready list with a time estimate per item and a total. Last line: ready to go live, yes or no, and why.

What they need

  • The staging URL and passcode (Xavi sends it through the vault, not chat).
  • Full code: GitHub invite to testedmedia/truecost-rx-app (see Code Access below).

Code Access (Full)

  1. Xavi pushes both projects to GitHub tonight as private repos under the testedmedia account: testedmedia/truecost-rx-app and testedmedia/tcg-member-app. Each repo gets a README-DEVS.md: how to run it locally, where the mockups are, where the handoff is.
  2. Each developer sends his GitHub username. Xavi adds him as a collaborator with Write access (full code, branches, pull requests). testedmedia is a personal account, so it is one invite per repo, no org seats, free.
  3. They clone and work on a branch. Main is protected: a change reaches main only through a pull request that Xavi or Victor approves. Nothing deploys from their push.
  4. Staging and production stay with Xavi. Cloudflare, the domains, the database and the keys are not part of code access. A developer who needs a staging deploy opens the PR and gets it deployed the same hour.

Secrets (the BaxRx test key, Resend key, staging passcode) travel through a shared vault, never a chat message, and are never committed to the repo.