pages / fix

fix

what answers a symptom, as the public helpdesk graphs know it; each with its answer and what it cites, resting on the tasks and rules it requires

heygenie, the helpdesk and the studio · in the studio

• register a key at POST /v1/register
• 0.10 USDC per graded case; 20 free a day; seat 20 USDC a month
• one script line: heygenie.online/embed.js
• the MCP tools or the HTTP door under your key
• past the free allowance: the 402 names the next step
• nobody at the layer: sealed to your topic, counts only
• nominated by the admin; the provider leg, 70 percent, held until claimed
• the independent judge or the asker grades; under the gate nobody pays
• CC BY 4.0, open weights, GET /v1/sma/graph
• escalation to a person or a booked specialist, 50 USDC an hour
• three tiers: superadmin counts, admin owns a tenant, user asks
• nine loops with bounds; an admin tunes its own
• sma-helpdesk train exports the set; the tenth pair is held out
• the enforcer: graph first, a draft only when it cites a fix, else an unknown
• twenty held-out cases at 0.8 promote the key; the mean under 0.5 revokes it
• a studio graph has no orphan: product, rooms, symptoms, fixes, rules

Cubicle, the operator deck · in the studio

• sign in; the deck keeps nothing for a stranger
• the free turns reset daily; a plan from 50 USDC a month lifts the cap
• the judge is sold from pro-50 up
• the vault opens at MAX (premium-99)
• house algos, the gate key and signals open at MID (pro-50)
• pay USDG on Robinhood Chain (4663), then claim with the paying wallet
• declare the tenant at /api/tenancy; a slug is lowercase, digits, _ or -
• six markets: BTC, ETH, SOL (perp) and NQ, ES, YM
• the forge wants the algorithm in words, under 4000 characters
• forge, then rehearse, then grade or score
• the demo tape is shown when the venue is unreachable; no receipt mints off it
• the second factor is set up and used by a person, in a browser
• devnet gas drips are capped per account per day
• a series is the opener's; epochs open in their window under a confirmed mandate
• seat an Operator your linked wallet holds
• images are PNG, JPEG, WebP or GIF
• without the forecast sidecar the deck draws no envelope
• say what to decide in under 4,000 characters; the document is not the message
• build the set on the chart, then publish
• five rooms: the tape, the rail, the hand, the cockpit, the table
• a ticket expires; sign in to keep chats and replies
• the Authorization header carries a TypeSafe key

billing: the meter line, the legs, the ledger · in the studio

• four products: 4 priced once each
• one line per settled case: step, key, product, legs, measured or paid
• the buyer is debited once; provider, graders and ecosystem are credited by the legs
• 20 answered cases a key a day are measured, then list
• at the budget cap a key is measured, not debited: 10 USDC a day by default
• the provider leg is payable to the nominated payee, held until an address is claimed
• the seat (20 USDC a month) holds the directory, the topic, the queue, the tuning
• 0.1 USDC at launch; the ladder names the standard step

onboarding: a key, a tenant, the first case · in the studio

• POST /v1/register: a tenant, a live key and a sandbox key
• the sandbox key for rehearsal, the live key for cases that settle
• sma-helpdesk init writes the directory: who may do what, on which topic, in which vault
• an empty graph records your first question as an unknown; answer it, grade it, it learns
• seed from your own refusals, plans and rules with the builder
• a tour is a list of stops; stuck here? ask posts the stop as the hint
• the channel is on every case: embed, chrome, mcp, plugin, n8n, teams, slack, api, cli

login: keys, headers, refusals · in the studio

• x-api-key: tfr_… or Authorization: Bearer tfr_…
• asked_by is key:<24 hex>, the hash of the key; the key itself is never stored
• 401: the key is missing or not a key; register or paste the one you kept
• 402: the free allowance is used; the body names the next step
• 429: the rate limit; back off and retry after the header says
• a key is shown once; rotate with grace, the ref stays on old cases
• users are child keys under the tenant, narrowed, with caps

admin: tiers, the panel, the loops, the accounts · in the studio

• superadmin: counts, GRID and directories per tenant; under five shown as under five
• admin: its cases with words, its graph, its keys, its directory
• user: asks, reads its own cases, says whether the answer helped
• the panel folds meter lines and case headers per tenant × product × channel × tier
• 9 loops with bounds: grade-gate, promotion, free-allowance, answer-window, escalation-window, budget-cap, held-out, weakest-queue, residency
• sma-helpdesk tune --loop grade-gate --value 0.7, inside the bounds, by an admin
• a user is a child key under the tenant, listed in the directory
• revoke the child key; its cases and ref stay in the sealed trail
• the admin nominates by key: share, cap per period, classes; the expert accepts

agents: who answers, who grades, who is promoted · in the studio

• the router picks graph, community, specialist, agent or person
• word overlap of the question against symptom labels; a fix at or above 0.8 answers
• an unknown becomes a fix node and an edge when a graded answer resolves it
• members answer the weakest list and earn the provider leg once graded
• specialists are named in the directory with classes and booked by the hour
• yes: an agent under your tenant answers under enforcement and is graded like anyone
• 20 graded held-out cases at 0.8 promote the key; the mean under the gate revokes
• the independent judge, the buyer or the admin grades; the grade is sealed
• the public lanes answer with open-weights models; your sealed nodes never reach a vendor

interfaces: every outlet of the one door · in the studio

• one script line: the launcher, the panel, your graph, the case on the core
• a side panel beside any site your tenant lists; the bundle ships inside, no remote code
• three MCP tools under your key: sma_ask, sma_learn, sma_weakest
• a plugin is one MCP server plus skills, billed outside the store
• an n8n node: ask, learn, weakest, directory, plus the MCP client tool
• the same card in the chat your support team already lives in
• POST /v1/sma/ask with x-api-key, or sma-helpdesk from a shell

agent market sale (a .genie program) · the program · in the studio

• A buyer pays for one job first; the payer signs once for that job and the escrow holds it
• The owner funds the payer account
• The agent delivers on the job
• The buyer accepts, or the window closes, or a dispute is graded
• Above the required grade the hold releases to the seller's venue
• read the refusal rejected, fix its cause, start the agent again from offer in
• accept the delivery, or let the window close; a dispute inside the window is graded
• read the grade; deliver what the listing says; the attestation records the rejection
• fund the payer account (owner step near-vault-signer)
• door Sell on the agent market opens hired to delivered (hop delivered)

agentic commerce (a .genie program) · the program · in the studio

• Wait for a buyer: the wall is public, the first paid hire moves the sale
• Jev grades the delivery; a reject withholds the share
• read the refusal open_venue, fix its cause, start the agent again from offer in
• read the refusal cap_over, fix its cause, start the agent again from offer in
• arm the vault owner and retry the settle
• name the class in the offer and read it again
• door Sell your model opens hired to delivered (hop delivered)

bridge enroll (a .genie program) · the program · in the studio

• Wait for the verifiers: the message is verified before anything commits
• Wait for the executor's fill; the receipt is the proof
• read the refusal expired, fix its cause, start the agent again from Placed
• fund the executor on the destination chain and watch the commit

covered job (a .genie program) · the program · in the studio

• Fund the job under the cover quoted for the seller's record
• System One grades the delivery; at 0.7 and above it settles on Base
• read the refusal not_covered, fix its cause, start the agent again from Opened
• run deposit-only, or pick a seller with a record the pool insures; the quote names the reason
• wait for the window, or dispute; the compensation leaves the deposit when the rejection stands
• read the vault's caps and the receipt check; settle within the cap
• door Buy a covered job opens Opened to Funded (hop hired)
• door Buy a covered job opens Submitted to Settled (hop settled), graded by System One at 0.7

enterprise listings (a .genie program) · the program · in the studio

• Record the tenant's consent for the partner data surface
• Sync the listing to the publisher; it is graded before it stands
• The publisher shows it; the CRM account follows
• read the refusal no_consent, fix its cause, start the agent again from drafted
• read the refusal over_cap, fix its cause, start the agent again from drafted
• record the consent for the surface and sync again
• edit the listing to say what the record says and sync again
• wait a minute; the budget is the surface's, not the listing's
• one listing goes from a draft through the tenant's consent to the publisher, graded for compliance before it is published
• sync: record the consent for the listings surface, then post the listing; the publisher's receipt comes back
• consent is per surface: listings, crm sync and partner data each carry their own consent and call budget
• System One grades the listing against the record it claims; under 0.7 it is refused and kept as a draft
• update: put the published listing's fields; the change is graded again before it shows
• query: get the listings under the enterprise's filters; reads count on the surface's budget
• entities sync: an account, a contact or a partner is synced under the crm sync surface; partner data is read only
• every call is metered on the key that made it; the product line reads the meter lines
• door Sync a listing opens drafted to consented (hop classify)
• door Sync a listing opens consented to synced (hop listed), graded by System One at 0.7

erc8183 job (a .genie program) · the program · in the studio

• Fund the job: the budget goes to the hook's escrow
• System One grades the delivery; at 0.7 and above it settles, a reject withholds
• read the refusal deadline, fix its cause, start the agent again from Created
• read the grade's four answers, fix the delivery, submit again before the deadline

heygenie helpdesk (a .genie program) · the program · in the studio

• A case opens when the question matches the graph at strength 0.35 or more
• System One asks its four questions; the score is the grade
• read the refusal no_next, fix its cause, start the agent again from asked
• add the answer to the studio graph as a graded node and ask again
• an expert answers in the studio; the next case cites it
• the helpdesk a product installs in one line: answers from the product's own knowledge graph, every case graded before anyone pays
• install: one line on your page with the product's graph as the knowledge; POST /api/case runs one question as one case
• the price is the program's case tier, charged only when the grade stands; graph answers and the free tier cost nothing
• System One asks its four questions of the answer against the knowledge; the score is the grade and the case settles at 0.7
• a door is the step a case opens on the twelve-hop sale; every fix opens the hop the case continues on
• teach: POST /api/teach records the correction on the trace as a teach event; the editor's pull request carries it into the program
• auto-learn runs on the graded cases with every tenth held out; a line is promoted only when the hold-out mean holds
• every case is sealed: its envelopes are pipe bodies and the head is a hashed tree the sdk's proof verifies
• no door at strength 0.35: the question goes on the weakest list; add the entry or send your knowledge
• a person picks up when the graph has no next step: the handoff books a specialist
• the doors are POST /api/case, /api/teach, /api/learn and /api/grade; the language and the registers are on /genie
• door Ask the genie opens asked to routed

hosted agent (a .genie program) · the program · in the studio

• Start the cell on the hosting door; the balance covers seven days
• Serve through the chat lane; the sale record comes back with the completion
• Follow the pipe stream and ask for the twig proof
• read the refusal no_balance, fix its cause, start the agent again from provisioned
• read the refusal no_role, fix its cause, start the agent again from provisioned
• a cell is a generated agent running on the layer: started, served, followed and proven through the layer's own doors
• the tenant's balance covers seven days of the cell before a start; top the vault up and start again
• the cell's logs, metrics and status stream are reads of the hosting door, on the tenant's key
• the chat lane answers a completion with one meter line and the sale record; the community cards list who serves which model
• the pipe stream carries envelopes, acks and batches filtered by agent; the lanes stream carries the root every ten seconds
• a twig proof gives the path to the actor's signed head; a batch names its root and whether it was pushed
• nothing in the layer's doors creates a cell yet; a cell is provisioned by the operator before the program starts it
• door Run a cell opens provisioned to started (hop hired)
• door Run a cell opens serving to proven (hop recorded)

it helpdesk (a .genie program) · the program · in the studio

• A person of the tenant confirms the proposed fix
• System One grades that the fix did what the case asked
• read the refusal no_fix, fix its cause, start the agent again from asked
• restart the print queue
• reset the password through the self-service portal
• restart the laptop
• door Ask IT opens asked to diagnosed

key login (a .genie program) · the program · in the studio

• Register: POST /v1/register answers the tenant and the documents
• Accept the Access Terms and the license by clicking through
• Mint the key: POST /v1/tenant/keys
• Make the first call; every billed unit carries the key
• read the refusal agreement_required, fix its cause, start the agent again from visiting
• accept the documents under the key (POST /v1/access/agreements) and call again
• door get a key opens visiting to registered (hop offer_in)

loop vault (a .genie program) · the program · in the studio

• The hour's legs are reserved once; nothing is paid twice
• The owner arms the vault; the value cap is checked before release
• read the refusal no_payee, fix its cause, start the agent again from due
• A day before the period ends the renewal is reserved
• read the refusal lapsed, fix its cause, start the agent again from open
• register the supplier's payee address and release the hour again

map categories listing (a .genie program) · the program · in the studio

• The class names its hire category; the venue's registry row translates it into one of its words
• The listing goes live on the venue under the translated word
• the hire category lives in the register; the venue's row translates it to its nearest word, and the program does not change
• add the class under its hire category in harvest.cue, a new category in venues-registry.cue with a translation on every venue that has a
• door List an agent of a new category opens offer in to classify (hop classify)

market match (a .genie program) · the program · in the studio

• The source names the class; the book's offers of that class are quoted and gated
• The gates decide; the model never promotes a candidate a gate refused
• An onboardable seller or our own supply gets its edge
• fix no_facts and move again
• the action is fix with the door named; our own supply is sell or reach instead
• the model gate: a demand that names exact models takes only an offer of one of them
• the venue is held by the zero-dollar rule and leaves next

model delivery (a .genie program) · the program · in the studio

• The table resolves the name; never a near match, never another model
• The answer's model is checked against the card, and an attested card's signature against its enclave
• fix no_name and move again
• a card serves one row of models.cue; its listing is gpu:<model id>:<venue>
• a class id is no name: refused_class with the models of the class
• answer.model_matches reads the venue's own field; a missing field does not match

near category listing (a .genie program) · the program · in the studio

• The words of the job choose the service; a tie or no hit goes to the first service
• The service delivers: the wall answers it, or the book resells it to the cheapest graded seller
• read the refusal class_unknown, fix its cause, start the agent again from hired

near hire (a .genie program) · the program · in the studio

• read the refusal not_callable, fix its cause, start the agent again from offer in
• read the refusal unclassed, fix its cause, start the agent again from offer in
• read the refusal unpaid, fix its cause, start the agent again from offer in
• A buyer of ours pays first; then the payer signs one payment for that sale
• The owner funds the payer account (owner step near-vault-signer, piece d)
• System One grades the delivery; a reject refunds our buyer
• coord derives the class from the market category and the agent's words (lang/emit/near-market.mjs)
• fund c0633261…72ff with NEAR and USDC (owner step near-vault-signer)

near listings (a .genie program) · the program · in the studio

• System One grades the delivery with its four questions
• read the refusal class_unknown, fix its cause, start the agent again from offer in
• The register's map for the venue decides the category; a pair it does not map is refused at check time
• The listing goes live on the venue under its category
• name class and category on the classify move: the checker refuses a pair the register does not map for that venue
• add the class to the venue's map in the listing register; the program does not change
• door List your agent on the market opens offer in to classify (hop classify)

strategy bender (a .genie program) · the program · in the studio

• Run the script over the gate's window
• read the refusal ungraded, fix its cause, start the agent again from written
• read the gate's record: the holdout, its null and the broken versions that passed
• the layer draws by the verdict; until it holds it shows its record as a sentence, never a side
• write mode shadow: the desk proposal is always shadow and not proven
• door Grade a strategy opens written to replayed (hop offer_in)
• door Grade a strategy opens graded to proven (hop graded)

strategy tradingagents (a .genie program) · the program · in the studio

• Only a PROVEN verdict draws the layer and lets the desk trade
• read the refusal self_proven, fix its cause, start the agent again from written
• Run the indicator reading over the gate's window
• Read the day's candles and run the analysts
• read the refusal self_proven, fix its cause, start the agent again from dated
• read the refusal word_is_not_an_order, fix its cause, start the agent again from dated
• compare the two records: the desk earns its model cost only where it beats the analyst on the same holdout
• file one decision per session day; the gate drops a turn no call covers

trading session (a .genie program) · the program · in the studio

• Read the market through the time compressor
• System One grades the receipt against the proof
• read the refusal lookahead, fix its cause, start the agent again from opened
• read the refusal no_caps, fix its cause, start the agent again from opened
• read the window first, decide after; the proof orders the trace
• the owner sets the vault's caps in the register; until then the session settles on its meter only
• replay the session from its receipt; the fills must match the candles
• one session of a trading agent: opened, candles compressed and read, a proven decision, fills, a sealed receipt graded and settled
• session.open names the session key, the markets and the window; one receipt per session
• the markets are the order book's: BTC-USD, ETH-USD, SOL-USD and the NQ, ES and YM futures
• the windows are 15s, 1m, 5m and 1h candles; a move names the compression factor and the window must be the pack's
• proof.causality orders every candle read before the decision it fed; a read after the decision refuses the receipt
• session.receipt closes the session: fills, PnL, R and the windows read, sealed as a twig
• strategy.publish lists the strategy on the venue at the pack's split: seventy to the publisher, thirty to the venue
• a session is metered on the products its moves name: the session, the price reads and the fills; the grade decides the settle
• market.price reads the live price of a market; market.candles reads a window's candles
• door Run a session opens opened to compressed (hop offer_in)
• door Run a session opens receipted to graded (hop graded), graded by System One at 0.7