Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0704

Publish what attribution guarantees, and what it still cannot

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
3
Waiting on
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI0703I0703 is not DONE
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0704

majordomus plan verify I0704

majordomus plan done I0704

What it is

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.
Now
The behaviour will exist and be tested. Nothing on the public surface says what it covers.
Wanted
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.
Done when
unknown: the record declares no `completion`
Risk
A claim about attribution read as a claim about authentication would be the most damaging overstatement on the site.

Acceptance

  • 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 --checkbash test/run.sh
Evidence required
docs_build
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docssite/data/generated
Not
Any behaviour changeAny claim about verifying who a worker is
Depends on
Priority
p2
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-04
Updated
2026-09-04
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.