Legal AI Editorial Methodology

Legalai.guide is maintained as an educational workflow guide for lawyers and legal teams. The editorial standard is practical: a page should help a legal professional decide what to do next, what to verify, and where the risk boundary is.

Source Standard

We prefer:

• Official product documentation for Codex, OpenAI, Claude, Claude Code, MCP, and GitHub behavior.
• Allowlisted GitHub repositories for implementation details where official docs point to code.
• Legal-tech vendor pages only for claims about that vendor's own product.
• Primary legal sources when a workflow discusses legal authority.

We avoid:

• Unsourced product claims.
• Pricing claims without a current official source.
• Claims that a model can guarantee legal accuracy.
• Jurisdiction-specific legal advice unless the page is intentionally scoped and reviewed.

Freshness Standard

Pages that discuss fast-changing tools should include:

• last_validated in frontmatter.
• docs_checked URLs for product-sensitive claims.
• A visible route to /updates when the topic is likely to change.
• Conservative wording when a feature, plan, model, or integration may change.

Legal Safety Standard

Every workflow should make clear:

• What the AI system is allowed to do.
• What the human reviewer must verify.
• What should be escalated.
• What source material was used.
• Whether the output is a draft, triage aid, checklist, code change, or final deliverable.

Editorial Test

Before publishing a page, ask:

1. Does this start from a lawyer's real workflow?
2. Does it distinguish facts, tool behavior, and legal judgment?
3. Does it include a review gate?
4. Does it avoid invented authority?
5. Does it route the reader to the next useful step?

If a page fails any of these, it needs revision before it can be treated as a cornerstone page.

Current Maintenance Loop

The public /updates page records source-backed changes that affect legal AI workflows. Daily and backfill automation should update tutorials only when the source is strong enough and the legal workflow impact is concrete.

Next Steps

• Check product and workflow updates
• Use the legal workflow template library
• Review citation and verification checks