Mnemoverse Docs

Appearance

Schemas Index (v0) ​

All canonical v0 schemas are centralized in architecture/contracts/schemas/.

Orchestration Layer Schemas ​

  • render_request.v0.json — CEO → ACS: render request with intent and budgets
  • render_context_reply.v0.json — ACS → CEO: context fragments with KV policy
  • provider_request.v0.json — Generic provider request (L1/L2/L4)
  • provider_response.v0.json — Generic provider response (L1/L2/L4)

Layer-to-Layer Contract Schemas ​

L1↔L2: Noosphere ↔ Orchestration ​

  • noosphere_search_request.v0.json — Search request to Noosphere layer
  • noosphere_search_response.v0.json — Search results with quality metrics

L2↔L5: Orchestration ↔ Evaluation ​

  • evaluation_request.v0.json — Task completion for quality assessment
  • evaluation_response.v0.json — Quality scores and feedback

L4↔L5: Adapters ↔ Evaluation ​

  • experience_record.v0.json — Experience submission for learning
  • experience_response.v0.json — Recording confirmation and metadata
  • hint_request.v0.json — Request for optimization hints
  • hints_response.v0.json — Task completion hints and patterns

Schema Properties ​

  • $schema: Always http://json-schema.org/draft-07/schema#
  • $id: Canonical URL at https://mnemoverse.dev/schemas/{name}.v0.json
  • additionalProperties: Set to false where type safety is enforced
  • required: Minimal required fields for contract compliance

Validation ​

All schemas support:

  • Request/response pattern with request_id tracking
  • Error handling with standardized error codes
  • Metadata with latency, cost, and operational metrics
  • Optional warnings for degraded service conditions

Locations ​

  • Current: architecture/contracts/schemas/ (canonical location)
  • Legacy: architecture/orchestration/schemas/ (migrated)