Skip to content

Add typed recursive WARP graph attachment references #819

Description

@flyingrobots

Plan: https://github.com/git-stunts/git-warp/blob/plan/streaming-recursive-materialization/docs/plans/streaming-indexed-recursive-warp.md
Design PR: #813

Outcome

Model a graph-valued attachment as a validated WARP graph reference rather than an undifferentiated PropValue or byte asset.

Required work

  • Define runtime-backed inline, asset, and WARP graph attachment kinds.
  • Define graph identity, repository/resolver authority, coordinate/frontier posture, handle kind/schema, capability/trust, and retention posture.
  • Support pinned immutable roots and explicitly live locators.
  • Resolve a live locator once per reading execution and record the pinned result.
  • Keep child graph ordinals local to the child manifest.
  • Reject ambiguous plain-object graph references at admission boundaries.

Acceptance

  • Typed graph references round-trip deterministically.
  • Pinned references participate in commitments without opening child state.
  • Live references resolve once and receipts name the observed root.
  • Missing capability, unsupported schema, and unresolved locator fail closed.
  • Cross-repository resolvers do not leak storage mutation authority into the domain.
  • Generic attachment docs distinguish assets from graph links.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:apiPrimary work area: api.priority:nextNext in line after active work.status:availableOpen and available for prioritization; not blocked or actively in progress.type:featureNew capability or product behavior.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions