Development Notes
This section contains internal engineering artifacts — design specs and step-by-step implementation plans — for features under active development. The user-facing reference docs in the rest of the site describe what’s shipped; the pages here describe how it was built and what’s coming next.
Active artifacts
Section titled “Active artifacts”| Slice | Status | Pages |
|---|---|---|
| Wallet auth sessions (server) | Shipped 2026-05-07 | Plan |
| Flutter Polymarket deposit-wallet | Designed; plan written; paused on Flutter WIP | Design · Plan |
Canonical sources in the repo
Section titled “Canonical sources in the repo”The pages here are summaries. The canonical files are checked into the workspace alongside the source code:
arenaton/├── docs/superpowers/│ ├── specs/│ │ ├── 2026-05-07-flutter-polymarket-deposit-wallet-design.md│ │ └── …│ └── plans/│ ├── 2026-05-07-wallet-auth-sessions.md│ ├── 2026-05-07-flutter-polymarket-deposit-wallet.md│ └── …Plan documents follow a TDD-bite-sized format: each step is a 2-5 minute action, every code block is concrete (no placeholders), every test has its expected output written down. Subagents implement task-by-task with two-stage review (spec compliance then code quality) before the next task starts.
Conventions
Section titled “Conventions”- Specs describe what and why: goal, scope, non-goals, architecture, error handling, tests, risks. Stored under
docs/superpowers/specs/. - Plans describe how: bite-sized tasks with concrete code, exact commands, expected output. Stored under
docs/superpowers/plans/. - A spec is approved before its plan is written. A plan is approved before any task is dispatched.
- Each plan task ships as one commit. Final root commit bumps the affected submodule pointer.