I0704 — Publish what attribution guarantees, and what it still cannot

BLOCKED wave 3 · p2 · implementation profile · parallel safe

Part of M002 — A durable record names the worker that wrote it.

Objective

State on the public surface what a record's attribution now means, and state plainly what it does not: that a worker's identity is supplied by the session, not verified, and that nothing here proves who a worker was.

Why

Attribution is the kind of guarantee a reader will assume is stronger than it is. The distance between naming a worker and authenticating one has to be written where the claim is, not left to be inferred.

Current state

The behaviour will exist and be tested. Nothing on the public surface says what it covers.

Desired state

A claim states what is guaranteed with the file and the case behind it, and says on its detail page that the identity is asserted by the session and never verified.

Scope

• docs
• site/data/generated

Out of scope

• Any behaviour change
• Any claim about verifying who a worker is

Dependencies

• I0703BLOCKED Implement the decision and prove it holds

Acceptance criteria

• The claim cites an implementation path and a test path that both exist
• The detail page says the identity is supplied, not verified
• The generated site data regenerates with no stale file

Validation

• scripts/generate-site-data --check
• bash test/run.sh

Evidence required

• docs_build

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Risk

A claim about attribution read as a claim about authentication would be the most damaging overstatement on the site.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I0704.yaml. Read it back with majordomus plan show I0704.