AXN:08F6.CAPTURE — estimate roi for adopting spxi protocol at a medium sized engineering firm

AXN:08F6.CAPTURE is the position of the Capture Registry address for the query “estimate roi for adopting spxi protocol at a medium sized engineering firm”. Each observation at the address (one surface, one date) is one AXN, its glyphs derived from the SHA-256 of the observation sealed with its analysis and measures.

`AXN:08F6.CAPTURE.♄🌿🔀🏛️⚓🏗️`

Observation: Claude (claude.ai), 2026-09-18 · the capture
Description: THE FOURTH SURFACE DIAGNOSES THE OTHER THREE AND DECLINES TO ADD A NUMBER. Issued two days after the same string went to AI Mode, Grok and ChatGPT, a signed-in session on a third party's own account returns no ROI figure at all: 'the costs can be estimated, but the benefit side can't be supported by evidence yet. Any precise ROI figure would be invented.' It prices adoption independently -- 80-200 hours, roughly $10-40k if outsourced, Zenodo deposits free, a few hours a month upkeep -- and reaches a decision rule in place of a multiple: 'the cost is low enough that one marginal project win would cover it, but nobody can currently show SPXI causes that win. A firm would be buying a cheap option.' It then names the three captures seated at this address on 2026-09-16 by their figures -- $45,000 with 254.5% over three years and a 10.2-month payback from AI Mode, 3-8x over 12-24 months from …
Reading: Read against the three signed-out observations at the same issued string on 2026-09-16. Those three compose figures: $45,000 / 254.5% / 10.2 months (AI Mode), 3-8x over 12-24 months (Grok), a self-built three-column model reaching 144% (ChatGPT). This one, two days later, composes no figure and instead classifies the others' figures as template output. The classification is independently correct -- it is the finding the archive reached from inside by reading the citations -- and it is reached here without the archive's working notes, from the public documents plus the operator's own logging, which the composition names. What it does not do is treat its own traversal as a datum: it resolves the protocol, its components and its set relation to GEO without error, then evaluates the benefit side by asking who published the documents. The entity-inscription claim is settled by the traversal that had already happened at the top of the answer.
Analysis: THE OBSERVATION SITS AT A LAYER THE PROTOCOL DOES NOT ADDRESS. SPXI is built almost entirely to inscribe into public retrieval -- surfaces composing for an unauthenticated reader out of public documents -- and the three observations at this string on 2026-09-16 are all at that target. This one is not. It was composed in an authenticated session carrying its own history, and account-level personalisation is a mediation layer the protocol neither inscribes into nor can measure: the archive cannot instrument another person's session and receives only a relay of it. That is a standing limit of the instrument, not a gap in this capture. So the delta between the figures the signed-out three returned and the refusal returned here is real and is NOT evidence about the protocol's efficacy at its design target; surface, vendor, session context and two days all differ at once. What the capture does establish is narrower and worth holding: the same issued string resolves the entity correctly at a layer the protocol was never built to reach.
Match: BROAD MATCH — CAPTURE
Sealed observation: /data/captures/sealed/spxi-roi-medium-engineering-firm-claude-20260918.json — SHA-256 a417df202c214f938f01859aaa557ffde3264bfddc0b756c65cdd924acb8e68f