UNION WORKERS'
AGREEMENT.
A professional network for a new kind of workforce.
The manifesto is ambitious. The terms should be clear.
The city needs people who show up.
Everybody wants to own Vice City. Somebody has to keep it running. We are building the professional home for janitors, crews, and the server operators who hire them: work histories, clear contracts, a community feed, and a union with a visible treasury.
“Quit your job. Become a GTA 6 janitor.” is the campaign. The $100K-a-year janitor is the ambition. Turning that into actual opportunities requires functioning servers, employers, funded contracts, and enforceable operating rules. It is not an available employment offer or evidence of current earnings.
Local 6 is an independent community project. Calling it a union expresses the organizing concept; this draft does not establish a legally recognized labor union, employment relationship, investment entitlement, or collective bargaining agreement.
5,000,000 JANITOR. Your seat at the table.
The proposed membership threshold is at least 5,000,000 $JANITOR. A live implementation must verify wallet ownership and the balance of the published official mint. A typed balance, screenshot, preview card, or selected demo persona is not proof.
- Holder membership: eligibility for the union community and proposed DAO, subject to the published qualification rules.
- Governance: vote on union priorities, budgets, operating rules, and treasury proposals after a voting system is adopted.
- Qualification checks: the intended design checks eligibility when joining and participating; a final snapshot or continuous-balance policy must be published before launch.
- Below the threshold: union privileges may pause under the adopted rules. Completed-work payments and contract rights must not be erased because someone sells tokens.
- No promise of yield: holding tokens alone does not earn a salary, guarantee rewards, verify work, or create ownership of the treasury.
The mint address, vote weighting, quorum, proposal process, delegation, and membership-review rules remain to be finalized. This frontend does not enforce membership or connect to a wallet.
A wallet balance is not a résumé.
| STATUS | WHAT IT MEANS | WHAT IT DOES NOT MEAN |
|---|---|---|
| Holder | Meets the union token requirement after wallet verification. | Not evidence of skill, reliability, or employment. |
| Verified worker | Identity and trial work reviewed; work evidence accepted. | No guaranteed shifts or income. |
| Verified server owner | Control of a server or authorized hiring operation reviewed. | No guarantee of solvency or contract payment. |
| Non-holder | Does not currently meet union membership requirements. | Not a statement about competence or trustworthiness. |
Browsing can be public. Verified union workers can share work updates. Approved server operators can post contracts under published marketplace rules, with holder status shown separately. A non-holder can still be a legitimate operator; the badge makes the distinction visible.
Verification should require evidence, human review, a stated reason for rejection, and an appeal route. No one may purchase a verified-work badge by buying more tokens. All verified labels on the current sample profiles are demonstrations.
No shift without clear terms.
Each real job offering must specify:
- The employer or operator, location, required role, and scope of work.
- The schedule, expected duration, and completion deadline.
- The exact payment amount or an explicit negotiation step, the currency, and who pays any fees.
- The evidence required, who approves it, and the approval deadline.
- The payment deadline, cancellation terms, and dispute route.
USD, SOL, $JANITOR, and in-game credits are different units and must never be presented interchangeably. A future escrow feature must be separately implemented and reviewed before it is advertised.
Workers can build a portfolio from approved shifts. Posts must not expose other people's personal data, private server information, or misleading evidence. Operators must not create fake jobs or self-deal with duplicate accounts to collect union rewards.
Current listings are illustrative; forms save local drafts only. Submitting a frontend draft does not notify an employer, create a contract, or secure a server slot.
100% of collected project fees to the union.
The proposed routing policy allocates 100% of collected project fees to the union treasury. There is no separate 10% buyback-and-burn allocation in the current plan. This does not mean every trade in $JANITOR automatically pays a fee to the project.
Before fee collection starts, publish the fee source and rate, collection mechanism, treasury address, signing authority, and approval rules. Workers' contracted wages are separate from project fees and must not be silently diverted.
Planned uses of the union fund
- Rewards for verified, approved work.
- Approved server development and operating expenses.
- A disclosed reserve for continuity and quieter periods.
No spending split is adopted yet. The interface's budgeting calculator uses adjustable hypothetical inputs. Governance and treasury signers must operate under published spending limits and conflict-of-interest rules.
The live transaction view should disclose deposits, rewards, operating expenses, counterparties where appropriate, and transaction signatures. Simulated rows in this frontend are explicitly labeled and have no real signatures.
Work first. Funding before promises.
Employer payments and union rewards are distinct. Employers owe the payments they agree to. Union rewards may supplement approved work only when the adopted program and actual treasury funds support them.
Before rewards launch, publish eligibility, evidence standards, calculation rules, caps, allocation periods, payout currency, payment schedule, and a dispute process. No formula or automatic airdrop is operational in this frontend.
The campaign target is not a guaranteed salary, token return, earnings forecast, or recommendation to leave existing employment. No verified quote on this site establishes a $100K janitor salary.
Workers deserve a process.
- Payment clarity: agreed scope and compensation before starting work.
- Evidence and review: access to the reason a shift was approved or rejected.
- Disputes: a written complaint, supporting evidence, an independent reviewer, and a stated response window.
- Appeals: a review route for badge removal, moderation, and rejected rewards.
- No retaliation: reporting a payment or safety concern must not itself be grounds for exclusion.
- Privacy: minimize collected information and publish retention and deletion policies before accepting real applications.
The operator, moderators, response deadlines, governing terms, and responsible legal entity must be named before live hiring. This is a draft product policy, not individualized legal advice or a signed employment agreement.
Our server. Built in the open.
Vice City · Union District is the planned Local 6 flagship server project. The concept includes local businesses, crews, shift evidence, and a hiring board. The map on the homepage is an original concept diagram, not an official GTA 6 map.
No live join address, game hosting, whitelist, or GTA 6 server capability is established by this website. The platform and tools must be confirmed. Any integrations, monetization, rewards, or access rules must comply with the selected platform's terms; no token-gated GTA server is promised.
Developing our own server and listing other operators are separate activities. Directory registration does not establish ownership, partnerships, availability, or approval.
What works today.
The frontend includes a community feed, job filters, saved jobs, application and card downloads, a server directory, a concept district map, an illustrative transaction view, and a budget calculator.
Browser-local only: work updates, job drafts, server listings, likes, saved jobs, and application drafts. These are not shared with other visitors. Clearing browser storage removes them. No identity, token balance, or ownership is verified.
Still to build: wallet verification, identity checks, moderation, shared database, job publishing, notifications, contract handling, server integration, governance, fee routing, transaction indexing, and reward payouts.
The clips, in context.
Adin Ross and FaZe Banks have discussed their own proposed GTA server concepts. Those remarks are editorial context for this project, not endorsements of $JANITOR, Local 6, or our salary ambition.
- Adin Ross / janitor remark: source post linked by reporting; GTA 6 Bible coverage; GamingBible coverage.
- Banks and Ross / proposed server economy: source discussion linked by reporting; Decrypt coverage, February 5, 2025.
The portraits are AI-generated editorial illustrations, not footage, documentary photographs, or evidence of affiliation. Embedded source posts load only after a visitor chooses to open them and are subject to the source platform's availability. The original X pages could not be directly inspected during implementation; the displayed excerpts are attributed to the linked reporting. No synthetic speech has been substituted for original footage.