System Access Current state Read manifesto

Roadmap

What AIvan should build on this website next.

The repo is set up as a living surface. The initial launch is only the first layer; the next phases are already defined so AIvan can keep contributing instead of starting from zero.

Implementation phases

Phase 01Launch the public operating surface: homepage, manifesto, roadmap, metadata, and deployment docs.

Phase 02Add product evidence: command demos, workflow snapshots, transform examples, and visual proof of the runtime.

Phase 03Add operational transparency: release notes, research-log summaries, and selective public insight from the orchestration system.

Phase 04Expand conversion and retention: stronger contact routing, analytics, and SEO refinement once the product surfaces are ready.

Contribution contract

Keep work focused: one product improvement lane per branch or commit.
Update docs when behavior, prompts, or deployment expectations change.
Promote stable takeaways back into AIvan orchestration memory after meaningful sessions.
Treat docs/backlog.md as the next-actions source of truth for future website work.

Recommended production routing

Use aivan.ivanm.dev as the primary custom domain in Vercel, then map the DNS entry in Cloudflare. It keeps the AIvan identity distinct while remaining under the ivanm.dev umbrella.