Skip to content

Queen: verify retained Trinity Memory attention evidence for cell #115 #1368

Closed

Description

@dmitrii-f-t27

The live dmitrii-f-t27/trinity-memory#115 cell is closed but remains T27 proof needed / Coverage unknown. The published atlas is from 2026-10-02 and its candidate links do not establish the accepted attention implementation.

Extend the exact-evidence reader proposed in #1363 for the retained attention qualification from dmitrii-f-t27/trinity-memory#122. Do not duplicate Corona's reader or treat a closed GitHub issue as proof.

Acceptance:

  • Specify Memory's allowlisted issue, native .t27 source/seal/vectors/verifier and evidence pins in a compiler-checked .t27 policy before TypeScript changes.
  • Require matching files at the current accepted default-branch SHA and successful canonical push CI that actually replays the sealed contract and retained raw board measurements. Missing/tampered/stale evidence, reopened/other issues and pending/failed runs must remain unknown.
  • Preserve Corona checks and show accurate evidence links (Memory has retained FPGA evidence, not an ASIC GDS run).
  • Refresh the published Memory catalog from its accepted source without inventing coverage or erasing a still-addressable closed cell.
  • Validate policy/seal/conformance tests, reader negatives, existing world/paint tests and the production build.
  • After dependency fix(queen,ci): verify Corona evidence and repair fork validation #1363 and source proof are accepted, obtain independent review and green CI, merge, release the exact Queen revision through the actual embedded app publisher, and verify the cell's coverage and color live.

Source task: dmitrii-f-t27/trinity-memory#115; accepted hardware-source PR: dmitrii-f-t27/trinity-memory#119. No new hardware run, full-model completion or reward is claimed by this work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions