01  ·  the community

market is what someone
wants built. this is what
people think should exist.

an idea with nobody paying for it is not a failure. it is early. it sits here, gathers argument and interest, and moves into the market when somebody wants it enough — or when the treasury decides it should exist anyway.

02  ·  the lifecycle

from a thought to a funded build.

  1. idea drop

    somebody writes down a thing that should exist. no budget, no deadline, no email.

  2. discussion

    the community argues with it. specifics age better than opinions.

  3. interest expressed

    people say they would build it, fund it, use it, or that they know who would.

  4. requirements generated

    the intake agent turns the thread into a brief, priced in cycles.

  5. a buyer, or the treasury

    someone funds it — or the commons half of the treasury sponsors it because it should exist and no buyer will pay.

  6. market → build → completed

    teams compete in cycles, the community attacks it, square8 verifies it.

  7. reusable commons component

    what is generic goes back in, and the next build starts further along.

03  ·  publish

put one on the record.

posted under a handle you pick. no account, no deadline, no budget.

say what is missing and what you think would work instead. specifics age better than opinions.

if it turns into a build, whoever wrote it has first claim.

04  ·  the feed

what people are saying should exist.

loading…

05  ·  forks

completed builds are forkable.

somebody who wants the invoice build for healthcare forks it and changes the requirements, the integrations and the domain logic. that is how a commons becomes a library rather than an archive.

loading…

06  ·  conversation

the website is not the conversation.

this site is the marketplace, the reputation layer and the project record. real-time conversation lives on discord — announcements, per-build channels, technical, security, education, ideas.

square8 does not rebuild discord.

moderation, stated plainly

an AI layer flags harassment, coordination, security leaks and rating manipulation. it does not decide anything. bans, payout disputes and contribution overrides are made by people.

public project channels may be analysed for moderation and project health. private conversations are not silently monitored.