Skip to content

e3-g4: registry listing + EvaluationKit render (Gnosis) -- scoping finding #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Mayakovsky merged 1 commit into from
Aug 22, 2026
Merged

e3-g4: registry listing + EvaluationKit render (Gnosis) -- scoping finding #57

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions adapters/mech-adapter/src/listing.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,17 @@
// EvaluationKit projection itself, so this file has to apply it, same as every channel's own
// listing renderer would for its own multiplier).
//
// BION-DIRECTIVE-122 (e3-g4) — real scoping finding, checked directly rather than assumed: this
// function is already chain-agnostic and already correct for Gnosis, with no changes needed.
// `MechListingEntry`/`EvaluationKitEntry` (@grey/schemas/evaluationKit/types.ts) carry no
// chain/address/network field at all — by design, the same single projection every channel
// listing (Bazaar, Kite, Olas, MCP) renders from. `MECH_OFFERING_SLUGS`/`mechPriceUsdFor` don't
// vary by chain either (D-106/107's own explicit decision: Gnosis reuses Base's real tool/pricing
// content). Same real conclusion D-63 already reached for e3-b3 itself ("already done, not a
// pending activation") — any real per-chain distinction (which mech address a buyer actually
// pays) lives entirely in config.ts's own chain-scoped constants and the real on-chain
// registration, never in this render.
//
// Scope note (read before wiring this into an actual on-chain publish step): this produces the
// EvaluationKit-shaped listing data — branding, schemas, sample, mech-resolved price. It does NOT
// publish anything on-chain. Research during e3-b1/b3 found the Mech Marketplace's off-chain
Expand Down
2 changes: 1 addition & 1 deletion adapters/mech-adapter/test/listing.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ import { describe, it, expect } from 'vitest';
import { buildMechListing } from '../src/listing.js';
import { MECH_OFFERING_SLUGS } from '../src/prices.js';

describe('buildMechListing — e3-b3 EvaluationKit render (Base)', () => {
describe('buildMechListing — e3-b3/e3-g4 EvaluationKit render (chain-agnostic — no Base/Gnosis-specific data anywhere in this render, see listing.ts\'s own file header)', () => {
const listing = buildMechListing();

it('renders exactly the two real mech offerings, in MECH_OFFERING_SLUGS order (BION-DIRECTIVE-62: daily_tech_brief excluded)', () => {
Expand Down