FolioU6Unit 6
As at
Sun 22 Nov 2026
Entries
12
Not yet
11
Page seal CA34, 260°07′. Drawn from the SHA 256 of this page’s source textCA34
Page sealCA34, 260°07′

Payment Page Script File

Quality gate (target)
Sat 23 Jan 2027
First sale (target)
Mon 25 Jan 2027
Turnaround
Not yet: set from measured Bench runs1

Unit 6. A checkout page loads scripts from many places: analytics, chat, tag managers, the payment form itself. Each one can read what a customer types. We list every script on the checkout with the business reason it is there, write the page settings that hold the page to that list, and write a memo on what the evidence shows about the merchant's card self assessment. At launch this job runs in runbook mode: AI agents load the page, write each step and test the result; your developer applies each change; we do not log in to your systems. At launch, a second AI model from another company and a named reviewer under contract will check every job.2 Launch price: 392 USD per checkout direct; agencies that resell it pay us 256 USD (wholesale) and set their own price to you. Full price, once we can make the changes ourselves: 490 USD direct, or 320 USD wholesale.

Quality test (Bench) gate: Sat 23 Jan 2027 (target). Not yet: Bench gate passed and sealed3 Until it passes, this unit is not on sale to anyone outside the firm.

Why now

Card rules give small online merchants a short self assessment form, SAQ A, when all card entry is handed to a payment provider. The PCI Security Standards Council now asks SAQ A merchants to confirm that their site "is not susceptible to attacks from scripts" (S45). Merchants meet that question at their yearly self assessment, so demand comes merchant by merchant through the year.

What we do

  • Inventory. Load the checkout and list every script it runs, with where it comes from and the business reason the merchant gives for it.
  • Content Security Policy. Write the page header that tells the browser which script sources may run, for your developer to apply. Anything not on the list is blocked.
  • Integrity tags. On each outside script served as a fixed file, write the tag that makes the browser refuse the file if it changes, for your developer to apply.
  • A written memo on SAQ A eligibility, from the evidence. The memo is the firm's reading of the evidence. It is not an assessment by a Qualified Security Assessor (an assessor certified by the PCI Council), and the merchant still answers its own form.
  • Retest and a signed file.

Change detection after delivery is part of Closure Watch, sold apart. Closure Watch carries Unit 6 change detection only after this gate passes.4

How it is accepted

  • Inventory complete. Every script the checkout runs in a test load is in the inventory, with a business reason.
  • Policy present. The checkout sends a Content Security Policy whose script sources match the inventory, and allows inline script only by a one time token or a hash of that script.
  • Integrity on fixed files. Every outside script served as a fixed file carries an integrity tag. A script that changes by design is listed with its reason.
  • Nothing unlisted runs. A fresh test load runs no script outside the inventory.
  • Memo on file, with the evidence it rests on.

Warranty

Proposed: we redo the work free until every acceptance test passes.5

Runbook mode

The merchant's developer applies the header and tag changes from our runbook. We hold no write access to the site. At launch every order runs this way; we make changes ourselves only once insurance that covers AI agent work is in place.6 Runbook mode is the launch price, 20 percent under the full price.

Price

The firm's own prices, in US dollars.

Launch priceLaunch price, through a partnerFullFull wholesale
Per checkout392 USD256 USD490 USD320 USD

Full: full price (once we can make the changes ourselves); Full wholesale: full price, wholesale (through a partner, once we can make the changes ourselves).

Tier shares apply by the client's region. Unit 6 is part of Public Perimeter Plus with Units 1, 2 and 3, from the same gate. Payment is taken in full at order.7

What the buyer gives

  • The checkout address, and a test path through it that uses no real card.
  • The business reason for each script, where the merchant knows it.
  • A developer who applies the runbook.
  • The name of the payment provider that takes card entry.

What the buyer gets back

  • The script inventory, with source and reason per script.
  • The policy header and integrity tags, ready to apply.
  • The SAQ A memo, with its evidence.
  • A signed file of the before and after test loads.8

Who checks it

AI agents load the page, build the inventory, draft the policy and memo, and test the result. At launch the merchant's developer applies each change, and we do not log in to the merchant's systems. A second AI model from a different company checks the work.9 At launch, a named reviewer under contract will review and sign every job.10 Is client data used to train AI? No, unless the client ticks a consent box that allows it.

The Bench

40 graded cases on checkout pages built for the purpose. No client data. Result: Not yet: cases, pass rate, date11

Sources

The spec file

Version 0.1.0 · Status: draft

The machine readable spec of this unit. Download it and hash it yourself: the seal below is drawn from its SHA 256.

Acceptance tests in the spec

  1. 01script_inventory_completeEvery script the checkout runs in a test load along the given test path is in the inventory, with a business reason.page load
  2. 02csp_matches_inventoryThe checkout sends a Content Security Policy whose script sources match the inventory and that allows inline script only by nonce or hash.page load
  3. 03integrity_on_fixed_filesEvery outside script served as a fixed file carries an integrity attribute; a script that changes by design is listed with its reason.page load
  4. 04no_unlisted_scriptA fresh test load runs no script outside the inventory.page load
  5. 05saq_a_memo_on_fileThe SAQ A memo is on file with the evidence it rests on.firm record
Seal of this unit’s spec file8D4F

Spec U6 0.1.0, 8D4F, 056°34′

8d4f2839 7486fbcc 238ad7f6 1aaaee7f 89706524 0cce2d28 5f00ba0b 6a842240

Download the spec file

Not yet in place11

Nothing is on sale yet; each numbered mark on this page points to a condition below. Every condition, with its state, is on the status board.

  1. 1set from measured Bench runs
  2. 2second model vendor connected; two contracted reviewers, target Mon 30 Nov 2026
  3. 3Bench gate passed and sealed
  4. 4Unit 6 gate passed; Closure Watch Bench gate set and passed
  5. 5warranty terms for Unit 6 set by the founder and printed before the gate
  6. 6cover that includes AI agent work bound
  7. 7company formed and checkout live
  8. 8client record signing live in our record log
  9. 9second model vendor connected
  10. 10two contracted reviewers, target Mon 30 Nov 2026
  11. 11cases, pass rate, date

Each item is also marked where it stands on this page.