Skip to content

id: validation gap — alias list has no creation date (P5.7): signed header has no time field #1422

Open

Description

@dezren39

Gap found by the #1075 validation audit (Phase 5, P5.7) — 2026-10-27

The plan of record (doc/2026-10-11T11-08-42Z_design_remaining_work/plan-phases.md, P5.7) specifies the alias list as (text, date, creator), with contested sets shown and shortest-unique-prefix disambiguation.

On current main 37418e56 the alias display module (pkgs/id/src/aliases.rs) implements text + creator, contested sets, pet-name/primary precedence, and unique-prefix disambiguation (pkgs/id/tests/aliases.rs — contested, primary, petname, prefix tests all present), but its own header states the remaining hole verbatim:

"The creation date is not shown, because the signed header has no time field (open)."

So the date element of the P5.7 alias list has no source and no display, and no existing issue tracks it (checked 2026-10-27: alias/date searches return only tangential items; the related user-subject hole is separately tracked as #160).

Acceptance criteria

  • Either: alias rows expose a creation date derived from a source the design accepts (with the source named in aliases.rs), and a test covers it; or
  • the plan's P5.7 row is amended to drop the date element with the reason recorded, and the "(open)" note in aliases.rs is replaced by a pointer to that decision.

Found by: queue task 1256 (slice 4 of the #1075 audit), Lane D worker shift 2026-10-27.

Activity

  1. added
    kind/featureNew feature or capability request
    priority/highImportant and time-sensitive
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    nowOrg Project gate: active priority — orchestrator adds to the board
    on Oct 27, 2026
  2. developing-today commented on Oct 27, 2026

    @developing-today
    Contributor
  3. dezren39 commented on Nov 2, 2026

    @dezren39
    MemberAuthor

    Triage verdict: confirmed — gap is real on current main

    Probed origin/main 0e26fa4b3 (2026-11-02):

    • pkgs/id/src/aliases.rs:17 still carries the hole verbatim: "The creation date is not shown, because the signed header has no time field (open)."
    • Alias has only claim: Hash, text: String, author: AuthorKey — no date field; Row/Shown expose no date either.
    • Claim in pkgs/id/src/tag_claims.rs:83 has id, author, subject, name, value — no time/timestamp; nothing downstream could source a creation date.
    • No created_at|timestamp|DateTime|creation (beyond that doc line) anywhere in aliases.rs or pkgs/id/tests/aliases.rs.

    Neither acceptance path has happened: no date on alias rows, and the plan row / (open) note are untouched.

    Route: enqueueing a scoped follow-up packet for issue #1422 (either expose a creation date from a design-accepted source + test, or amend the P5.7 plan row and replace the (open) note with a pointer to that decision). No hard-stop labels on this issue; triage claims no files changed.

  4. dezren39 commented on Nov 2, 2026

    @dezren39
    MemberAuthor

    Done: triaged, follow-up enqueued

    • Outcome: triaged — issue stays open, gap confirmed on origin/main 0e26fa4b3.
    • Follow-up: task 6589 (small_fix packet) queued — expose alias creation date with test, or amend the P5.7 plan row and repoint the (open) note.
    • Queue labels cleared (work/assigned, queue/claimed, status/in-progress removed).
  5. 67 remaining items

  6. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  7. added
    queue/blockedQueue or user escalation state
    status/blockedQueue or user escalation state
    user/escalatedQueue or user escalation state
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 4, 2026
  8. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  9. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · blocked / escalated to Drew

  10. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · blocked / escalated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)kind/featureNew feature or capability requestnowOrg Project gate: active priority — orchestrator adds to the boardpriority/highImportant and time-sensitivequeue/blockedQueue or user escalation statesource/creatorFiled by the new-issue-creator jobstatus/blockedQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this itemuser/escalatedQueue or user escalation statework/assignedQueue worker lifecycle state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions