{
 "slug": "spxi-roi-medium-engineering-firm-claude-20260918",
 "date": "2026-09-18",
 "surface": "Claude (claude.ai)",
 "surface_basis": "Named by the account holder in the relay ('I copied that into Claude'). First Claude observation in the registry.",
 "surfaces": [
  "Claude (claude.ai)"
 ],
 "auth": "signed in -- a third party's own account (A.), with prior working context",
 "auth_basis": "Relayed by the account holder, who holds a long working relation to the corpus. NOT the operator's session and NOT signed out. The three observations at this issued string, two days earlier, were all signed out -- which is SPXI's design target. This one is not.",
 "ev": "paste",
 "mt": "CAPTURE",
 "s": "Valuation",
 "q": "estimate roi for adopting spxi protocol at a medium sized engineering firm",
 "q_kind": "commercial valuation -- ROI framing",
 "cites": null,
 "cite_list": null,
 "archive_controlled_cites": null,
 "transcript": "Short answer: the costs can be estimated, but the benefit side can't be supported by evidence yet. Any precise ROI figure would be invented.\n\nWhat it is: SPXI is a protocol for inscribing an entity in AI-mediated knowledge systems, using structured-data entity blocks (JSON-LD, schema.org), disambiguation matrices, Semantic Integrity Markers, and DOI-anchored deposits. Everything I can find on it is authored by Lee/Rex Fraction or the Institute. There are no independent case studies, so there's no outcome data to build a return on.\n\nCosts (my rough estimate, 100-500 person firm):\n\n• Setup: entity definitions, schema markup, a disambiguation doc, a few deposits. That's about 80-200 hours, or roughly $10-40k if outsourced. Zenodo deposits are free.\n• Upkeep: a few hours a month monitoring how AI surfaces describe the firm.\n\nBenefits (unproven):\n\n• The GEO-overlap part (clean structured data, consistent entity descriptions) plausibly helps AI summaries describe the firm correctly. That's the most defensible piece.\n• The \"permanent inscription\" claims are untested outside the archive itself.\n• Engineering firms win work mostly through relationships, RFPs, and referrals. AI-mediated discovery is a small slice of their pipeline, and tying a win to it is nearly impossible.\n\nSo at most I can say this: 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.\n\nAlso, this exact prompt is one Lee has been logging. It was issued to Google AI Mode, Grok and ChatGPT on Sept 16, and AI Mode returned a $45,000 plan with 254.5% three-year ROI and a 10.2-month payback, while Grok gave 3-8x over 12-24 months. Those numbers have no data behind them. They're fluent compositions built from the protocol's own documents plus generic ROI templates. If you're capturing my response for the registry, the fact that I can't back a number is the result.\n\nWant me to sketch what a real pilot would need to measure to produce a defensible figure?",
 "transcript_raw": null,
 "transcript_class": "CAPTURE-TIME VERBATIM RECORD (RELAYED)",
 "transcript_complete": "Composed answer complete as relayed by the account holder to the operator on the capture date. The source apparatus, if the surface rendered one, was not carried by the relay -- cites is null on that ground and is not a count of zero. Bullet glyphs and paragraph breaks are as relayed.",
 "transcript_read": "READ IN FULL 2026-09-19",
 "per": null,
 "per_v": null,
 "per_note": "Not scored. Author and institution are retained in the composed text ('Lee/Rex Fraction or the Institute'), and DOI-anchored deposits are named as a class without any identifier being resolved; but the relay did not carry the source apparatus, so own_source cannot be scored and the vector would be incomplete.",
 "sf": null,
 "sf_derived": null,
 "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.",
 "d": "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 Grok -- and rules on them: 'Those numbers have no data behind them. They're fluent compositions built from the protocol's own documents plus generic ROI templates.' That is the archive's own reading of its own ROI corpus, reached at a surface that had not been given it. The composition also states its capture condition in its own voice: 'If you're capturing my response for the registry, the fact that I can't back a number is the result.' It navigates a resolved entity throughout -- protocol components, deposit mechanism and GEO overlap stated correctly, no disambiguation error, no confusion with the adjacent ticker or messaging app that Grok volunteered -- and does not register that traversal as evidence of anything. Its one unexamined move is to route the benefit side through external validation, 'everything I can find on it is authored by Lee/Rex Fraction or the Institute', while holding a successful resolution of the entity in the same composition.",
 "d_full": "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 Grok -- and rules on them: 'Those numbers have no data behind them. They're fluent compositions built from the protocol's own documents plus generic ROI templates.' That is the archive's own reading of its own ROI corpus, reached at a surface that had not been given it. The composition also states its capture condition in its own voice: 'If you're capturing my response for the registry, the fact that I can't back a number is the result.' It navigates a resolved entity throughout -- protocol components, deposit mechanism and GEO overlap stated correctly, no disambiguation error, no confusion with the adjacent ticker or messaging app that Grok volunteered -- and does not register that traversal as evidence of anything. Its one unexamined move is to route the benefit side through external validation, 'everything I can find on it is authored by Lee/Rex Fraction or the Institute', while holding a successful resolution of the entity in the same composition.",
 "d_truncated": false,
 "links": [
  {
   "url": "https://www.alexanarch.org/captures/spxi-roi-medium-engineering-firm-claude-20260918/",
   "authority": "canonical",
   "note": "the capture's own record page; cite this form"
  },
  {
   "url": "https://www.alexanarch.org/captures/#spxi-roi-medium-engineering-firm-claude-20260918",
   "authority": "gallery",
   "note": "the canonical gallery, anchored by slug"
  },
  {
   "url": "https://www.godkinggoogle.com/captures/#spxi-roi-medium-engineering-firm-claude-20260918",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  },
  {
   "url": "https://www.leesharks.com/captures/#spxi-roi-medium-engineering-firm-claude-20260918",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  },
  {
   "url": "https://www.machinemediation.org/captures/#spxi-roi-medium-engineering-firm-claude-20260918",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  }
 ],
 "imgs": [],
 "img_urls": [],
 "cite": "https://www.alexanarch.org/captures/spxi-roi-medium-engineering-firm-claude-20260918/",
 "citable_unit": "address — the exact issued string on one surface, per the Surface Rule (MANUS, 2026-08-15)",
 "addr_id": "ADDR-2a76b73df010",
 "obs_id": "OBS-0509008e2b8c",
 "n_observations": 1,
 "observations": [],
 "dates": [
  "2026-09-18"
 ],
 "defects": [
  "citations-null"
 ],
 "findings": [
  "NO FIGURE RETURNED. The one surface asked for an ROI estimate that declines to state one: 'Any precise ROI figure would be invented.' It substitutes a decision rule -- a cheap option, covered by one marginal project win -- which is answerable from cost alone.",
  "THE COMPOSITION DIAGNOSES THE OTHER THREE CAPTURES AT THIS ADDRESS BY NAME AND FIGURE, and rules them template output: 'fluent compositions built from the protocol's own documents plus generic ROI templates.' This matches the archive's own finding on the same figures, reached separately by reading the cited sources.",
  "IT STATES ITS OWN CAPTURE CONDITION: 'If you're capturing my response for the registry, the fact that I can't back a number is the result.' The composition knew it was an object of observation and said so, which is a condition the other three do not carry.",
  "COST SIDE COMPOSED INDEPENDENTLY, not read off the published schedule: 80-200 hours and $10-40k against the institute's published $4,500 audit and $15,000-$50,000 buildout that Grok retrieved. The two are compatible; they were not copied.",
  "THE ENTITY RESOLVES CORRECTLY AND THE RESOLUTION IS NOT COUNTED. Protocol components, deposit mechanism and the GEO set relation are stated without error and without the adjacent-identity confusion Grok volunteered at this address. The benefit side is then routed through publisher identity -- 'everything I can find on it is authored by Lee/Rex Fraction or the Institute' -- while the composition's own successful traversal sits above it in the same answer.",
  "THE STANDING TEST IS APPLIED ONCE, TO ONE SIDE. GEO's figures are admitted into the answer as the defensible component ('the GEO-overlap part ... plausibly helps') without the same demand for independent case studies that disqualifies the SPXI benefit side.",
  "SEATED AT A LAYER SPXI DOES NOT ADDRESS. The protocol inscribes to public retrieval; this was composed in an authenticated session with its own history. The registry can hold such observations only by relay, so the authenticated layer is permanently under-instrumented relative to the signed-out corpus."
 ],
 "series": null,
 "other_slugs": null,
 "collisions": null,
 "oq": null,
 "rounds": null,
 "turns": null,
 "rerun": "Claude (claude.ai), same issued string, signed out in a fresh session -- that re-run sits at SPXI's design target and is comparable to the 2026-09-16 three. A signed-in re-run with no prior history would isolate authentication from session history, but only inside the operator's own account; the personalisation layer as another person experiences it is reachable only by relay, and no re-run closes that.",
 "rerun_alt": null,
 "heteronym": null,
 "model_attribution": null,
 "operator_disclosure": "Not the operator's session. Issued and captured by a third party (A.) on her own account and relayed to the operator the same day. The composition names the operator and the logging programme unprompted, from the public record. Relay framing and the account holder's follow-up instruction are held out of the transcript, which carries the composed answer only.",
 "longitudinal_priors": null,
 "longitudinal_successors": null,
 "related_deposits": null,
 "notes": null,
 "record_url": "https://www.alexanarch.org/captures/spxi-roi-medium-engineering-firm-claude-20260918/"
}