Skip to content

BlobStore trait + content-addressed fs backend (ADR-0006) #63

Description

@filipeforattini

What to build

Introduce a content-addressed BlobStore trait with an fs backend, addressing blobs by a cas content key. It ships alongside existing storage and is exercised by tests only (the expand step of ADR-0006); no production caller yet.

Acceptance criteria

  • BlobStore trait with put/get by content-addressed key.
  • fs backend stores/retrieves blobs content-addressed, zero-config default path.
  • Round-trip and dedup-by-identical-bytes tests pass.

Current blocker

status: blocked
kind: main-red-untracked
summary: Refusing admin-merge onto red main because no open main-red repair issue exists. Restore the tracked-red visibility gate by letting syncMainRedRepairIssue auto-file "main-red repair: baseline probe failures on main" from the AFK feedback baseline probe before landing. The attempt branch afk/w8C4I/63-blobstore-trait-content-addressed-fs-bac is intact and validated, but landing is held until the tracked-red repair issue exists. The auto-file attempt for the main-red repair issue failed and must be inspected: gh: failed to create issue (code 1): could not add label: 'priority:urgent' not found. Requeue after the auto-file path recreates it.
next: Restore or create the auto-filed main-red repair issue, then requeue.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, AFK-ready — an agent can pick it up with no human context

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions