What you are buying, and what you are not.

Clause 1

What is delivered

One payment of 199 USD buys a licence to one repository of files. It is not a service, not a subscription, and not an account. You get no login, no dashboard, no hosted runner, and no uptime commitment, because nothing runs on the seller's side for you to log in to.

• Layer contracts 13 written layer specifications, L00 intake through L12 monitor, each declaring what it may read, the single artifact it must emit, its algorithm, its execution class, and its failure modes.
• Sprint stages 7 GEO sprint stage specifications for the recurring post-launch track, with their own agent prompts.
• Agent prompts The verbatim executing-agent prompt for every layer and every sprint stage, as files in the repository, plus 4 vendored claude.ai/design prompts for the manual design step.
• The gate suite 395 machine-evaluable gates across 20 gates.json files, each with a stable id and a written rationale showing the arithmetic behind its threshold, plus the assertion library those gates are evaluated by.
• The awp CLI A Python command line tool: run state machine, gate evaluation, prompt emission, an append-only decision log, a fleet keyword registry, and a working domain engine that performs live RDAP lookups against the .com registry.
• Documentation Architecture, layer contract, sprint contract, GEO sprint guide, design workflow, an operating manual, and the commercial analysis this page draws its risk statements from.
• verify.sh The self-check script that reports the repository's own state and exits non-zero if the tree is inconsistent. It is how you check, in minutes, that you received what was described.

The files reach you after payment by PLACEHOLDER: delivery mechanism, for example a download link or a repository invitation. Delivery is of files and nothing else. Nothing is installed, configured, or run on your behalf.

The state of the product is stated here, before you pay. Every layer contract is written and every gate is evaluable. No end-to-end run of the pipeline has been completed, and no demo site exists, because showing a site built some other way would be a fabrication. You are buying a specification, a gate suite, and working code, in the state this website describes, and you can verify that state yourself before the refund window closes.

Clause 2

What is not included

Every line below is a cost you pay to somebody else, or a thing that does not exist. None of it is bundled, discounted, or arranged on your behalf.

• NOT INCLThe domain. You buy the .com yourself, from your own registrar, on your own payment method, and you own it. The seller never registers, holds, transfers, or renews a domain for you.
• NOT INCLHosting and DNS. GitHub and Cloudflare accounts are yours, opened by you, governed by their terms, and billed to you if you exceed a free tier. The seller has no access to them.
• NOT INCLModel API credits. The generative layers spend tokens on your key, billed by your model provider. No credits, allowance, or discount is included, and the seller has no control over your provider's prices, rate limits, or acceptable use terms.
• NOT INCLA Claude subscription. The manual design step runs four vendored prompts at claude.ai/design, which requires your own subscription.
• NOT INCLKeyword and SERP data. Any keyword volume, difficulty, or SERP data is your own API subscription, billed to you. Without it, the layers that consume that data hold nulls rather than numbers, which the gates treat as unknown rather than as zero.
• NOT INCLSearch Console and analytics accounts. Yours, verified by you, in advance.
• NOT INCLAny done-for-you work. No site is built for you. The manual design step in particular is one to four hours of your own attention per site and does not become automatic because you bought this.
• NOT INCLA support commitment. See clause 8. None is sold, and the price reflects that.

The total of these external costs is not stated anywhere on this site, because it has not been measured. The repository's own cost model is written as formulas with every price left as a variable, and its one worked example is labelled as illustrative assumptions only.

Clause 3. The most important clause on this page

The refund policy, and what it is measured against

The refund question is whether the software is what this site describes and works as specified. It is never whether your website ranked.

What a refund is decided on

If you ask after the fourteen day window, the question is about the pipeline and the software, never about the outcome. Four conditions qualify.

• REFUNDThe repository is not what this site describes. Files, layers, gates, or the CLI are missing or materially different from what is stated.
• REFUNDThe software does not run as specified. verify.sh fails on a delivered tree, the CLI does not execute on a supported Python version, or documented commands do not do what the documentation says they do, and the problem is in the delivered files rather than in your environment or credentials.
• REFUNDThe gates do not evaluate. A gate cannot be evaluated because its assertion is missing from the library, or a gates file does not parse. The pipeline is sold on the property that gates run and that an unevaluable blocking gate halts the layer, so a gate suite that does not run is a defect in the thing sold.
• REFUNDDelivery failed. You paid and did not receive the files.

What a refund is not decided on

These are outcomes, and no outcome is sold here. A refund is not available on any of these grounds, at any point, because none of them was ever promised.

• NOYour site did not rank. No ranking is promised anywhere in this product, on this site, or in the repository.
• NOYour site got no traffic, or not enough of it. No traffic figure is promised, forecast, or implied.
• NOYour pages were not indexed, or were indexed and then dropped. See clause 4. Nobody controls this, and no seller who tells you otherwise is describing how search engines work.
• NOYour site earned no revenue. Revenue depends on your niche, your offer, your demand, and your execution, none of which are in the files you bought.
• NOA gate failed your run, or the pipeline halted. A gate that halts a layer is the product working. The gate suite is designed to fail runs, including the seller's own demo run, and a halted layer is the software doing exactly the job it is sold to do.
• NOYou do not want to do the manual design step, or found the terminal work harder than expected. Both are described in detail before purchase, in the prerequisites and in the FAQ.
• NOYour model, keyword data, hosting, or registrar costs were higher than you expected. Those are your suppliers, priced by them, and no estimate of them is given here.

Why the policy is drawn this line and not another

A guarantee attached to an outcome the seller does not control is not a guarantee. It is a liability hidden until month three, and it is the reason this category has a credibility problem. The seller controls whether the specifications are complete, whether the gates evaluate, and whether the code runs. The seller does not control whether Google indexes your pages or ranks them, so tying a refund to that would be selling something nobody can deliver.

This position is stated here, before purchase, deliberately. It is not disclosed in a support ticket after the fact.

How to ask, and what happens next

Send one message to the contact address in clause 11 stating the order reference and the date of purchase. Inside fourteen days no reason is needed. Outside fourteen days, describe which of the four refundable conditions above applies, and include the output of ./verify.sh and of the failing command, because in a gated pipeline that output is usually enough to answer the question on its own.

Refunds are issued through the original payment method by PLACEHOLDER: payment processor and merchant of record, which may hold the refund obligation and may impose its own timing. If something has gone wrong, ask for a refund before opening a chargeback: a refund can be issued immediately, and a chargeback cannot be reversed once filed.

Nothing in this clause is intended to reduce a statutory refund or cancellation right that applies to you as a consumer where you live. Digital goods delivered immediately are treated differently in different jurisdictions, and this is one of the specific points a lawyer must review before this page is published.

Clause 4

No outcome is guaranteed. Not traffic, not rankings, not indexation

No traffic, no ranking position, and no indexation is promised by this product, ever, in any channel, at any price.

Nobody can compel indexation. A search engine indexes a subset of what it crawls, and provides no mechanism to force inclusion. Submitting a sitemap through Search Console, or a URL through IndexNow, is a request. It is not an instruction, and it is not a guarantee that anything will be crawled, indexed, kept in the index, or shown to anyone. A technically flawless site can sit at partial or zero indexation indefinitely, and no amount of pipeline correctness changes that. Zero indexed pages at day 30 is a real and reportable measurement, not a defect in the software.

Ranking is not something this product touches at all. The pipeline produces no off-site signal whatsoever. It generates no backlinks, no mentions, no coverage, and no distribution. Ranking is limited in large part by authority and external signal, and nothing in layers L00 through L12 produces either. The repository's own commercial analysis names this as the single most likely reason the product disappoints a buyer: you get a technically correct, well-structured, indexable site, and day 90 arrives with almost no clicks. That analysis ships in the files you are buying and is quoted on the sales page rather than hidden in it.

The monitoring layer does something narrower instead. It reports measured Search Console coverage and measured performance data with sources and no probability language. It does not forecast. It does not estimate what your traffic will be. Where a value is unknown it emits null rather than a flattering default, which is the same rule the whole gate suite is built on.

So the decision comes down to one thing. If you are buying this in order to obtain traffic, rankings, or indexation, you are buying the wrong thing, and the seller would rather you did not buy it. If you are buying it because a specified, gated, auditable build process is worth 199 USD to you on its own, independent of how any individual site performs, then the product can deliver exactly that and the refund policy in clause 3 backs exactly that.

Clause 5

No base rate is claimed, because none has been measured

There are currently no customers. No reviews, no testimonials, no case studies, no revenue figures, and no measured distribution of outcomes exist, because nobody has run this pipeline enough times to produce one. No end-to-end run from intake through indexation has been completed by anyone, including the seller.

Therefore no base rate is claimed anywhere: not for indexation, not for time to first click, not for cost per page, not for hours spent at the design step, and not for results at day 90 or day 180. Every duration quoted on this site is labelled as a planning estimate, and every cost is written as a variable rather than a number.

If you ever encounter a page for this product showing a customer count, a testimonial, a rating, a revenue screenshot, or an outcome statistic, treat it as fabricated, because as of the date of these terms there is nothing real to draw one from.

If measured outcome data ever exists, it will be published as a distribution with its sample size stated, and it will not be published as a promise. Numbers measured across other people's sites would still not be a prediction about yours.

Clause 6

What the licence lets you do, and the one thing it does not

On payment you receive a perpetual, worldwide, non-exclusive, non-transferable licence to use the repository. You are not buying the copyright in it. One payment, one repository, yours permanently: there is no licence server, no seat count, no renewal, and no expiry. If your access to the delivery mechanism lapses, that does not end your licence to the copy you already hold.

You may

• YESUse it to build sites for yourself, as many as you like, with no per-site fee and no reporting.
• YESUse it for client work. The agency and the freelancer are two of the intended buyers. Sites you build for clients are yours and your client's, and the seller claims nothing in them.
• YESModify anything. Rewrite the specifications, change thresholds, add or remove gates and assertions, fork the CLI, replace the model, replace the deploy target. It is a repository of text and code, and it is intended to be edited.
• YESUse it inside one organisation. If you bought on behalf of a company, that company's employees and contractors may use it on that company's work and its clients' work. No seat is counted, because counting seats would require a licence server nobody wants.
• YESKeep everything you produce with it. Domains, content, code, and sites generated by your run are yours. The seller asserts no ownership over your output and no right to use it as a reference or an example without your permission.

You may not

• NORedistribute the repository, or any substantial part of it. That includes the layer specifications, the agent prompts, the design prompts, the gates files, the assertion library, the CLI source, and the documentation, whether unmodified or edited. Do not publish it, post it, upload it to a public or shared repository, attach it to a forum thread, or hand it to anyone who has not bought it.
• NOResell it, sublicense it, or repackage it. Not as a product, a template, a course, a bonus, a lead magnet, a paid community asset, or a bundle, whether modified or not.
• NODeliver the repository itself to a client. Selling sites built with it is expressly allowed. Handing the client the pipeline is a redistribution and needs its own licence, which the client can buy at the same price you did.
• NORemove or alter the authorship and licence notices in the files, or present the specifications as your own work when redistributing derivatives to third parties.

Client work is the common question, so here is the answer precisely. The line runs between output and tooling. The sites, the content, the domains, the configuration, and the audit trail from your runs are yours to sell, transfer, or hand over. The pipeline that produced them is licensed to you, not to your client.

A candid note on enforceability

The product's own analysis says this in plain terms and it is repeated here rather than softened: at this price point, licence terms on a repository of text are effectively unenforceable, and one buyer with a public copy ends any exclusivity. That reality is priced into 199 USD. It is a description of the seller's exposure, not an invitation, and the terms above are the terms regardless.

Clause 7

Search engine policy exposure, and your responsibility for what you publish

You are responsible for the content you generate and publish, and for whether it complies with the policies of the search engines you want it to appear in. That responsibility is yours alone, and it cannot be transferred to the seller by buying a tool.

Scaled content produced primarily to manipulate rankings is precisely what search engines are built to discount. That is not a hypothetical. Major search engines have explicit policies covering scaled content abuse, and they apply whether the content is written by a person, generated by a model, or produced by a pipeline like this one. Volume produced for the purpose of ranking, rather than for the purpose of being useful to someone, is the specific behaviour those policies target. Owning this repository does not exempt anything you publish from them.

The correlated version of this risk is the one people miss. The danger is not only that a single page or a single site attracts an action. Sites produced by one pipeline can share a fingerprint: the same template lineage, the same section structure, the same internal linking pattern, the same hosting footprint, the same deploy signature, and a similar publishing cadence. A pattern-level action does not arrive one site at a time. It can arrive across many sites at once, and no mitigation in this or any product removes that possibility.

The pipeline's countermeasures are real, and they are partial. The specifications include an information gain gate that fails a page restating the top results without adding a distinct fact, dataset, tool, or perspective; a requirement for at least one non-reproducible element per site; a hard cap on pages per site; and an instruction never to share hosting accounts, analytics identifiers, or contact details across sites. These are design decisions rather than disclaimers, and they reduce exposure. They do not eliminate it. No mitigation makes scaled content safe, which is why the documentation's own advice, when a site has no genuine differentiator, is to stop before deploying rather than to generate harder. That decision is yours to make on every run.

Four more things are yours to handle, and the seller can neither see nor control any of them.

• The accuracy, legality, and originality of everything you publish, including anything a model produced on your key. A model can generate a claim that is confidently wrong, and checking it is your job before it goes live.
• Not infringing trademarks, copyright, or prior rights, including in the domain you choose. The domain layer's own gates refuse to certify a shortlist for purchase when trademark and prior use screening has not been run, and that is a warning to act on rather than a screening service being provided to you.
• Compliance with the terms of every third party you use: registrar, host, DNS provider, model provider, keyword and SERP data provider, and analytics provider. Some of those terms constrain automated or high volume use, and they change.
• Any disclosure, privacy, advertising, affiliate, or consumer protection obligation that applies to the sites you publish, in whichever jurisdictions they reach.

The seller cannot and does not indemnify you for a manual action, an algorithmic demotion, a deindexation, a registrar or host suspension, a takedown, a third party complaint, or any legal claim arising from what you publish. If your site is actioned, the seller cannot appeal it, cannot escalate it, and has no relationship with any search engine that would help.

Clause 8

Support, updates, and availability

No support commitment is sold at this price. Questions are answered asynchronously, on a best effort basis, with no response time promised and no guarantee of an answer. If you need synchronous help, screen sharing, onboarding, or someone to work through a failing run with you, this product does not include it and no amount of it substitutes for it.

No updates are promised either. You receive the repository in the state this website describes, permanently. If updates happen you will receive them, and that sentence is a description of intent rather than a commitment, because a promise of future work cannot be verified at the moment of purchase and this product is not sold on unverifiable claims.

Nothing is hosted for you, so nothing can be up or down, and no availability commitment is given. This website itself carries no uptime commitment either, and your licence does not depend on it remaining online.

The product depends on third parties who may change. Model providers change prices, rate limits, capabilities, and acceptable use terms. Hosting and DNS providers change free tier limits. Registry and keyword data endpoints change. Any of these can make part of the pipeline more expensive or require you to change how you run it, and none of them is under the seller's control. The code is written to keep those things configurable rather than hardcoded, which reduces the work of adapting but does not remove it.

Clause 9. Flagged for legal review

Liability, in plain words

The repository is licensed as it is. The seller's intent, stated plainly rather than in the usual capital letters, is this: the seller's total liability arising from this sale is limited to the amount you paid, which is 199 USD, and the seller is not liable for losses that follow from what you do with the files. That includes lost traffic, lost rankings, lost revenue, lost profits, wasted spend on domains, hosting, model tokens or data subscriptions, time spent on a site that did not work out, or a search engine action against a site you published.

Two carve outs, because they are the honest ones: nothing here is intended to exclude liability for fraud or for a deliberate misstatement about what the repository contains, and nothing here is intended to exclude a liability that cannot lawfully be excluded where you live.

This clause in particular is a plain-language statement of intent written by a non-lawyer. Limitation of liability language is jurisdiction-specific, is frequently unenforceable when drafted informally, and interacts with consumer protection law. It must be reviewed and rewritten by a qualified lawyer before this product is sold.

Clause 10

Seller, payment, governing law, and changes to these terms

• Seller PLACEHOLDER: legal name, trading name, registered address, and any company or tax registration number required in the seller's jurisdiction
• Price and currency 199 USD, one payment. No subscription, no renewal, no per-site fee, and no automatic charge of any kind. Taxes are handled as described by the payment processor at checkout, and any tax shown there is additional to the price stated here unless the checkout says otherwise.
• Payment PLACEHOLDER: payment processor and merchant of record. That party's own terms apply to the payment itself, and it may be the party that processes any refund under clause 3.
• Governing law PLACEHOLDER: governing law and venue. This must be set by a lawyer, and it does not override consumer protection law that applies where the buyer lives.
• Changes These terms may be revised for future sales. The version in force for your purchase is the version published on this page on the date you paid, and a revision does not change the deal you already made. Keep a copy if it matters to you.
• Severability If any clause here turns out to be unenforceable, the rest is intended to remain in force.

Precedence, stated because this product is sold on verifiability: where this page and the repository's documentation disagree about what the software does, the repository is the authority and this page is stale. Where this page and any marketing statement disagree about traffic, rankings, or indexation, this page governs, and no marketing statement promising any of those three was ever authorised.

Clause 11

Contact

If you are reading this on a published site and the placeholders above are still visible, the page has not been finished and you should not treat it as a live offer.

The one sentence worth carrying away

You are buying a specified, gated, auditable build process for 199 USD, refundable on whether it is what this site says and whether it runs, and never on whether a search engine chose to index or rank anything you made with it.