Skip to content

Every error code ​

Every refusal carries one of these. The set is closed, and a code is a promise this page keeps: there is no failure that arrives without a name you can look up.

Two judges say them. The schema codes come from POST /v1/registry/validate (validate_schema), from npx @jtakeit/astro schema --judge, and from an import that reads a repository's schema. The build codes come from the annotation lint inside the build container, and appear in a build log.

A code that came with contract 3 says so under it, and so does one only the older contract 2 says — a site on jtk/catalogue.json and jtk/content/, until it is moved; a new site never meets those.

The schema judge has a second voice: advice, with JTK_W_ codes. A finding there refuses nothing — the file is valid — and says what it is allowed to do and would be wiser not to. POST /v1/registry/validate returns them under advice, apart from the refusals, and only once nothing is refused. So has the build's lint: what it advises is printed in the log and the build goes on.

Reading the schema ​

What is wrong with the schema itself: jtk/schema.json, or on contract 2, the older contract, jtk/catalogue.json.

codemeans
JTK_E_CATALOGUE_UNREADABLEContract 2's schema, jtk/catalogue.json, is not JSON, or carries a key that contract has no place for. Contract 3's jtk/schema.json says this as JTK_E_SCHEMA_UNREADABLE or JTK_E_SCHEMA_KEY_UNKNOWN.
JTK_E_CONTRACT_UNKNOWNThe schema names a contract number this service does not speak.
JTK_E_CATALOGUE_EMPTYContract 2's schema, jtk/catalogue.json, declares no blocks, so it describes no site. Contract 3 says this as JTK_E_SCHEMA_EMPTY.
JTK_E_GENERATOR_INVALIDThe generator string does not name a tool.
JTK_E_NAME_INVALIDA block type, field key, view key or collection name is not spelled the way an identifier must be.
JTK_E_NAME_DUPLICATETwo things in the same place are called the same thing.
JTK_E_LABEL_MISSINGA field, view or collection has no label.
JTK_E_TEXT_INVALIDA label or hint is written both once and per language, names a language that is not one, is empty, or runs too long.
JTK_E_BLOCK_VERSIONA block type has no version, or a version below one.
JTK_E_BLOCK_EMPTYA block type declares no fields.
JTK_E_COLLECTS_UNKNOWNA block says it collects something nothing knows about.
JTK_E_KIND_UNKNOWNA field's kind is not one of the 19 — 17 on contract 2, which has neither sku nor picks.
JTK_E_BOUNDS_INVALIDA min or max is negative, or the minimum is above the maximum.
JTK_E_SELECT_NO_OPTIONSA select field offers nothing to select.
JTK_E_LIST_INVALIDA list nests lists deeper than its contract allows, declares no item fields, or of appears on a field that is not a list.
JTK_E_MEDIA_INVALIDA media field's accept, ratio or multiple do not go together — or one of the three appears on a field that is not media.
JTK_E_BESIDE_INVALIDA field's beside names no field of the same block (or row), names the field itself, or names a field that is not on the page either — or the field carrying it is on the page.
JTK_E_TITLED_BY_INVALIDA field's titled_by names no field of the same block (or row), names the field itself, or names a field that is not a line of text.
JTK_E_VIEW_INVALIDA block declares arrangements but has no gallery to arrange, sets its bounds in two places, or a view's own bounds do not make sense.
JTK_E_LOCALE_INVALIDA language is not a language, is declared twice, or the site's own language appears again among the others.
JTK_E_MODULE_UNKNOWNThe schema turns on a module this service does not have.
JTK_E_MODULE_ROLE_INVALIDA module is pointed at nothing, or at something that is not a collection of this schema.
JTK_E_MODULE_FILE_INVALIDContract 2 only, the older contract: its settings file jtk/<module>.json is not a settings document — it is not JSON, it has no blocks, its one block is not the module's own config type, or a field holds what its kind refuses.
JTK_E_COLLECTION_INVALIDA collection's place, icon, entry type or blocks list is wrong — or, on contract 2, its prefix or pagination.
JTK_E_ENTRY_TYPE_INVALIDThe block type a collection names cannot be used for entries.
JTK_E_ORDER_INVALIDA collection is ordered by a field that will not order it.
JTK_E_SCHEMA_UNREADABLEjtk/schema.json is not JSON, or a value in it has the wrong shape — words where a number goes, a list where an object does. Nothing else in the file is read until it is.
JTK_E_SCHEMA_EMPTYThe schema declares no block types.
JTK_E_SCHEMA_KEY_UNKNOWNThe schema says a key contract 3 does not have, at any depth: a typo, or a word of contract 2's that contract 3 replaced — business_facts, deprecated, a collection's prefix or body, option_labels, a view's sample. Every one is said at once, each at its place.
JTK_E_ROUTE_INVALIDA collection says nowhere, or somewhere that cannot be, where its entries are: no route, a detail without {slug} or that is no address, a listing with a slug in it, "none" with no shown_on, a pattern for a language the site does not have, or two collections whose entries would share addresses.
JTK_E_REF_INVALIDA reference points nowhere, or where no reader follows it: a ref with no to, a collection named twice, an on_delete other than restrict and nullify, a ref written as contract 2 wrote it — or a group or a tree through a reference to several collections or several entries, which nothing groups by yet.
JTK_E_SHARED_INVALIDshared names a block type the schema does not declare, or names one twice; or a field says a role that is not one of the list, sits outside the shared text, or says a role another field says already.
JTK_E_ATTRIBUTE_INVALIDA field says an attribute its kind does not take, or a value the attribute does not have: localized on a kind with no language, integer on anything but a number, qualifiers on anything but money or besides from and on_request, an untranslated that is neither base nor hide.
JTK_E_SKU_TAKENTwo variants on the site share a SKU, compared without regard to case, hidden products included.
JTK_E_PICKS_INVALIDA variant's picks do not name one value of each of its product's options, or two variants pick the same.
JTK_E_PRODUCT_INVALIDA product is outside the shop's limits, or a customization lacks what its kind needs.
JTK_E_UPCAST_INVALIDA block type's upcast says a step that cannot be one: from a version the type has not had (each step is from 1 up to one below the type's v), two steps from one version, a name that is not a field's, a rename of two fields into one, or a last step that writes, renames into or changes the rows of a field the type does not declare now — or drops one it still does.
JTK_E_PANEL_FORM_INVALIDAn entry type's form — how the panel lays out its card and a new entry — cannot be drawn as written: it names a field the type does not declare, body, or one field twice; a row holds more than three fields, spans more than six columns, or shares what is left unevenly; a gallery, a list or a document shares a row; a paragraph, a gallery or a list stands in the aside; a widget is not one of its field's kind or does not fit it; a required field has no place (but for one a module's own card draws, which no form lays out); or form is on a block type that is no collection's type. The sentence says which, at its place.

Building the site ​

What is wrong between the schema, the content and the pages the build produced.

codemeans
JTK_E_UNANNOTATED_FIELDA content field is on the page and carries no data-jtk-path.
JTK_E_PAGE_NOT_BUILTThe content has a page and the build did not produce it — or a collection without pages of its own shows its entries on a page no build made: its shown_on page on contract 3, its prefix on contract 2.
JTK_E_ROBOTS_DISALLOWThe build ships a robots.txt that keeps every crawler out.
JTK_E_SITEMAP_EMPTYThe build ships a sitemap with no pages, or pages on another host.
JTK_E_CANONICAL_ELSEWHEREThe build says its canonical page is on another host.
JTK_E_NOINDEXThe page tells search engines to go away.
JTK_E_SHARED_NOT_RENDEREDA shared field is rendered on no page at all.
JTK_E_ANNOTATION_UNKNOWNA page: annotation names a page this site has not got, or a field that page's document has not got.
JTK_E_CONTENT_VARIANTThe site's code fails to build, or loses an annotation, on content an owner can write: every optional field empty, or every one filled and long.
JTK_E_CATALOGUE_MISSINGThe repository has no schema: neither jtk/schema.json (contract 3) nor jtk/catalogue.json (contract 2, the older contract).
JTK_E_FORM_INCOMPLETEA form posting to /api/lead is missing a control the enquiry's structure needs.
JTK_E_FORM_FIELD_UNDECLAREDA form posting to /api/lead has a control the schema does not declare.
JTK_E_FORM_UNDECLAREDA page has a form posting to /api/lead and no block on it says collects: "enquiry".
JTK_E_UNNAMEDA page or an entry has no id, or a block, a row of a list or a gallery's picture has no _key, that an annotation can name — an id is a lowercase UUID, a key a lowercase letter and then lowercase letters, digits and hyphens. Nothing in it can be annotated, so the owner taps it and nothing opens.
JTK_E_META_INVALIDThe build's dist/_meta.json says what the platform does not read: it is not a JSON object, it holds drafts — which contract 3 removed — or a key other than redirects, immutable and cache, or one of those in a shape the platform would pass over.

Refused while building ​

Not a fault in a file: what the runner would not do for the build while it ran — a host it may not reach. Printed into the build log by the runner, with the request and the list.

codemeans
JTK_E_BUILD_REACHThe build asked for a host it may not reach. A build runs with no network of its own: the repository on github.com, the npm and yarn registries, the platform's media host and Google Fonts are forwarded, and nothing else is — GET and HEAD, with POST only for the clone.

Refused once stored ​

Not a fault the lint can see: the build's files, compared with the build they would replace on a site with an address. The build fails, and a publish of it is refused, with the files named in the log.

codemeans
JTK_E_CACHED_FILE_CHANGEDA name a public build let browsers keep — under immutable or a cache directory of _meta.json — has other contents in this build while it is still held.

Refused by the platform ​

Not a fault in a file — an operation that cannot be carried out in the state the site is in. These arrive as details on an API refusal, with the same code, meaning and remedy printed below.

codemeans
JTK_E_SLUG_TAKENA site already answers to that slug.
JTK_E_BOOKING_FIELD_UNKNOWNA booking page sent /api/book a field, or /api/availability a parameter, that the contract does not have — or one of the wrong shape, "count": "4" for 4. Refused when it comes from somebody the site knows: the studio, its agent, a preview. From a stranger it is dropped, and the booking goes ahead without it.
JTK_E_SHOP_PROTOCOLA shop page named a version of the shop protocol this platform does not answer — a page newer than the platform, or one so old its version has been retired. The answer says what the page said (said) and the versions the platform speaks (supported).
JTK_E_SHOP_FIELD_UNKNOWNA shop page sent one of the shop protocol's addresses a field the contract does not have, at any depth of a cart — coupon at the top, lines[0].colour in a line — or one of the wrong shape, "qty": "2" for 2. Refused when it comes from somebody the site knows: the studio, its agent, a preview. From a stranger it is dropped, and the cart is read without it.
JTK_E_ACCOUNT_PAUSEDThe studio's account is paused by the platform: a report, a loop of builds, a scripted sign-up — something a person is looking at. Every request of its members and agents answers this; its sites answer 503 to visitors. Nothing is deleted.
JTK_E_DOCUMENTS_DUEA new version of the terms, the data processing agreement or the privacy policy binds from a date that has passed, and it has not been accepted — by the person signed in, or, for an agent, by any owner or admin of its studio. Every call answers this until it is; nothing is lost meanwhile.
JTK_E_CROSS_ORIGINA request that would change something was signed in with the panel's session cookie and came from a page that is not the panel — a demo, a site, another tab's script, a sandboxed frame. The cookie is sent by the browser on its own, so the API takes a change made with it only from the panel's origin. Nothing was changed.
JTK_E_OUT_OF_SYNCThe site's content has changed in its repository since the panel last read it, so publishing would delete work nobody has seen.
JTK_E_STUDIO_ONLYA field the schema does not give the owner — client_editable not true on contract 3, false on contract 2 — was written by somebody who may change the site's words and not that field. The panel shows such a field read-only, with «the studio edits this one»; the server refuses the write as well, and its details name the path.
JTK_E_CONTENT_FILE_INVALIDA content file under jtk/ cannot be read as a document — it is not JSON, an entry is markdown, a show and a hide moment are the wrong way round — or a field in it holds what its kind refuses: text where a number is, a clock string for minutes, a select value that is not an option.
JTK_E_ENTRY_NO_COLLECTIONContract 2 only, the older contract: a content file under a collection's prefix in jtk/content/ names no collection, or names one the schema does not have or whose prefix is not where the file sits — so it would be imported as a page, and no listing, no diary and no route would know it.
JTK_E_MEDIA_MISSINGThe content names a picture or file that is not in this site's media library — a scaffold's example picture (media/jtk-example/…) never pushed, a key of another site, a file that was deleted, a key written by hand — so the build would fail downloading it. Said by a save (nothing committed; the message names the page and the field), by the import of a contract-3 tree (nothing imported; the message names the file and the key) and by the build's download.
JTK_E_ENTRY_INCOMPLETEAn entry that is on the site and changed since the last version is not finished — a required value is missing, a value does not fit its field, or a reference names an entry that is not there — so it cannot become part of a version. The save did not happen and nothing was committed; the message names the first entry and field, and details.unfinished lists each entry once (page_id, title, field, and live where visitors see it now). An entry that is not on the site is not judged: a draft may be unfinished.
JTK_E_CODE_NOT_KEPTThis deployment keeps no code of its own, so a site's code cannot live on the platform here.
JTK_E_CODE_ELSEWHEREThis site's code lives in a repository on GitHub, not on the platform, so push_code, pull_code, read_files and write_files do not apply to it.
JTK_E_CODE_TOKENThe URL jtk push or jtk pull was given has ended — used, expired after fifteen minutes, or never valid — or is for the other direction.
JTK_E_CODE_REFUSEDA path in the working copy cannot be part of a site's code: absolute, with .., \ or a control character, inside .git in any case, .gitmodules, longer than 4096 bytes, a symlink or a submodule — or the archive did not carry exactly the files asked for, with the bytes the manifest named. Nothing was committed; the paths are named.
JTK_E_CODE_SECRETA file looks like a secret: .env, an .npmrc with a token, a private key, an access key of GitHub, Stripe or AWS. Nothing was committed; the paths are named.
JTK_E_CODE_TOO_BIGThe push is over a limit of code on the platform: 20 000 files, 50 MB a file, 200 MB a repository, 90 MB a part — or a write_files call over its own: 200 paths, 2 MB of text.
JTK_E_CODE_CONFLICTSomething this commit changed was also changed on the branch since this copy's base — by a save in the panel (the person's edits, as a rule) or another machine — and the two differ. On a contract-3 site the content files under jtk/ are merged by field, so only one value both sides changed to two different values conflicts: fields names each, with the branch's value (theirs) and yours. A file is named whole where it is not such a file, or one side deleted it. Nothing was committed.
JTK_E_CODE_BASEThe commit this working copy says it started from is not in the branch's history, so what it changed cannot be told.
JTK_E_CODE_TAKENThe platform already holds a repository by this site's name that is not this site's, so its first push cannot create one.
JTK_E_CODE_RATEThis studio created more repositories on the platform in the last hour than it may.
JTK_E_CODE_COMMITSMore commits went into this site's code in the last hour than the platform takes: 60 a site, 120 a studio across its sites — pushes, and everything else that commits code. Nothing was committed; the message says when there is room again.
JTK_E_RATE_LIMITEDMore requests came from this caller in the window than the platform takes: 9 000 in 15 minutes from one account — its people in the panel and its agents together — 1 200 in 15 minutes from one address without a session, 300 uploads an hour to one site's library. Nothing was done; retry_after (and the Retry-After header) says in how many seconds there is room again.
JTK_E_THEIR_DRAFTThe panel holds unsaved changes a person made, and a save commits the whole draft — theirs with yours, half-done or not. Nothing was saved or built; the refusal names each change, the document and the field, and who made them.
JTK_E_KIT_RUNNINGA kit job of this site — the schema job after a write_files, a create_site's create — is queued or running in the builder, and it commits on top of the branch when it is done. A build now would build the branch without it. Nothing was saved or built.
JTK_E_CODE_UNCHECKEDThe build's code has not passed the platform's checks, so it cannot go live on a launched site.
JTK_E_PUBLISH_HELDA person rolled the site back, and a rollback holds it on the version it chose: no build, publish or scheduled showing moves what visitors see until a person lifts the hold.
JTK_E_DRAFT_AHEADThe panel holds unsaved changes that are in no commit, and the branch's content would write over them. On a contract-3 site only the documents where both changed one field wait — named, document → field — or one the person edited and the branch deleted; everything else came in. On a contract-2 site the whole import waits.
JTK_E_PLAN_SHORTThe studio's plan is short of a line of the kind named — a site, a diary or a shop — so the site cannot hold one.
JTK_E_NO_PLANThe studio has no plan yet, so there is nothing to change, manage or draw a line from.
JTK_E_NOT_ON_SALENo active Stripe price carries the lookup key the operation needs.
JTK_E_FROZENThe site is frozen: a subscription is fourteen days unpaid. Reading and export work; editing, publishing, new bookings and new orders do not.
JTK_E_DIARY_NOT_READYA visitor could not book: the diary is missing one of its two halves, and the sentence names which.
JTK_E_NO_DESTINATIONThe site collects enquiries, takes bookings or takes orders and nothing verified is set up to receive them, so a visitor could send one into nothing.
JTK_E_BOOKING_PROTOCOLThe site's booking page named a version of the booking protocol this platform does not answer — a kit newer than the platform, or one so old its version has been retired.
JTK_E_MOVE_PRICE_CHANGESA visitor tried to move, on their own link, a booking paid for online — or still to be paid — to a time the price table prices differently. The difference would be money nobody collected or owed back, so the link does not move it.
JTK_E_PROPOSAL_NO_CONTACTAnother time was offered for a request whose customer left only a telephone: no email and no Telegram chat, so the offer would reach nobody. Nothing was written.
JTK_E_VISITOR_CONTACTA booking from the site was refused because the visitor cannot be reached by what they left: neither a telephone (seven to fifteen digits) nor an email address that is one, a field filled with something that is neither, or only one of the two where the business's booking settings ask for both (contact: both).
JTK_E_BOOKING_NOT_BEGUNA booking was marked as having taken place, or as one nobody came to, before its start. Neither can be said of a time still ahead. A booking already out with the customer is closed by coming back whenever it does, and is not refused.
JTK_E_PAYMENTS_OFFThis environment has no payment provider configured, so nothing that prices, charges or pays out can be answered here — the prices included, because they are read from the provider.
JTK_E_NO_BUSINESSNobody is this site's business: no owner or admin has made the site theirs, and the studio has not taken it as its own. A launched site's enquiries, bookings and orders would be answered by nobody in particular.
JTK_E_PAYMENT_COUNTRYThe business's country is not set, or Stripe does not operate there, so no payment account can be made for it.
JTK_E_PAYMENT_ACCOUNT_NOT_READYThe Stripe account this needs does not exist or may not charge yet: the studio's own under Reselling, on the Stripe account tab, or the business's under Payments.
JTK_E_HANDOVER_BLOCKEDThe site cannot change hands as it stands. Every reason is in the sentence at once: not live, enquiries still going to the studio, the studio's Stripe account still attached, or the owner still paying the studio through us.
JTK_E_SUBSCRIPTION_RUNNINGA running subscription's price, interval, method or address cannot be edited in place; a subscription sold at one price is not silently resold at another.
JTK_E_TERMS_FIRSTThe owner's link was asked for before the studio said what the client pays. The terms travel on the link, so a link minted first would be an invitation with no price on it.
JTK_E_DOCUMENT_INVALIDA document under jtk/pages/, jtk/entries/ or jtk/modules/ is not where it says it is, or not what contract 3 writes: a page without its name, a path, collection or slug that disagrees with the file's place, no id or a block, row or picture without a _key, a key a document does not have, seo on an entry with no page of its own, a shown_on page that is not there, a folder or a segment named media, a value in contract 2's shape (a price as a bare number, a picture as its key, a reference by slug), a reference naming an id no entry of its collections has, or a module's settings that are not {v, settings}.
JTK_E_BLOCK_BEHINDA block in a document says a v its type's steps cannot bring to the type's own: an older version with no upcast step from it, or a version newer than the schema's type — content written against a schema that has not arrived.
JTK_E_CURRENCY_SETA contract-3 tree's jtk/site.json says a new currency: neither the site's own nor the one the platform's last save wrote there. An import takes the currency from that file only while the site has none — as create_site takes it in currency — and once a site has its currency, a person changes it in the panel. A branch still carrying the last save's currency, from before a person changed or cleared it, is not refused: it is left, and the next save writes the site's.
JTK_E_SKU_ORDEREDA variant whose SKU a paid order named lost it, or the SKU was given to a variant it was not named for. Stock and orders are kept by the SKU, so a SKU an order named sits only on a variant it was named for, or on none, and a variant an order bought carries one of the SKUs orders named for it: the save, import_branch and validate_schema (by site and ref, or with the tree's files and the site in site_id) refuse the draft or the tree that moves it, naming the variant. A checkout never paid, one that lapsed and a test order name no SKU; an order gone at its retention names none either.
JTK_E_TRANSLATION_SHAREDA translation — <name>.<locale>.json beside its original — says a value that is the same in every language: a price, a number, a date, a choice, a reference, a phone number, a link, a picture's file, focus or poster. A translation holds only the words; the translation of a shared value is the original's, everywhere, so a photograph changed in one language is changed in all of them.
JTK_E_TRANSLATION_RECORDA translation's translated holds a record that is not one. A record is {from, by, at} under a value's path in the file — from the eight hex digits of the digest of the original's value the translation was made from, by person, agent or machine, at a moment in RFC 3339 — and nothing else. A record whose from is empty is read as none: a value whose original is empty has nothing it was made from.
JTK_E_MACHINE_OFFTranslate, in the panel's languages, asked a deployment that translates nothing by machine: it has no DeepL key — staging until a person sets one, production until DeepL is named in the data processing agreement — or the site's other languages are copies (contract 2) rather than translations of one original.
JTK_E_MACHINE_ALLOWANCEThe site's machine translation allowance is not enough for what was asked: a paid site's 30,000 characters of a calendar month, a demo's 10,000 once. What the cache already holds costs nothing and is not counted; everything sent to DeepL is.

Advice from the schema judge ​

Valid, and unwise. Nothing is refused on these; they come back under advice from POST /v1/registry/validate and from validate_schema, and an agent acts on them before the first build.

codemeans
JTK_W_MODULE_TWINA page block types again a fact the bookings module already holds — the opening hours the owner keeps in the diary, or the prices the services carry — so the site has two copies and one of them goes stale.
JTK_W_MODULE_POSTAn entry type the bookings module reads is shaped as a post — a body, or excerpt, cover and body together — or its services get a page each, so the panel draws a service or a table as an article with its own address.
JTK_W_KIND_UNKNOWNkind in the bookings settings names a kind of business the platform has no dictionary for, so its bookings are spoken of in neutral words — «бронювання», «Забронювати».
JTK_W_KIND_MISSINGThe bookings settings say no kind, so the bookings are spoken of in the salon's words — «запис», «майстер» — which is what every site before kinds existed spoke, and nothing changes for it. Said so that a business that is not a salon is not given a salon's words by omission.
JTK_W_LOCALE_FALLBACKThe site takes bookings and its language (locale) is none of the eight the platform writes to customers in — uk, en, de, ru, es, it, pt, fr — so the letters to the customers and the messages to the owner go out in English. A region is read off first: de-CH is German, pt-BR Portuguese; pl or ka is English.
JTK_W_PAYMENT_UNCHECKEDThe site takes money online for its bookings, and the self-check (preflight with self_check) never pays: what needs the money paid — a booking confirmed by its payment, moved, offered another time — was not walked, and neither was the payment itself.
JTK_W_WORD_UNKNOWNA row of words in the bookings settings names a key the platform's dictionary does not have, so the word is said nowhere.
JTK_W_KIND_NO_DAYSThe bookings settings name the hours a stay goes out and comes back at (hand_out, hand_back), and not one of the services is sold by the day — the hours frame nothing, and it can only be booked by the hour, like a salon.
JTK_W_KIT_BEHINDkit and kit_version in a module's settings — the bookings' or the shop's — say which kit the site was laid out from and when, and the kit has changed since — a fix to it, or to a part it shares with other kits, that this site has not got.
JTK_W_UNPRICED_HOURSA service priced by the hour of the week (rates instead of costs) is open, by the hours in the bookings settings, at hours none of its rows prices — and an hour nobody priced is not sold: the form does not offer it for this service, and a page that asks for it is refused.
JTK_W_DIARY_UNSETThe site takes bookings and its settings say no time zone (zone) or no opening hours (hours): until both are set the diary refuses every visitor — /api/availability and preflight's try_booking answer JTK_E_DIARY_NOT_READY — and the form shows «nobody has said which timezone this business keeps». A draft may be unfinished, so nothing is refused; this is said so the gap is not found by a visitor.
JTK_W_SESSION_OUTSIDE_HOURSA bookable's own hours — a class's times in a sessions kit, a master's or a room's own week — reach outside the business's opening hours that day, and the diary offers only the part inside them (it clips one to the other, as the panel's diary shades): a class at 18:00–19:15 on a day the business closes at 18:00 is offered never, and nothing else says why.
JTK_W_ADDON_ALONEA service with no takes and a price is an add-on — shoes, a racket, a towel — taken only beside a timed service in one visit (wiki/70), and this site's bookings take one service per visit (combine off in the bookings settings), so nobody could take it.
JTK_W_OWNER_LOCKEDA field holding a date, an hour or an amount of money is not client_editable, so the owner cannot change it: the next event's date, the hour the doors open, a price — facts of the business that change on its calendar, and that the studio is then asked to change every time.
JTK_W_HIDDEN_UNEXPLAINEDA field the owner edits is not on the page (no_tap_target) and names nothing it belongs to (beside) and says nothing about itself (hint): the panel shows it under More, at the foot of the editor of every field of its block, by its label alone, and the owner has to guess what it changes.
JTK_W_LINK_NOT_BESIDEA link the page does not show (no_tap_target, a url or a key ending in href, link or url) names no field it belongs to (beside). The panel opens it under its button by the names alone — the words field named alike (cta_href with cta_label), or else the one field whose key says cta or button — and where that names one field, says which; where it names none or two, the link is under More with the block's other values, a step from the button it is about.
JTK_W_CONTENT_ORPHANA content file carries a block type, or a field, that the schema does not describe — text the panel cannot show and the build cannot annotate. Or a whole file sits where the site's contract keeps nothing: in a tree whose schema is jtk/schema.json, a page in contract 2's places, under jtk/content/, or settings at contract 2's jtk/<module>.json, which nothing reads.
JTK_W_CONTENT_BOUNDSA value in a content file is longer or shorter than its field allows, or a list has more or fewer rows than it may — the panel will refuse to save the field as it stands, though the build serves it.
JTK_W_NOT_LIVEThe schema does not say render: "live": the template does not draw a draft at request time, so the owner sees a change in the panel's preview only after a build, and an entry's card cannot be previewed before it is saved.
JTK_W_DATE_HIDESThe site's template compares an entry's date with the clock to choose what it shows — the next night, the ones left out, the ones marked past. A build freezes that comparison until the next build, a visitor sees what is over as ahead, and the panel, which cannot know, shows it as on the site. Said by the kit's jtk schema, from the site's code.
JTK_W_PANEL_FORM_GUESSEDThe panel placed fields of an entry type by itself: a form places no row for some — they are drawn after its sections, under More — or a type of seven fields or more says no form, and the panel lays them out in their order, short ones two to a row and pictures aside. The fields a module's own card draws are the exception: no form lays them out and the count leaves them out, so the shop's product type is not advised for its eight — and a form that places one of them is, since the panel leaves it out of the form all the same.
JTK_W_FIRST_SCREENOn the home page the heading or the first action ends below the first screen — a phone 390 × 844 or a desktop 1280 × 800 — so a visitor sees a picture and not what the business does or how to book it. Measured in a browser by preflight (the floor's F8). Advice, never a refusal.
JTK_W_ANCHOR_LANDINGA link in the home page — the header's #angebot, #kontakt — scrolls its target to where its first words land more than 96 px below the header, across the section's own top padding, or under the header. The visitor arrives at air, or at a cut heading, and scrolls again. Measured in a browser by preflight at a phone's and a desktop's width. Advice, never a refusal.
JTK_W_SCREEN_FITOn a desktop (1280 × 800) a section of the home page is a little taller than the screen under the header — by less than a third — so it is never seen whole; or a form, with its heading, is taller than that screen and its button is out of sight while it is filled. Measured in a browser by preflight. Advice, never a refusal.
JTK_W_RAGGED_GALLERYA wall of four or more pictures on the home page ends ragged: its columns end more than 24 px apart — a masonry of mixed proportions, or a last row left half empty. Measured in a browser by preflight. Advice, never a refusal.
JTK_W_BOOKING_LINKA button on the home page — the header's «book» — opens another page of the site at its top, and that page's booking form starts more than half a screen down: the visitor who asked to book scrolls to find it. Measured in a browser by preflight. Advice, never a refusal.
JTK_W_TRANSLATION_ORPHANA translation gives words to a block, a row of a list or a gallery's picture by a _key its original has not got — removed in the original, or a key misspelt. Its words are shown nowhere, and the next save leaves them out of the file; the history keeps them.

Advice from the build ​

The build passes, and leaves the owner something they cannot tap, or the person a design that is not the one they were promised. Nothing is refused on these; the annotation lint and the design count print them in the build log with their JTK_W_ code, after their own verdict.

codemeans
JTK_W_UNANNOTATED_FIELDA value the owner edits — a phone, an email, a link, a choice, a date, an hour or a number — is on the page and carries no data-jtk-path: the owner taps it and nothing opens. Advice for now, for these kinds; a contract-3 build will refuse it as JTK_E_UNANNOTATED_FIELD once the kit's example draws them all. Advice too, of any kind, on contract 3, where a filled value's words are on no part of the built page: a field the template shows only on a condition — a label while another document has a value — is not refused on the build that hides it.
JTK_W_DRAWN_UNTAPPABLEA value the owner edits is drawn as text where nothing answers a tap: under data-jtk-fixed, or under no annotation at all — the business's name in a © line, a postcode joined to its city. Matched as the whole value, four characters or more, on the pages its document is drawn on; the shared text's on every page of its language. Advice, never a refusal.
JTK_W_TEMPLATE_DESIGNThe site's design path is custom — the person gave their site or sites they like and wants a design of their own (create_site's design) — and the site still wears the template's design: more than 60 % of the scaffold's design files (its components, styles and layouts, the forms and the kit's galleries, motion and helpers aside) are byte for byte the kit's, or its hero, header and footer all are. Recoloured tokens are not a custom design. Counted on every build (design in the build's answer: untouched, of, the files); said only where the path is custom. Advice, never a refusal.
JTK_W_DESIGN_AXESThe site's design path is custom and jtk/design.json chooses fewer than ten of the fourteen axes — a choice is a line of three words or more, what and from where; a tag like split or linen is not one — the hero, the ground, the measures, the shape, the header, the phone's menu, the overlap, the surfaces, the mark, the motion, the fonts, the hook, the proof, the contact — or no mark. Where the site shows directions, the first one's axes are counted. A design nobody chose on falls back on what a model reaches for first. Advice, never a refusal.
JTK_W_DIRECTIONS_ALIKETwo of the directions in jtk/design.json's directions differ on fewer than three axes, or not on the hero: the person is shown one design in other colours and asked to choose. Advice, never a refusal.

JTK_E_SLUG_TAKEN ​

A site already answers to that slug.

What to do: If it is this account's, the refusal names its id — work with that site instead of making another. «That slug is taken» with no id is another account's site, which this one cannot see or claim: choose a different slug.

Said by: the platform.

JTK_E_BOOKING_FIELD_UNKNOWN ​

A booking page sent /api/book a field, or /api/availability a parameter, that the contract does not have — or one of the wrong shape, "count": "4" for 4. Refused when it comes from somebody the site knows: the studio, its agent, a preview. From a stranger it is dropped, and the booking goes ahead without it.

What to do: Send what the booking protocol lists, with the names and shapes it gives: the answer's fields names what was wrong and takes everything that would have been read. A stay of several nights is count, never units, nights or days.

Said by: the platform.

JTK_E_SHOP_PROTOCOL ​

A shop page named a version of the shop protocol this platform does not answer — a page newer than the platform, or one so old its version has been retired. The answer says what the page said (said) and the versions the platform speaks (supported).

What to do: Send a version the answer lists in X-Jtk-Shop, or none, which is version 1, and see the shop protocol for what each address takes.

Said by: the platform.

JTK_E_SHOP_FIELD_UNKNOWN ​

A shop page sent one of the shop protocol's addresses a field the contract does not have, at any depth of a cart — coupon at the top, lines[0].colour in a line — or one of the wrong shape, "qty": "2" for 2. Refused when it comes from somebody the site knows: the studio, its agent, a preview. From a stranger it is dropped, and the cart is read without it.

What to do: Send what the shop protocol lists, with the names and shapes it gives: the answer's fields names what was wrong, by path, and takes every name that would have been read.

Said by: the platform.

JTK_E_ACCOUNT_PAUSED ​

The studio's account is paused by the platform: a report, a loop of builds, a scripted sign-up — something a person is looking at. Every request of its members and agents answers this; its sites answer 503 to visitors. Nothing is deleted.

What to do: Nothing an agent can do. The studio writes to the platform; a person resumes the account, and its sites come back in one step.

Said by: the platform.

JTK_E_DOCUMENTS_DUE ​

A new version of the terms, the data processing agreement or the privacy policy binds from a date that has passed, and it has not been accepted — by the person signed in, or, for an agent, by any owner or admin of its studio. Every call answers this until it is; nothing is lost meanwhile.

What to do: Nothing an agent can do. Tell the developer: an owner or an admin of the studio opens the panel, reads the new version and accepts it, and the agent works again at once.

Said by: the platform.

JTK_E_CROSS_ORIGIN ​

A request that would change something was signed in with the panel's session cookie and came from a page that is not the panel — a demo, a site, another tab's script, a sandboxed frame. The cookie is sent by the browser on its own, so the API takes a change made with it only from the panel's origin. Nothing was changed.

What to do: Make the change in the panel, or from a program with an agent's token (Authorization: Bearer jtk_…), which is not asked where it comes from. A script on a site or a demo cannot act with the session of whoever opened it.

Said by: the platform.

JTK_E_OUT_OF_SYNC ​

The site's content has changed in its repository since the panel last read it, so publishing would delete work nobody has seen.

What to do: Run import_branch to bring the repository's content into the panel, then publish again. If the panel holds unsaved changes the import says so (JTK_E_DRAFT_AHEAD) rather than writing over them — read them with get_content, then import with overwrite_draft or carry them into the branch yourself.

Said by: the platform.

JTK_E_STUDIO_ONLY ​

A field the schema does not give the owner — client_editable not true on contract 3, false on contract 2 — was written by somebody who may change the site's words and not that field. The panel shows such a field read-only, with «the studio edits this one»; the server refuses the write as well, and its details name the path.

What to do: Nothing an owner does: the studio changes it. If the owner should, the studio says client_editable: true on the field in the schema, commits it and imports it.

Said by: the platform.

JTK_E_CONTENT_FILE_INVALID ​

A content file under jtk/ cannot be read as a document — it is not JSON, an entry is markdown, a show and a hide moment are the wrong way round — or a field in it holds what its kind refuses: text where a number is, a clock string for minutes, a select value that is not an option.

What to do: Fix the file where the finding points: every value is what its field's kind says (reference/field-kinds.md), and a document is the shape reference/jtk-files.md gives — on contract 3 a page jtk/pages/<path>.json, an entry jtk/entries/<collection>/<slug>.json, the shared text jtk/shared.json; on contract 2, the older contract, jtk/content/<page>.json as {path, seo, blocks}. validate_schema by site and ref says every such finding for the whole commit at once; import_branch refuses on the first.

Said by: the platform.

JTK_E_ENTRY_NO_COLLECTION ​

Contract 2 only, the older contract: a content file under a collection's prefix in jtk/content/ names no collection, or names one the schema does not have or whose prefix is not where the file sits — so it would be imported as a page, and no listing, no diary and no route would know it.

What to do: An entry says which collection it is an entry of: add "collection": "<name>" (and "visible": true) to the file, the way publish writes it, then import again. A page that is not an entry lives outside every collection's prefix. Contract 3 has no prefix to mistake: an entry is jtk/entries/<collection>/<slug>.json, its directory its collection.

Said by: the platform, on contract 2 only — the older contract; a new site never meets it.

JTK_E_MEDIA_MISSING ​

The content names a picture or file that is not in this site's media library — a scaffold's example picture (media/jtk-example/…) never pushed, a key of another site, a file that was deleted, a key written by hand — so the build would fail downloading it. Said by a save (nothing committed; the message names the page and the field), by the import of a contract-3 tree (nothing imported; the message names the file and the key) and by the build's download.

What to do: From a working copy: media_link, then npx @jtakeit/astro push '<url>' --media '<media url>' (the media push runs before the code) or npx @jtakeit/astro media push '<media url>' — it puts the pictures into this site's library and writes their keys into the content — then push or import_branch again. In the panel: choose the picture again, or upload it. A key of another site is never served here.

Said by: the platform.

JTK_E_ENTRY_INCOMPLETE ​

An entry that is on the site and changed since the last version is not finished — a required value is missing, a value does not fit its field, or a reference names an entry that is not there — so it cannot become part of a version. The save did not happen and nothing was committed; the message names the first entry and field, and details.unfinished lists each entry once (page_id, title, field, and live where visitors see it now). An entry that is not on the site is not judged: a draft may be unfinished.

What to do: Finish the entry in the panel, or keep it off the site for now (its switch off, which a person does in the panel); then save again. From the repository: fill the field in the entry's file, commit, import_branch.

Said by: the platform.

JTK_E_CODE_NOT_KEPT ​

This deployment keeps no code of its own, so a site's code cannot live on the platform here.

What to do: Use the GitHub path: a repository with our GitHub App installed by a person, attach_repo, git push, import_branch.

Said by: the platform.

JTK_E_CODE_ELSEWHERE ​

This site's code lives in a repository on GitHub, not on the platform, so push_code, pull_code, read_files and write_files do not apply to it.

What to do: Work as with any GitHub repository: git pull, commit, git push, then import_branch and commit_and_build. get_site says where a site's code lives (code).

Said by: the platform.

JTK_E_CODE_TOKEN ​

The URL jtk push or jtk pull was given has ended — used, expired after fifteen minutes, or never valid — or is for the other direction.

What to do: Ask for a new one: push_code or pull_code, then run the command it answers with, as it is.

Said by: the platform.

JTK_E_CODE_REFUSED ​

A path in the working copy cannot be part of a site's code: absolute, with .., \ or a control character, inside .git in any case, .gitmodules, longer than 4096 bytes, a symlink or a submodule — or the archive did not carry exactly the files asked for, with the bytes the manifest named. Nothing was committed; the paths are named.

What to do: Remove or rename what is named, or add it to .gitignore if it is not the site's code, and push again. A symlink is replaced by the file it points to. Through write_files: each path once a call, text with no NUL byte, a deletion only of a file the base has, never over a symlink.

Said by: the platform.

JTK_E_CODE_SECRET ​

A file looks like a secret: .env, an .npmrc with a token, a private key, an access key of GitHub, Stripe or AWS. Nothing was committed; the paths are named.

What to do: A secret does not belong in a site's code. Remove it, add it to .gitignore, and if it was ever pushed anywhere, change it. Settings a build needs go through the site's settings, never through a file.

Said by: the platform.

JTK_E_CODE_TOO_BIG ​

The push is over a limit of code on the platform: 20 000 files, 50 MB a file, 200 MB a repository, 90 MB a part — or a write_files call over its own: 200 paths, 2 MB of text.

What to do: Pictures and video belong in the site's media (upload them through the panel or the media endpoint), not in its code. Remove the large files from the working copy, or add them to .gitignore. A write_files over its call's limits goes in parts, each on the last one's sha.

Said by: the platform.

JTK_E_CODE_CONFLICT ​

Something this commit changed was also changed on the branch since this copy's base — by a save in the panel (the person's edits, as a rule) or another machine — and the two differ. On a contract-3 site the content files under jtk/ are merged by field, so only one value both sides changed to two different values conflicts: fields names each, with the branch's value (theirs) and yours. A file is named whole where it is not such a file, or one side deleted it. Nothing was committed.

What to do: The person wins by default. Keep their value: tell them what they changed — the field and the value — and that you left it; then pull (pull_code and its jtk pull into a new, empty directory, or git pull where the code is on GitHub), carry your change over onto what the branch holds now — never over their value — and commit again — through write_files: read_files the named files at the tip, lay your change over what they hold now, and write on that tip. Write over their value only when the person says so in the chat. jtk pull writes nothing over a conflict, and its URL is spent on the try.

Said by: the platform.

JTK_E_CODE_BASE ​

The commit this working copy says it started from is not in the branch's history, so what it changed cannot be told.

What to do: The copy came from somewhere else. pull_code and jtk pull into an empty directory, then bring your changes over and push from there. Through write_files: the base is the tip read_files answered with, or the last write's sha — read_files again and write on its tip.

Said by: the platform.

JTK_E_CODE_TAKEN ​

The platform already holds a repository by this site's name that is not this site's, so its first push cannot create one.

What to do: Ask the platform's support: a repository by that name is being kept for a reason, and it is not overwritten.

Said by: the platform.

JTK_E_CODE_RATE ​

This studio created more repositories on the platform in the last hour than it may.

What to do: Wait an hour. A site's repository is created once, on its first push; later pushes are not counted.

Said by: the platform.

JTK_E_CODE_COMMITS ​

More commits went into this site's code in the last hour than the platform takes: 60 a site, 120 a studio across its sites — pushes, and everything else that commits code. Nothing was committed; the message says when there is room again.

What to do: Wait the minutes the message names (Retry-After says the seconds), then push again. A loop that pushes after every small change is the usual cause: change more, push once.

Said by: the platform.

JTK_E_RATE_LIMITED ​

More requests came from this caller in the window than the platform takes: 9 000 in 15 minutes from one account — its people in the panel and its agents together — 1 200 in 15 minutes from one address without a session, 300 uploads an hour to one site's library. Nothing was done; retry_after (and the Retry-After header) says in how many seconds there is room again.

What to do: Wait the seconds retry_after names, then ask again — the same call will work. A loop that asks without a pause is the usual cause: wait a few seconds between get_build calls while a build runs, and read a site once rather than before every step.

Said by: the platform.

JTK_E_THEIR_DRAFT ​

The panel holds unsaved changes a person made, and a save commits the whole draft — theirs with yours, half-done or not. Nothing was saved or built; the refusal names each change, the document and the field, and who made them.

What to do: Ask the person, naming their changes: are they ready to go with yours? On their yes, commit_and_build with with_their_draft: true saves and builds them with yours. Without it, branch_only: true builds the branch as it stands — your commits — and leaves their draft unsaved in the panel for them. Never pass with_their_draft on your own.

Said by: the platform.

JTK_E_KIT_RUNNING ​

A kit job of this site — the schema job after a write_files, a create_site's create — is queued or running in the builder, and it commits on top of the branch when it is done. A build now would build the branch without it. Nothing was saved or built.

What to do: Wait for it: get_site's kit_job says done — usually within a minute — or failed, with why. Then commit_and_build again. The MCP's commit_and_build waits for it on its own for a while before it answers this.

Said by: the platform.

JTK_E_CODE_UNCHECKED ​

The build's code has not passed the platform's checks, so it cannot go live on a launched site.

What to do: The checks judge code, not who started the build: the annotation lint — noindex, robots, the sitemap, the canonical, the enquiry form's contract — and the site built with every optional field empty and with every one filled and long. A person's build of new code goes on for the preview and says what failed in its log; fix that in the repository, push, and build again. A build of code that has passed goes live, and a save that changed only content keeps the verdict of the code it was made on.

Said by: the platform.

JTK_E_PUBLISH_HELD ​

A person rolled the site back, and a rollback holds it on the version it chose: no build, publish or scheduled showing moves what visitors see until a person lifts the hold.

What to do: Nothing to retry. A build made meanwhile is kept as the candidate and shown in the preview; a person lifts the hold on the panel's builds card once the source is fixed, then publishes. Fix the source first — the rollback restored the artifact, not the repository.

Said by: the platform.

JTK_E_DRAFT_AHEAD ​

The panel holds unsaved changes that are in no commit, and the branch's content would write over them. On a contract-3 site only the documents where both changed one field wait — named, document → field — or one the person edited and the branch deleted; everything else came in. On a contract-2 site the whole import waits.

What to do: The person has been editing in the panel. Tell them what waited, by the names the answer gives (waited), and keep their value: read it with get_content and build on it, or ask them; import_branch with overwrite_draft: true writes the branch over their edits on purpose, only on their word. Nothing is lost: the code has landed and what waits is in the branch; the panel's next save — commit_and_build, or theirs — brings it in first and lays their changes over it, theirs standing where both changed one field (synced in the answer), and commit_and_build's dry_run says it is waiting (pending). Bring your copy to the branch first, always — every version is a commit on it: git pull where the code is on GitHub, pull_code and its jtk pull where it is on jtakeit (get_site says which, code).

Said by: the platform.

JTK_E_PLAN_SHORT ​

The studio's plan is short of a line of the kind named — a site, a diary or a shop — so the site cannot hold one.

What to do: One more of that kind under Reselling, by the studio's owner or admin; get_allowance says what is held and where it went. A demo costs nothing until it goes live, which is when this arrives.

Said by: the platform.

JTK_E_NO_PLAN ​

The studio has no plan yet, so there is nothing to change, manage or draw a line from.

What to do: Buy one under Reselling. Everything the studio holds today was granted rather than bought.

Said by: the platform.

JTK_E_NOT_ON_SALE ​

No active Stripe price carries the lookup key the operation needs.

What to do: A deployment step, not a repository fix: scripts/stripe-prices.sh creates the prices, in test mode and in live mode separately.

Said by: the platform.

JTK_E_FROZEN ​

The site is frozen: a subscription is fourteen days unpaid. Reading and export work; editing, publishing, new bookings and new orders do not.

What to do: Pay. Whose payment the sentence says — the studio's plan with us under Reselling, or the owner's invoice to the studio on the owner's Subscription screen. Paying thaws; nothing else does.

Said by: the platform.

JTK_E_DIARY_NOT_READY ​

A visitor could not book: the diary is missing one of its two halves, and the sentence names which.

What to do: The schema's modules.bookings and its collections are the repository's — commit, import_branch, build. The time zone and the hours are the owner's — Diary → Opening hours, then save and publish. preflight reports this. One entry the diary cannot compute on — a resource with both seats and spots, a service with two prices or a most under its fewest — is left out of a visitor's diary while the rest stays open, and the launch's gate names it until it is fixed.

Said by: the platform.

JTK_E_NO_DESTINATION ​

The site collects enquiries, takes bookings or takes orders and nothing verified is set up to receive them, so a visitor could send one into nothing.

What to do: A person adds a destination on The site → Notifications: a Telegram chat, an email address, or the panel alone. Telegram and email are confirmed before they count; the panel's own inbox needs no confirming and answers the gate on its own. It is the site's owner or admin, or the studio while it runs the site — never an agent, which records.destinations refuses. The gate is derived from the schema and cannot be switched off.

Said by: the platform.

JTK_E_BOOKING_PROTOCOL ​

The site's booking page named a version of the booking protocol this platform does not answer — a kit newer than the platform, or one so old its version has been retired.

What to do: Update @jtakeit/kit in the site's repository to a release this platform supports (the answer lists the versions it speaks), build, and run preflight with try_booking. A visitor's booking is not refused for it; the studio's and its agent's are, so the mismatch is heard before it matters.

Said by: the platform.

JTK_E_MOVE_PRICE_CHANGES ​

A visitor tried to move, on their own link, a booking paid for online — or still to be paid — to a time the price table prices differently. The difference would be money nobody collected or owed back, so the link does not move it.

What to do: Nothing to fix in the site. The visitor rings the business, and the business moves the booking in the diary and settles the difference with them. A move to a time at the same price goes through on the link as before.

Said by: the platform.

JTK_E_PROPOSAL_NO_CONTACT ​

Another time was offered for a request whose customer left only a telephone: no email and no Telegram chat, so the offer would reach nobody. Nothing was written.

What to do: Ring the customer. Agree the time with them and move the request in the diary, or confirm it. An offer can be made once the booking has an email or a chat linked to it.

Said by: the platform.

JTK_E_VISITOR_CONTACT ​

A booking from the site was refused because the visitor cannot be reached by what they left: neither a telephone (seven to fifteen digits) nor an email address that is one, a field filled with something that is neither, or only one of the two where the business's booking settings ask for both (contact: both).

What to do: Nothing to fix in the site for a visitor's typo: the form says which field to correct. If every booking is refused for this, the form does not send what the settings ask for — a form with no email field cannot book while contact is both; add the field (the kit's form has it) or set contact back to one is enough. A booking the business adds in the panel is never refused for it.

Said by: the platform.

JTK_E_BOOKING_NOT_BEGUN ​

A booking was marked as having taken place, or as one nobody came to, before its start. Neither can be said of a time still ahead. A booking already out with the customer is closed by coming back whenever it does, and is not refused.

What to do: Wait until the booking's start has passed, then mark it. A booking that will not happen is cancelled instead; one moved to another time is moved.

Said by: the platform.

JTK_E_PAYMENTS_OFF ​

This environment has no payment provider configured, so nothing that prices, charges or pays out can be answered here — the prices included, because they are read from the provider.

What to do: Nothing in the site or the account is wrong. Say so to whoever asked: there are no payments in this environment (staging and local development usually have none). The prices are on the production platform's own pricing page and in its panel.

Said by: the platform.

JTK_E_NO_BUSINESS ​

Nobody is this site's business: no owner or admin has made the site theirs, and the studio has not taken it as its own. A launched site's enquiries, bookings and orders would be answered by nobody in particular.

What to do: Two doors, and the launch takes either: invite the owner from the site's People screen and let the client make the site theirs — a client who will never open the panel opens it once, and lets the studio at the records and the money from there — or press This is our own site on the site's screen.

Said by: the platform.

JTK_E_PAYMENT_COUNTRY ​

The business's country is not set, or Stripe does not operate there, so no payment account can be made for it.

What to do: The country is set under The site → The business. A country Stripe does not serve cannot be paid through us today; there is no second provider yet.

Said by: the platform.

JTK_E_PAYMENT_ACCOUNT_NOT_READY ​

The Stripe account this needs does not exist or may not charge yet: the studio's own under Reselling, on the Stripe account tab, or the business's under Payments.

What to do: Set it up on that screen and answer Stripe's questions; charges are allowed when Stripe says so, usually within a day or two. Nothing can be billed before that.

Said by: the platform.

JTK_E_HANDOVER_BLOCKED ​

The site cannot change hands as it stands. Every reason is in the sentence at once: not live, enquiries still going to the studio, the studio's Stripe account still attached, or the owner still paying the studio through us.

What to do: Undo each named thing — launch, remove the studio's destinations, remove the payee, stop the client billing — then mint the offer again.

Said by: the platform.

JTK_E_SUBSCRIPTION_RUNNING ​

A running subscription's price, interval, method or address cannot be edited in place; a subscription sold at one price is not silently resold at another.

What to do: Stop it and start a new one. The owner sees a new first invoice rather than a surprise on the next; what was paid stays paid.

Said by: the platform.

JTK_E_TERMS_FIRST ​

The owner's link was asked for before the studio said what the client pays. The terms travel on the link, so a link minted first would be an invitation with no price on it.

What to do: Set what the client pays under the site's Subscription — zero is an answer — and mint the link from there.

Said by: the platform.

JTK_E_CATALOGUE_UNREADABLE ​

Contract 2's schema, jtk/catalogue.json, is not JSON, or carries a key that contract has no place for. Contract 3's jtk/schema.json says this as JTK_E_SCHEMA_UNREADABLE or JTK_E_SCHEMA_KEY_UNKNOWN.

What to do: Read the error's own words: they name the offending key. A key that used to be valid means the toolkit is newer than the service.

Said by: the schema, on contract 2 only — the older contract; a new site never meets it.

JTK_E_CONTRACT_UNKNOWN ​

The schema names a contract number this service does not speak.

What to do: A higher number than ours is a service to deploy, not a repository to fix. A lower one is upgraded silently and never reaches you.

Said by: the schema.

JTK_E_CATALOGUE_EMPTY ​

Contract 2's schema, jtk/catalogue.json, declares no blocks, so it describes no site. Contract 3 says this as JTK_E_SCHEMA_EMPTY.

What to do: Declare at least one block type. A schema is the list of shapes a site's content comes in.

Said by: the schema, on contract 2 only — the older contract; a new site never meets it.

JTK_E_GENERATOR_INVALID ​

The generator string does not name a tool.

What to do: Letters, digits and the punctuation a package name uses, up to eighty characters — or leave it out.

Said by: the schema.

JTK_E_NAME_INVALID ​

A block type, field key, view key or collection name is not spelled the way an identifier must be.

What to do: Lowercase letters, digits and underscores, starting with a letter, up to forty characters. These strings become annotation paths and generated TypeScript names.

Said by: the schema.

JTK_E_NAME_DUPLICATE ​

Two things in the same place are called the same thing.

What to do: Rename one of them. Which of the two wins would otherwise depend on the order of a slice.

Said by: the schema.

JTK_E_LABEL_MISSING ​

A field, view or collection has no label.

What to do: Give it words. The label is what the owner reads in the admin, and a form of keys is not a form.

Said by: the schema.

JTK_E_TEXT_INVALID ​

A label or hint is written both once and per language, names a language that is not one, is empty, or runs too long.

What to do: Write it once as a string, or per language as an object of language to words — never both. Three hundred characters is the ceiling.

Said by: the schema.

JTK_E_BLOCK_VERSION ​

A block type has no version, or a version below one.

What to do: Give the block "v": 1. The version is how stored content knows which shape it was written against.

Said by: the schema.

JTK_E_BLOCK_EMPTY ​

A block type declares no fields.

What to do: Declare at least one field, or remove the block. A block with no fields is a block nobody can edit.

Said by: the schema.

JTK_E_COLLECTS_UNKNOWN ​

A block says it collects something nothing knows about.

What to do: The only thing a block may collect today is "enquiry". A typo here would quietly exempt the site from the publishing gate that asks where enquiries go.

Said by: the schema.

JTK_E_KIND_UNKNOWN ​

A field's kind is not one of the 19 — 17 on contract 2, which has neither sku nor picks.

What to do: Use a kind from the reference. The set is closed because each kind is a validator, a form control, a zod schema and an annotation rule.

Said by: the schema.

JTK_E_BOUNDS_INVALID ​

A min or max is negative, or the minimum is above the maximum.

What to do: Bounds count characters for text, the value for a number, and items for a list or a gallery.

Said by: the schema.

JTK_E_SELECT_NO_OPTIONS ​

A select field offers nothing to select.

What to do: Give it options. A select with no options is a control that cannot be used.

Said by: the schema.

JTK_E_LIST_INVALID ​

A list nests lists deeper than its contract allows, declares no item fields, or of appears on a field that is not a list.

What to do: On contract 3 a row may hold one list of its own, whose rows are a flat set of fields; on contract 2 every row is flat. There is no form control and no annotation path deeper than that.

Said by: the schema.

JTK_E_MEDIA_INVALID ​

A media field's accept, ratio or multiple do not go together — or one of the three appears on a field that is not media.

What to do: A video needs multiple because it is stored with its poster; so does a ratio, because the focus is stored beside the picture. Use max: 1 when there is only one.

Said by: the schema.

JTK_E_BESIDE_INVALID ​

A field's beside names no field of the same block (or row), names the field itself, or names a field that is not on the page either — or the field carrying it is on the page.

What to do: beside goes on a no_tap_target field and names the field the owner taps that this value belongs to: the hour beside the date, the address beside the button's words. The panel opens it under that field.

Said by: the schema.

JTK_E_TITLED_BY_INVALID ​

A field's titled_by names no field of the same block (or row), names the field itself, or names a field that is not a line of text.

What to do: titled_by names the text field whose words stand over this value on the page — age_label over night_age — so the panel calls the value what the page calls it. Point it at a text field of the same block or row.

Said by: the schema.

JTK_E_VIEW_INVALID ​

A block declares arrangements but has no gallery to arrange, sets its bounds in two places, or a view's own bounds do not make sense.

What to do: Views arrange one multiple media field, and the limits live on the views rather than on the field.

Said by: the schema.

JTK_E_LOCALE_INVALID ​

A language is not a language, is declared twice, or the site's own language appears again among the others.

What to do: Two letters, or two and a region — uk, en, de-CH. The site's own language is locale, and it does not repeat in locales.

Said by: the schema.

JTK_E_MODULE_UNKNOWN ​

The schema turns on a module this service does not have.

What to do: Modules are a closed set — see the reference for which ones exist. A module that is not there is not one you can enable by naming it.

Said by: the schema.

JTK_E_MODULE_ROLE_INVALID ​

A module is pointed at nothing, or at something that is not a collection of this schema.

What to do: Every required role must name one of this schema's own collections: bookings needs services and resources.

Said by: the schema.

JTK_E_MODULE_FILE_INVALID ​

Contract 2 only, the older contract: its settings file jtk/<module>.json is not a settings document — it is not JSON, it has no blocks, its one block is not the module's own config type, or a field holds what its kind refuses.

What to do: On contract 2 the file has one shape — {"blocks": [{"type": "bookings_config", "v": 1, "zone": …, "hours": […]}]} — the same one publish writes; settings written as top-level keys are not read: put them inside the block. Import refuses rather than importing an empty diary, so nothing is silently lost. Contract 3 keeps a module's settings in jtk/modules/<module>.json as {"v": 1, "settings": {…}} and says a fault in them as JTK_E_DOCUMENT_INVALID; reference/jtk-files.md shows both and the modules reference lists the fields.

Said by: the schema, on contract 2 only — the older contract; a new site never meets it.

JTK_E_COLLECTION_INVALID ​

A collection's place, icon, entry type or blocks list is wrong — or, on contract 2, its prefix or pagination.

What to do: Give a collection an entry type that is a declared block, and a place and an icon the schema reference lists. On contract 3 where the entries live is the collection's route, judged as JTK_E_ROUTE_INVALID; on contract 2 a prefix is a path like /blog with no trailing slash, and no two collections may own the same addresses.

Said by: the schema.

JTK_E_ENTRY_TYPE_INVALID ​

The block type a collection names cannot be used for entries.

What to do: An entry needs a required title, must not use a reserved key for something else, and must give the reserved keys their reserved kinds.

Said by: the schema.

JTK_E_ORDER_INVALID ​

A collection is ordered by a field that will not order it.

What to do: Order by a required date or number, or arrange the entries by hand with "by": "manual".

Said by: the schema.

JTK_E_UNANNOTATED_FIELD ​

A content field is on the page and carries no data-jtk-path.

What to do: Annotate the element that renders the value. Without it the visual editor silently stops opening when the client taps that text.

Said by: the build.

JTK_E_PAGE_NOT_BUILT ​

The content has a page and the build did not produce it — or a collection without pages of its own shows its entries on a page no build made: its shown_on page on contract 3, its prefix on contract 2.

What to do: Give the site a route for that path, or remove the page. A page nothing renders cannot be previewed or served. For a collection with route: "none", name in shown_on the page that shows the entries, or build one there (on contract 2, a pages: false collection's prefix is that page).

Said by: the build.

JTK_E_BUILD_REACH ​

The build asked for a host it may not reach. A build runs with no network of its own: the repository on github.com, the npm and yarn registries, the platform's media host and Google Fonts are forwarded, and nothing else is — GET and HEAD, with POST only for the clone.

What to do: Read the line in the build log: it names the request and the list. A dependency pinned to the registry needs nothing more; a dependency that downloads a binary from a release is one that is not on the registry, and the install fails on it by design. A font goes in the repository or through Google Fonts; anything fetched from a service at build time belongs in jtk/ as content, or is not a site of this shape.

Said by: the runner.

JTK_E_ROBOTS_DISALLOW ​

The build ships a robots.txt that keeps every crawler out.

What to do: robots.txt says Disallow: / for everybody. Every build is made for the site's address and serves it once the site is live; the preview is kept out of the index by the platform, not by this file. Allow crawlers and name the sitemap.

Said by: the build.

JTK_E_SITEMAP_EMPTY ​

The build ships a sitemap with no pages, or pages on another host.

What to do: sitemap.xml lists nothing, or lists addresses on a host that is not the one the build was made for (SITE_URL). List every page on SITE_URL, always — there is no build that should ship an empty sitemap.

Said by: the build.

JTK_E_CANONICAL_ELSEWHERE ​

The build says its canonical page is on another host.

What to do: The front page's <link rel="canonical"> names a host other than the one the build was made for (SITE_URL). Derive the canonical from import.meta.env.SITE, not from a constant: a canonical on another host hands the site's ranking to a page nobody can reach.

Said by: the build.

JTK_E_NOINDEX ​

The page tells search engines to go away.

What to do: The front page carries a noindex robots tag. Nothing in a page decides whether it is indexed: every build is made for the site's address, a preview is kept out of the index by the platform's own header, and a launch is a pointer moved. Take the tag out — and take out the switch that wrote it, because a switch somebody flips at launch is a site quietly telling search engines to go away, the most expensive mistake a studio makes.

Said by: the build.

JTK_E_SHARED_NOT_RENDERED ​

A shared field is rendered on no page at all.

What to do: Render it somewhere, or take it out of the shared document. A shared field nothing renders is a control that edits nothing.

Said by: the build.

JTK_E_ANNOTATION_UNKNOWN ​

A page: annotation names a page this site has not got, or a field that page's document has not got.

What to do: Check the address and the field key. A mistyped cross-page annotation is a tile the owner taps and nothing opens.

Said by: the build.

JTK_E_CONTENT_VARIANT ​

The site's code fails to build, or loses an annotation, on content an owner can write: every optional field empty, or every one filled and long.

What to do: Make the template take an optional field's absence — draw nothing, or a fallback — and a long value — let it wrap. The log says which of the two and what failed. An agent's build tries both because a save in the panel never fails a build: a person's build goes on and the studio reads the log, so the code has to be right before it is accepted.

Said by: the build.

JTK_E_CATALOGUE_MISSING ​

The repository has no schema: neither jtk/schema.json (contract 3) nor jtk/catalogue.json (contract 2, the older contract).

What to do: Commit one: on a new site npx @jtakeit/astro schema writes jtk/schema.json from src/content/blocks.ts. Nothing can check that a site's content is annotated without knowing what fields it has.

Said by: the build.

JTK_E_FORM_INCOMPLETE ​

A form posting to /api/lead is missing a control the enquiry's structure needs.

What to do: Every enquiry form has a name control, one of contact, phone or email, and the honeypot website. Without them the edge refuses every visitor as anonymous or unreachable, or every bot gets through.

Said by: the build.

JTK_E_FORM_FIELD_UNDECLARED ​

A form posting to /api/lead has a control the schema does not declare.

What to do: Declare it in asks on the block that carries collects: "enquiry", with a label — that is what lets the inbox, the notification and the export say what the value is.

Said by: the build.

JTK_E_FORM_UNDECLARED ​

A page has a form posting to /api/lead and no block on it says collects: "enquiry".

What to do: Put collects: "enquiry" on the block that carries the form. The launch gate that demands a destination for enquiries reads the schema, not the markup — a form nothing declares is one whose messages can go nowhere.

Said by: the build.

JTK_W_UNANNOTATED_FIELD ​

A value the owner edits — a phone, an email, a link, a choice, a date, an hour or a number — is on the page and carries no data-jtk-path: the owner taps it and nothing opens. Advice for now, for these kinds; a contract-3 build will refuse it as JTK_E_UNANNOTATED_FIELD once the kit's example draws them all. Advice too, of any kind, on contract 3, where a filled value's words are on no part of the built page: a field the template shows only on a condition — a label while another document has a value — is not refused on the build that hides it.

What to do: Annotate the element that draws the value, as for a heading: {...facts.at('phone')} on the link that shows the number, a date or an hour formatted as the page likes, with the field's path on its element. A value the page does not show is no_tap_target, beside the field it belongs to. A value shown on a condition: annotate it where it is drawn, and check a build where it is; one the template never draws is a field the owner edits for nothing — draw it, or take it out of the schema.

Said by: the build advice.

JTK_E_CACHED_FILE_CHANGED ​

A name a public build let browsers keep — under immutable or a cache directory of _meta.json — has other contents in this build while it is still held.

What to do: A browser cannot be purged: whoever has seen the site keeps the old file under that name for as long as the edge said, so the platform holds the name until the last of them may have let go — the served build's for as long as it is served and its lifetime after, and every earlier build's until its own hold runs out. The log names each file and when it is free; get_build and preflight list what is held. Give the new file a new name, with a version in it, and point the page at it. Lowering maxAge, dropping the file or rolling back frees nothing sooner: browsers already hold the old lifetime.

Said by: the store.

JTK_W_MODULE_TWIN ​

A page block types again a fact the bookings module already holds — the opening hours the owner keeps in the diary, or the prices the services carry — so the site has two copies and one of them goes stale.

What to do: Read the fact from where it lives: the hours from the bookings settings — jtk/modules/bookings.json, or jtk/bookings.json on contract 2 — which a save writes from the owner's, and the prices from the services collection the booking form reads. Drop the text rows from the block.

Said by: the advice.

JTK_W_MODULE_POST ​

An entry type the bookings module reads is shaped as a post — a body, or excerpt, cover and body together — or its services get a page each, so the panel draws a service or a table as an article with its own address.

What to do: A service is filled in, not written: short fields (a name, takes, costs, a line), no body, and route: "none" on the collection (pages: false on contract 2). A resource is a record the diary occupies — a name, its own hours, what it does, seats or spots — with a line and a photograph if the page wants them.

Said by: the advice.

JTK_W_KIND_UNKNOWN ​

kind in the bookings settings names a kind of business the platform has no dictionary for, so its bookings are spoken of in neutral words — «бронювання», «Забронювати».

What to do: Name an existing kind — the nearest one the modules reference lists, car_rental, hotel, restaurant and the rest — and write over the words that do not fit in words beside it (kits). A word of the site's own goes in words, not in a kind nobody knows. No kind at all speaks a salon's words (JTK_W_KIND_MISSING).

Said by: the advice.

JTK_W_KIND_MISSING ​

The bookings settings say no kind, so the bookings are spoken of in the salon's words — «запис», «майстер» — which is what every site before kinds existed spoke, and nothing changes for it. Said so that a business that is not a salon is not given a salon's words by omission.

What to do: Name the kind of business: one of the kinds the modules reference lists (salon, clinic, car_rental and the rest), the nearest one where none is exact, with the words that do not fit overridden in words (kits). A salon may say salon, or nothing. Nothing is refused.

Said by: the advice.

JTK_W_LOCALE_FALLBACK ​

The site takes bookings and its language (locale) is none of the eight the platform writes to customers in — uk, en, de, ru, es, it, pt, fr — so the letters to the customers and the messages to the owner go out in English. A region is read off first: de-CH is German, pt-BR Portuguese; pl or ka is English.

What to do: Nothing is refused: a site may be written in any language, and its letters are English. Tell the developer, so the owner is not surprised; the panel says it too, under Working hours. If the business writes to its customers in one of the eight, name that language as the site's. A booking keeps no language of its own: every letter speaks the site's.

Said by: the advice.

JTK_W_PAYMENT_UNCHECKED ​

The site takes money online for its bookings, and the self-check (preflight with self_check) never pays: what needs the money paid — a booking confirmed by its payment, moved, offered another time — was not walked, and neither was the payment itself.

What to do: Nothing is refused, and ready is not held back by it. Tell the owner the online payment was not checked, and check it by hand: a test booking paid with a test card on the preview, confirmed, then cancelled and refunded.

Said by: the advice.

JTK_W_WORD_UNKNOWN ​

A row of words in the bookings settings names a key the platform's dictionary does not have, so the word is said nowhere.

What to do: The keys are the dictionary's — letter.subjectConfirmed, diary.done, owner.new and the rest, listed in the modules reference. A typo in a key is a word that silently never appears.

Said by: the advice.

JTK_W_KIND_NO_DAYS ​

The bookings settings name the hours a stay goes out and comes back at (hand_out, hand_back), and not one of the services is sold by the day — the hours frame nothing, and it can only be booked by the hour, like a salon.

What to do: Give at least one service scale: daily — «Доба», «Ніч» — or leave its scale empty with the settings' scale: daily; the kit of the kind has them. Rates by the hour beside a daily one — a photo session and a day's hire of the same van — are the ordinary case and nothing is said about them. A business that hands a key over by the hour — a boat — says hands_over: true without the hours, and is not advised.

Said by: the advice.

JTK_W_KIT_BEHIND ​

kit and kit_version in a module's settings — the bookings' or the shop's — say which kit the site was laid out from and when, and the kit has changed since — a fix to it, or to a part it shares with other kits, that this site has not got.

What to do: Read the kit's page (jtakeit:///kits/<kind>.md, or /v1/kits/<kind>; the shop's kit is shop) and carry over what this business needs of what changed — the finding names the changes the kit records; then set kit_version to the version the finding gives. The site is yours: nothing is changed in it for you, and nothing is refused on this.

Said by: the advice.

JTK_W_UNPRICED_HOURS ​

A service priced by the hour of the week (rates instead of costs) is open, by the hours in the bookings settings, at hours none of its rows prices — and an hour nobody priced is not sold: the form does not offer it for this service, and a page that asks for it is refused.

What to do: Add a row for the hours the finding names, under the service's rates, or narrow the opening hours. A table copied from a website has a gap somewhere; this is where it is found rather than by a customer who could not book Tuesday noon. The panel says the same beside the rate, in the owner's language.

Said by: the advice.

JTK_W_DIARY_UNSET ​

The site takes bookings and its settings say no time zone (zone) or no opening hours (hours): until both are set the diary refuses every visitor — /api/availability and preflight's try_booking answer JTK_E_DIARY_NOT_READY — and the form shows «nobody has said which timezone this business keeps». A draft may be unfinished, so nothing is refused; this is said so the gap is not found by a visitor.

What to do: Set zone from the business's address — Europe/Zurich for Zürich — and hours from what the business publishes, in the bookings settings — jtk/modules/bookings.json, or jtk/bookings.json on contract 2; or leave them for the owner, under Diary → Opening hours, and say so. Then preflight with try_booking.

Said by: the advice.

JTK_W_SESSION_OUTSIDE_HOURS ​

A bookable's own hours — a class's times in a sessions kit, a master's or a room's own week — reach outside the business's opening hours that day, and the diary offers only the part inside them (it clips one to the other, as the panel's diary shades): a class at 18:00–19:15 on a day the business closes at 18:00 is offered never, and nothing else says why.

What to do: Widen the opening hours in the bookings settings — jtk/modules/bookings.json, or jtk/bookings.json on contract 2 — to hold the row, or move the row inside them. The finding names the row and the hours it meets. Advice, not a refusal: the hours are the owner's and the panel may already say otherwise.

Said by: the advice.

JTK_W_ADDON_ALONE ​

A service with no takes and a price is an add-on — shoes, a racket, a towel — taken only beside a timed service in one visit (wiki/70), and this site's bookings take one service per visit (combine off in the bookings settings), so nobody could take it.

What to do: Turn combine on in the booking settings, so a visitor picks the lane and the shoes together; or give the service a takes if it is a service of its own.

Said by: the advice.

JTK_W_OWNER_LOCKED ​

A field holding a date, an hour or an amount of money is not client_editable, so the owner cannot change it: the next event's date, the hour the doors open, a price — facts of the business that change on its calendar, and that the studio is then asked to change every time.

What to do: Make it client_editable: true. If it is not on the page — an hour a countdown counts to — give it no_tap_target: true and beside the field it belongs to. Leave it the studio's only when it really is the design's, and say so to the developer.

Said by: the advice.

JTK_W_HIDDEN_UNEXPLAINED ​

A field the owner edits is not on the page (no_tap_target) and names nothing it belongs to (beside) and says nothing about itself (hint): the panel shows it under More, at the foot of the editor of every field of its block, by its label alone, and the owner has to guess what it changes.

What to do: Put it beside the field the owner taps that it belongs to — a photograph's description beside the photograph, the hour beside the date — or give it a hint that says what it does on the page: «The countdown on the ticket counts to this hour».

Said by: the advice.

A link the page does not show (no_tap_target, a url or a key ending in href, link or url) names no field it belongs to (beside). The panel opens it under its button by the names alone — the words field named alike (cta_href with cta_label), or else the one field whose key says cta or button — and where that names one field, says which; where it names none or two, the link is under More with the block's other values, a step from the button it is about.

What to do: Say beside the key of the button's words: "cta_href": {"kind": "url", "no_tap_target": true, "beside": "cta_label"}. The finding names the field the panel would pick, or that it cannot.

Said by: the advice.

JTK_W_CONTENT_ORPHAN ​

A content file carries a block type, or a field, that the schema does not describe — text the panel cannot show and the build cannot annotate. Or a whole file sits where the site's contract keeps nothing: in a tree whose schema is jtk/schema.json, a page in contract 2's places, under jtk/content/, or settings at contract 2's jtk/<module>.json, which nothing reads.

What to do: Either the schema lost a block or a field the content still has (declare it again, or rename the content's key to the new one), or the content names a type this site never had. Import keeps it rather than dropping it; validate_schema by ref says it so the commit is not the first to find out. A file nothing reads: move what it says to where the contract keeps it — jtk/pages/, jtk/entries/<collection>/, jtk/modules/ — or delete it.

Said by: the advice.

JTK_W_CONTENT_BOUNDS ​

A value in a content file is longer or shorter than its field allows, or a list has more or fewer rows than it may — the panel will refuse to save the field as it stands, though the build serves it.

What to do: Shorten or lengthen the value to the field's min/max (the finding names the path), or widen the bound in the schema if the content is right and the bound is not. Nothing is refused on this; the owner meets it on the first edit.

Said by: the advice.

JTK_E_SCHEMA_UNREADABLE ​

jtk/schema.json is not JSON, or a value in it has the wrong shape — words where a number goes, a list where an object does. Nothing else in the file is read until it is.

What to do: Fix what the finding names: it says where, and what that place takes. The file is read as contract 3 because it says "contract": 3.

Said by: the schema, since contract 3.

JTK_E_SCHEMA_EMPTY ​

The schema declares no block types.

What to do: Declare the block types the site's pages are made of. A schema with no blocks describes nothing an owner could edit.

Said by: the schema, since contract 3.

JTK_E_SCHEMA_KEY_UNKNOWN ​

The schema says a key contract 3 does not have, at any depth: a typo, or a word of contract 2's that contract 3 replaced — business_facts, deprecated, a collection's prefix or body, option_labels, a view's sample. Every one is said at once, each at its place.

What to do: Remove it, or say it in contract 3's words: a collection's prefix, pages, listing and per_page are its route, its body is blocks, an option's words are its label in options: [{value, label}], a field is retired by removing it, and the business's facts are shared text with roles. A key is refused rather than dropped, so nothing is lost by being told.

Said by: the schema, since contract 3.

JTK_E_ROUTE_INVALID ​

A collection says nowhere, or somewhere that cannot be, where its entries are: no route, a detail without {slug} or that is no address, a listing with a slug in it, "none" with no shown_on, a pattern for a language the site does not have, or two collections whose entries would share addresses.

What to do: Give each collection a route: {"detail": "/works/{slug}"}, with "listing": "/works" and per_page where a page lists them — or "none" with "shown_on": ["/prices#{slug}"] for entries shown only on another page. A pattern written per language names the site's own languages and says what follows the language's prefix.

Said by: the schema, since contract 3.

JTK_E_REF_INVALID ​

A reference points nowhere, or where no reader follows it: a ref with no to, a collection named twice, an on_delete other than restrict and nullify, a ref written as contract 2 wrote it — or a group or a tree through a reference to several collections or several entries, which nothing groups by yet.

What to do: Write "ref": {"to": ["categories"]}, with "many": true for several entries. A group is a reference to one other collection, one entry each; a tree is a parent that is {"to": [<its own collection>]} and nothing more.

Said by: the schema, since contract 3.

JTK_E_SHARED_INVALID ​

shared names a block type the schema does not declare, or names one twice; or a field says a role that is not one of the list, sits outside the shared text, or says a role another field says already.

What to do: List in shared the block types the shared document holds. Give a role — name, phone, email, street, postal_code, city, region, country, maps, social, price_range, business_type, hours — only to a field of one of those types, and each role to one field: the business's structured data is built from them.

Said by: the schema, since contract 3.

JTK_E_ATTRIBUTE_INVALID ​

A field says an attribute its kind does not take, or a value the attribute does not have: localized on a kind with no language, integer on anything but a number, qualifiers on anything but money or besides from and on_request, an untranslated that is neither base nor hide.

What to do: Say localized on text, a picture, a link or a list; integer on a number; qualifiers of from and on_request on money; a collection's untranslated as "base" or "hide". Each may be left out, and then the kind's own answer stands.

Said by: the schema, since contract 3.

JTK_E_SKU_TAKEN ​

Two variants on the site share a SKU, compared without regard to case, hidden products included.

What to do: A SKU names one variant on the whole site: stock and orders are kept by it. Give the later variant its own SKU; FOX-S-RED and fox-s-red are one.

Said by: the schema, since contract 3.

JTK_E_PICKS_INVALID ​

A variant's picks do not name one value of each of its product's options, or two variants pick the same.

What to do: Name every option once, by its _key, with the _key of one of that option's values; a product without options picks nothing (leave picks out or {}). Two variants cannot pick the same values.

Said by: the schema, since contract 3.

JTK_E_PRODUCT_INVALID ​

A product is outside the shop's limits, or a customization lacks what its kind needs.

What to do: A product has 1 to 2,000 variants, and a value in each option. A choice customization has at least one choice, a text one a max of 1 to 500 characters, and choices belong to a choice alone; a yes_no is ticked or not, so it is never required — a buyer who must answer is asked a choice.

Said by: the schema, since contract 3.

JTK_E_UPCAST_INVALID ​

A block type's upcast says a step that cannot be one: from a version the type has not had (each step is from 1 up to one below the type's v), two steps from one version, a name that is not a field's, a rename of two fields into one, or a last step that writes, renames into or changes the rows of a field the type does not declare now — or drops one it still does.

What to do: One step for each older version content may still be written at, {"from": 1, "rename": {"heading": "title"}}, each making that version the next; the last one makes the block the type as it is declared now, so every name it writes is one of its fields. A version that changed nothing stored content feels still says its step, empty: {"from": 2}.

Said by: the schema, since contract 3.

JTK_E_PANEL_FORM_INVALID ​

An entry type's form — how the panel lays out its card and a new entry — cannot be drawn as written: it names a field the type does not declare, body, or one field twice; a row holds more than three fields, spans more than six columns, or shares what is left unevenly; a gallery, a list or a document shares a row; a paragraph, a gallery or a list stands in the aside; a widget is not one of its field's kind or does not fit it; a required field has no place (but for one a module's own card draws, which no form lays out); or form is on a block type that is no collection's type. The sentence says which, at its place.

What to do: A form is {"sections": [{"title": …, "note": …, "rows": [["title"], ["takes", "costs"]]}], "aside": ["photo"], "widgets": {"category": "segmented"}}, every key optional. A row is one to three keys, or {"field": "title", "span": 4} on a grid of six; a cell without a span shares what is left. Place every required field — all but the ones a module's own card draws, as the shop's product card draws variants and the rest of a product's options and Advanced; leave body out — it is written beside the page. The schema reference lists each kind's widgets.

Said by: the schema, since contract 3.

JTK_W_NOT_LIVE ​

The schema does not say render: "live": the template does not draw a draft at request time, so the owner sees a change in the panel's preview only after a build, and an entry's card cannot be previewed before it is saved.

What to do: Keep the scaffold's src/live/ and RENDER = 'live', and write every page so a server can draw it: content read through the door (site.*), pictures through the kit's helpers and the library, nothing in a page that only a build can do. Leave it out only where a page does at build what a server cannot and cannot be rewritten — and say why in BRIEF.md (the kit's docs/live.md).

Said by: the advice, since contract 3.

JTK_W_DATE_HIDES ​

The site's template compares an entry's date with the clock to choose what it shows — the next night, the ones left out, the ones marked past. A build freezes that comparison until the next build, a visitor sees what is over as ahead, and the panel, which cannot know, shows it as on the site. Said by the kit's jtk schema, from the site's code.

What to do: Declare ends_by on the collection — then: keep to keep past entries as an archive, hide to take them off — and read ended from the entries the door gives (site.entries(…)): the platform says when each is over and rebuilds the site then. A countdown in the visitor's browser is drawing, and may stay.

Said by: the advice, since contract 3.

JTK_W_PANEL_FORM_GUESSED ​

The panel placed fields of an entry type by itself: a form places no row for some — they are drawn after its sections, under More — or a type of seven fields or more says no form, and the panel lays them out in their order, short ones two to a row and pictures aside. The fields a module's own card draws are the exception: no form lays them out and the count leaves them out, so the shop's product type is not advised for its eight — and a form that places one of them is, since the panel leaves it out of the form all the same.

What to do: Say where each field stands: put the ones under More in a section's rows or the aside, or write a form that groups what belongs together — the price beside the length, the portrait aside, the words for the page under a title of their own.

Said by: the advice, since contract 3.

JTK_E_UNNAMED ​

A page or an entry has no id, or a block, a row of a list or a gallery's picture has no _key, that an annotation can name — an id is a lowercase UUID, a key a lowercase letter and then lowercase letters, digits and hyphens. Nothing in it can be annotated, so the owner taps it and nothing opens.

What to do: Run jtk schema (jtkit schema on another generator), which mints every name that is missing. One that is misspelt is renamed by hand, here and in every file that names it. The platform's own saves mint them, so only a file written by hand lacks one.

Said by: the build, since contract 3.

JTK_E_META_INVALID ​

The build's dist/_meta.json says what the platform does not read: it is not a JSON object, it holds drafts — which contract 3 removed — or a key other than redirects, immutable and cache, or one of those in a shape the platform would pass over.

What to do: Write redirects as [{"from": "/old", "to": "/new", "status": 301}], immutable as the directories whose files are named by their contents, and cache as [{"prefix": "/clips/", "maxAge": 86400}], and nothing else. Leave drafts out: which entries a visitor may not see is the platform's to say, from each entry's visible and its moments.

Said by: the build, since contract 3.

JTK_W_DRAWN_UNTAPPABLE ​

A value the owner edits is drawn as text where nothing answers a tap: under data-jtk-fixed, or under no annotation at all — the business's name in a © line, a postcode joined to its city. Matched as the whole value, four characters or more, on the pages its document is drawn on; the shared text's on every page of its language. Advice, never a refusal.

What to do: Draw it with its path ({...facts.at('postal_code')}), each value in an element of its own where two were joined; where it cannot be told apart, put the element in a region that names its source, data-jtk-from ({...facts.from()}), so a tap opens the source. Words that only look like the value — the design's — are left as they are.

Said by: the build advice, since contract 3.

JTK_W_TEMPLATE_DESIGN ​

The site's design path is custom — the person gave their site or sites they like and wants a design of their own (create_site's design) — and the site still wears the template's design: more than 60 % of the scaffold's design files (its components, styles and layouts, the forms and the kit's galleries, motion and helpers aside) are byte for byte the kit's, or its hero, header and footer all are. Recoloured tokens are not a custom design. Counted on every build (design in the build's answer: untouched, of, the files); said only where the path is custom. Advice, never a refusal.

What to do: Rewrite the hero, the header, the footer, the sections and their composition from DESIGN.md — the short design brief at the site's root, written from the person's site and the references: palette, type pairing, grid and spacing, how photographs are treated, the sections' rhythm, motion (the kit's docs/compositions.md is the vocabulary) — and delete the template's files the site no longer draws. Or, if the person accepts the quick template adapted, tell them exactly that: never call a recoloured template custom.

Said by: the build advice, since contract 3.

JTK_W_DESIGN_AXES ​

The site's design path is custom and jtk/design.json chooses fewer than ten of the fourteen axes — a choice is a line of three words or more, what and from where; a tag like split or linen is not one — the hero, the ground, the measures, the shape, the header, the phone's menu, the overlap, the surfaces, the mark, the motion, the fonts, the hook, the proof, the contact — or no mark. Where the site shows directions, the first one's axes are counted. A design nobody chose on falls back on what a model reaches for first. Advice, never a refusal.

What to do: Choose on every axis of the design guide (docs/guides/design.md, «The axes») from the business's own material — the mark first: a motif from their material, repeated in the interface — one short line per key under axes, and the reasons in DESIGN.md.

Said by: the build advice, since contract 3.

JTK_W_DIRECTIONS_ALIKE ​

Two of the directions in jtk/design.json's directions differ on fewer than three axes, or not on the hero: the person is shown one design in other colours and asked to choose. Advice, never a refusal.

What to do: Make each direction a design of its own — another hero, another shape, other surfaces, another mark — at least three axes apart, the hero among them; write each direction's choices under its axes.

Said by: the build advice, since contract 3.

JTK_W_FIRST_SCREEN ​

On the home page the heading or the first action ends below the first screen — a phone 390 × 844 or a desktop 1280 × 800 — so a visitor sees a picture and not what the business does or how to book it. Measured in a browser by preflight (the floor's F8). Advice, never a refusal.

What to do: Bring the heading and the one action onto the first screen at both widths: a shorter picture above them, the words over the photograph, or the photograph beside the words; get_built_page with shot shows the fold.

Said by: the advice, since contract 3.

JTK_W_ANCHOR_LANDING ​

A link in the home page — the header's #angebot, #kontakt — scrolls its target to where its first words land more than 96 px below the header, across the section's own top padding, or under the header. The visitor arrives at air, or at a cut heading, and scrolls again. Measured in a browser by preflight at a phone's and a desktop's width. Advice, never a refusal.

What to do: Give each target scroll-margin-block-start: the header's height and a little air, less the section's top padding — the kit's layout writes --header-h — so the first words land just under the header; or put the id on the section's heading instead of the section.

Said by: the advice, since contract 3.

JTK_W_SCREEN_FIT ​

On a desktop (1280 × 800) a section of the home page is a little taller than the screen under the header — by less than a third — so it is never seen whole; or a form, with its heading, is taller than that screen and its button is out of sight while it is filled. Measured in a browser by preflight. Advice, never a refusal.

What to do: Tighten the section to a screen: a shorter picture, less padding, two columns. A form: fields side by side, a shorter message box, the lead beside the form rather than above it. A section long on purpose — a price list, a journal — is left as it is.

Said by: the advice, since contract 3.

A wall of four or more pictures on the home page ends ragged: its columns end more than 24 px apart — a masonry of mixed proportions, or a last row left half empty. Measured in a browser by preflight. Advice, never a refusal.

What to do: End the wall on one line: rows of one height (each picture its own width), one proportion for every picture, or one picture spanning two cells to fill the gap; or fewer pictures, a count the columns divide.

Said by: the advice, since contract 3.

A button on the home page — the header's «book» — opens another page of the site at its top, and that page's booking form starts more than half a screen down: the visitor who asked to book scrolls to find it. Measured in a browser by preflight. Advice, never a refusal.

What to do: Link the button to the form itself: the page and the form section's anchor — /services/#book on the kit's price page; give the section an id where it has none.

Said by: the advice, since contract 3.

JTK_E_DOCUMENT_INVALID ​

A document under jtk/pages/, jtk/entries/ or jtk/modules/ is not where it says it is, or not what contract 3 writes: a page without its name, a path, collection or slug that disagrees with the file's place, no id or a block, row or picture without a _key, a key a document does not have, seo on an entry with no page of its own, a shown_on page that is not there, a folder or a segment named media, a value in contract 2's shape (a price as a bare number, a picture as its key, a reference by slug), a reference naming an id no entry of its collections has, or a module's settings that are not {v, settings}.

What to do: Fix the file where the finding points; a reference to an entry that is not in the tree is refused (on_delete is restrict), so put the entry back or take its id out. An entry deleted in the panel is taken out of every reference to it by the deletion itself, and the files that named it come with the next save — pull before you push; an entry deleted in the tree leaves them to you. A page is {id, path, name, seo?, blocks} at jtk/pages/<path>.json, an entry {id, collection, slug, visible, fields, blocks?} at jtk/entries/<collection>/<slug>.json, a module's settings {v, settings} at jtk/modules/<module>.json; every block, row and picture has a _key, a price is {"minor": 4500}, a picture {"src": …}, a reference the entry's id. jtk schema (jtkit schema on another generator) mints the ids and keys a file lacks.

Said by: the platform, since contract 3.

JTK_E_BLOCK_BEHIND ​

A block in a document says a v its type's steps cannot bring to the type's own: an older version with no upcast step from it, or a version newer than the schema's type — content written against a schema that has not arrived.

What to do: Declare the step from that version in the type's upcast (the finding names the block, its v and the type's), and the platform brings the block up when it reads it and the next save writes the current v — or rewrite the block in the current shape and give it the type's v. A block newer than its type is a schema that was not pushed with its content: push them together.

Said by: the platform, since contract 3.

JTK_E_CURRENCY_SET ​

A contract-3 tree's jtk/site.json says a new currency: neither the site's own nor the one the platform's last save wrote there. An import takes the currency from that file only while the site has none — as create_site takes it in currency — and once a site has its currency, a person changes it in the panel. A branch still carrying the last save's currency, from before a person changed or cleared it, is not refused: it is left, and the next save writes the site's.

What to do: Write the site's currency there (get_site says it), or leave currency out of jtk/site.json. If the prices really are in another currency, ask a person to change it in the panel — The site → The business, the currency — which asks first on a site with prices; the next save writes it into the file. validate_schema says this before the import does, in both its forms: by site and ref, or with the tree as text — schema, and files with jtk/site.json — and the site in site_id. Where the site's code is on jtakeit, push_code's push is the import, so send the text with site_id before it: without a site there is no currency to hold the file to, and nothing is said.

Said by: the platform, since contract 3.

JTK_E_SKU_ORDERED ​

A variant whose SKU a paid order named lost it, or the SKU was given to a variant it was not named for. Stock and orders are kept by the SKU, so a SKU an order named sits only on a variant it was named for, or on none, and a variant an order bought carries one of the SKUs orders named for it: the save, import_branch and validate_schema (by site and ref, or with the tree's files and the site in site_id) refuse the draft or the tree that moves it, naming the variant. A checkout never paid, one that lapsed and a test order name no SKU; an order gone at its retention names none either.

What to do: Keep the SKU on its variant — or, where orders named the variant under more than one SKU, any one of them — and give any other variant that has it a SKU of its own; a variant that is not to be sold is taken off sale (on_sale: false). A variant or a product may be removed, and a product hidden, and their SKUs are never given to another variant. No tool reads orders, so the finding is how an agent learns which SKUs an order named; a variant no order has bought may be changed freely.

Said by: the platform, since contract 3.

JTK_E_TRANSLATION_SHARED ​

A translation — <name>.<locale>.json beside its original — says a value that is the same in every language: a price, a number, a date, a choice, a reference, a phone number, a link, a picture's file, focus or poster. A translation holds only the words; the translation of a shared value is the original's, everywhere, so a photograph changed in one language is changed in all of them.

What to do: Take the value out of the translation and keep it in the original. If the value really differs per language — a photograph with words on it, a link to a page in that language — say localized: true on the field in jtk/schema.json; a text that is a name and never translated says localized: false.

Said by: the platform, since contract 3.

JTK_E_TRANSLATION_RECORD ​

A translation's translated holds a record that is not one. A record is {from, by, at} under a value's path in the file — from the eight hex digits of the digest of the original's value the translation was made from, by person, agent or machine, at a moment in RFC 3339 — and nothing else. A record whose from is empty is read as none: a value whose original is empty has nothing it was made from.

What to do: Leave the record out — or translated whole: the import records each value the translation gives as made from the original as it stands, by the agent, and keeps the record it wrote for a value you did not change, which is how an outdated value stays outdated until it is translated again. Write a record yourself only to say who made a value, with the digest the platform wrote.

Said by: the platform, since contract 3.

JTK_W_TRANSLATION_ORPHAN ​

A translation gives words to a block, a row of a list or a gallery's picture by a _key its original has not got — removed in the original, or a key misspelt. Its words are shown nowhere, and the next save leaves them out of the file; the history keeps them.

What to do: If the original lost the block, the row or the picture on purpose, take its words out of the translation. If the key is misspelt, write the original's: a translation names what it translates by its _key, never by its place.

Said by: the advice, since contract 3.

JTK_E_MACHINE_OFF ​

Translate, in the panel's languages, asked a deployment that translates nothing by machine: it has no DeepL key — staging until a person sets one, production until DeepL is named in the data processing agreement — or the site's other languages are copies (contract 2) rather than translations of one original.

What to do: Nothing an agent does: the machine is a person's, in the panel, and an agent is a translator in its own right — write the translation into <name>.<locale>.json beside its original, and the import records it. A person in the panel translates by hand meanwhile.

Said by: the platform, since contract 3.

JTK_E_MACHINE_ALLOWANCE ​

The site's machine translation allowance is not enough for what was asked: a paid site's 30,000 characters of a calendar month, a demo's 10,000 once. What the cache already holds costs nothing and is not counted; everything sent to DeepL is.

What to do: Translate fewer texts at a time, or by hand — the line's own field — which costs nothing; a paid site's allowance starts again on the first of the month. An agent translates in the files and never through the machine.

Said by: the platform, since contract 3.