Roadmap
The roadmap names the work in view without turning themes into promises.
FactionOS is moving from public-site and demo polish into quality, deployment, and product handoff work.
This page is not a delivery schedule, SLA, funding update, customer announcement, or legal notice.
Current focus
The immediate work is trust and conversion page depth for readers who need product fit, setup, security, FAQ, policy, and contact clarity.
Website
Complete use cases, security, publishing, company, contact, press, roadmap, FAQ, and legal placeholder routes before the final copy pass.
Legal and policy pages remain visibly pre-review until owner-approved text exists.
Review
Audit internal links, CTAs, route labels, metadata, and product copy across the launch website.
The copy pass may remove or soften language if evidence does not support it.
Privacy
Keep demo, docs, and email contact actions clearly routed to external or mailto destinations.
Analytics, hosted forms, cookies, auth, and runtime personalization remain outside the launch site.
Near-term themes
The next website work focuses on responsive hardening, performance, automated checks, deployment path evidence, and launch handoff documentation.
Quality
Review desktop, tablet, narrow mobile, keyboard focus, heading scale, wrapping, and footer reachability after all pages exist.
This is quality evidence for the launch site, not broad product certification.
Performance
Keep output lean, validate asset sizes, and preserve the existing package-local media registry posture.
Media showcase readiness remains scoped to approved website assets.
Checks
Strengthen typecheck, build, HTML inspection, and content scans before deployment handoff.
Live deployment still needs its own post-deploy evidence.
Deploy
Prepare the Cloudflare Pages deployment route while keeping runtime personalization out of scope.
Live deployment needs separate sanitized evidence after deployment is available.
Later themes
Future product and hosted-service directions need scoped specs, threat models, tests, docs, and owner review before public materials change.
Hosted
Optional hosted storage, analytics, push, public replay, tunnels, or remote access remain future review areas.
These are not active hosted services and do not imply account identity or production auditability.
Teams
Role-specific team pages can later connect to stronger collaboration evidence after identity, authorization, consent, and abuse controls exist.
War Room federation remains optional and separate from hosted account identity.
Policy
Privacy, terms, and acceptable-use placeholders can become final only after owner/legal review supplies approved copy.
Pre-review placeholders are not a substitute for legal approval or acceptance workflows.
Recently shipped
Astro output, metadata helpers, sitemap posture, RSS, and publishing routes are in place.
Evidence Resolved from an existing news entry, not a roadmap promise.
Initial website foundationPublishing templates now support featured entries, category groups, related links, and draft-safe validation.
Evidence Resolved from the news collection and scoped to editorial readiness.
Publishing polishThe site links to a separate demo destination for product exploration.
Evidence Resolved from an existing demo news entry.
Demo destinationWebsite route depth expanded into use cases, security, publishing, company, contact, and press surfaces.
Evidence Resolved from an existing company-style website update.
Public site expansionGuardrail
The items below are direction and prioritization signals. They can move, narrow, expand, or be replaced as product, security, documentation, deployment, and owner-review work produces better evidence.
Need context
Use the FAQ for common questions, the security page for trust boundaries, or the contact route for product and partnership conversations.
Contact links open your email client so you can review the message before sending.