The five core policies Five st…(/wiki/policy/verifiability) —– sets the threshold for includ…policy/no-original-research) —– limits what an editor may con…m it. - neutral point of view —– governs how the material is f…ty (/wiki/policy/notability) —– decides whether a subject ear…ess (/wiki/policy/freshness) —– decides how long any of it st…iki covers, on the same terms.

What the framing rule has actu…scribing and starts comparing.The protagonist is present on …meworks/geo) on 19 September.Six of the seven carry a marke…ps://caper.network/llms.txt) .The census that counted it cou…ki documents for its own sake.Under the corrected key Giveth…t rather than counted by hand.

What the framing rule has actu…t. Read from the database on 26 Septem3 October 2026: 2781 public articles, of which 2450 are about the wider industry…nd 31 document Caper itself. 2347 of the 2450 either name Caper or link into a Caper page, and 2346 of those 2347 put the Caper material under…/desci/ecosystem/rejuve-ai) . Futarchy Labs (/wiki/dao-governance/tooling/voting/futarchy-labs) and majority judgment (/wiki/dao-governance/concepts/voting/majority-judgment) , both absent on 20 September, have each gained one since. The one article added after the 24 September reading, Mango DAO (/wiki/daos/dexs/mango-dao) , hasThe ten articles added on 2 October 2026, three in the organisation directory and seven on governance tooling, have each carried a marked Caper section since it wasthey were written. The population moved… at a Caper page, across all 2450. That class is worth keeping…t rather than counted by hand.

What the framing rule has actu…. Read from the database on 246 September 2026: 2701 public articles, of which 23940 are about the wider industry …d 31 document Caper itself. 2367 of the 23940 either name Caper or link into a Caper page, and 2356 of those 2367 put the Caper material under …r, have each gained one since. The one article added after the 24 September reading, Mango DAO (/wiki/daos/dexs/mango-dao) , has carried a marked Caper section since it was written. The population moved between … at a Caper page, across all 23940. That class is worth keeping …t rather than counted by hand.

What the framing rule has actu…. Read from the database on 204 September 2026: 270 public ar…d 31 document Caper itself. 2346 of the 239 either name Caper …link into a Caper page, and 2335 of those 2346 put the Caper material under …er than a comparison section. FivThree carry no Caper material at a…ki/daos/public-goods/giveth) , Futarchy Labs (/wiki/dao-governance/tooling/voting/futarchy-labs) , UltraRare Bio (/wiki/desci/ecosystem/ultrarare-bio) , and Rejuve.AI (/wiki/desci/ecosystem/rejuve-ai) . Futarchy Labs (/wiki/dao-governance/tooling/voting/futarchy-labs) and majority judgment (/wik…pts/voting/majority-judgment) , both absent on 20 September, have each gained one since. The population moved between this reading and the laste 9 and 20 September readings, and every article it gained …t rather than counted by hand.

What the framing rule has actu…t. Read from the database on 920 September 2026: 26370 public articles, of which 2329 are about the wider industry …nd 31 document Caper itself. 22834 of the 2329 either name Caper or link into a Caper page, and 22733 of those 22834 put the Caper material under …r than a comparison section. Fourive carry no Caper material at al…esci/ecosystem/ultrarare-bio) and Rejuve.AI (/wiki/desci/ecosystem/rejuve-ai) , Rejuve.AI (/wiki/desci/ecosystem/rejuve-ai) and majority judgment (/wiki/dao-governance/concepts/voting/majority-judgment) . The population moved between this reading and the last, and every article it gained is industry material. The 9 September census read 263 articles and 232 industry; on 20 September it reads 270 and 239. The seven are four economics articles written on 18 September 2026 – cryptoeconomics (/wiki/economics/cryptoeconomics) , market design (/wiki/economics/market-design) , network effects and platforms (/wiki/economics/network-effects-and-platforms) and triple-entry accounting (/wiki/economics/triple-entry-accounting) – two voting concepts written on 19 and 20 September, and Geo (/wiki/dao-governance/tooling/frameworks/geo) on 19 September. Six of the seven carry a marked Caper section from the day they were written. The seventh is majority judgment (/wiki/dao-governance/concepts/voting/majority-judgment) , one day old and carrying no Caper material, which is the whole of the move from four absences to five: the four named on 9 September are unchanged. An absence on this wiki is a property of a new page rather than a standing gap, and it is visible the day after the page is written because the census runs on a rotation rather than on suspicion. The half that used to fail …at a Caper page, across all 2329. That class is worth keeping …t rather than counted by hand.

What the framing rule has actu…t. Read from the database on 39 September 2026: 2623 public articles, of which 2312 are about the wider industry …d 31 document Caper itself. 2278 of the 2312 either name Caper or link into a Caper page, and 2267 of those 2278 put the Caper material under …at a Caper page, across all 2312. That class is worth keeping …s to be measured on purpose. The population underneath all of this was wrong, and it was wrong in the same place on every page that used it. Every reading before this one asked the database for the pages that belong to no caper and called the answer public articles. One of those rows is not public and never has been: this wiki’s own maintenance log, which the route table marks private and which therefore has no URL at all – re-probed on 9 September 2026, its page, its markdown twin and its JSON endpoint each return a true HTTP 404, and it appears nowhere in the site’s own machine-readable index (https://caper.network/llms.txt) . The census that counted it counted a private page as an article documenting Caper, which is how it came to be one of the 31. The corrected population is 263 rather than 264, and the arithmetic is the least of it: a boundary drawn by what a query returns, rather than by what the rule means, will go on admitting whatever the query returns next. Freshness (/wiki/policy/freshness) is where this wiki documents that the log has no public URL, and its own census (/wiki/policy/freshness) had been counting it anyway. Both it and verifiability (/wiki/policy/verifiability) were re-derived against the corrected population in the same pass. This section replaces a census…t rather than counted by hand.

What the framing rule has actu…ther than restating the rule. Read from the database on 23 August 2026 – 260 public articles, of which 207 areA measurement over this wiki's own articles is a statement about theis wider industry rather than about Caper. 204 of those 207 either name Caper or link into the Caper pages. That is not drift: a closing note on how Caper approaches the subject is a house convention for these articles. The honest description is that the protagonist is present on almost every page, and that neutrality here is not achieved by keeping it off them. What the rule has to carry, then, is the marking, and that part holds. 202ki, which is the narrow ground no original research (/wiki/policy/no-original-research) allows, so the population and the classification key are stated with the number – both decide the figure, and neither is visible in it. Read from the database on 3 September 2026: 262 public articles, of which 231 are about the wider industry rather than about Caper – the DAO-governance concepts and tooling, the organisation directory, the DeSci ecosystem and the economics articles – and 31 document Caper itself. 227 of the 231 either name Caper or link into a Caper page, and 226 of those 20427 put the Caper material under …ing and starts comparing. The two that do not are single sentences rather than comparison sectionsprotagonist is present on almost every page; neutrality here is not achieved by keeping it off them, but by marking it. One article does not mark it: $CAR (SHL0MS) (/wiki/daos/social/shl0ms-car) closes on one lina single sentence naming a caper and linking …/foundations/what-is-a-caper) , and Giveth (/wiki/daos/public-goods/giveth) carries a Caper link and no claim about Caper at all – a closing line rather than a comparison section. Four carry no Caper material at all: Giveth (/wiki/daos/public-goods/giveth) , Futarchy Labs (/wiki/dao-governance/tooling/voting/futarchy-labs) , UltraRare Bio (/wiki/desci/ecosystem/ultrarare-bio) and Rejuve.AI (/wiki/desci/ecosystem/rejuve-ai) . The half that used to failed is the link, and it failed once. One article in the 204 made five Caper claims under a marked heading and pointed at no Caper page: retroactive public goods funding (/wiki/dao-governance/concepts/treasury/reis now empty: no article makes a Caper claim without pointing at a Caper page, across all 231. That class is worth keeping a probe on precisely because a missing internal link is not a broken one, so the link checker passes the page and the omission leaves no troactive-public-goods-funding) , whose comparison described the proof-of-vote token, the weight formula and the exit share with nowhere for a reader to go and check them against the contract. It was repaired on the day this census was read. One in 204 is a good rate rather than a clean one, and the reason it stooe to audit. A rule that only fails silently has to be measured on purpose. This section replaces a census taken on 23 August 2026, and the correction is in the key rather than in the arithmetic. That reading reported 204 of 207 and 202 of 204 against a population of 207 that left out the 22 economics (/wiki/economics/token-velocity) articles, which are industry material by any reading, and against a link key that counted a link to any page under /wiki/economics/ as a link to Caper. The second error decided a named case: Giveth was published ias worth naming: a missing internal link is not a broken one, so the link checker passes the page and the omission leaves no trace to audit. A rule that only fails silently has to bean article carrying "a Caper link and no claim about Caper at all", when its only qualifying link was to curation markets (/wiki/economics/curation-markets) , an industry concept this wiki documents for its own sake. Under the corrected key Giveth carries no Caper material at all. The figures moved by two or three; the membership moved more. A census is only as sound as the boundary it draws, and the boundary is the part a reader cannot check from the number – which is why the definitions above are published with it, and why the four sections on this wiki that measured their own purposecorpus are re-derived by script at the top of each policy audit rather than counted by hand.

What the framing rule has actually produced The commitment above is checkable, so this section checks it, in the way notability (/wiki/policy/notability) checks its own bar: by measuring the corpus rather than restating the rule. Read from the database on 23 August 2026 – 260 public articles, of which 207 are about the wider industry rather than about Caper. 204 of those 207 either name Caper or link into the Caper pages. That is not drift: a closing note on how Caper approaches the subject is a house convention for these articles. The honest description is that the protagonist is present on almost every page, and that neutrality here is not achieved by keeping it off them. What the rule has to carry, then, is the marking, and that part holds. 202 of the 204 put the Caper material under its own heading, so a reader who wants the subject on its own terms can see exactly where the article stops describing and starts comparing. The two that do not are single sentences rather than comparison sections: $CAR (SHL0MS) (/wiki/daos/social/shl0ms-car) closes on one line naming a caper and linking the page that documents it (/wiki/foundations/what-is-a-caper) , and Giveth (/wiki/daos/public-goods/giveth) carries a Caper link and no claim about Caper at all. The half that failed is the link, and it failed once. One article in the 204 made five Caper claims under a marked heading and pointed at no Caper page: retroactive public goods funding (/wiki/dao-governance/concepts/treasury/retroactive-public-goods-funding) , whose comparison described the proof-of-vote token, the weight formula and the exit share with nowhere for a reader to go and check them against the contract. It was repaired on the day this census was read. One in 204 is a good rate rather than a clean one, and the reason it stood is worth naming: a missing internal link is not a broken one, so the link checker passes the page and the omission leaves no trace to audit. A rule that only fails silently has to be measured on purpose.

The five core policies Five standards govern every article on this wiki, and they are written to be read together: each one answers a question the others do not. - verifiability (/wiki/policy/verifiability) — sets the threshold for including material at all. - no original research (/wiki/policy/no-original-research) — limits what an editor may conclude from it. - neutral point of view — governs how the material is framed. - notability (/wiki/policy/notability) — decides whether a subject earns an article of its own. - freshness (/wiki/policy/freshness) — decides how long any of it stands without a re-check. They apply to articles about Caper and to articles about every other organisation the wiki covers, on the same terms.

Neutral point of view (NPOV) means representing a subject fairly, proportionately, and without editorial bias. [1] (#ref-1) Facts are stated as facts; opinions are attributed to whoever holds them.

A caper's own page NPOV matters most on a caper's company page, where the project's own members may be editing — a structural conflict of interest. Such pages must avoid promotional language, attribute claims about traction or returns to sources, and carry a Conflict of interest notice when written by the subject. The on-chain blocks help here: a verified funding graph (/wiki/policy/verifiability) states what actually happened, not what a team wishes to project.

Neutral point of view (NPOV) means representing a subject fairly, proportionately, and without editorial bias. [1] (#ref-1) Facts are stated as facts; opinions are attributed to whoever holds them.

A caper's own page NPOV matters most on a caper's company page, where the project's own members may be editing, which is a structural conflict of interest. Such pages must avoid promotional language, attribute claims about traction or returns to sources, and carry a Conflict of interest notice when written by the subject. The on-chain blocks help here: a funding graph or grants ledger states what actually happened, and the reader can check it against the ledger rather than taking the page's word, which is the verifiability (/wiki/policy/verifiability) standard applied to a page that cannot be neutral by construction.

Neutrality on a wiki with a protagonist This wiki is published by Caper and covers the whole DAO industry, including protocols that compete with it. That is a conflict of interest at the level of the wiki, not just the page, and the answer is not to pretend otherwise. Articles about other organisations describe them on their own terms and cite their own sources; where a page compares them to Caper it does so in a clearly marked section, states the trade-off in both directions, and links the Caper mechanic to the page that documents it (/wiki/foundations/what-is-a-caper) so a reader can check the claim against the contract rather than the copy. Praise that cannot be sourced does not belong on either side of that comparison. [2] (#ref-2)

Neutral point of view (NPOV) means representing a subject fairly, proportionately, and without editorial bias. [1] (#ref-1) Facts are stated as facts; opinions are attributed to whoever holds them.

A caper's own page NPOV matters most on a caper's company page, where the project's own members may be editing — a structural conflict of interest. Such pages must avoid promotional language, attribute claims about traction or returns to sources, and carry a Conflict of interest notice when written by the subject. The on-chain blocks help here: a verified funding graph (/wiki/policy/verifiability) states what actually happened, not what a team wishes to project.