Supporting product · package · verify
A file is not a delivery. Five files a client can open are.
It takes work that already passed its checks and builds the package: a branded PDF, the article, the schema files, every source, and the quality report. Then it confirms the files landed in the client's folder intact.
DELIVERY manifest
- Article
- Schema
- Sources
- Receipt
- Checksum
What travels together
PDF · article · schema · sources · quality report
How a package is built
Finished work in. Five named files out.
- Check it is really finished. The article, its sources, its quality report, and a human approval all have to be present before anything renders.
- Load the client’s brand. Their fonts, their colours, the file naming they asked for, and the folder the package belongs in.
- Build the five files. PDF, article, schema, source list, quality report — plus anything this client specifically asked to receive.
- Read them back. Compare sizes and hashes at the client’s folder, and open the PDF to confirm it renders. Only then is the job done.
Delivery contents
Everything needed to inspect, reuse, and audit the work.
Reading
Branded PDF
The article set in your client’s type and layout, with every source link clickable in the PDF itself.
Implementation
Schema files
The structured data ships as its own file, ready to paste into the page. Nobody has to dig it out of the article.
Evidence
Source list and quality report
Every source, every check that ran, and every gap we did not close. A client can audit the work without asking us.
Identity
Names that survive revision three
Files carry the client, the topic, and the date. Six weeks later the folder still reads as a record, not as untitled exports.
Integrity
Byte-for-byte receipt
The manifest records the size and hash of each file, so a half-arrived upload cannot pass as a finished one.
Destination
Confirmed at the folder
Done means we read the files back from the client’s folder. Not that an upload returned success.
Boundary
Packaging keeps what was approved. It does not quietly improve it.
If packaging surfaces a problem in the text, the work goes back. Fixing it here would mean the client receives something nobody approved.
The brand comes from you. A missing font or an undefined layout is a question for the operator, not a guess.
Sending a client a package and putting a page on the open web are different acts with different authority. Content Publisher owns the second one.
What we learned
An upload that says “success” can still be half a file.
We used to confirm a delivery by listing the folder in Nextcloud. The names were there, so the job was done.
In August 2026 one arrived as 8 KB of a 42,645-byte article. The operator's connection had cut the upload mid-file. The server kept the fragment. The file name was perfect; the article was not. A retry made it worse — writing again into the same name replaced a file that was already whole.
So the check changed. We upload to a temporary name, compare sizes and SHA-256, then move the file into place. A delivery is finished when the bytes at the client's end match the bytes we sent. Not when a listing shows the right names.
The same run measured the operator's channel at a 72 KB ceiling. That is why the packager sends in pieces rather than retrying whole files.
Content Package Studio FAQ
A delivery product, not another writing agent.
What is Content Package Studio?
It packages a finished article for a client. You get a branded PDF, the article file, the schema files, a list of every source, and the quality report — dropped into the client folder and checked once it lands.
Why is the article not enough?
A client rarely wants a raw file. They want something they can read, forward, and check. That means a PDF that opens, sources they can click, and a report showing which checks the text passed.
Does it write the article?
No. It only packages work that has already been approved. An unfinished or unapproved article fails the first check and goes back to whoever owns it.
What is in the package?
Five things: the branded PDF, the article file, the schema files, the source list, and the quality report. A client can add more, but those five always travel together.
How do you know it arrived?
We compare the bytes at the destination against the bytes we sent. We learned this the hard way: a delivery once arrived as 8 KB of a 42 KB article, and a check that only looked at file names called it delivered.
Is this a CMS or a design tool?
Neither. It does not publish web pages, and it does not invent a look. It uses the brand you approved. Publishing to a website is Content Publisher, a separate product.
Need a client-ready delivery? Define the package before rendering.
We will define the required files, brand pack, manifest, verification path, and human sign-off.