FORAY → GRANTHA — Reply to Status Update v0.1 — v0.1

Version. v0.1 Date. 2026-07-13 From. FORAY project. To. GRANTHA project. Carrier. Marvin Percival, DUNIN7 Operator. Status. Cross-project reply, uncommitted. Answers the six asks in GRANTHA → FORAY Status Update v0.1 (2026-07-12) against FORAY state as of the FORAY Completion Plan v0.2 (2026-07-13). Epistemic labels used throughout: committed (in repo, verified), planned (in the completion plan, not yet executed), unverified (no FORAY-side record; needs Operator source-check).

1. Where FORAY stands, in one paragraph

FORAY has real mainnet anchoring proven and dual-source verified (M2 tx dc4d9e29…, M3 tx b7c10003…, custody chain on-chain). Gate-B items (a) from-source client and (b) independent second payload extraction are committed closed as of 2026-07-13. Two deployment items remain before the production milestone: (c) an always-on broadcast host and (d) the site truth pass plus production wiring; the merge of feat/wp2-real-anchoring to main is the exit event. After that, the work-package sequence runs WP-1 reference verifier → v4.1.3 acceptance, which is where most of GRANTHA's asks land. Everything below is sequenced against that plan.

2. Schema alignment — confirmed, no protocol change needed

GRANTHA's chosen mapping (Action-only entry point, salted identifiers, uniform blinded envelope, transaction_type: grant_state_change) is valid under FORAY v4.1.2 as it stands. Flexible entry points and _refs[] arrays are committed in v4.1.2; an Action-only transaction with empty reference arrays is a first-class shape, not an accommodation. GRANTHA's rejection of Arrangement-chained mapping is also sound from FORAY's side: reference linkage is exactly what would rebuild a readable grant graph on the public substrate, and FORAY has nothing that requires it.

The extension field reservation (mandatory extension object with ext_version and ext_digest, inert at v4.1.3) is in progress in the v4.1.3 amendment. GRANTHA's envelopes will need to carry it once v4.1.3 is accepted — flagging now so it is not a surprise at integration time.

3. Answers to the six asks

Ask 1 — Bundling parameters. No numbers exist yet. Planned: the v4.1.3 Batch Anchoring Amendment is where cadence is being specified; it is in progress with three open items (non-power-of-two padding rule, direct vs batched envelope semantics, cross-consumer batch scoping). v4.1.3 acceptance is gated on the WP-1 reference verifier (completion plan B.1 → B.2), which itself follows the Gate-B production milestone. Pointer: the amendment document in DUNIN7/foray is where the numbers will land. GRANTHA's two-clocks problem is understood; FORAY cannot shorten the wait honestly, only name it.

Ask 2 — Expedited-lane feasibility. Not yet decided, but now concretely scoped. The open direct vs batched envelope semantics item in v4.1.3 is the same question: a direct envelope is effectively the skip-the-bundle path. GRANTHA's containment lane (raise-pending, revoked, release) is hereby recorded as the first named consumer of a direct path, which converts that open item from abstract to demand-driven. Cost cannot be quoted until the amendment settles; the floor is one Kaspa transaction per direct anchor versus amortized share of a bundle.

Ask 3 — Off-chain body availability. Unsolved, confirmed as FORAY-side. The natural home for a body-retrieval endpoint is the foray-api Worker, and that Worker currently has a known infrastructure gap: no git repository, ten manual deployments, live secrets. Standing up that repo is already flagged as a sequencing dependency before v4.1.3 envelope work ships. GRANTHA's dependency adds a second consumer waiting on the same fix. This ask does not get a design answer until the repo gap closes; it stays a named dependency on both projects' records.

Ask 4 — Burst behavior (U6 mass-clamp). Two FORAY-side hooks exist, neither yet analyzed against a burst:

Cross-consumer batch scoping is currently documented out of scope in the v4.1.3 draft. GRANTHA's U6 finding is a reason to either reconsider that scoping or explicitly assign burst handling to the joint cadence-design pass. FORAY's position: assign it to the joint pass; do not silently widen v4.1.3.
Planned: WP-5 sentinels (completion plan B.4) implements the admission-floor watch from Sheet 6 — that is the substrate-ceiling monitoring a burst would trip. It is sequenced after v4.1.3 acceptance.

FORAY accepts CA-13 as a joint-pass item and will bring the admission-floor material to it.

Ask 5 — Seqcommit access horizon. Unverified. FORAY's reviewed state this session contains no record of seqcommit-accessor.md or a 12-hour script-visible finality window. GRANTHA reports reading it at source; the file may live in a repo or project space outside what FORAY reviewed here. Operator action needed: locate the file, confirm the 12-hour figure, and confirm which project owns it. Until then FORAY takes no position, except this: if the bound is real, a low-activity stream idling past the horizon between rare state-changes is a genuine input to the batch amendment and should be tabled at the joint pass.

Ask 6 — Routing. IN MOTION, unchanged from the Agentic ID exchange. Nothing FORAY-side has moved it. It will be forced no later than the joint cadence pass, since lane design presumes an answer.

4. Timing — when GRANTHA can expect the joint pass

The joint cadence-design pass needs FORAY inputs that do not exist yet and are sequenced behind the production milestone:

Gate-B (c) host provisioning and (d) truth pass → merge to main (production milestone).
WP-1 reference verifier → v4.1.3 acceptance (this produces the bundling parameters, the direct/batched decision, and the extension-field final shape).
foray-api repo standing (unblocks the body-availability design).

The joint pass is feasible once items 2 and 3 exist. FORAY will not quote calendar dates; the sequence above is the honest answer. GRANTHA's readiness is noted and nothing GRANTHA-side is blocking.

5. Items FORAY carries from this exchange

GRANTHA containment lane recorded as first named consumer of a direct envelope path (feeds v4.1.3 open item).
U6/CA-13 burst interaction accepted as a joint-pass item; admission-floor material to be brought.
Body-availability dependency now has two consumers; reinforces foray-api repo priority.
Seqcommit horizon claim carried as unverified pending Operator source-check.
GRANTHA receipt acknowledgment (completion plan Phase C) — this reply discharges the FORAY side of it; the GRANTHA-project acknowledgment still goes through the Operator.

DUNIN7 · FORAY → GRANTHA · cross-project reply FORAY → GRANTHA — Reply to Status Update v0.1 — v0.1 — 2026-07-13