Roadmap & Ask
Ambitious, but gated
Dravenkor’s roadmap is now organized around a simple principle: keep private validation moving while protecting the public and commercial path with the right legal, release, and operational gates.
The private review site is live and operating. The roadmap now also makes the pre-work visible: Mimir architecture, Mimir/Dravenkor strategy, and Phase 1A backend deployment. The backend deployment is still in progress, roughly 70% complete, and will feed into WS-4 as integration subtasks for ODIN/DORI and the Tier-1 Community MVP.
The next major work runs in two parallel streams: Legal/IP/Release Governance and Demo-1 Product Validation. Demo-1 stays private, fixture-backed, and non-commercial while the legal stream confirms what must be true before any Community GitHub release or commercial revenue begins.
Roadmap sequence
| Workstream | Focus | Current posture |
|---|---|---|
| Foundation / Pre-work — Architecture, Strategy, Phase 1A Backend | Mimir architecture, Mimir/Dravenkor strategy, and Phase 1A backend deployment foundation | Foundation set / backend ~70% |
| WS-0 — Development Command Center | Plane, GitHub, Ravenforge roles, evidence, and validation flow | |
| WS-1 — Private Narrative and Review Site | protected Dravenkor review site, reviewer packet, private walkthrough path | |
| WS-2 — Legal/IP/Release Governance | attorney review prep, employment/IP checks, release boundary, trademark/name posture, commercialization gates | Active in parallel |
| WS-3 — Demo-1 Product Validation | private fixture-backed ODIN/DORI walkthrough, tooling lessons, coding standards, testing, and peer-review workflow | Active planning |
| WS-4 — Tier-1 / Community MVP Implementation | first real local-first Community MVP slice informed by Demo-1 and remaining Mimir backend deployment/integration work | Planned |
| WS-5 — Public Release and Documentation | public docs, community repo boundary, release checklist, contribution path | Planned / gated by WS-2 |
| WS-6 — Commercial Readiness | entity, terms, pricing, support, customer/data posture, revenue gates | Future / gated by WS-2 |
Current gates
| Gate | What it controls | Current decision |
|---|---|---|
| Private R&D | ongoing private planning and prototype work | may continue with strict operational separation |
| Private advisor/investor review | protected site and private Demo-1 walkthroughs | may continue if access-controlled, non-commercial, and fixture-backed |
| Community GitHub release | public repo, public docs, community announcement | blocked until WS-2 legal/IP/release review clears enough |
| Commercial revenue | paid pilots, subscriptions, consulting, managed services, customer onboarding | blocked until attorney review and commercial readiness are complete |
| Real customer/environment data | hosted assessment, live connectors, customer evidence, telemetry | blocked until security/privacy/data-handling rules and terms exist |
Near-term execution path
| Step | Output |
|---|---|
| 1 | Confirm the updated roadmap and WS-2/WS-3 parallel posture. |
| 2 | Build the WS-2 legal document inventory, attorney review packet, and operational separation checklist. |
| 3 | Define the Demo-1 fixture scenario and future-API-shaped data contract. |
| 4 | Decide Demo-1 programming tools that can carry lessons into the Tier-1 Community MVP. |
| 5 | Define coding standards for readable, modular, maintainable code Chris can debug and extend. |
| 6 | Define the ODIN/DORI walkthrough flow before building screens. |
| 7 | Build the private prototype shell and core Demo-1 screens behind Cloudflare Access. |
| 8 | Convert accepted Demo-1 lessons into Tier-1 Community MVP implementation tasks. |
| 9 | Convert remaining Mimir backend deployment work into WS-4 ODIN/DORI integration subtasks. |
What Demo-1 should prove
Demo-1 is not the full product. It should answer one practical operator question:
What should I improve next, and is it safe to do it?
The first prototype should show:
- an ODIN overview of a fictional home-lab environment;
- a small topology map from route to service to host to backup/monitoring evidence;
- service detail with owner, criticality, exposure, and operational state;
- evidence-backed readiness cards;
- DORI Guided Mode recommending a backup-first update path;
- Technology Health movement from unknown to mapped, observed, evidenced, and advised;
- clear fixture/prototype labeling and no real mutation;
- an obvious bridge from Demo-1 fixture data to the real Mimir backend services that are still being deployed.
Reviewer asks
| Reviewer type | Ask |
|---|---|
| Advisor | Does the sequence make sense: private validation now, legal/release gates before public/commercial movement? |
| Legal/business reviewer | Are the WS-2 gates and separation controls pointed at the right risks? |
| Technical reviewer | Are the trust boundaries, degraded modes, data-fixture boundaries, and proof-loop claims credible? |
| Investor | Is the wedge understandable? What proof is needed before deeper commercial discussion? |
| Early user/community reviewer | Would the Demo-1 proof loop be useful in a real home-lab or small-operator environment? |
Closing CTA
If this direction is interesting, the next step is a private walkthrough:
- review the narrative path;
- inspect the updated roadmap gates;
- discuss the Demo-1 fixture scenario;
- identify which proof point matters most before public Community release or commercial planning.
Reviewer focus
| Area | Question |
|---|---|
| Category | Is Technology Health understandable without a long explanation? |
| Pain | Do the practical operator questions feel real? |
| Product | Is ODIN clearly different from a dashboard or CMDB? |
| DORI | Is DORI clearly different from a chatbot? |
| Trust | Does the DORI guidance feel useful without adding too much implementation detail? |
| Legal/release gates | Does the plan clearly separate private validation from public release and revenue? |
| Demo-1 | Does a private, fixture-backed ODIN/DORI walkthrough feel like the right next proof point? |
| Commercial | Does the commercial path feel credible while remaining properly gated? |
| Roadmap | Does the sequencing feel ambitious but believable, including the foundation/pre-work and backend dependency? |
| Missing proof | What would you need to see next before investing, advising, or piloting? |
Reviewer questions
- Is the next ask clear?