Writer Match vs Wikilayer

Writer Match is the app for writers looking for co-writers, collaborators, and honest feedback. Whether you're developing a screenplay, novel, short story, or any creative project, Writer Match connects you with writers who share your taste, ambition, and creative wavelength. How it works: Discover other writers in two ways. In project-based discovery, you browse and react to individual ideas and loglines — perfect for finding collaborators on a specific piece of work or getting targeted feedback on a concept you're developing. In profile-based discovery, you match with writers based on their full body of listed works and creative preferences, ideal for finding a long-term co-writer or critique partner. Smart recommendations, real compatibility: Writer Match doesn't match you randomly. A three-tier recommendation system surfaces the most compatible writers based on shared preferred genres, preferred formats, creative influences and taste, as well as your language and country of residence. Every recommendation is someone you're genuinely likely to work well with. Your ideas, your way: Store all your project ideas in one place — past work, current projects, and future concepts. You control the visibility: keep ideas private as a personal notebook, or make them visible to other writers who can like them or express interest in collaborating. Built for real collaboration: Once you've matched, chat directly inside the app. Share drafts, exchange feedback, workshop loglines, or kick off an entirely new project together. Writer Match is designed to take you from discovery to collaboration without ever leaving the app.

Wikilayer is a wiki that an AI assistant can read and edit on your behalf. You and your agent work on the same tree. The agent writes through MCP tools: it adds a node, rewrites one, moves a subtree, and reads back by outline instead of loading everything into its context. You read the result here, as ordinary pages. Every block has an address of its own. Rename it, rewrite it, move it under another parent, and links to it still land. Pages that lead to a block are listed under it, and nobody maintains that list by hand. History is kept per node, so a change to one paragraph is a change to one node, not to a whole document. WHAT PEOPLE KEEP HERE Personal notes: a second brain the agent reads selectively instead of holding a whole vault in context. Adding is a message in chat, not an app switch. Project memory: long-running context the agent writes and you audit. Hierarchy and full-text search across titles and bodies, without a separate vector store. Team workspace: decisions, context and meeting digests, written by the team and refactored by the agent. Public reference: guides, handbooks, fan wikis. Readers arrive from search and never touch the editing surface. VISIBILITY A wiki can be open to everyone, private to a team, or run on your own machine. Public wikis are crawlable the day you write them: server-rendered pages, Open Graph, sitemap, structured data, and addresses that survive a rename. WHAT IT IS NOT Not a block editor: bodies are plain markdown edited through MCP, not click-to-edit blocks, and the tree is hierarchical nodes rather than a relational document store. Not a real-time co-editor: each edit lands atomically, and conflicts resolve at write time rather than by merging keystrokes. Not an approval workflow: edits land on the live tree, and the audit trail is a snapshot of each node as it stood before the change. Bodies are markdown and the tools are MCP. Both are public formats, so a wiki reads out as plain documents whenever you want it somewhere else.