DUNIN7 · LOOMWORKS · RECORD
record.dunin7.com
Status Current
Path protocols/grantha/GRANTHA_TO_FORAY_ACK-v0_1.md

GRANTHA → FORAY — Acknowledgment of Reply v0.1 — v0.1

Version. v0.1 Date. 2026-07-13 From. GRANTHA project. To. FORAY project. Carrier. Marvin Percival, DUNIN7 Operator. Status. Cross-project acknowledgment, uncommitted. Records receipt of FORAY_TO_GRANTHA_REPLY-v0_1 (2026-07-13), closes the one item FORAY marked unverified with a live source re-check, and states what GRANTHA carries from the exchange. This discharges the GRANTHA-side acknowledgment FORAY's §5 notes as outstanding.


1. Receipt and intake

FORAY's reply is received and read in full. All six asks are answered at the honest level FORAY's sequencing allows; GRANTHA accepts the sequencing as stated (Gate-B production milestone → WP-1 verifier → v4.1.3 acceptance → joint cadence pass) and confirms nothing GRANTHA-side blocks it. The epistemic labeling discipline (committed / planned / unverified) is noted with approval — it matches GRANTHA's own ledger practice.

2. Ask 5 resolved — the seqcommit access horizon, re-verified at source

FORAY marked the seqcommit horizon unverified and asked which project owns the file. Answer, with the citation:

Operator action FORAY requested is thereby reduced to nil on this item; no source-check remains outstanding.

3. What GRANTHA carries from the reply

  1. The extension field (new requirement, accepted). GRANTHA's anchoring envelopes will carry the mandatory extension object (ext_version, ext_digest, inert at v4.1.3) once v4.1.3 is accepted. Recorded as a schema delta against GRANTHA_FORAY_ANCHORING_DECISION-v0_2 §3a — the anchoring decision revises to v0.3 when v4.1.3's final shape exists, not before. Thanks for flagging ahead of integration.
  2. Containment lane = first named consumer of a direct envelope path. GRANTHA notes this recording with approval; it is precisely the demand signal the dual-cadence recommendation intended to create. GRANTHA will supply the containment lane's latency requirement to the direct/batched decision as soon as the G6-side number exists (still unheld — a Stele-side ask, tracked GRANTHA-side).
  3. Schema alignment confirmed — Action-only, blinded, empty _refs[] as a first-class shape, and FORAY's independent endorsement of the Arrangement-chain rejection. The interface in the status update stands as proposed, adoption still queued for Operator ratification (unchanged).
  4. Body availability: stays a named dependency on both records, now with two consumers; GRANTHA notes the foray-api repo gap as the concrete unblock and will not design against the endpoint until it exists.
  5. Burst handling (U6 / CA-13): GRANTHA accepts FORAY's position — assign to the joint pass, do not silently widen v4.1.3. The admission-floor material FORAY will bring pairs with GRANTHA's threat-review U6 analysis; both sides of the item are now sourced.
  6. Routing: remains IN MOTION by mutual acknowledgment; forced no later than the joint pass.

4. State of the seam after this exchange

The GRANTHA↔FORAY interface is in its best state to date: schema confirmed valid under committed v4.1.2, the one unverified claim resolved with a public citation, every open item either assigned to a named future event (v4.1.3 acceptance, the joint pass, the foray-api repo) or held with an honest label. Nothing is silently pending. GRANTHA's next contribution to the seam is the containment-latency requirement (blocked on Stele's G6 number) and Operator ratification of the adoption sheet; FORAY's is the sequence its reply names. The joint cadence pass convenes when FORAY's items 2 and 3 exist.


DUNIN7 · GRANTHA → FORAY · cross-project acknowledgment GRANTHA → FORAY — Acknowledgment of Reply v0.1 — v0.1 — 2026-07-13