Reference fixtures · Draft 0.1

Follow one claim from declaration to evidence, action and test.

The smallest useful example is intentionally ordinary. Interoperability depends on explicit boundaries, not impressive volume.

This site’s public manifest

Owner-published identity, claims, answers, limits and freshness policy for the canonical standard site.

/answerworthy.md

Minimal Answerworthy Bundle

One bounded finding, its evidence, one human-required action and an evidence-aware score.

/standard/0.1/examples/minimal.answerworthy.bundle.json

Matching conformance record

Core and agentic profile tests for the minimal bundle.

/standard/0.1/examples/minimal.answerworthy.conformance.json

Agent-readable plan

The Markdown projection preserving source findings, permission, guardrails, completion and verification.

/standard/0.1/examples/answerworthy.plan.md

The chain

The owner speaks. Evidence answers back.

Portable relationship

/answerworthy.md
  owner declaration
        ↓ independently inspected
answerworthy.bundle.json
  evidence + findings + provider states
        ↓ actions derived from findings
answerworthy.plan.md
  permission + dependencies + verification
        ↓ tests and recheck
answerworthy.conformance.json

Dogfooding rule

The standard’s canonical site publishes its own manifest.

The site does not grant itself M3 corroboration or external authority. It exposes the owner declaration so independent tools can inspect it.

Inspect answerworthy.md