Skip to content

feat: content-hash-at-timestamp attestation over cited sources #129

Description

@HMAKT99

Raised by Mike Czerwinski on the launch post.

The problem: agents re-derive "has this source changed since I captured it" — decision stores full of clipped facts rot quietly as sources move.

Proposed: generalize the dependency-hash mechanism from #124/PR #126 (local imports) one ring outward to cited sources: when a claim has a src that is a resolvable file or URL, record src_hash (content hash at stamp time). akf check then reports STALE reason=source_changed when the cited source no longer matches — retiring a whole class of re-reads.

  • Files: reuse deps._hash_file
  • URLs: hash fetched content (opt-in flag — network at check time is a behavior change)
  • Schema: additive optional field on Claim, wire-compatible

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