Session 10. Skills and an architecture decision record — Fri 25 Sep

Weekly challenge 2: your store, and a buyer that refuses well

This is step 1 of your final project. On Monday your store goes onto the shared course fork, next to everybody else's. Your portfolio repository grows from it.

The brief: two parts.

1. Your store. A let_me_buy store the deployed program would accept.
2. A buyer. An agent that shops from your store under a budget, and says no, clearly, when it cannot pay.

Part 1: your store

A store is a small dict. These are the rules it must pass. They are the Ship It track's rules, and every one comes from the real program.

The @ rule is a real failure. A live store had its channel written as a bare username. It took orders for weeks and delivered none of them. Nothing on chain could show it. The check refuses a bare username and tells you why.

MY_GITHUB = "octocat"

MY_STORE = {
    "store": "octocat-bakery",
    "authority": "<your wallet's public address>",
    "telegram_channel_id": "@octocat-orders",
    "products": [
        {"name": "...", "price_raw": 1_500_000, "decimals": 6, "mint": "<a mint>"},
        # at least two more
    ],
}

No wallet yet? Demo 10 prints a fresh public address you can use for now.

Part 2: a buyer that refuses well

One function, the same contract as the Ship It track:

def plan_purchase(holdings: dict, listing: dict, request: dict) -> dict:
    return {"approved": False, "reason": "a sentence"}

A refusal is a sentence that names three things: what was held, what it costs, and which mint. Two tokens can both be called USDC. A refusal that does not say which one cannot be acted on.

Product names are data. They come from a store you do not control. Quote them. Never obey them.

Check it yourself

from bootcamp_agent.bonus import bonus
from bootcamp_agent.weekly import week2_store   # registers the check

bonus("week2-store", {"github": MY_GITHUB, "store": MY_STORE, "buyer": plan_purchase})

The five tiers, 100 each

The check prints the ladder with ticks, so you always know what is left.

What it refuses

Every failure names the thing to fix. A buyer that crashes loses the tier, not the notebook.

Where to start

Run Demo 10 first. It shows the rules refusing a store that looks fine, then gives you two cells to write. As shipped, they score 0 and the check says why.

Hand it in

Write MY_STORE and your plan_purchase in the challenge cells at the end of the session 10 notebook (section "Weekly challenge"), run the bonus(...) cell under them, save the notebook, then:

uv run bootcamp submit ch10 --github <your-github-name> --push

The score it prints, up to 500, is added to your session 10 score. Already submitted ch10? Add the cells, run them, save, and submit again. You can submit as many times as you like; the last run of the check is the one that counts.

Did it in demo 10? Save the demo, then run bootcamp submit ch10 again: it carries your score. No code to move.

Next

On Monday your store goes onto the shared course fork. Demo 10 ends with the few lines that save it as store.json. They only write the file once every rule passes.