generated from hack-ink/vibe-mono
-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Labels
area:apiHTTP API service and request/response contracts.HTTP API service and request/response contracts.area:docsDocumentation and developer experience docs.Documentation and developer experience docs.kind:specSpecification or contract definition (APIs, schemas, invariants, query semantics).Specification or contract definition (APIs, schemas, invariants, query semantics).theme:provenanceEvidence, citations, lineage, and explainability.Evidence, citations, lineage, and explainability.
Description
Parent
Problem
source_refis 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_refschema 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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area:apiHTTP API service and request/response contracts.HTTP API service and request/response contracts.area:docsDocumentation and developer experience docs.Documentation and developer experience docs.kind:specSpecification or contract definition (APIs, schemas, invariants, query semantics).Specification or contract definition (APIs, schemas, invariants, query semantics).theme:provenanceEvidence, citations, lineage, and explainability.Evidence, citations, lineage, and explainability.