Prompted LinesAI guidance for insurance

Practice · Method · ~5 min

Agents that build this site

How human direction, AI assistance, and automated checks work together on this site, and what those checks can establish.

What this example demonstrates

This website is a small example of AI-assisted research and publishing: an owner defines the work, agents produce changes, automated checks identify common defects, and editorial review addresses meaning and evidence. It illustrates the harness approach on a public content project.

These controls are proportionate to maintaining a website. An insurance workflow also needs access controls, data protection, validation against representative cases, and the approvals appropriate to its business consequences.

Roles and responsibilities

Aaron, the site's owner and editor, sets direction and remains accountable for publication. Specialist auditors are reusable review procedures that an agent invokes; they are not independent human reviewers.

The builder

Research and implementation

A coding agent turns the owner's instructions into researched drafts and reviewed changes. It runs the checks required for the affected pages and records the result before integration.

Specialist review supplements the builder's checks, while editorial responsibility stays with the owner.

Evidence Auditor

Claims and sources

Identifies factual claims and their citations. Source review compares the figure, date, and framing with the original publication, and records whether the claim is supported, needs correction, or cannot yet be verified.

A citation link is an evidence pointer. The automated check cannot establish that the linked source supports the sentence.

Prose Auditor

Clarity and concision

Flags repeated wording, long passages, and common writing patterns for review. Revisions are made in context so that technical meaning and qualifications survive the edit.

A clean scan still needs an editor to assess tone, relevance, and whether the reader can understand the explanation.

Structural Auditor

Navigation and organization

Checks page metadata, headings, navigation consistency, internal links, and section anchors. The content map records each page's purpose and the intended reading paths.

The review also asks whether each page has a clear job and whether readers have a useful next step.

Reference steward

Link maintenance

Checks external links, distinguishes dead pages from access failures, and records status changes. Archive and PDF preservation procedures support later source comparisons.

An accessible source can still be outdated. Link checking and factual verification are separate tasks.

Design Auditor

Presentation and accessibility

Checks shared styles, color contrast rules, image labels, overflow containment, and reduced-motion support. Visual review covers desktop and mobile layouts in light and dark themes.

Automated rules catch selected defects; keyboard, reading-flow, and visual checks remain necessary.

How a change reaches publication

Publication controls · schematic

Check the files and the meaning before release

Automated checks and editorial review answer different questions. A defect in either sends the change back for revision.

Owner brief → draft and source recordDefine the audience, file ownership, evidence, and acceptance checks. Parallel editors use separate branches and worktrees.

Automated checks

Do the files pass the configured rules?
  • Structure and internal links
  • Prose and presentation checks
  • Evidence pointers and regression tests

Output: recorded test results

Editorial checks

Does the page say the right thing?
  • Claim compared with its source
  • Scope, date, and caveats preserved
  • Meaning and audience reviewed

Output: accepted wording and evidence

Failed check or unresolved claim? Revise the draft, then rerun the affected checks.

Integrate the verified change → publishReview the commits before pushing. When production deployment is enabled, the configured workflow requires its audit job to pass.

The owner remains accountable for publication. A green test result does not establish that a factual claim is true.

The repository includes edit-time checks for Claude Code. Other editing tools must run the checks explicitly. The full suite provides a common checkpoint across those workflows.

What a passing audit means

A pass means the configured checks found no blocking defects in the files tested. It does not certify factual accuracy, regulatory compliance, completeness, or usability. Source comparison and reader testing require separate judgment, and the agents performing different reviews can still share the same blind spots.

The transferable practice is to define an observable result, keep a record of changes and checks, and assign responsibility for acceptance. In an insurance deployment, use the same discipline with the integration gates and governance requirements appropriate to the work.

For the claims behind this guide, continue to the evidence page. It collects source passages, corrections, and material awaiting further verification.