Skip to content

Spec: versioned source_ref schema for doc pointers #76

@aurexav

Description

@aurexav

Parent

Problem

  • source_ref is required and flexible, but lacks a standard, versioned schema for document pointers.
  • Without a schema, downstream agents cannot reliably hydrate original long-form content.

Scope

  • Define a versioned source_ref schema for doc pointers (e.g., kind, schema_version, doc_id, uri, content_hash, locator/span, mime_type, access hints).
  • Define compatibility rules (forward/backward), validation expectations, and safe limits.

Acceptance criteria

  • Add a spec or guide page that defines the schema and rules.
  • Provide at least one reference example payload.
  • Explicitly document how this interacts with the English-only boundary (canonicalize facts to English; store originals elsewhere).

Notes

  • Backlog draft: docs/plans/2026-02-23-agent-memory-mcp-skills-backlog.md.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:apiHTTP API service and request/response contracts.area:docsDocumentation and developer experience docs.kind:specSpecification or contract definition (APIs, schemas, invariants, query semantics).theme:provenanceEvidence, citations, lineage, and explainability.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions