Skip to content

V-L2-F2: implement the JSON sidecar storage backend (split from #45) #112

Closed

Description

@hyperpolymath

Split out of #45 per its acceptance note ("json sidecar storage is either implemented or removed from manifest (separate issue)").

[sidecar].storage advertised sqlite | json but only sqlite has code; #45 stops silently emitting SQLite DDL for a json store and rejects storage="json" with a pointer here. This issue tracks actually implementing a JSON sidecar (append-only JSON document store mirroring the verisimdb_* tables) OR formally dropping json from the manifest schema + validation if a JSON store is not wanted.

Acceptance:

  • Decision: implement JSON store vs drop the option from the manifest enum + docs + validate
  • If implement: a JSON storage module with the same octad-dimension coverage as the sqlite path; generate/drift/gc honour it
  • If drop: storage enum, SidecarConfig docs, manifest template, and validate/doctor messaging no longer mention json

Activity

  1. hyperpolymath commented on May 30, 2026

    @hyperpolymath
    OwnerAuthor

    Wrap-up note: the decision behind this resolution (drop json; the octad data layer is intrinsically relational, so storage is closed to sqlite + postgres) is now recorded as ADR-0011 (docs/decisions/0011-sidecar-storage-is-relational.adoc), with a CHANGELOG Removed entry and a README correction, in #149. No reopen needed — this issue stays closed/completed (resolved by #144, test coverage in #147).


    Generated by Claude Code

  2. added a commit that references this issue on May 30, 2026
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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions