--- title: The dev packs description: "The area is built and the documents are held. Nineteen documents, every one of them hashed and listed, none of them published — because five checks run before anything opens, none has been run by a person, and two of them a script can already show would fail." lead: "**The instruction was to publish these documents on the site. The same document that gave the instruction named five checks that run first, called every one of them \"a real edit or a real hold\", and recorded that who runs them is not decided.** So this area exists, its manifest is published, and its documents are not. Two of the five checks are measurable and are measured below: **11 of the 19 documents would break a hard rule on contact with this site.**" order: 10 toc: true wide: true --- ## What is published here today **The manifest, and nothing else.** Every document, its kind, its size and its sha256. That is enough for somebody holding the pack to check their copy against this page, and not enough to read a word of it here. That is deliberate, and it is the same discipline the pack asks of everything else: **checkable by a reader who does not trust the page.** A documents area that published its own text but not its own hashes would be arguing against the product it sits beside. {{pack-manifest}} ## Why nothing is published yet **Publishing is not a formatting change.** The five checks below are quoted from the instruction itself, and each of them is a real edit or a real hold. {{pack-checks}} **Two of the five can be measured by a script, and the script has run:** - **Hard rule 1** — the word that may never appear anywhere on a site carrying prices — appears in **11 of the 19 documents**, including in the title of one of them. The rule's stated reason is that a positioning phrase is a claim but a priced checkout is an offer, and **an offer is what the regulated perimeter is about**. There is no page of this site where the word is safe, and a published document is a page. - **Check 5** — the open naming collision, ruled on 8 September to block any public page — appears in **4 of the 19**. **The other three need a person.** Auditing every named third party for adjectives is the check most likely to fail, because these were written for an internal reader and internal briefs are blunt — and no script reads for tone. Verifying or cutting every unverified claim that names a company needs the sources open. Re-reading the two documents with unresolved legal exposure needs somebody who is not only a builder. ## What is not being asked for here **Not permission to soften them.** The gaps in these documents are the point. A document that says a pipeline does not exist, or that an application built in August cannot be located, is doing exactly what the method is for, and **a dev packs area whose uncertainty has been edited out is a marketing page wearing a lab coat.** Nothing in the manifest above has been rewritten and nothing will be. **What is being asked for is two rulings and three reads.** The word: does hard rule 1 reach a republished working document, or only original copy? The collision: close it, or hold the four documents that carry it. Then the three checks a person has to run. Until those happen, this page is what the area is. ## The structure it will open into The shape is already specified and the build already follows half of it: one index, one folder per pack, a `pack.json` manifest with hashes, and **compiled files rather than one file per record** — because the published performance cliffs punish thousands of small objects, and a cold open of 2,375 objects was measured at over three minutes. ``` /dev-packs/ index.html this page — the list of packs, with date, count and state pack.json the manifest, machine-readable ← published today llms.txt per the estate convention llms-full.txt the quotation set, the gaps, the open questions /store/ this pack — held ``` **Two things are already decided and neither is a formatting question.** A published pack is **frozen, not maintained**: a dated document with hashes is a promise about a moment, and a pack that gets quietly updated breaks that promise — so new versions are added beside, never over. And whether packs from other days and other subjects follow this one is **a separate decision with a much larger surface**, not an extension of this instruction. ## One thing this area is not sure about **Whether it belongs on this site at all.** The instruction said "the site", and this pack was written for this one. The reasonable alternative is that a dev packs area belongs on the platform domain and indexes packs for every site, with each pack linked from the site it concerns — which fits the convention that **every site in the network is named for an argument**, and a documents index is not an argument. It is built here, every internal link is relative, and the folder is self-contained **so it can be moved without rewriting it.** Same as [the host question](/offers/#the-offer-identifier-is-the-stable-part), and for the same reason. {{claim:domain-ruling-overruled}} --- This document is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).