
Credit stealing is rampant in architecture. Here is how we use the Knowledge Graph and community moderation to kill false attribution.
Credit stealing is rampant in architecture. Here is how we use the Knowledge Graph and community moderation to kill false attribution.
There is a joke in legal circles: "Success has many fathers, but failure is an orphan." In architecture, the joke is: "Every project has 10 people who claim they were the Lead Designer on their LinkedIn."
It is rampant. It is dishonest. And it damages the industry.
When a junior staffer claims they "Designed" a skyscraper because they modeled the lobby stairs, two things happen:
Archade is built to stop this.
On Instagram, you just post a picture. No context required. On Archade, you cannot post a project without defining your Role.
We force the user to choose:
By forcing a choice, we force a moment of honesty. It is psychological friction designed to filter out the ego-inflation.
If you claim to be the "Lead Designer" on a Zaha Hadid project, the system prompts you: "Who was the Partner in Charge? Tag them to verify."
If you don't tag them, your claim remains "Unverified" (Grey Check). If you do tag them, they get a notification: "John Doe is claiming he designed the Stadium. Confirm?"
If John is lying, the Partner clicks "Deny." And just like that, the lie is dead.
What happens when two people claim the same role? The Community decides.
In the old social web, "Viral" was the goal. Get likes, get famous. In the professional web, "Verified" is the goal.
A profile with 500 followers and 100% Verified Attribution is infinitely more valuable to an employer than a profile with 50,000 followers and zero proof.
We will never prioritize "Engagement" over "Truth." We would rather have fewer posts that are true, than a million posts that are lies.
Architecture is a profession of integrity. Your online profile should be too.


