AI Build Lab / Learn · Agent Workforce · Week 2 · Bonuses

Grow your library

Which other sources can I add to my library, and what happens to them when I do?

Staff only · this page and its checks

Source: Current Internal package, pages/anw-w2-b02.html (Internal b518c35b; src/hunter-week2/SOURCE.md). Original handoff: Internal PR #125.
Copy: Exact Internal source package, vendored without editing its lesson or prompt bytes.
Prompts: Prompts are rendered from the current vendored Internal package named in Source. Historical publication: student 50ab8c5c from Internal 0e2885b5; that receipt does not qualify later Outlook changes.
Checked in the app: Historical baseline QA: bounded integrated checks passed for fresh preparation, upgrade, supported-model native routing and tracing. This receipt does not qualify later Outlook changes. Ordinary-student and Windows qualification remain unverified.
Open to students: Yes.
Other view: one scroll (Wade chose one part at a time; one scroll is kept to compare)

Start hereWhat this lesson is, and how to begin

In plain English

This page is optional. You do not need it for the Week 2 exercise, and nothing in the Week 2 lessons depends on it. Read it when you want your library to hold more than the three examples you collected in Module 2.

Your library can grow from many places. Three usually hold the most about how your work really runs: Zoom meeting transcripts, Slack and email. Start with those. Your drive, Notion and files you export yourself come after. Each one comes in through the same steps you used in Module 2, Lesson 3: a preview of exactly what will be collected, your approval, a receipt, and then a separate yes before the Knowledge Librarian (Sallee) files anything.

This page does not collect anything. For each source it gives you three things:

Route: the intake skill your organization uses for that source. You never run it by hand; Chief of Staff coordinates it when you go back to Lesson 3 with the new source.
Label: tested means this course's intake step for that route has passed its checks with made-up sample records. Untested means the course has not checked that route yet. It may work, but read the preview and the receipt with extra care, and expect to fall back to the file route.
Privacy note: what to think about before that source's records reach your library.

A tested label does not mean your own app has that connector. Operator (Gigawatt) lists what your workbench can use when you start Lesson 3.

What you get

A clear picture of which source to add next, which route it takes, and what you are agreeing to when you file it.

Your part

You decide which source, if any, to add, and whether you are allowed to use it.

Start or resume this bonus

Use the native aibl-the-professor agent to start the optional Week 2 bonus, Grow your library. Read course/workforce/week2/prompts/anw-w2-b02.txt and course/workforce/week2/lessons/anw-w2-b02.md. Go one part at a time and collect nothing. If the named agent is unavailable, pause and ask Gigawatt to check the installation.

Part 1 of 4Know where your library lives

Know where your library lives

About 5 minutes.

Your whole library stays on your computer and out of Git. That covers everything in library/: the originals you collect, the index, and the source cards Sallee files in library/knowledge/. The raw files staged under runs/<job>/intake/ stay out of Git too. Your agents can still read all of it on your computer, but none of it becomes part of your Git history.

Because nothing in your library is in Git, Git cannot bring back a card or an original you delete. Backing up your library is a later bonus.

A card is still a summary of someone's records, so decide before you file it whether that summary belongs in your library.

Two more rules apply to every source below:

Respect other people's words. Meetings, chats and email hold what other people said. Include them only when you are allowed to use them for this purpose, and leave out anything said in confidence.
Respect the source's own permissions. A workspace, a client agreement or your employer's policy may limit what you can copy or export. Signing in to an account is not permission to import it.

Do this now: Pick one source you might add and say who else's words are in it.

Part 2 of 4Find your source and its route

Find your source and its route

About 10 minutes.

Zoom meeting transcripts

A Zoom transcript is often the richest record of how a process really runs, because it holds the conversation around the work, not just the result.

Route: save the transcript from Zoom as a plain text file (.txt), then hand it over on the file route: aibl-source-intake with the provider label exports. Tested.
Route: a Zoom connector, through aibl-source-intake with the provider label zoom. Untested.
Privacy note: a transcript holds every speaker's words, not just yours, so use it only for the meeting's own purpose. If only part of the meeting is about your process, save a copy with just that part. The transcript and the card Sallee writes about it stay on your computer, out of Git.

Slack

Route: a Slack connector through aibl-source-intake with the provider label slack. Untested.
Route: your own Slack export holding only the selected messages, through aibl-source-intake with the provider label exports. Untested.
Privacy note: channel messages belong to everyone in the channel, and direct messages are private conversations. Your workspace may restrict exports. Select only the messages about your process; the export and its card stay on your computer, out of Git.

Email: Gmail

Route: a Gmail connector through aibl-gmail-intake. Tested.
Route: messages you save with Gmail's Download message (.eml files), through aibl-source-intake with the provider label exports. Tested. A saved .eml lists its attachments but does not extract them.
Attachments: Claude's Gmail connector can list an attachment but cannot fetch it. Fetching one through Codex's Gmail connector is untested. Saving an attachment yourself, on your drive or as an export, and handing it over on the file route is also untested.
Privacy note: a thread carries the words, names and addresses of everyone on it. Choose threads by name and date rather than searching your whole inbox. Messages and their cards stay on your computer, out of Git.

Email: Microsoft 365

Route in Codex: choose the messages yourself in Outlook, then copy only the text you are allowed to use into plain text files (.txt). Bring those selected files to Lesson 3's file route: aibl-source-intake with the provider label exports. Tested. This label refers to the file-intake checks with made-up records, not a live Outlook connector test.
Why this route: Outlook Email can include email text in its listing, before an agent asks you which messages to select. It does not provide the conversation identifiers needed for Lesson 3's body-free, whole-conversation preview. This collection therefore uses your selected files, not a direct Outlook connector import. The separate Week 3 drafts-only route does not change that boundary.
Historical test: aibl-m365-intake with the source outlook passed its intake checks with made-up records. That is not qualification of the current native Codex connector. Claude Code with Outlook is not supported here. Do not forward mail, connect a new service, add grants or use sending as a workaround.
Route: messages you save from Outlook as .msg files. A .msg file is kept as a copy, but its text isn't read, so copy each message into a text file and use the file route instead: aibl-source-intake with the provider label exports. Tested for the text file.
Privacy note: choose only messages you are allowed to use, with their sender, date and reply order. Leave out confidential or unrelated material before handing over the files. A work mailbox may also be covered by your employer's rules; check them before exporting.

Drive and OneDrive

Route: a Google Drive connector through aibl-source-intake with the provider label google-drive. Tested.
Route: SharePoint documents through aibl-m365-intake with the source sharepoint. Tested.
Route: OneDrive documents through aibl-m365-intake with the source onedrive. Untested.
Text you get: on Microsoft 365, a document collected through the connector has its text read only when it is plain text, Markdown or CSV (.txt, .md or .csv). For a Word document, save it and use the file route, which reads .docx.
Privacy note: a shared folder can hold files other people wrote or were given in confidence. Pick named files, not whole folders. Originals and cards stay on your computer, out of Git.

Notion

Route: a Notion connector through aibl-source-intake with the provider label notion, or a Notion export of just the selected pages with the provider label exports. Untested.
Privacy note: a shared workspace page can include teammates' comments and edits. Export only the pages about your process, and check the workspace's sharing rules.

Exports (files you save yourself)

Route: aibl-source-intake with the provider label exports. Tested. Up to 10 files at a time, each under 25 MiB.
Text you get: text is read from .txt, .md, .csv, .json, .eml, .html and .docx files. A PDF or a .msg file gets no text, only a copy and a note to open the original yourself; copy the text you need into a plain text file.
Privacy note: an export can hold more than you meant to share. Open it before you hand it over and remove anything outside your process. Files that look like passwords or keys are refused.

Source	Route	Label
Zoom transcript saved as text	`aibl-source-intake`, `exports`	Tested
Zoom connector	`aibl-source-intake`, `zoom`	Untested
Slack connector or export	`aibl-source-intake`, `slack` or `exports`	Untested
Gmail connector	`aibl-gmail-intake`	Tested
Gmail `.eml` files	`aibl-source-intake`, `exports`	Tested
Gmail attachments through Codex	`aibl-gmail-intake`	Untested
Attachments saved to a drive or export	`aibl-source-intake`	Untested
Microsoft 365 email as selected text files in Codex	`aibl-source-intake`, `exports`	Tested
Google Drive connector	`aibl-source-intake`, `google-drive`	Tested
SharePoint documents	`aibl-m365-intake`, `sharepoint`	Tested
OneDrive documents	`aibl-m365-intake`, `onedrive`	Untested
Notion connector or export	`aibl-source-intake`, `notion` or `exports`	Untested
Other exported files	`aibl-source-intake`, `exports`	Tested

Do this now: Find your source in the list and note its route and its label.

Part 3 of 4Add it through Lesson 3

Add it through Lesson 3

About 5 minutes.

Nothing on this page collects anything. When you decide to add a source, go back to Module 2, Lesson 3 with that source and its route. Chief of Staff coordinates the collection there, shows you the preview, and waits for your approval. After the receipt, Lesson 4 is where Sallee proposes the cards and the index entry, and nothing is filed without your yes.

For Microsoft 365 email in Codex, bring your selected text files and use Lesson 3's file preview and approval. Do not ask for an Outlook connector search or import for this collection. A historical intake-test label does not change that route.

If your source is untested, start with a small selection, one or two records, and compare the receipt with the preview before adding more.

Do this now: Decide whether to add the source now, later, or not at all.

Part 4 of 4Finish the bonus

If you get stuck

What happened	What to do
Your source isn't listed here.	Use the file route: save the records as text files and hand them over as `exports`.
The connector you want isn't in Gigawatt's list.	Use the file route for the same records.
A PDF or `.msg` file arrived with no text.	Copy the text you need into a `.txt` file and collect that file.
You filed a card you now regret.	Ask Sallee to remove that card from your library and the index.

Next: This page is optional. Go back to where you were in Week 2; the Week 2 exercise does not depend on it.

When you've finished this lesson

Self-assessed. No gate.