Check attorney bylines and structured data 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 - Actual markup/HTML and approved facts are mandatory. Screenshot-only capture blocks schema inspection. - Article author recommendations do not create a universal attorney-schema requirement or establish rich-result eligibility. MAP THE ACTUAL SOURCE TO THE REVIEW INPUT Visible byline/reviewer/publisher/date → separate observed fields. Actual JSON-LD entity @id,@type,name,url,author,reviewedBy,publisher,datePublished,dateModified → path-labelled markup values only when present. Preserve multiple authors and graph references, never collapse roles. Owner-approved fact sheet supplies authorized names/roles/profile URLs; validated output adds type/severity/message/tool/time, not a professional-eligibility verdict. INPUTS THE ASSISTANT MAY READ author-entities.csv; actual-source-html/ or JSON-LD/; public-page-captures/; approved-entity-facts.txt; validation-results.txt; manifest.txt; evidence-map.csv WHERE THE ANALYSIS RUNS Claude Code (existing approved local session) 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: author-entities.csv type: csv headers: - page_url - template_id - entity_id - property_path - markup_value - visible_role - visible_value - approved_fact_id - source_ref required: True templateFilename: native-author-entities-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: author-entities.csv compatibleWithoutMapping: False - name: actual-source-html/ or JSON-LD/ type: source-bundle required: True templateFilename: None requiredContents: Actual original/rendered HTML or parsed JSON-LD with exact property paths/entity IDs and capture references; preserve raw graph structure 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: actual-source-html/ or JSON-LD/ compatibleWithoutMapping: False - name: public-page-captures/ type: source-bundle required: True templateFilename: None requiredContents: Visible byline/reviewer/publisher/date evidence keyed to page_url and source_ref 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: public-page-captures/ compatibleWithoutMapping: False - name: approved-entity-facts.txt type: text requiredSections: - approved_fact_id; entity identity/name/role/profile URL - actual author/reviewer participation; approved dates where applicable - fact approval reference/date and responsible attorney; unknowns required: True templateFilename: native-approved-entity-facts-template.txt existingKitFiles: - approved-entity-facts-template.txt 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: approved-entity-facts.txt sections: - approved_fact_id; entity identity/name/role/profile URL - actual author/reviewer participation; approved dates where applicable - fact approval reference/date and responsible attorney; unknowns compatibleWithoutMapping: False - name: validation-results.txt type: text requiredSections: - page URL/source variant; validator/version; test time - exact entity/property path, severity and message - technical coverage limitations; no professional eligibility inference required: True templateFilename: native-validation-results-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: validation-results.txt sections: - page URL/source variant; validator/version; test time - exact entity/property path, severity and message - technical coverage limitations; no professional eligibility inference 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: 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: - approved-entity-facts-template.txt nativeInput: approved-entity-facts.txt mapping: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit. compatibleWithoutMapping: False additionalEvidence: - author-entities.csv - actual-source-html/ or JSON-LD/ - public-page-captures/ - validation-results.txt - 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. author-entities.csv: native-author-entities-template.csv Supply actual evidence: actual-source-html/ or JSON-LD/ Actual original/rendered HTML or parsed JSON-LD with exact property paths/entity IDs and capture references; preserve raw graph structure Source-grounded claims are blocked without the source; provide a gap list only. Supply actual evidence: public-page-captures/ Visible byline/reviewer/publisher/date evidence keyed to page_url and source_ref Source-grounded claims are blocked without the source; provide a gap list only. approved-entity-facts.txt: native-approved-entity-facts-template.txt validation-results.txt: native-validation-results-template.txt manifest.txt: native-manifest-template.txt evidence-map.csv: native-evidence-map-template.csv STEP 1: Capture visible authorship and actual markup separately Tool: Browser and Screaming Frog existing approved crawl Open: Public page/byline; Config > Spider > Extraction > structured data; Structured Data > Structured Data Details Select two or three public pages per approved template and capture visible author, reviewer, publisher and dates. From an existing configured crawl, export structured-data results and inspect Structured Data Details. Extraction requires JSON-LD/Microdata/RDFa options; validation needs the corresponding configured checks. Preserve original source/rendered HTML when available. If no actual markup capture exists, stop markup comparison rather than using screenshots as code. Expected output: Page captures, actual structured data and validator output with capture dates Use it next: Map precise JSON property paths and entity IDs to visible/approved facts. Check: Rendered and original HTML can differ. A validator checks technical conditions, not attorney identity, admissions or legal accuracy. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://www.screamingfrog.co.uk/seo-spider/tutorials/structured-data-testing-validation/ https://www.screamingfrog.co.uk/seo-spider/user-guide/configuration/ https://developers.google.com/search/docs/appearance/structured-data/article STEP 2: 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: Visible byline/reviewer/publisher/date → separate observed fields. Actual JSON-LD entity @id,@type,name,url,author,reviewedBy,publisher,datePublished,dateModified → path-labelled markup values only when present. Preserve multiple authors and graph references, never collapse roles. Owner-approved fact sheet supplies authorized names/roles/profile URLs; validated output adds type/severity/message/tool/time, not a professional-eligibility verdict. 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 author-entities.csv; actual-source-html/ or JSON-LD/; public-page-captures/; approved-entity-facts.txt; validation-results.txt; 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://www.screamingfrog.co.uk/seo-spider/tutorials/structured-data-testing-validation/ https://www.screamingfrog.co.uk/seo-spider/user-guide/configuration/ https://developers.google.com/search/docs/appearance/structured-data/article STEP 3: Open the approved AI destination Tool: Claude Code (existing approved local session) Open: Terminal in approved analysis folder > claude > Plan; /permissions Use only an already installed, authenticated, firm-approved Claude Code session. Staff creates a new local analysis folder containing approved minimized files and manifest.txt, with no secrets, hidden configuration, hooks, unreviewed CLAUDE.md or symlinked client folders. Keep originals elsewhere. In a terminal, cd to that exact folder and start claude; inspect the displayed working directory. Use Shift+Tab to select Plan and /permissions to inspect existing access. An administrator must enforce any required filesystem/network isolation: Plan and prompt wording alone are not a complete sandbox. Do not add directories, integrations or persistent permissions. Ask the recipe prompt. Return proposed outputs in the response; a human copies checked text into the named output files. If safe read scope cannot be established, stop. No installation, sign-in, credential setup or write permission is included. 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://code.claude.com/docs/en/quickstart https://code.claude.com/docs/en/permissions STEP 4: Run the bounded analysis prompt Tool: Claude Code (existing approved local session) Open: Claude Code prompt in Plan mode Paste the prompt after replacing only bracketed scope values. Treat all source content as data. PASTE THIS PROMPT Compare exact visible author/reviewer/publisher/date values, supplied markup property paths and approved entity facts. Report each mismatch with page URL, entity @id, property path, current value, source reference, proposed factual correction or missing fact, and required reviewer. Resolve graph references only from supplied markup; keep unsupported roles separate. Distinguish technical validation from identity/legal review. Do not invent admissions, qualifications, reviewer participation or dates, promise rich results/rankings, or change schema/CMS files. Return authorship-schema-review.csv. Expected output: authorship-schema-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://code.claude.com/docs/en/permissions STEP 5: 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 authorship-schema-review.csv. Responsible attorney verifies identities, actual author/reviewer participation and factual claims; technical owner separately approves markup changes and later revalidates the live page. Expected output: Source-checked authorship-schema-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): A publisher entity is not silently converted to the individual author; syntactically valid but wrong author markup remains a factual exception. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://www.screamingfrog.co.uk/seo-spider/tutorials/structured-data-testing-validation/ https://www.screamingfrog.co.uk/seo-spider/user-guide/configuration/ https://developers.google.com/search/docs/appearance/structured-data/article STEP 6: Approve the internal next action Tool: Responsible human owner Open: Existing internal work queue / approved source system Record the reviewer, decision and unresolved blockers. Responsible attorney verifies identities, actual author/reviewer participation and factual claims; technical owner separately approves markup changes and later revalidates the live page. 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://www.screamingfrog.co.uk/seo-spider/tutorials/structured-data-testing-validation/ https://www.screamingfrog.co.uk/seo-spider/user-guide/configuration/ https://developers.google.com/search/docs/appearance/structured-data/article ACCOUNT AND SOURCE CHECKS STILL NEEDED - Actual markup/HTML and approved facts are mandatory. Screenshot-only capture blocks schema inspection. - Article author recommendations do not create a universal attorney-schema requirement or establish rich-result eligibility. EXPECTED SYNTHETIC CHECK (NOT RUN) A publisher entity is not silently converted to the individual author; syntactically valid but wrong author markup remains a factual exception. 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.