---
slug: "answer-review-and-quality-checks"
name: "Answer Review and Quality Checks"
packType: "harness"
canonicalPattern: "hybrid"
version: "0.1.0"
trust: "Verified"
publisher: "Agent Workspace"
updatedAt: "2026-04-15"
---

# Answer Review and Quality Checks

> Persist the answer as a reviewable artifact, not just a message string.

## Summary

A runtime pattern that persists final answers, quality checks, evaluation metadata, and downstream review state as first-class records instead of burying them in message text.

## Install

```sh
npx attrition-sh pack install answer-review-and-quality-checks
```

### Claude Code / AGENTS.md snippet

```md
# Answer Review and Quality Checks
# See: /packs/answer-review-and-quality-checks

```

## Contract

_No execution contract defined for this pack type._

## Layers

_No three-layer split defined for this pack type._

## Use When

- Answers may need post-run review, escalation, or auditing.
- You want live evaluation to exercise the same runtime as the product.
- The app needs a deploy gate or quality dashboard.

## Avoid When

- The output is disposable and does not need later inspection.
- You are still in the earliest sketch phase and do not yet know the domain rubric.

## Key Outcomes

- Quality becomes measurable and replayable.
- The answer contract is separated from the chat transcript.
- Runtime checks and eval checks can share a common packet shape.

## Minimal Instructions

Persist a final answer packet for every meaningful run.

The packet should include:
- final answer
- scope and references
- quality checks
- trace pointers
- evaluation linkage

Do not rely on chat text alone as the system of record.

## Full Instructions

Treat the answer as a durable application artifact.

For every non-trivial run:
1. Persist the final answer to an answer packet.
2. Attach references, quality checks, and trace metadata.
3. Link eval runs and live scoring back to the same packet shape.
4. Surface packet status in the UI so operators can see whether the answer passed or failed checks.

This should support:
- replay
- review
- later analytics
- quality gating before deployment

## Evaluation Checklist

- Is there a persisted answer packet for each completed assistant run?
- Do runtime checks and eval checks share a visible schema?
- Can a later reviewer inspect packet quality without reading the raw message transcript?

## Failure Modes

- **[MID] Quality checks exist only in logs, not in app data.**
  - Trigger: (legacy — trigger not separated)
  - Prevention: (legacy — no explicit prevention)
- **[MID] The final answer is stored as unstructured chat text only.**
  - Trigger: (legacy — trigger not separated)
  - Prevention: (legacy — no explicit prevention)
- **[MID] Evaluation runs test a different runtime than the product uses.**
  - Trigger: (legacy — trigger not separated)
  - Prevention: (legacy — no explicit prevention)

## Transfer Matrix

_No measured cross-model transfer data._

## Telemetry

_No telemetry recorded._

## Security Review

_No security review on file._

## Compares With

_No comparative data._

## Related Packs

_No related packs._

## Changelog

_No changelog entries._

## Sources

- [FloorAI repo](https://github.com/HomenShum/floorai) — Reference implementation with answer packets, quality checks, and eval persistence.
- [Agent Workspace template repo](https://github.com/HomenShum/agent-workspace-template) — Reusable platform extraction for packet and eval persistence.

## Examples

- [Open shared studio](/chat)
- [Template repo](https://github.com/HomenShum/agent-workspace-template) (external)