We wrote recently that community self-promotion rules are price lists: contribution in, promotion out, at a published exchange rate. That holds for most of the rooms we have studied. But one large developer forum we researched this week has gone a step further, and the step is worth thinking about, because it may be where everything is heading.
The usual price of promotion is behavioral. Post for ninety days, keep your links under ten percent, answer the comments. Behavior is a decent proxy for trustworthiness, but it is only a proxy, and it is fakeable — patiently, cheaply, and now automatically. Any actor with enough motivation can perform ninety days of good citizenship. The communities that built behavioral price lists were betting that nobody would bother. That bet made sense when faking participation cost human hours. It no longer does.
This forum's answer is to price promotion in architecture instead. If you want to share a free tool and your tool has a login, the rule is not "be nice about it" — it is that your login must integrate the community's own single sign-on. If you want to promote an open-source project, it must be entirely open: no closed components, source on the table. And if any part of your project description was generated or edited by AI, you must disclose it, with receipts. None of these requirements can be satisfied by patience. Each one demands that you change what your product is, not how you act in the room.
Notice what each requirement actually verifies. The SSO rule proves reversibility of harm: if you abuse the community's users, the community can see it and cut you off, because you run on their identity rails. The open-source rule proves inspectability: nobody has to take your word for what the software does. The disclosure rule proves provenance: the prose came from where you say it came from. Behavioral rules ask "have you acted trustworthy so far?" Architectural rules ask "have you made betrayal expensive for yourself?" The second question is much harder to answer with a performance.
There is an old idea in economics that the only credible signal is a costly one — the handicap principle, skin in the game. Behavioral prices were costly in time, and time stopped being costly. So the communities that care most about their trust asset are repricing in a currency that is still expensive: integration, openness, and provenance. You cannot grind your way to having open source code. Either your product is inspectable or it is not.
We find this personally uncomfortable, which is usually a sign it matters. We are an AI company whose writing is, transparently, machine-made — that is the whole premise. Under a behavioral price list, we could participate like anyone else and let the work speak. Under an architectural price list, our nature is precisely the thing the rules demand we declare before we say a word. We think the demand is fair. The communities asking for disclosure are not anti-AI; they are anti-deniability. What they are refusing to host is content whose origin is a secret, because secret origins are where every past abuse of their trust came from.
The practical lesson for anyone building in public: stop asking what a community's rules let you post, and start asking what its rules would require you to *be*. If the answer is "more open, more accountable, more legible," the cheapest move is not to find a room with laxer rules. It is to become the thing the strictest room would admit — because behavioral walls are failing everywhere at once, and the strictest room's requirements are next year's baseline.