diff --git a/docs/session-ledger.md b/docs/session-ledger.md
index 0221070..7c68846 100644
--- a/docs/session-ledger.md
+++ b/docs/session-ledger.md
@@ -82,7 +82,23 @@
    NEVER bridged onto the site LAN. The install script hard-fails if MAAS DHCP is on any other subnet.
    **REMAINING on Office1:** deploy + install NetBox (composed, Ready, not yet deployed); compose +
    install GitBucket and Tailscale; then run the NetBox import.
-1b. **`10.10.1.0/24` IS AN UNBLESSED ALLOCATION.** Chosen deliberately (DC1=10.12.x, DC2=10.13.0.0/19,
+1a. **PINNED -- NEXT AFTER NETBOX: deploy Office1's LAN IPv6** (operator ruling 2026-07-13, D-115
+   question 3: "register AND deploy dual-stack on Office1 now", sequenced AFTER the NetBox deploy).
+   Add `2602:f3e2:f01:100::1/64` to the OPNsense edge LAN + RA, and let `voffice1` take its address.
+   Do it via the D-113(a2) REST API -- NEVER a config.xml push.
+   **KNOWN LIMIT, do not forget it:** IPv6 DOES NOT EGRESS THE LAB (measured 2026-07-13: v6 gateway
+   reachable, v6 internet 100% loss, v4 fine). So this proves v6 ADDRESSING / RA / services-binding,
+   which is most of D-101's family matrix -- but NOT internet GUA reachability, which is unprovable
+   in VR1 until the lab's upstream carries v6. Deploy the LAN leg; DEFER the WAN v6 leg (it would be
+   a path to nowhere and untestable). See D-115's amendment.
+1b. **`10.10.1.0/24` IS NOW A BLESSED ALLOCATION (D-115 ADOPTED).** VR1 Office1 = `10.10.0.0/22`
+   (Office role, `10.10.0.0/16`): LAN `10.10.0.0/24` + compose `10.10.1.0/24` + 2 spare. Zero
+   renumber. Also adopted: Edge role `172.30.0.0/16` (legitimises `office1-wan`'s 172.30.1.0/24,
+   which had been squatting in the Corp OOB block), and **DC2 moved to `10.12.64.0/19`** inside the
+   Cloud /16 (its old `10.13.0.0/19` sat outside every allocated block). STILL TO DO: write the
+   carve into NetBox -- production write is operator-gated; the plan is to import into the Office1
+   sandbox NetBox first, verify, then feed back.
+1c. **(superseded note kept for context)** the original unblessed-allocation finding: Chosen deliberately (DC1=10.12.x, DC2=10.13.0.0/19,
    tenant pool=10.20.0.0/16 per D-016 -- the obvious `10.20.x` would have COLLIDED with tenant space),
    but NetBox has not assigned it. Register it once NetBox exists. Known chicken-and-egg: NetBox is
    one of the VMs this headend composes.