Skip to content

BriefLoop v0.11.6

Choose a tag to compare

@Stahl-G Stahl-G released this 03 Jul 08:52
· 613 commits to main since this release
1441ef1

BriefLoop v0.11.6 — Product Baseline, Reader Quality, Topology, And Launch Readiness

v0.11.6 ships the accumulated v0.11 product-baseline line on top of the
BriefLoop control spine. It promotes the modest CLI product entries for
industry weekly, management monthly, and document-review workspaces while
keeping wider Product OS, quality, release, and evidence-extraction surfaces
bounded by their support status.

This release does not provide semantic truth proof, output-quality proof,
automatic publication, public-release authorization, legal/compliance advice,
investment advice, IR/disclosure readiness, or a completed Evidence Extraction
Mode.

What Changed

  • Promoted the product-facing briefloop new industry-weekly,
    briefloop new management-monthly, and briefloop new document-review
    workspace entries as the supported v0.11 baseline, while keeping canonical
    internal ReportPack ids stable.
  • Added product-baseline, public-claim, skill-freshness, launch-smoke, and
    release-checklist guards so release prep fails closed when public docs,
    support status, or source-checkout setup drift.
  • Added reader-quality projection surfaces for materiality selection, reader
    template conformance, support-calibrated wording, citation profile split,
    coverage/omission, Quality Panel closeout, and scoped final-abstract warnings.
  • Added public-safe reference and evaluation packets, including same-evidence
    reader-quality regression coverage, a Product OS reader-quality reference
    note, and a minimal comparative evaluation packet.
  • Hardened role topology guidance so default topology can satisfy Screener
    through Scout without losing distinct candidate_claims.json and
    screened_candidates.json artifacts, while strict topology remains available.
  • Added deterministic trajectory-regulation decision narrowing for repeated
    retry, repair-cycle, or blocker loops, limiting exhausted current-stage
    decisions to request_human_review and block_run.
  • Added Evidence Extract source locks, logical page inventory seeds, and UTF-8
    text-span seed registries for registered document-review sources.
  • Added release/evidence synthetic blocker cases and release-branding readiness
    metadata checks for internal readiness workflows.
  • Added launch-facing wording and evidence-link polish, plus
    docs/release-checklist.md for operator release preparation.

Compatibility

This release keeps these compatibility surfaces:

  • multi-agent-brief remains the engine CLI.
  • briefloop remains the shell CLI alias.
  • /briefloop remains the Claude writer command.
  • /mabw remains a compatibility Claude command.
  • multi_agent_brief remains the Python package/module path.
  • multi-agent-brief-workflow remains the Python distribution package name.
  • Existing workspace artifacts, MABW experiment IDs, and control files are not
    renamed.

Support Status

Supported for the v0.11 baseline:

  • briefloop new industry-weekly
  • briefloop new management-monthly
  • briefloop new document-review
  • baseline ReportSpec / ReportPack contracts for the supported packs

Still experimental unless explicitly stated in the support matrix:

  • solar-periodic
  • Quality Panel / Summary / static HTML projections
  • SourceHub Lite
  • internal release approval records
  • Evidence Extract source-lock/page/span seed artifacts beyond bounded
    registration
  • reader-quality warning/projection surfaces
  • synthetic evaluation fixtures and minimal comparative evaluation packets

Boundaries

BriefLoop still does not prove that a source semantically supports every claim,
eliminate hallucinations, replace human review, provide legal/compliance or
investment judgment, or make reports automatically ready to send.

v0.11.6 does not complete issue #156 as a full page-cited Evidence Extraction
Mode. It adds bounded source-lock, logical-page, and text-span seed contracts
that future extraction work can build on.

The public reference and evaluation packets are measurement infrastructure and
traceability evidence. They are not benchmark-win claims, output-quality proof,
or publication approval.