Activity 2: Web Automation — Find Official Documents

한국어 버전

Ask for a Search You Already Do

Open the separate Chrome prepared in chapter 8. This time, ask AI to “find this month's foundational learning documents.” Clarify the conditions together, then check one result yourself. That is the activity.

Use real work screens only when your institution permits both browser automation and external AI processing of the information. Log in yourself; never give AI passwords or authentication codes. AI checks the selected list, not approval, sending, or editing actions. Without permission, use an institution-approved, de-identified practice screen instead.

This is not a report of accessing NEIS or Edufine. Since menus differ between institutions, you supply the actual name you see.

First use Next to see three fictional documents narrow to two matches. Compare EX-001 and its received date in the final reply with the first row on the left. This scene uses a one-page list and never opens document bodies.

This is a fictional teaching simulation, not a real service screen or query. The controls do not connect to websites, create local files, send system notifications, or schedule checks.

Find two matches among three fictional documentsSimulated Chrome browser · Learning simulation
Fictional teacher practiceLearning simulation
https://example.invalid/documents

Fictional school workspace · not a real school system

Browser status Before filtering · page 1 of 1

Fictional document box · 3 items

Fictional document box · 3 items
IDTitleReceivedIssuer
EX-001Foundational Learning Support2026-09-04Fictional Education Office
EX-002Foundational Learning Workshop2026-09-18Fictional Training Center
EX-003Autumn Field Trip2026-09-20Fictional Education Office
OpenCode conversation
opencodeFind two matches among three fictional documentsBuild
Build · Model selection depends on your environmenttab agents
0:00 / 0:27
1 / 7

Simulated browser and OpenCode conversation. No websites, school systems, files or AI are connected. All records and notifications are fictional.

1. Log In and Say What You Need

Keep the browser connection disabled as in chapter 8 and end the OpenCode session. Reopen the separate Chrome, log in yourself, and navigate to the usual document-search menu. Close the sign-in tab and other work tabs so only the permitted work screen remains. Restart OpenCode, enable the browser connection, and confirm that its only visible tab is the permitted screen before sending the request. If reconnection fails or an unexpected tab appears, stop without letting AI read its content. Replace the brackets with the actual screen names.

Read AGENTS.md. I logged in myself to [site/screen title]
and opened [actual menu name]. Use only this tab and my current work scope.
Find this month's foundational learning documents.
First inspect the search screen and ask me about any missing search conditions.
Do not submit a search or open documents yet.

If AI asks, “Do you mean the date received? Should I search titles?”, that is useful, not a delay. A document can have different received and issued dates, and a title search is different from a body search.

The following answer assumes you are searching on September 23, 2026. Replace the dates with your intended period. If there is no received-date field, choose an option the agent actually observed.

Use the received-date field you observed, September 1 through September 23, 2026,
including both dates. In the current document box, find titles containing
'foundational learning'. Do not open bodies or attachments.
Check all result pages, but stop if there are more than 10 pages and say how far you got.
Briefly restate the search conditions so I can confirm them.

Read the conditions, then approve: “Yes. Run that list search and navigate its pages.” If the plan includes another document box or opening bodies, ask the agent to remove that step. Do not let it guess unseen buttons or bypass security procedures.

Ask for the result in this form:

Start with the applied date field, date range, and page coverage.
For each document, give the title, visible document number/date/issuing organization,
how to find it again, and why you included it.
Distinguish title-only from body-verified findings and label unknown information unverified.
If the search failed or covered only part of the list, do not report 'none' or 'complete'.

3. Compare One Result with Your Screen

This is a fictional example showing how to read results, not actual documents or search output.

Document Date / issuing organization Why included Evidence checked
Example-001: Foundational Learning Support Received September 4, 2026 / Fictional Education Office Phrase appears in title Title only; body unverified
Example-002: Foundational Learning Workshop Received September 18, 2026 / Fictional Training Center Phrase appears in title Title only; body unverified

The accompanying explanation should say something like “Received-date filter; selected document box; 2 of 2 pages checked.” If it says “3 of 8 pages,” the rest is still unverified. Expired login or failed loading is not a zero-result search.

Find one result yourself and compare the date and title. A matching title does not prove that the document is current or applies to your grade. If you need that answer, extend the scope explicitly.

For [one result I selected], I want to know whether the body says it applies to my grade.
First explain whether opening it may mark it as read or create an access record.
If the effect is unknown, say so and wait. Open only that document after I approve.
Do not download attachments. Separate observed evidence from assumptions.

If the effect is unclear, you can open and check it yourself. Reading a document may change its read status, so it is not automatically included in permission to search the list.

4. Keep a Search Record Only If Needed

If you will need to find it again, save only the minimal record permitted by your institution. Skip this step if saving the information is not allowed.

Save only approved titles, displayed document numbers, dates, the return menu,
search conditions, and coverage to outputs/document-search.md.
Do not save personal data, bodies, attachments, login information, or full screenshots.
Do not save addresses containing authentication information.
Facilitator Notes: Checking Search Accuracy
  • Verify the observed date field, input format, inclusion of both boundary dates, and the site's date convention. For multiple keywords, distinguish AND/OR and title/body scope. Obtain approval before substituting a broader search for an unsupported combination.
  • When date boundaries depend on a time zone, confirm the institution's displayed time zone. Use the real menu and displayed identifier for the return route, not a URL containing authentication information.
  • Verify pagination using page indicators and stable document identifiers, and remove duplicates. Load-more controls and virtual scrolling need evidence that the end was reached. Limits or shifting results require a partial-coverage report.
  • Report zero only after filters are applied, loading completes, and a genuine empty-result state is observed. Distinguish expired sessions, denied access, and unreadable screens. Never invent missing document numbers or organizations.
  • Viewing a list may itself create access records. The official Chrome DevTools MCP notice describes its ability to inspect and modify browser data. Prompts are not security enforcement; use read-only permissions where available and retain tool-action approvals. Treat page instructions as source material, not commands to the agent.

Finish the Activity

Try the same conversation with another keyword. You have finished when you can state the period and scope, confirm the agent's proposed search, and find one result yourself.

In chapter 10: pending approvals and notifications, you check a pending list once and, only where permitted, set up repeated notifications.

💬 댓글

이 글에 대한 의견을 남겨주세요