VSL/MSL coordination: M1→M3 trackers, kickoffs, memory (incl. M3 storage seam + notional-DBIA)#2
Merged
Conversation
…one) Refreshed kickoff for the v-stdlib T1.3 session. The original assumed v-pkg could already package a #8989.51 PARAMETER DEFINITION + Required Build; v-pkg was routine-only. That enabler is now done (v-pkg branch t1.3-kids-data-components, proven both engines). This prompt points the session at the v-pkg capability memory, the proven build-spec shape, the verbatim per-engine recipes, and the required-build-enforcement nuance. Supersedes the original kickoff (kept). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The v-pkg enabler (branch t1.3-kids-data-components) was merged to v-pkg main (2a3f273). Update the prerequisite to build the standalone v-pkg binary from main rather than the feature branch. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ean both engines VSL/MSL M1 task T1.3 complete (v-stdlib branch t1.3-vsl-kids): the VSL layer packaged as a KIDS build (VSLCFG + a VPNG GREETING #8989.51 PARAMETER DEFINITION at SYS + a Required Build on MSL*0.1*1), with install->verify->uninstall-> verify-clean GREEN on both engines (vehu YDB + foia-t12 IRIS) over the driver, plus a deterministic+golden check-kids drift gate. Row 🟢 + progress-log entry. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Kickoff for the final two M1 tasks, folded into one session: build the VPNG
walking-skeleton consumer in a NEW `vpng` repo (T1.4), then close the §12.1
determinism-ledger exit gate (T1.5) — install-once base (MSL→VSL→VPNG), seed,
golden `{"greeting":"hello"}` byte-identical on both engines, test-in-place,
uninstall clean. Records the three session decisions (new repo, fold T1.5,
prove install-once base).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Flip the T1.4 (VPNG golden match) and T1.5 (§12.1 determinism ledger, both
engines) rows to green; update the Phase C status line (T1.1–T1.5 all done,
M1 complete → next M2) and add a progress-log entry. The vpng consumer returns
the golden {"greeting":"hello"} byte-identical on YDB (vehu) + IRIS (foia-t12)
on the install-once MSL→VSL→VPNG base, test-in-place 3/3, uninstall-clean.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The next-session kickoff for M2 — the most engine-sensitive seam (R1). Cross-repo leaf-first: author + tag the STDNET MSL leaf in m-stdlib (v0.8.0), then bind it with a VSLIO adapter in v-stdlib over ^%ZIS/CALL^%ZISTCP + named TLS. Tiered acceptance (outbound POP=0 -> plain loopback echo -> TLS echo), both engines. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…6-16) Neither vehu (YDB) nor foia-t12 (IRIS) has a DEFAULT TLS SERVER CONFIG #8989.51 param def (or any named TLS config); IRIS has no native Security.SSLConfigs. So M2 tier-3 (TLS echo) is blocked-on-infra from the start — tiers 1-2 are clear. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…le stand-in) The "Broker TLS patch" is actually Kernel XU*8.0*787, IRIS-only per the gold corpus (value names an IRIS Security.SSLConfigs cert); vehu is GT.M and neither engine has it. Rather than the (inapplicable) patch, provision just the DEFAULT TLS SERVER CONFIG #8989.51 param def via a reversible param-def-only v-pkg build (ZTLSCFG*1.0*1, Z namespace) so M2 VSLIO's config-read of the named-config parameter is testable. Installed + verified + settable on BOTH vehu (YDB) and foia-t12 (IRIS); reversible via v-pkg uninstall. Ships NO cert / Kernel TLS API / working socket — tier-3 real TLS stays infra-blocked. Updates the M2 kickoff TLS note with the premise correction + provisioning state. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The MSL half of M2 (the VSLIO socket/TLS seam, S4): STDNET portable raw-TCP API over the engine-native SOCKET device, @seam STDNET emitted + bump-forcer green, YottaDB loopback echo green 9/9 on m-test-engine; IRIS soft-skips (deferred). m-stdlib branch m2-stdnet (700fbd6). Owed: tag MSL v0.8.0 -> Lane B (VSLIO). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Lane A done + MSL v0.8.0 tagged, so the next step is Lane B: the VSLIO adapter in v-stdlib binding STDNET to ^%ZIS/CALL^%ZISTCP. m2-lane-b-vslio-kickoff.md is the focused, self-contained fresh-session prompt (re-pin v0.8.0 -> @icr-tagged VSLIO -> tiered acceptance: POP=0 / loopback echo / TLS blocked-on-infra). The original m2-vslio-kickoff.md is marked as the deep design context with a pointer. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
VSLIO (v-stdlib, branch m2-vslio db3c5e0) binds the STDNET socket seam (MSL v0.8.0) to VistA's Kernel device handler — outbound TCP via CALL^%ZISTCP (#2118), the client subset (no Supported listen/accept in VistA; server stays in STDNET). vehu 10/10 (POP=0 + echo) · foia-t12 6/6 (binding wired; loopback soft-skips on STDNET's IRIS leg). 3 boundaries green; TLS gap loud; tier-3 TLS infra-blocked. M2 functionally complete for tiers 1-2; owed: STDNET IRIS leg + tier-3 TLS. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ession The next milestone after M2: VSLFS binds a portable MSL record-store seam to VistA's FileMan DBS API (GETS^DIQ/$$GET1^DIQ/UPDATE^DIE/FILE^DIE/FIND1^DIC; R4). Cross-repo leaf-first (define+tag the storage seam in m-stdlib v0.9.0, then VSLFS re-pins+binds). Frames the two design questions to resolve first — the storage seam's home (Q3: new MSL module recommended) and the test-file approach (existing file first; the FileMan-DD-install v-pkg enabler deferred) — plus the DIERR->$ECODE contract and per-call @iCr grounding. Parallel-safe with M2's owed tail. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Per user directive (2026-06-16): the VistA DBIA/ICR registry is a manually human-curated FORUM list — not in code, not in a FileMan DD, not enforced programmatically. So the check-icr gate's real invariants are (a) the call is a documented Supported API and (b) no direct global access; the ICR *number* is notional and must never be a hard requirement or a warning. - Amend coordination plan §5.4: a declaration may use a notional marker (@iCr DBS / notional) + real @status/@custodian/@source; the gate accepts it and emits no warning about the missing number. FileMan DBS (GETS^DIQ / $$GET1^DIQ / UPDATE^DIE / FILE^DIE / $$FIND1^DIC) is the concrete case — no ICR number exists in the gold corpus, by design. - New shared memory notional-dbia-not-a-blocker.md (+ index). Coded into v-stdlib gen-icr.py at M3 (VSLFS). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Flip the M3 row: the storage seam is proven end to end. Lane A STDKV (MSL v0.9.0 storage leaf) + Lane B VSLFS (binds it to FileMan DBS), dual-engine GREEN 7/7 (vehu + foia-t12) over an existing low-risk file (#8989.51) with DIERR -> ,U-VSL-FS-DIERR, $ECODE. DD-install decoupled/deferred to a v-pkg track. ICR notional (FileMan DBS has no corpus number; @iCr DBS marker). Owed: the v-pkg FileMan-DD-install enabler + merge m2-vslio/m3-vslfs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rafael5
added a commit
that referenced
this pull request
Jun 16, 2026
…ose-out) Close out the M3 increment: flip the M3 row to "ALL MERGED" and add a dated log entry. STDKV (MSL v0.9.0) + VSLFS (FileMan DBS storage adapter) proven dual-engine (7/7 vehu + foia-t12), DIERR -> ,U-VSL-FS-DIERR, $ECODE, ICR notional. Merged to default branches: m-stdlib m3-stdkv->master (PR #17, tag v0.9.0); v-stdlib m2-vslio->main (PR #4) + m3-vslfs->main (PR #5); docs coordination->main (PR #2). Merged main re-verified 22/22. Next: M4 (VSLSEC + VSLLOG). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lands the accumulated VSL/MSL coordination docs from main onward: M1 (VPNG vertical), M2 (VSLIO) and M3 (VSLFS storage seam) tracker flips + kickoff prompts, plus the M3 deliverables — the notional-DBIA resolution (plan §5.4 amended + docs/memory/notional-dbia-not-a-blocker.md) and the M3-DONE tracker row. Clean merge (main is a strict ancestor).
🤖 Generated with Claude Code