Skip to content

[v0.8] Update docs, roadmap, and release notes for agent-rated evidence/release boundary #97

Description

@Stahl-G

Parent: #89

Depends on: #90, #91, #92, #93, #94, #95, #96

Summary

Update public docs so v0.8 is described accurately as agent-rated evidence readiness and release eligibility, not automatic truth verification or automatic publication approval.

Motivation

The wording matters. If v0.8 says "Evidence Readiness and Release Eligibility" without boundary text, users may assume MABW proves facts or authorizes formal publication. That is not the product claim.

The correct claim is:

Semantic reviewer agents rate evidence and release risks. Deterministic schemas, policy packs, and control artifacts convert those ratings into warnings, blockers, allowed-use labels, and human-review requirements.

Files to update

README.md
README.zh-CN.md
README_en.md
docs/roadmap.md
docs/control-surfaces.md
docs/features.md
docs/releases/v0.8.0.md
docs/red-lines-and-anti-patterns.md
docs/support-matrix.md

Add docs for new artifacts:

docs/evidence-readiness.md
docs/release-readiness.md

Required wording

README / release note should include wording close to:

MABW v0.8 introduces agent-rated evidence readiness and release eligibility. Semantic reviewers rate source authority, source-to-claim support, metric scope, official-source coverage, and branding authorization. Deterministic policy packs convert those ratings into warnings, blockers, allowed-use labels, and human-review requirements.

MABW does not certify truth, provide legal or investment advice, or authorize publication.

Chinese version:

MABW v0.8 引入 agent 评审驱动的证据就绪与发布资格检查。语义评审 agent 对来源等级、来源对 claim 的支持程度、指标口径、官方源覆盖和主体授权进行结构化评级;确定性 policy pack 将这些评级转换成 warning、blocker、允许用途和人工复核要求。

MABW 不证明事实绝对正确,不提供法律或投资意见,也不自动授权发布。

New control-surface docs

Document:

output/intermediate/semantic_review_report.json
output/intermediate/evidence_report.json
output/intermediate/release_readiness_report.json
output/intermediate/human_approval_ledger.json

For each surface, document:

  • writer;
  • reader;
  • authority level;
  • reset/freeze rule;
  • whether it blocks;
  • whether it is deterministic or agent-written.

Boundary table

Add a table:

Status Meaning Does not mean
workflow pass stages/artifacts complete facts are semantically true
semantic review completed agents produced rubric-based review review is final authority
evidence pass evidence meets mode policy truth is certified
release eligible candidate may enter human release review publication is authorized
release blocked known blocker exists report has no internal draft value

Example status block

Docs should show this expected v0.8 result:

workflow_status: pass
semantic_review_status: completed
evidence_status: conditional
release_status: blocked
release_mode: research_review
allowed_use:
  - internal discussion draft
  - analyst review input
not_allowed_use:
  - formal external publication
  - institution-branded distribution
  - investment recommendation
  - legal or compliance conclusion

Acceptance criteria

  • README explains agent-rated boundary.
  • Chinese README explains the same boundary.
  • v0.8 release notes exist.
  • Control surfaces doc includes semantic/evidence/release/approval artifacts.
  • Docs distinguish workflow pass, evidence pass, release eligibility, and human approval.
  • Docs clearly state non-goals: no truth certification, no legal/investment advice, no publication authorization.
  • Red-lines doc mentions institution branding/confidential-label misuse.
  • Support matrix reflects experimental/implemented status accurately.

Non-goals

  • Do not overclaim output quality improvement.
  • Do not promise formal research publication.
  • Do not remove the existing "traceability, not semantic proof" boundary; extend it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions