Loading article…
Loading 4weird…
Loading 4weird…
Loading article…
DocsAxioms
Docs · remastery axioms
Every remastery feature — squads, kanban, timers, invoices — must obey these axioms. If a design breaks one, the design changes, not the axiom.
Axiom one
100 🪙 = exactly $1.00 USD. One coin is one cent, everywhere: compute rentals, studio tools, squad budgets, invoice totals. Never deviate, never invent a second exchange rate.
parity — one rate, every surface
100 = $1Axiom two
Every commercial hosted service or creator payout splits automatically: 75% to the creator/provider as on-site credits (games, cloud compute, AI services; non-withdrawable) and 25% retained by the platform for infrastructure. The gross is the price — the split is never added on top, and routing around metering violates terms.
Example: a 400-coin ($4.00) job → 300 coins provider credits, 100 coins platform. You only ever see the gross 400. All credits are on-site only (cloud compute, game credits, other on-site services); never cash-out, never withdrawable.
Axiom three
External AI or auxiliary services failing must never brick user navigation. If an AI service is unreachable, fall back to heuristic patterns or graceful error states: cached boards still render, timers keep ticking locally, invoices still draft.
🤖 AI down → heuristics
Visual QA, title generators, and chat summaries degrade to local fallbacks with a visible notice — never a blank page.
📡 Realtime down → polling
Notifications and chat fall back to periodic refresh; nothing the user typed is lost.
Axiom four
All client components sanitize localStorage and DOM state to prevent Next.js SSR/CSR mismatch errors. Stateful browser APIs mount inside useEffect or client guards. Coin-moving buttons disable on first click — double-spending via double-click is a bug, not a feature.
Axiom five
An open, public freelancer directory and public labor marketplace was explicitly evaluated and rejected. Public labor marketplaces bring labor-law liability (worker misclassification, tax withholding), privacy and harassment exposure (scraping, doxxing, spam), money-transmitter licensing for escrow, and off-platform disintermediation.
🚫 Rejected: public labor marketplace
✅ Adopted: private squads (UnitUnite)
The companion rule
Every tool publishes standard events to the interop bus and reads/writes the cross-clipboard, so assets flow across tools: a kanban estimate feeds the timer, timer entries feed invoices, invoice events feed notifications.
Worked examples
One cent per coin, no exceptions. Three conversions that cover every Wave 1 surface: compute, invoices, and custom amounts.
| Surface | Input | Coins | Split |
|---|---|---|---|
| Cloud compute escrow | $4.00 job | 400 | 300 provider, 100 platform |
| Invoice line | 2 hours at $50 per hour | 10,000 | 7,500 provider, 2,500 platform |
| Custom tip jar | $7.50 thank you | 750 | 563 provider, 187 platform, rounded to whole coins |
Design checklist
Run every proposal through these five gates before writing schema. A miss at any gate sends the design back, not the axiom.
FAQ
The questions reviewers ask most, with the ruling for each.
Can a squad set its own coin rate?
No. Parity is global: 100 coins equal one dollar in every squad, invoice, and compute job. Local discounts happen in dollars before conversion, never as a competing rate.
Are provider credits withdrawable?
No. The 75 percent lands as on-site credits for games, cloud compute, and AI services. Cash-out paths would trigger licensing the platform deliberately avoids.
What breaks when the timer disagrees with the server?
The local clock keeps ticking and reconciles on reconnect. Fail-open means the worker is never blocked by a stalled sync; the time tracker documents the drift-proof design.
Where do I start implementing?
Run the SQL migration runbook first, then open the Wave 1 overview rollout order for the squad to invoice path.
Next: run the SQL migration runbook or return to the Wave 1 overview.