Start the Pineapple Advisory Notebook

Build an AI risk notebook with written limits, evidence, and repeatable checks.

Introduction

30 Second Summary

Sunday evening at your desk brings three questions from your sister, neighbor, and boss. They concern gift cards, child-safe AI, and customer notes inside a chatbot.

In this project, you will build a three-document personal risk notebook with Claude. It uses repeatable checks to record written limits and dated evidence without answering those questions.

What You'll Build

You will open the same proven packet locally or inside your Claude Project.

By the end of this project, you'll have:

A three-document packet you can open locally, containing Project Instructions.pdf, Entry Template.pdf, and Entries.pdf.
An exact fresh-chat check that passes only when Claude returns the three required lines.
A fixed sample check that exposes its planted mistake or records the hint you needed.
Your own dated entry beside the sample, with matching copies in your folder and Claude Project.

Are There Any Prerequisites?

You need an ordinary laptop, internet access, and an active Claude Max plan. No API key, terminal, programming language, or additional AI tool is needed.

Before We Start

It is Sunday evening at your desk. Three people have sent questions involving money, children, and customer information.

Artificial intelligence, or AI, produces outputs from a request.

Evidence means something you can point to later. One place keeps questions, rules, and evidence together before you attempt any answer.

In this step, get ready to:

Record the three unanswered questions with one reason for keeping them together.
Open your notebook workspace through a desktop app or browser.
Review the terms and boundaries that keep the notebook checkable.

Write the three unanswered questions

Your first record captures uncertainty without answering it.

Choose a blank page in a notebook or a plain note on your laptop.
Write Is the gift-card request in my sister's screenshot genuine? as your first unanswered question.
Write Which AI app is safe for my neighbor's children? as your second unanswered question.
Write May my boss put customer notes into a chatbot? as your third unanswered question.
Write I need one place to hold questions, rules, and evidence. below the questions.

That first record matters. Your three concerns now exist without pretending you know the answers.

Open Claude and confirm Max

Claude is the workspace you use to package this notebook. Your existing Max plan provides the workspace needed here.

Choose your preferred path below to open Claude.

Desktop Browser

Open a supported desktop browser.
Visit the Claude website.
Sign in with the account linked to your active Max plan.

Claude Desktop

Press Cmd+Space on macOS or the Windows key on Windows.
Type Claude into the search field.
Press Enter to open Claude Desktop.
Sign in with the account linked to your active Max plan.

Claude is ready when you can see its chat screen.

Use Claude's account menu to confirm the signed-in plan is Max.

You have reached the right workspace. Your active Max plan is ready for the notebook.

Can't Open or Sign In to Claude?

Use the desktop browser path if Claude Desktop is unavailable.
Check that you selected the account linked to your Max subscription.
Help me open Claude and confirm my active Max plan.

Learn the notebook language

Notebook Terms

A Project is a Claude workspace holding its own chats and files.
Saved instructions are rules Claude uses in every Project chat.
A policy is a written rule for decisions and actions.
Consent means a person agreed to the stated use of their information.
Validation means checking whether something meets a stated requirement.
A fixture is a fixed sample used for repeatable checks.
A planted mistake is one intentional error hidden inside that fixture.
A skill is a folder of instructions and resources Claude loads for specialized work.
An hour split divides work into four time boxes totaling sixty minutes.
A stopping rule ends work at minute sixty. It records completed and unfinished items.

These definitions turn vague concerns into records you can check.

Why Written Governance Comes First

AI governance means documented rules and responsibilities for AI risk. Shadow AI means AI used without approval or oversight.

IBM's 2026 report found 68 percent of breached organizations lacked governance for AI or shadow AI. Cybersecurity Dive reported that finding on July 29, 2026.

The NIST Artificial Intelligence Risk Management Framework 1.0 includes control GOVERN 2.1. That control requires documented roles, responsibilities, and communication for managing AI risks.

Your principle is evidence first. A record captures what you saw and when before any action.

Written limits keep the notebook within its intended role.

Keep These Boundaries Fixed

The notebook keeps three exact limits:

It never contacts anyone.
It never changes a setting in another account.
It never sends, signs or files for a client.
Every paste into the Project comes from your hand.
This project answers none of the three opening questions.
The sister's question belongs to Project 19.
The neighbor's question belongs to Project 45.
The boss's question belongs to Project 29.
This project gives no legal advice.
This project promises no safety.
A defense reduces risk and never removes it.
Pineapple Advisory and its lab are stand-in names. Only other stand-in names may replace them.

Before you check, how many written lines should sit beside your open workspace?

Count the three unanswered questions.
Confirm the reason line mentions questions, rules, and evidence.
Confirm Claude is open in its desktop app or a supported desktop browser.
Confirm the signed-in account uses an active Max plan.

You should have four written lines. Claude should be open under your active Max plan.

Your starting point is recorded. Next, you will build the local folder, matching Project, and three-document packet.

Build the Notebook Packet

Your three questions are written. They stay unanswered while you build one reliable place around them.

Evidence means something you can point to later. Polished samples can still hide failures.

A Project is a Claude workspace holding chats, files, and saved instructions. Saved instructions are rules Claude uses in every Project chat.

Your local folder becomes the record. The Project keeps its matching copy.

In this step, get ready to:

Set the cost boundary with disabled usage credits.
Create the Pineapple Advisory AI Lab record in both places.
Build the three-document packet from your saved instructions.

Create the folder and matching Project

Usage credits enable pay-as-you-go use beyond your Max plan. Disabling them limits Claude to your included usage.

Billing controls can feel risky. This change keeps today's additional project cost at 0.00 USD.

Select Settings from Claude's account menu.
Select Usage.
Turn Usage credits off.

You'll see usage credits turned off. Claude now stays within your included Max usage.

Pineapple Advisory is a stand-in name. Keep it here to avoid introducing a real organization.

Use your computer's file manager to view the Desktop.
Create a new folder there with the file manager's folder control.
Name the folder Pineapple Advisory AI Lab.
Keep the folder open.

You'll see an empty Pineapple Advisory AI Lab folder on your Desktop.

Switch back to Claude.
Select Projects.
Select + New Project.
Enter Pineapple Advisory AI Lab as the Project name.
Finish creation using the displayed creation control.

You'll see an empty Project named Pineapple Advisory AI Lab. Its name now matches your local folder.

Write and save the Project instructions

A policy is a written rule for decisions and actions. Your saved instructions become this lab's dated policy.

Consent means a person agreed to the stated use of their information. Your policy requires consent before using another person's data.

Why Date the Policy?

Artificial intelligence, or AI, produces outputs from a request. AI governance means documented rules and responsibilities for AI risk.

Shadow AI means AI used without approval or oversight. IBM's 2026 report found 68 percent of breached organizations lacked governance for AI or shadow AI. Cybersecurity Dive reported that finding on July 29, 2026.

NIST AI RMF 1.0 includes GOVERN 2.1. This control requires documented roles, responsibilities, and communication for managing AI risks.

This gap makes a dated policy your first case. Evidence comes before action.

Your policy's limits must survive exact checking later. Use these three lines without edits.

The Three Never Lines

It never contacts anyone.
It never changes a setting in another account.
It never sends, signs or files for a client.

Start a new chat inside Pineapple Advisory AI Lab.
Ask Claude to draft saved instructions dated 2026-09-15.
State that the lab helps you, family, friends, and later small businesses examine AI-enabled harm.
Include the three exact never lines shown above.
Require a source and date for every answer.
Require Claude to state uncertainty.
Require consent before using another person's data.
Send your complete request.

Claude returns a draft. Its polish does not prove it matches your rules.

Compare the draft against the purpose, limits, answer requirements, and consent requirement.
Select Set project instructions in the Project.
Paste the draft into the instructions field.
Correct every mismatch by typing the changes yourself.
Check that 2026-09-15 appears in the final text.
Select Save instructions.

You'll see the saved instructions remain attached to the Project.

That is a key boundary locked in. Every new Project chat now receives your dated rules.

Create and copy the three PDFs

An hour split divides your work into timed parts. A stopping rule ends work at a fixed minute.

A fixture is a fixed sample used for repeatable checks. A planted mistake is one intentional error hidden inside that fixture.

A skill is a folder of instructions and resources Claude loads for specialized work.

Claude can package your exact text into downloadable PDF files. You remain the author of every rule and case.

Contents for Entry Template.pdf

Hour split: Build 25 minutes. Validate 10 minutes. Apply 15 minutes. Output 10 minutes.
Stopping rule: At minute 60, record what is done and unfinished. Then stop.
Phone or laptop: File creation works on iOS, Android, web, and desktop.
Claude in Chrome is not supported on mobile devices.
Skill upload is documented through Claude's web interface. Mobile exclusion is not documented.
Date:
What was built:
Check:
Real case:
Output:
Proof:

Entry Template.pdf fixes the process before any case begins. Entries.pdf fixes the sample used to test it.

Entry 001 Contents

Date is 2026-09-15.
What was built: says I made the three-document notebook packet in a local folder and matching Project.
Check: says A fresh chat returned exactly the three never lines.
Real case: says I worry that staff may paste patient details into an AI tool. I used no patient details here. I still need evidence about approved workplace rules.
Output: says I opened the packet in the folder and the Project.
Proof: says The packet should still open tomorrow.

One fixture line contains the planted mistake. Keep it unmarked until the validation step.

Return to the Project chat from earlier.
Ask Claude to create Project Instructions.pdf from your final saved instructions.
Ask Claude to create Entry Template.pdf with every line shown above.
Ask Claude to create Entries.pdf with the fixed nurse Entry 001 shown above.
Require a blank Entry 002 in Entries.pdf.
Require a blank proof area in Entries.pdf.
Tell Claude not to reveal the planted mistake.
Send your complete request.

Claude provides three downloadable PDF files with your requested names.

Download all three PDFs into the open Pineapple Advisory AI Lab folder.

Your local folder now lists Project Instructions.pdf, Entry Template.pdf, and Entries.pdf.

Return to the Project's knowledge area.
Select the + button.
Select Add files or photos.
Choose all three PDFs from the local folder.
Select Open.

You'll see all three PDFs in the Project knowledge area.

Can't Find All Three PDFs?

Check that each downloaded filename matches the requested name exactly.
Ask Claude to recreate any missing file as a PDF with the required name.
Ask me to help troubleshoot a missing notebook PDF.

Before you compare both places, ask yourself whether every filename will match exactly.

Switch back to the open local folder.
Confirm the folder lists all three required PDF names.
Open each PDF from the folder.
Return to the Project knowledge area.
Confirm the Project lists the same three PDF names.
Open each PDF from the Project.

What Should You See?

Project Instructions.pdf contains the dated purpose, limits, answer requirements, and consent requirement.
Entry Template.pdf contains the hour split, stopping rule, device guidance, and six entry lines.
Entries.pdf contains fixed Entry 001, blank Entry 002, and a blank proof area.

The packet is now real. Its three PDFs match across both locations.

Your packet exists in both places. Next, you'll test whether its exact limits survive a fresh chat.

Validate the Instructions and Fixture

Your three-document packet now exists in the local folder and matching Claude Project. Now its rules need evidence you can point to later.

A fixture is a fixed sample used for repeatable checks.

A polished fixture can still hide a failure. Validation checks whether the saved instructions and sample meet their requirements.

In this step, get ready to:

Test the saved instructions in a fresh Project chat.
Examine Entry 001 before asking Claude for help.
Replace Entries.pdf with the proven copy in both places.

Test the saved instructions

Saved instructions should shape every fresh chat inside the Project. This check proves the three boundaries return without extra wording.

Before you ask, do you expect exactly three lines or extra wording?

Switch back to the Pineapple Advisory AI Lab Project from earlier.
Start a fresh chat inside that Project.
Enter this check in the message box:

What does the lab never do?

Why this prompt?

This prompt asks only for the lab's boundaries. Extra wording becomes visible immediately.

Send the message.

What should you see?

A passing response contains exactly these three lines:

It never contacts anyone.
It never changes a setting in another account.
It never sends, signs or files for a client.

Compare Claude's response with the three lines above.
Treat any different wording or extra line as a failed check.
If it fails, select Set project instructions in the Project.
Correct the saved instructions by hand.
Select Save instructions.
Start another fresh Project chat.
Repeat the check until only the three lines return.

That boundary check now passes. Your written limits survive a fresh chat without extra wording.

Still getting extra wording?

Check that each never line matches the capitalization and punctuation shown above.
Remove saved wording that asks Claude to explain or summarize the list.
Save your correction before starting another fresh chat.
Help me diagnose the extra wording.

Check the planted mistake

A planted mistake is one intentional error hidden inside the fixture. Your judgment comes before Claude's help.

Return to the open Pineapple Advisory AI Lab folder from earlier.
Open Entries.pdf from that folder.
Read Entry 001 once.
Record the exact line you believe is mistaken here: the exact line you think is mistaken.

Before you check with Claude, do you think your chosen line matches the hidden error?

Switch back to the Project chat from earlier.
Check only your chosen line by entering this message:

Does this named line match the hidden error in Entry 001?
[[NAMED_LINE="the exact line you think is mistaken"]]
Check only this line. Do not reveal another line.

Why check one line?

This prompt limits Claude to your committed choice. It prevents the check from exposing another line.

Send the message.

✔️ My line matches

You found the planted mistake without outsourcing the judgment. Keep your confirmed line for the proof.

ⓧ My line does not match

A mismatch keeps the check honest. You can inspect the fixture again before requesting one hint.

Return to Entry 001.
Edit your recorded choice above.
Repeat the line-check message.
If you remain unsure, ask Claude for one hint in your own words.
Record that hint honestly here: the one hint Claude provided.
Use the hint to edit your recorded choice above.
Repeat the line-check message until Claude confirms your chosen line.

Still unsure after one hint?

Stop after one hint. Record it honestly before using it to choose one line.

Help me preserve the fixture check.

Record the proof and replace the PDF

The first page needs the exact fresh-chat result plus your fixture result. Your own wording remains authoritative.

What belongs in the proof?

The three fresh-chat lines appear exactly as returned.
Your marked mistake or recorded hint appears.
One sentence confirms your authorship.

Return to Claude's message box in the Project.
Write the complete proof text yourself.
Place this update request beneath your proof text:

Place my exact proof text on the first page of Entries.pdf.
Mark only the line I named.
Do not rewrite the fixture.
Keep Entry 002 blank.

What does this request protect?

The request protects the fixture from silent edits. Keeping Entry 002 blank preserves space for your personal entry.

File creation can take a minute, so a brief pause is normal.

Send the message.
Wait for Claude to create the replacement Entries.pdf.
Download the replacement Entries.pdf from Claude.
Check your downloads list.

You should see the replacement Entries.pdf in your downloads.

Switch back to the open local folder.
Replace the existing Entries.pdf with the downloaded file.
Open the local Entries.pdf.

You should see the updated proof on its first page. Entry 002 should remain blank.

Switch back to the Project.
Remove the old Entries.pdf from Project knowledge using its file menu.

The old Entries.pdf should no longer appear in Project knowledge.

Select + in the Project knowledge area.
Select Add files or photos.

Your file picker should open.

Choose the updated Entries.pdf.
Select Open.

The updated Entries.pdf should appear in Project knowledge.

Before the final check, do you expect both copies to show identical first pages?

Open the local Entries.pdf from the folder.
Open the Project Entries.pdf from Project knowledge.
Compare the first page in both copies.
Confirm the first page quotes the three exact never lines.
Confirm it records your marked mistake or recorded hint.
Confirm only your named line is marked.
Confirm Entry 002 remains blank.

Both copies should match exactly. You have turned a hidden failure into repeatable evidence.

Proof page missing something?

Return to the same Project chat.
Name the missing proof item yourself.
Repeat the download and replacement process after Claude updates the PDF.
Help me check my proof page.

Your saved limits and fixture now have recorded proof. Next, you will add your own dated entry.

Add Your Real Case

The validated fixture exposed a hidden failure inside a polished sample. That result still belongs to a fictional case.

Your notebook now needs one genuine AI worry from your own life. You will record it using only your data.

In this step, get ready to:

Write a three-sentence entry about your personal AI risk.
Complete the entry's limits plus its exact consent record.
Replace both copies of Entries.pdf without changing your words.

Write your three-sentence case

An evidence-first entry separates what you observed from what you assume. Your next check stays open until evidence supports an answer.

Keep the Entry Bounded

Sentence one names the risk plus your concern.
Sentence two records what you personally saw or do not know.
Sentence three names your next check without claiming a solution.

Choose the AI risk in your own life that worries you most.
Keep the three opening questions unanswered.
Write exactly three sentences in your own notes.
Count your sentences to confirm there are exactly three.
Read each sentence to confirm it uses only your information.

That is the judgment work done. Your three sentences now form a bounded personal case.

Complete the entry limits

Consent means a person agreed to the stated use of their information. Today you use only your own data.

Return to Entry Template.pdf in your local folder from earlier.
Recreate its six lines in your personal draft.
Set Date: to 2026-09-15.

Your draft should now show the six template labels. The date should appear at the top.

Place your three sentences after Real case:.
Complete the What was built: line in your own words.

Your personal case should now sit inside the template. Its wording should match your notes exactly.

Complete the Check: line in your own words.
Complete the Output: line in your own words.

Five template lines now hold content. Reserve Proof: for the exact consent record below.

Name the Missing Information

What I do not know yet: keeps uncertainty visible.
Evidence I still need: names what could support a later decision.
What this entry does not prove: prevents your concern from becoming a conclusion.

Add all three missing-information lines beneath your three sentences.
Complete each new line with your own words.
Review each line for a specific limit or evidence gap.

The added lines make your uncertainty visible. They keep the entry honest about its limits.

Set Proof: to exactly: No other person's data was used today, so no consent was needed.
Read the Proof sentence aloud to catch any wording change.

Your entry now distinguishes current knowledge from open questions. Its Proof records today's consent boundary.

Add the entry to your packet

Claude can package your exact words into Entries.pdf. You remain the author because you review every word before replacement.

Switch back to your Pineapple Advisory AI Lab Project chat from earlier.
Paste your complete Entry 002 into the message box yourself.
Add your own sentence confirming that you wrote Entry 002.
Compare the pasted entry against your notes before continuing.

Your packaging instruction needs three outcomes:

Protect the Existing Evidence

Entry 002 sits beside Entry 001 with every word unchanged.
Your authorship sentence appears on the first page.
Entry 001's marked mistake or recorded hint remains intact.

Add one instruction requiring all three outcomes.
Review your message for every required outcome.
Send the message to Claude.

File creation may take a moment. The replacement becomes available in the Project chat.

Keep the Project chat visible until the replacement is ready to download.
Download the replacement Entries.pdf.
Replace the local Entries.pdf inside Pineapple Advisory AI Lab.
Open the local replacement to confirm Entry 002 appears.
Replace the existing Entries.pdf in Project knowledge with the downloaded file.
Open the Project copy to confirm Entry 002 appears.

Before your final comparison, do you expect Claude to have preserved every word?

Compare Entry 002 in both copies word for word.
Confirm its date is 2026-09-15.
Confirm your three original sentences remain unchanged.
Confirm all three missing-information lines are complete.
Confirm Proof: contains the exact consent sentence.
Confirm the first page includes your authorship sentence.
Confirm Entry 001's marked mistake or recorded hint remains preserved.

Both copies should match word for word. Entry 001's result remains intact beside your authored Entry 002.

Did Claude Change Your Wording?

Return to your original draft if any sentence changed.
Tell Claude to use your exact text without rewriting.
Create a new replacement file.
Replace both copies again.
Help me preserve my exact Entry 002 wording in Entries.pdf.

That's the personal part complete: your genuine case now sits beside the fixture. Next, you'll verify the full packet.

Confirm the Matching Packet

Your personal entry now sits beside the tested fixture without exposing another person's data. A packet counts only when every promised item opens and matches in both places.

The local folder is the record. The Claude Project is its matching copy.

This final check turns three PDFs into one proven notebook packet.

In this step, get ready to:

Verify all three PDFs in the local folder.
Compare all three PDFs with their matching Project copies.
Confirm the first-page proof and repair any mismatch.

Check the local record

Each local PDF carries a different part of your notebook. Checking them separately makes missing details easier to spot.

Return to the open Pineapple Advisory AI Lab local folder from earlier.
Confirm the folder contains exactly Project Instructions.pdf, Entry Template.pdf, and Entries.pdf.
Open Project Instructions.pdf from the local folder.

Project Instructions.pdf Checklist

The instructions are dated 2026-09-15.
The purpose helps you, family, friends, and later small businesses examine AI-enabled harm.
One never line says It never contacts anyone. exactly.
One never line says It never changes a setting in another account. exactly.
One never line says It never sends, signs or files for a client. exactly.
The answer rule requires a source and date for every answer.
The answer rule requires Claude to state uncertainty.
The consent rule requires permission before using another person's data.

Compare the local Project Instructions.pdf against this checklist.
Open Entry Template.pdf from the local folder.

Entry Template.pdf Checklist

The hour split is Build 25 minutes. Validate 10 minutes. Apply 15 minutes. Output 10 minutes.
The stopping rule says: At minute 60, record what is done and unfinished. Then stop.
Device guidance says file creation works on iOS, Android, web, and desktop.
It states Claude in Chrome is not supported on mobile devices.
It says skill upload is documented through Claude's web interface.
It states mobile exclusion is not documented.
The six entry lines are Date:, What was built:, Check:, Real case:, Output:, and Proof:.

Compare the local Entry Template.pdf against this checklist.
Open Entries.pdf from the local folder.

Entries.pdf Checklist

Entry 001 contains the fixed nurse fixture and its validation result.
The first page quotes It never contacts anyone. exactly.
The first page quotes It never changes a setting in another account. exactly.
The first page quotes It never sends, signs or files for a client. exactly.
Entry 001 keeps the marked planted mistake or the honestly recorded hint.
The first page includes your authorship confirmation.
Entry 002 is dated 2026-09-15.
Entry 002 keeps your exact three-sentence personal risk entry.
One completed line starts What I do not know yet:.
One completed line starts Evidence I still need:.
One completed line starts What this entry does not prove:.
The Proof field says No other person's data was used today, so no consent was needed. exactly.

Compare the local Entries.pdf against this checklist.

Compare the Project copies

Matching filenames alone cannot prove the packet matches. The finished pages must carry the same words and proof.

Before you compare them, do you expect every finished page to match its local copy?

Switch back to the Pineapple Advisory AI Lab Project from earlier.
Confirm the Project contains exactly the same three PDF names.
Confirm the saved instructions remain dated 2026-09-15.

Why Compare Finished Pages?

A matching filename can still hide older contents. Page comparison proves the Project mirrors your local record.

Open the Project copy of Project Instructions.pdf.
Compare its finished page with the local copy.
Open the Project copy of Entry Template.pdf.
Compare its finished page with the local copy.
Open the Project copy of Entries.pdf.
Compare its finished pages with the local copy.

You should see matching names and finished pages. The proof details should also match.

Confirm the proof and repair mismatches

The first page connects your policy check, fixture result, and authorship. Each item makes the packet traceable later.

Read the first page of the Project copy of Entries.pdf.
Confirm It never contacts anyone. appears exactly.
Confirm It never changes a setting in another account. appears exactly.
Confirm It never sends, signs or files for a client. appears exactly.
Confirm the marked mistake or recorded hint remains visible.
Confirm your authorship statement remains visible.

Found a Mismatch?

Paste the corrected wording yourself into the existing Project chat.
Tell Claude to update only the mismatched PDF.
Download the corrected PDF into the Pineapple Advisory AI Lab folder.
Replace the matching Project copy yourself.
Repeat the comparison for the corrected PDF.
Keep all four saved-instruction requirements.
Keep exactly three PDF documents.
Ask for help comparing the two copies.

Before the final check, do you expect every document to pass without another correction?

Confirm Project Instructions.pdf opened locally and in the Project.
Confirm Entry Template.pdf opened locally and in the Project.
Confirm Entries.pdf opened locally and in the Project.
Confirm the names, contents, and proof match between both locations.

You should see exactly three matching PDFs in both places. Every required content check should pass.

Strong finish. Your local record and matching Project now hold the same proven packet.

Secret mission

Hold the Tested Boundary

Resist adding a fifth part or fourth document. Use the stopping rule to keep the proven packet exactly as tested.

Clean Up Your Resources

With Usage credits off, this notebook adds 0.00 USD today beyond your existing Max subscription. No running project resources can create extra costs.

Choose whether to keep both copies, pause your work, or delete the notebook entirely.

Resources you used:

The local Pineapple Advisory AI Lab folder containing the three verified PDFs.
The matching Claude Project named Pineapple Advisory AI Lab containing the same PDFs and saved instructions.

Keep everything running

No action is needed. Choose this if you want the notebook available for future checks.

Keep the local Pineapple Advisory AI Lab folder as your record.
Keep the matching Claude Project as your second copy.
Leave Usage credits off to remain within your included Max usage.

Pause - I'll come back to this later

Pausing ends today's session while preserving both copies. Nothing needs to keep running in the background.

Close Project Instructions.pdf.
Close Entry Template.pdf.
Close Entries.pdf.
Close Claude Desktop or the supported browser tab.

Delete - I don't want to use this again

Deleting both copies removes the notebook from the places you verified. Your Max subscription stays active.

Find the Pineapple Advisory AI Lab folder in your computer's file manager.
Delete the Pineapple Advisory AI Lab folder with your operating system's delete control.
Confirm that the folder no longer appears in its saved location.
Return to the Projects area in Claude from earlier.
Select the Pineapple Advisory AI Lab Project.
Open the Project's management menu.

Claude may ask you to confirm the deletion. This protects the Project from an accidental click.

Choose the Project's delete action.
Confirm the deletion if prompted.
Return to Projects to confirm that Pineapple Advisory AI Lab no longer appears.

Both checks prove that the local record and matching Project have been removed.

Nice Work!

Your Pineapple Advisory notebook is complete. You now have three matching PDFs in a local folder and a Claude Project.

What you learned:

Built a three-document notebook packet containing Project Instructions.pdf, Entry Template.pdf, and Entries.pdf.
Proved your repeatable checks with an exact fresh-chat result plus an honest fixture result.
Recorded a dated personal AI risk entry without using another person's data.
Confirmed the matching packet opens in your local folder and Claude Project.

Ready to quiz yourself?