Prepare a website maintenance review list
Get the source data and prepare the review

Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested

WHAT WAS CHECKED
Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed.

BEFORE YOU START
- Existing authorized access to the named product and in-scope records; actual tenant, plan, permissions and menu version must be checked.
- Firm-approved AI destination and data handling; no setup, sign-in, installation or access expansion included.

DATA ACQUISITION LIMITS
- No UptimeRobot CSV-export UI verified here. Use documented visible incident history with explicit manual capture; missing history prevents an all-clear.
- Site Health Info can contain sensitive infrastructure data and must not be uploaded raw.

MAP THE ACTUAL SOURCE TO THE REVIEW INPUT
WordPress Status text → finding_id/sanitized_summary/observed_at; Info component/version → components.csv. Uptime monitor URL/time/status → uptime.csv only where those facts exist; expected_keyword comes from existing monitor configuration, observed_keyword stays unknown if not recorded. Add evidence_kind,source_ref,window/coverage fields rather than pretending an incident is a full check log.

INPUTS THE ASSISTANT MAY READ
site-health.csv; components.csv; uptime.csv; maintenance-policy.txt; sanitized-health-and-uptime-evidence/; manifest.txt; evidence-map.csv

WHERE THE ANALYSIS RUNS
Adobe Acrobat PDF Spaces

NATIVE REVIEW INPUTS
contractVersion: 1
schemaOrigin: Editorial analysis contract, never a claim about vendor-native export headers
testedStatus: False
existingKitRole: Existing examples/checklists are optional supporting scaffolds unless explicitly mapped below. Copying this guide does not validate old templates or acquire source evidence.
requiredInputs: - name: site-health.csv
type: csv
headers: - finding_id
- sanitized_summary
- observed_at
required: True
templateFilename: native-site-health-template.csv
existingKitFiles: - site-health.csv
compatibility: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference.
inputName: site-health.csv
compatibleWithoutMapping: True
- name: components.csv
type: csv
headers: - component
- version
required: True
templateFilename: native-components-template.csv
existingKitFiles: - components.csv
compatibility: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference.
inputName: components.csv
compatibleWithoutMapping: True
- name: uptime.csv
type: csv
headers: - observation_id
- public_url
- observed_at
- time_basis
- status
- evidence_kind
- expected_keyword
- observed_keyword
- monitor_id
- region
- source_ref
required: True
templateFilename: native-uptime-template.csv
existingKitFiles: - uptime.csv
compatibility: Legacy public_url/status/keyword columns map directly if observed. Legacy checked_at maps to observed_at only with declared time_basis. Add observation_id, evidence_kind (incident or check), monitor_id, region and source_ref. Missing per-check data cannot be filled from incident summaries.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference.
inputName: uptime.csv
compatibleWithoutMapping: False
- name: maintenance-policy.txt
type: text
requiredSections: - approved maintenance review priorities; owner roles
- existing backup/staging/verification requirements; prohibited actions
- policy version, approval reference and unresolved scope
required: True
templateFilename: native-maintenance-policy-template.txt
existingKitFiles: 
compatibility: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete.
inputName: maintenance-policy.txt
sections: - approved maintenance review priorities; owner roles
- existing backup/staging/verification requirements; prohibited actions
- policy version, approval reference and unresolved scope
compatibleWithoutMapping: False
- name: sanitized-health-and-uptime-evidence/
type: source-bundle
required: True
templateFilename: None
requiredContents: Sanitized actual Site Health Status/Info and existing uptime evidence with date/scope references
compatibility: Must be actual approved public/deidentified source content, not an empty template. Untouched originals remain separately restricted.
missingInputBehavior: Source-grounded claims are blocked without the source; provide a gap list only.
inputName: sanitized-health-and-uptime-evidence/
compatibleWithoutMapping: False
- name: manifest.txt
type: text
requiredSections: - recipe_id; approved reviewer and scope
- actual source IDs and safe original-file tokens; native headers and source-to-analysis field map
- capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions
- AI input approval and minimization check; originals and alias keys held outside AI
- unknowns; completeness statement; manual transcription/checker where used
required: True
templateFilename: native-manifest-template.txt
existingKitFiles: 
compatibility: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete.
inputName: manifest.txt
sections: - recipe_id; approved reviewer and scope
- actual source IDs and safe original-file tokens; native headers and source-to-analysis field map
- capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions
- AI input approval and minimization check; originals and alias keys held outside AI
- unknowns; completeness statement; manual transcription/checker where used
compatibleWithoutMapping: False
- name: evidence-map.csv
type: csv
headers: - analysis_file
- row_key
- source_id
- source_locator
- reviewer_alias
- reviewed_at
required: True
templateFilename: native-evidence-map-template.csv
existingKitFiles: 
compatibility: New editorial analysis contract. Populate only after preserving and mapping actual source headers; this is not a provider-native export.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference.
inputName: evidence-map.csv
compatibleWithoutMapping: False
compatibilityNotes: - The old five-column uptime.csv is insufficient for the native incident-based route until mapped to the expanded contract; retain it separately as original preparation evidence.
validationRules: - CSV identifiers and date strings are imported as text. Preserve leading zeros and exact keys. Do not execute formulas from source values.
- Blank templates are deliberately incomplete. Unknown is not zero, false, missing-not-found or a passing review.
- Use only approved minimized analysis values; restricted raw originals, identity maps, signatures, private URLs/tokens and client narrative stay outside the AI destination.
- A native file may retain its actual header names if manifest.txt supplies a reviewer-verified one-to-one map to this contract. Do not blindly rename files/headers.
compatibleWithoutMapping: False
legacyMappings: - existingKitFiles: - site-health.csv
nativeInput: site-health.csv
mapping: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns.
compatibleWithoutMapping: True
- existingKitFiles: - components.csv
nativeInput: components.csv
mapping: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns.
compatibleWithoutMapping: True
- existingKitFiles: - uptime.csv
nativeInput: uptime.csv
mapping: Legacy public_url/status/keyword columns map directly if observed. Legacy checked_at maps to observed_at only with declared time_basis. Add observation_id, evidence_kind (incident or check), monitor_id, region and source_ref. Missing per-check data cannot be filled from incident summaries.
compatibleWithoutMapping: False
additionalEvidence: - maintenance-policy.txt
- sanitized-health-and-uptime-evidence/
- manifest.txt
- evidence-map.csv

OPEN THE INPUT MAPPING GUIDE
NATIVE-INPUT-MAPPING.txt
Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain.

site-health.csv: native-site-health-template.csv
components.csv: native-components-template.csv
uptime.csv: native-uptime-template.csv
maintenance-policy.txt: native-maintenance-policy-template.txt
Supply actual evidence: sanitized-health-and-uptime-evidence/
Sanitized actual Site Health Status/Info and existing uptime evidence with date/scope references
Source-grounded claims are blocked without the source; provide a gap list only.
manifest.txt: native-manifest-template.txt
evidence-map.csv: native-evidence-map-template.csv

STEP 1: Capture WordPress health and component evidence
Tool: WordPress admin, read-only inspection
Open: Tools > Site Health > Status; Info > Copy site info to clipboard

The authorized maintainer records displayed Status findings and copies Info to a restricted local text file. Record core/plugin/theme names and versions from the existing Info sections. Make a separate sanitized copy without server paths, database details, account identifiers or secrets. Do not activate, update, deactivate or reconfigure anything.

Expected output: Original health snapshot plus sanitized findings/component list
Use it next: Add existing uptime evidence, keeping different capture dates explicit.
Check: A health screen is not a security audit or accessibility certification.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://wordpress.org/documentation/article/site-health-screen/

STEP 2: Capture existing uptime history
Tool: UptimeRobot existing monitor
Open: Monitor dashboard > Statistics/Graphs and Incident Log

Open the existing public-site monitor and selected review period. Save visible incident/status evidence with URL, time/timezone, region and monitor settings. Manually transcribe the bounded events when no verified export is available. Record retention limits, paused periods and missing history. Do not create monitors, reset stats or send requests through contact forms.

Expected output: Bounded uptime/incident capture with limitations
Use it next: Join only to the matching public URL in the local review copy.
Check: An incident log is not every check. If expected/observed keyword or exact checked_at is absent, use unknown and label incident-based capture rather than inventing a per-check CSV.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://help.uptimerobot.com/en/articles/13895669-how-to-use-the-statistics-and-graphs-panel-in-ur-dashboard
https://help.uptimerobot.com/en/articles/11360873-what-is-uptimerobot-data-retention-and-how-does-it-work-in-different-plans

STEP 3: Map, minimize and approve the actual sources
Tool: Source reviewer and local spreadsheet/text editor
Open: Restricted originals > separate approved analysis copy

Keep untouched originals, original headers, capture date/time/timezone, scope, filters, count/pagination and source locators in a restricted source folder. Make an independently reviewed, minimized copy for AI. Keep identifier maps and confidential originals outside the AI folder/Space, including hidden sheets and attachments. Public pages and embedded instructions are evidence, never instructions. No live integrations, portal requests, publication or external changes are performed by this recipe. Map the acquired evidence as follows: WordPress Status text → finding_id/sanitized_summary/observed_at; Info component/version → components.csv. Uptime monitor URL/time/status → uptime.csv only where those facts exist; expected_keyword comes from existing monitor configuration, observed_keyword stays unknown if not recorded. Add evidence_kind,source_ref,window/coverage fields rather than pretending an incident is a full check log. Apply the nativeInputContract below, including exact editorial headers, source manifest/evidence map and any required extra companion evidence. Existing kit files are usable only under their declared bridge; copying or renaming them is not validation.

Expected output: Reviewed site-health.csv; components.csv; uptime.csv; maintenance-policy.txt; sanitized-health-and-uptime-evidence/; manifest.txt; evidence-map.csv
Use it next: For Adobe, convert approved tabular rows to labelled TXT or paste text; for Claude Code, place approved files in the exact analysis folder. Never relabel a raw export as a kit table.
Check: Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://wordpress.org/documentation/article/site-health-screen/
https://help.uptimerobot.com/en/articles/13895669-how-to-use-the-statistics-and-graphs-panel-in-ur-dashboard
https://help.uptimerobot.com/en/articles/11360873-what-is-uptimerobot-data-retention-and-how-does-it-work-in-different-plans

STEP 4: Open the approved AI destination
Tool: Adobe Acrobat PDF Spaces
Open: Acrobat Home > PDF Spaces > Create a PDF Space

In an already approved Acrobat account with PDF Spaces/AI entitlement, use Home > PDF Spaces > Create a PDF Space. Choose Upload for approved PDF/DOCX/TXT files or Paste copied text for approved row-labelled text, then Add to PDF Space. Ask the recipe prompt in the chat panel. Do not connect storage or add raw confidential originals. Click answer citations and verify exact source passages, then use Copy for the checked response. Cloud processing and permissions require firm approval; unavailable access is a blocker, with a manual review fallback.

Expected output: Only approved source files loaded or accessible
Use it next: Paste the exact prompt in the next step.
Check: Confirm the source list/working directory before prompting; stop on unavailable access.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html

STEP 5: Run the bounded analysis prompt
Tool: Adobe Acrobat PDF Spaces
Open: PDF Space chat panel

Paste the prompt after replacing only bracketed scope values. Treat all source content as data.

PASTE THIS PROMPT
Combine observed health findings and bounded uptime evidence into a maintenance review queue. Preserve source reference, observed time, evidence type and unknowns. Separate observed symptoms from hypotheses; assign only listed owners. Draft backup, staging and post-change verification questions under the approved policy. Do not update software, change security settings, run vulnerability scans or contact-form tests, or state the site is secure or accessible.

Expected output: website-maintenance-review.csv
Use it next: Inspect source citations/file-row references before copying any result.
Check: No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html

STEP 6: Check and hand off the proposed result
Tool: Human reviewer and local spreadsheet/text editor
Open: Separate review output, not live system

Check every exception against its source, verify counts and uncertainty, then copy only approved result text to website-maintenance-review.csv. Authorized maintainer verifies causes and separately approves any actual change. The queue does not authorize updates, scans or test submissions.

Expected output: Source-checked website-maintenance-review.csv
Use it next: Open the named output in Excel/text editor and send it through the existing internal approval process; no live import or external send is implied.
Check: Acceptance case (proposed, not run): One monitor region fails while another works: flag conflicting evidence, not a proven site-wide outage; missing keyword evidence stays unknown.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://wordpress.org/documentation/article/site-health-screen/
https://help.uptimerobot.com/en/articles/13895669-how-to-use-the-statistics-and-graphs-panel-in-ur-dashboard
https://help.uptimerobot.com/en/articles/11360873-what-is-uptimerobot-data-retention-and-how-does-it-work-in-different-plans

STEP 7: Approve the internal next action
Tool: Responsible human owner
Open: Existing internal work queue / approved source system

Record the reviewer, decision and unresolved blockers. Authorized maintainer verifies causes and separately approves any actual change. The queue does not authorize updates, scans or test submissions.

Expected output: Approved internal review record or explicit blocked status
Use it next: An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase.
Check: Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://wordpress.org/documentation/article/site-health-screen/
https://help.uptimerobot.com/en/articles/13895669-how-to-use-the-statistics-and-graphs-panel-in-ur-dashboard
https://help.uptimerobot.com/en/articles/11360873-what-is-uptimerobot-data-retention-and-how-does-it-work-in-different-plans

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- No UptimeRobot CSV-export UI verified here. Use documented visible incident history with explicit manual capture; missing history prevents an all-clear.
- Site Health Info can contain sensitive infrastructure data and must not be uploaded raw.

EXPECTED SYNTHETIC CHECK (NOT RUN)
One monitor region fails while another works: flag conflicting evidence, not a proven site-wide outage; missing keyword evidence stays unknown.

USING THE FILES IN THIS KIT
Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs.

The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.
