# Hussh Future Roadmap

> Planning-only home for future-state concepts, R&D assessment, and promotion criteria.

## Visual Map

```mermaid
flowchart TD
  root["docs/future/<br/>planning-only roadmap home"]
  kai["kai/<br/>assistant and workflow concepts"]
  oneInfra["hussh-one-infra/<br/>One infrastructure future architecture"]
  oneSurface["one-product-surface-evolution-plan.md<br/>One product surface scaling"]
  oneNav["one-nav-runtime-plan.md<br/>One/Kai/Nav/KYC runtime migration"]
  execution["promotion to execution docs<br/>only after approval"]

  root --> kai
  root --> oneInfra
  root --> oneSurface
  root --> oneNav
  root --> execution
```

## Purpose

Use `docs/future/` for:

- future-state architecture concepts
- R&D risk assessments
- architecture options and dependency maps
- promotion criteria before execution starts

Do not use this home for:

- durable product thesis
- current implementation contracts
- package-local technical references

## Boundary Model

| Layer | Purpose | Home |
| --- | --- | --- |
| Vision | durable north stars and product thesis | `docs/vision/` |
| Future roadmap | planning-only future-state concepts and R&D assessment | `docs/future/` |
| Execution | active implementation contracts and package docs | `docs/reference/`, `consent-protocol/docs/`, `hushh-webapp/docs/` |

## Promotion Rule

A document may move out of `docs/future/` only when:

1. the concept is approved for execution
2. the execution owner is known
3. the implementation surfaces are known
4. the content can be split into execution-owned docs instead of remaining a speculative concept note

Promotion targets:

- cross-cutting execution contracts -> `docs/reference/...`
- backend execution docs -> `consent-protocol/docs/...`
- frontend/product execution docs -> `hushh-webapp/docs/...`

## Current Domains

- [kai/README.md](./kai/README.md): Kai future-state concepts and superseded planning history that has not yet moved
- [hussh-one-infra/README.md](./hussh-one-infra/README.md): planning-only One infrastructure architecture for Founder Wiki validation, Salesforce/MuleSoft partner boundaries, private compute, BYOA, and code-persona alignment
- [one-product-surface-evolution-plan.md](./one-product-surface-evolution-plan.md): planning-only product-surface evolution path for One, Kai, Nav, KYC, PCHP, PKM, OpenClaw/LLM Wiki-style projections, signature, brokerage, and brand-side access
- [one-nav-runtime-plan.md](./one-nav-runtime-plan.md): planning-only migration path from the current Kai-first runtime to the One/Kai/Nav/KYC ontology

## References

- [../vision/README.md](../vision/README.md): durable Hussh north stars
- [../reference/operations/documentation-architecture-map.md](../reference/operations/documentation-architecture-map.md): canonical docs-home map
- [../reference/operations/docs-governance.md](../reference/operations/docs-governance.md): docs placement and promotion rules
