Consulting Automation
AI Industry Research OS
A consulting research workflow that links report claims to sources, fact checks, viewpoints, challenge evidence, reviewer decisions, and fixed public reports.
Live static proof · Sanitized historical snapshot · No live crawler or report-generation API
A consulting research workflow that links report claims to sources, fact checks, viewpoints, challenge evidence, reviewer decisions, and fixed public reports.
- Domain
- Consulting Automation
- Role
- Original engagement: Business–Technology Bridge & Joint Developer · Later public productization: narrower product-level attribution
- Current status
- Live static proof · Sanitized historical snapshot · No live crawler or report-generation API
- Team boundary
- The original work bridged an eight-person, CTO-led department, iResearch researchers, and CSDN engineers. Later productization is described at product level without claiming sole authorship of every component.
Problem
The user problem
Researchers, engineers, and delivery reviewers need to see which source supports a report claim, which evidence challenges it, and what changed during review.
Context
Project context
The original engagement covered requirements translation, a source audit, two delivery rounds, internal QA, and coordination. The later LaurenceYang site is a separate sanitized historical snapshot with narrower product-level attribution.
Workflow
Steps from question to review
- Translate research pain points into scope and testable workflow requirements
- Audit and validate the source set
- Keep sources, facts, viewpoints, and evidence associations distinct
- Attach challenge evidence and review to the delivery workflow
- Publish a fixed, allowlisted snapshot without live mutation or collection services
Controls
Controls I chose
- Original delivery evidence and later public-snapshot evidence remain separate.
- Supporting, limiting, and challenging evidence is not flattened into one certainty level.
- The public package is read-only and allowlisted.
- Crawler, scheduler, mutation, model, and report-generation services remain outside the public release.
Evidence
What has been verified
- The original delivery included a 262-source audit, an 88-item evidence-validation table, five thematic reports, and 57 of 57 internally closed second-round content checks.
- The later public proof is a frozen 2026-07-29 snapshot with five fixed English Evidence Briefs in DOCX and Markdown.
Public version
Open the current public version
The link opens the public version described above. Its status and limits are the same ones listed on this page.
Continue