From e6e47dd98a2adbfb4bf3e17c5e29cd1f4fe1025d Mon Sep 17 00:00:00 2001 From: Erik Date: Mon, 7 Sep 2026 11:51:14 +0200 Subject: [PATCH] =?UTF-8?q?docs(vt):=20post-campaign=20idea=20=E2=80=94=20?= =?UTF-8?q?readable=20export/diff=20for=20settings=20and=20loot,=20not=20a?= =?UTF-8?q?=20second=20storage=20format?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Fable 5.1 --- docs/plans/2026-09-06-campaign-vt-vtank-oracle.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/plans/2026-09-06-campaign-vt-vtank-oracle.md b/docs/plans/2026-09-06-campaign-vt-vtank-oracle.md index 9e04092c..4a2365f1 100644 --- a/docs/plans/2026-09-06-campaign-vt-vtank-oracle.md +++ b/docs/plans/2026-09-06-campaign-vt-vtank-oracle.md @@ -86,3 +86,4 @@ Linux-clean by construction; the Ubuntu CI closure runs the MossTank tests. - 2026-09-06 VT0 complete. VT1 docs 01/02/03/08 dispatched first, 04–07/09 next. - 2026-09-06 VT1: all nine catalog docs landed; index written; Opus citation pass in flight. - 2026-09-06 Files decision amended by the owner: metas and navs are metaf `.af`, not `.met`/`.nav` (see Decisions). Docs 06 §1 and 07 §1 stay as the binary-format record (they describe what the metaf tool converts from); the semantics sections (06 §2-5, 07 §2-4) remain the behavior oracle. VT2 doc: `2026-09-06-campaign-vt-vt2-gap-audit.md`; slice-1 contract: `2026-09-06-campaign-vt-slice1-files-and-columns.md`. +- 2026-09-07 owner asked whether every VTank format should get a human-readable twin like `.af`. Lead's answer, recorded as a post-campaign idea: VTank's `.usd`/`.ugd`/`.utl`/`.met` are already text (the one-value-per-line table grammar) and `.nav` is plain lines; only metas/navs had a community-authored readable format (metaf) with a converter both ways, which is why `.af` is safe as storage. For settings/loot a second format would be our own invention with two sources of truth. Instead: a one-way readable EXPORT + a profile DIFF command (`/vt settings export`, `key = value` lines) for inspection and version control, VTank's format staying the only storage. Revisit only if hand-editing loot rules becomes routine.