#1. Who writes this
The journal is written by Ahsan Raza Khokhar, Founder & Chief Executive and a practising architect at arka.pk. Articles carry his byline because the expertise is the point — an architect writing about proportion is a different proposition from a content agency writing about furniture, and the byline is how you can tell which one you are reading.
Product descriptions are written in-house from the specification, the materials list and the piece itself. Nobody describes a chair here without having sat in it.
#2. Where AI is used, and where it is not
We use a large language model (DeepSeek, server-side) as a drafting tool. Being specific about this is more useful than either pretending we do not or waving vaguely at "AI-assisted".
| Task | AI involved? | What actually happens |
|---|---|---|
| Product descriptions | Yes, first draft | Generated from the real specification, then edited by a person who has seen the piece. Never published unedited |
| Journal articles | Structure and outline only | The argument, the judgements and the numbers are human. An article whose opinion came from a model is not worth publishing under a byline |
| Social captions | Yes, first draft | Reviewed and approved before scheduling |
| Alt text for images | Yes, first draft | Checked by a person, because wrong alt text is worse than none |
| Translation into Urdu | Yes, where enabled | Reviewed by a fluent speaker before publication |
| Anything factual — dimensions, materials, prices, care instructions | No | Read from the product record. A model is never asked what a table is made of |
| Replies to customers | No | A person answers. Every time |
| Reviews and testimonials | Never | Fabricating a review is fraud, and it is also the fastest way to lose a business its reputation |
#3. Standards we hold the writing to
- Verifiable. Numbers — circulation widths, seat depths, timber moisture content — come from architectural practice and standard references, and we say which.
- Useful before promotional. An article that only makes sense as a route to a product page is not an article. Several of ours advise against buying something.
- Sourced outward. We link to museum collections, standards bodies and genuine authorities. Not to link farms, and not reciprocally for search value.
- Original. We do not spin, rewrite or paraphrase other people's articles. Where we quote, we quote, attribute and link.
- Experience-based. Written from projects and from the showroom floor, which is the only real answer to the question of why anyone should read a furniture shop's blog.
#4. The relationship between the writing and the selling
Articles link to our products where a product genuinely illustrates the point, and those links are internal and unpaid. Nobody outside the business can buy a mention, a recommendation or a link.
Any sponsored arrangement, free sample or affiliate link is disclosed under the Advertising & Sponsorship Disclosure. Advertising placement has no influence on editorial content, and the advertising network cannot see what is being written before it publishes.
#5. Corrections
Tell us at sales@vevarte.com if something here is wrong. We would genuinely rather know.
- Typographical fixes are made silently. Nobody needs a changelog for a misplaced comma.
- A factual correction is made and noted at the foot of the article with the date and what changed.
- A substantive change to the argument or the advice updates the "last updated" date at the top, and says what was revised.
- An article that turns out to be wrong enough to mislead is withdrawn, and a note left at the URL explaining why. We do not quietly delete things.
#6. Reuse, and machine consumption
Quote a paragraph with attribution and a link — please do. Reproducing an article in whole or substantial part needs permission under the IP & Copyright Policy.
Use of this content to train, fine-tune or evaluate a machine-learning model is not permitted, and is listed as prohibited in the Acceptable Use Policy. Search-engine indexing and the ad crawlers are welcome, and are named in robots.txt.