output-template

Demo Manufacturing BV

Source intake runs stored source-traceable

template-review-needed

Output template

Review specification for planned PowerPoint, PDF, and Word handoffs. Binary rendering is intentionally not implemented in this internal demo.

Target formats

template-review-needed

PowerPoint

planned-template-spec-only

Client-presentable evidence-to-canvas deck for meeting discussion.

Audience

Advisor or engagement lead presenting DigiBeat findings.

Binary rendering is not implemented; CLMBS template and QA rules are still required.

PDF

planned-template-spec-only

Locked handoff package generated from the reviewed canvas and evidence appendix.

Audience

Client/reviewer needing a stable non-editable review artifact.

Binary rendering is not implemented; CLMBS template and QA rules are still required.

Word

planned-template-spec-only

Advisor memo with narrative recommendations, assumptions, and source citations.

Audience

Consultant preparing editable advisory language from reviewed DigiBeat output.

Binary rendering is not implemented; CLMBS template and QA rules are still required.

Deck / document outline

  1. 1. Title and case context
  2. 2. Evidence-to-canvas overview
  3. 3. Source package readiness and conversion warnings
  4. 4. Canvas summary with confidence and evidence status
  5. 5. One detail slide or section per canvas block
  6. 6. Retrieval validation appendix with positive, negative, borderline, and known-miss checks
  7. 7. Governance, approval, and client-facing boundary
  8. 8. Next actions before live OpenAI or production use

Field map

case metadata

Case id, client name, sector, website, phase, and status.

canvas blocks

Block title, summary, confidence, evidence status, assumptions, and source ids.

source package

Source id, title, kind, owner, category, anchors, conversion status, and warnings.

retrieval validation

Validation query, expected sources, hit sources, rank, verdict, and notes.

pipeline runs

Run id, mode, status, created timestamp, step outputs, and live-error messages.

approval register

Gate, current local decision, owner, note, created timestamp, and production boundary.

archive handoff

Archive naming proposal, retention blockers, checksum/storage gaps, and review actions.

Source appendix policy

PowerPoint should keep visible source ids on claims and place detailed evidence in appendix slides.
PDF should include or attach the reviewed source appendix according to the agreed CLMBS handoff policy.
Word should use inline citation markers plus a source table so narrative recommendations remain traceable.
Embedded, linked, or attached source behavior still needs CLMBS approval per output format.

Acceptance checks

Every client-facing claim has source ids or is explicitly marked as an assumption.
Low-confidence or weak-evidence canvas blocks are visually flagged.
Live/model-produced output is labeled only after `OPENAI_API_KEY` is provisioned and a live smoke run is inspected.
Approval, retention, archive, and client-facing boundaries are displayed before export.
Binary PowerPoint/PDF/Word output receives manual QA until an audited renderer exists.

Renderer blockers

Agreed CLMBS PowerPoint/PDF/Word templates and brand rules are not yet supplied.
Binary renderer implementation, file storage, immutable archive records, and checksums are not implemented.
Tenant, retention, deletion, and legal-hold policy are not approved for production exports.
QA rules across PowerPoint, PDF, and Word need approval before generated files can be trusted.

Visual requirements

Use an agreed CLMBS output template and brand treatment before external use.
Keep evidence ids, confidence flags, and low-confidence warnings visible near claims.
Do not use dark, stock-like, or decorative imagery where reviewers need to inspect content.
Separate deterministic internal-demo output from any future live/model-produced output labels.