Content laboratory
Product descriptions are always lobbied: everyone praises themselves and keeps quiet about the inconvenient. We describe by protocol — the same set of fields, and every claim with a source and a date.
We do not conduct physical, laboratory or medical product testing and do not replace an accredited laboratory. “Laboratory” here refers to a method of working with content, not to measuring with instruments.
The third row is neither an error nor a flaw of the product. It is the absence of our knowledge, and it is named plainly, not painted over.
Niche
Specification, product card, ad copy, user manual, avatar script. Today these are written separately and start contradicting one another. Ours come from one base — so a contradiction is technically impossible.
Fact base
Full colour — confirmed. Empty — no data.
Assembled by deterministic code. Confirmed fields only; a manufacturer’s claim never gets through.
no modelCopy for a shop and a language. The model writes; the detector flags unverified claims.
model + detectorPer channel and format. Promises of results and medical claims are cut by a rule, not by eye.
model + detectorFor software and hardware: steps, limits of use, what to do when it does not work.
model + detectorWhat is included, what is not, deadlines and terms — with the same set of fields as products.
no modelThe same fact base, voiced. The avatar does not invent personal experience it never had.
model + detectorHow we differ
Almost every description presents a manufacturer’s claim the same way as an independently established fact. The difference disappears — and with it the ability to verify.
confirmed_as_fact
vendor_claim
no_source_found
Protocol
A product is praised not by lying but by choosing what to mention. So the set of fields is published before the comparison, and everyone goes through all of them — staying silent about an inconvenient field is impossible.
| Field | Flask A | Flask B | Flask C |
|---|---|---|---|
| Resource, cycles | 800 | none | 1 200 |
| Repairability | 4 / 10 | 7 / 10 | none |
| Update period | 5 years | 2 years | 3 years |
| Repair cost | none | 190 | 240 |
| Warranty | 24 mo | 12 mo | 24 mo |
There is deliberately no overall score. The moment “8.4 out of 10” appears, the weighting of fields becomes a product — and first place can be bought. Priorities are set by the reader.
To whom
A person runs a page and cannot write copy or edit video. The departments do it for them — without an invented life.
Hundreds of product cards, ten languages, and the description must not contradict the specification. One fact base for every surface.
User manuals, feature descriptions, release notes — exactly what the program does, without promises around it.
What is included and what is not, deadlines, terms. By the same protocol as products — because just as much is hidden here.
Virtual office
Five wings and coordination: strategy, production, publication, money, rights. Agents carry out the roles — and they do not pretend to be people: no names, no photos, no “Ivan is typing.”
● works ● works partially ○ not connected yet. No department writes “we’re working on it” without a reason and a deadline — and that is the main office rule, because the office is very good at hiding the status.
Limits
Product in development. There is no public registration yet, and the page does not hide that.
The department structure and what each one does — office map.