Register or sign in

There is no password. We email you a sign-in link, and you open it on this device. Use the same form to sign in again later.

Never paste passwords, tokens or keys here.

Never paste passwords, tokens or keys here.

Google and Microsoft sign-in are coming soon. Until then, the email link works with any address, including Gmail and Outlook.

Foundry · Chapter 12

Your 30 Days with Foundry

One short task a day that walks you through the whole book again, and an expert to ask when you get stuck.

The 30-day plan

This is the plan from the end of Chapter 12. Do one task a day. If you miss a day, carry on from where you stopped. Reading this page needs no account.

Week one, the idea (Chapters 1 to 3)

  1. Day 1Write three ideas. Run the "explain my idea back to me" prompt from Chapter 1.
  2. Day 2Reread the AI's answer. List what it said it was unsure about.
  3. Day 3Fill in your Idea Canvas from Chapter 2.
  4. Day 4Turn the canvas into a one-page intent file. Add one line on who might attack it.
  5. Day 5Draw the DevSecOps loop from Chapter 3 for your own idea.
  6. Day 6Answer Chapter 3's four questions: what to protect, how, how sure you are, and who pays.
  7. Day 7Rest. Read your notes once. Change nothing.

Week two, Dev (Chapters 4 to 7)

  1. Day 8Set up your workbench and project folder, as in Chapter 4.
  2. Day 9Connect GitLab and Azure. Check which account is active before you do anything else.
  3. Day 10Let the AI interview you and draft your instructions, as in Chapter 5.
  4. Day 11Add the beginner safety profile and the finish-the-job rule to those instructions.
  5. Day 12Reread Chapter 6. Write down one feature you would add to your idea later.
  6. Day 13Plan your website with the AI. Read the plan and the cost. Say go only when both are right.
  7. Day 14Deploy it. Open the live page on your phone.

Week three, Sec (Chapters 8 and 9)

  1. Day 15Note one time the AI stopped and asked you. Write down why that was good.
  2. Day 16Check your permission mode from Chapter 8. Make sure it is not a bypass mode.
  3. Day 17Create a scoped, expiring GitLab token, as in Chapter 9.
  4. Day 18Store it in Key Vault. This is the hard day. Be patient with it.
  5. Day 19Add your first security scan with one prompt.
  6. Day 20Read the scan results. Ask the AI to explain one finding and fix it.
  7. Day 21Rest.

Week four, Ops (Chapters 10 and 11)

  1. Day 22Open the free services page. Set a budget with alerts, as in Chapter 10.
  2. Day 23Open Cost analysis. Confirm your real spend matches what the AI promised.
  3. Day 24Add a fingerprint to your page and set up an uptime check, as in Chapter 11.
  4. Day 25Rehearse an outage. Time the alert. Recover, then look.
  5. Day 26Break a practice branch on purpose. Read the failed pipeline. Ask the AI to fix it properly.
  6. Day 27Run the teardown prompt. Remove what you do not need. Keep your live site.
  7. Day 28Rest.

The last two days (Chapter 12)

  1. Day 29Make one small, real change to your site. Take it all the way: idea, merge request, pipeline, live page, fingerprint. Check it yourself.
  2. Day 30Write one page about the month. What worked? What bit you? Which principle did you nearly forget? Keep it. It is the start of your own rulebook.

Your diary

Opens soon

The online diary is not open yet. Soon you will be able to tick off each day, note your time and what you learned, and share a week with an expert.

Until then, use the diary pages in your book, and register (Sign in, top right) so you are ready when it opens. You can already ask an expert below.

Ask an Expert

An expert has seen the mistakes before you make them. Tick the questions you want to ask; they are attached to your question or consultation request below.

Ten Questions to Ask Your Expert

Post a question

Only the author and his experts see it. Tick "OK to share anonymously" if a good answer may go on a public FAQ, without your name.

Never paste passwords, tokens or keys here.

Book a consultation

Pick the questions above, tell us about your project, and choose a call or a written reply. We confirm by email. Any fee is shown to you in that email before anything is booked; nothing is charged on this page.

Never paste passwords, tokens or keys here.

How would you like the answer?

Never paste passwords, tokens or keys here.

Feedback on the book

Tell the author what worked and what did not, chapter by chapter. Feedback goes to him directly.

Your rating1 is poor, 5 is excellent

Never paste passwords, tokens or keys here.