[Epic] Phase 8 — Explicitly Deferred (Post-v0.1)

[burakdede]

Epic. Phase 8: Explicitly Deferred (Post-v0.1)

Theme: Work the architecture deliberately excludes from v0.1, recorded as tasks so the exclusions stay decisions rather than drift.

Entry condition

Nothing in this phase may start before v0.1.0 ships (#102). §24.13 names scope expansion, connectors, chat, memory, agents, enterprise permissions, as the risk that would kill the wedge.

Contents

• Optional local semantic package with the §5.6 bounded download contract (Optional @lorepack/semantic-local package with bounded download contract #103) and the bounded exact-cosine scan with RRF fusion (Bounded exact cosine scan and Reciprocal Rank Fusion #104).
• Vectorize semantic projection, gated on exact EmbeddingProfile compatibility and query-visibility verification (Vectorize semantic projection with embedding-profile and visibility gates #105).
• Spikes with written recommendations: additional deployment targets (Spike: additional deployment targets (Docker/SQLite, PostgreSQL) #106), SaaS source connectors (Spike: SaaS source connectors and the determinism/permission boundary #107), visual artifact parsing and PPTX (Spike: visual artifact parser class (OCR, scanned PDFs) and PPTX #108), hosted control plane boundary (Spike: hosted control plane boundary and local-first guarantees #109).

Guardrails that survive this phase

• Semantic support never enters the default installation or the first-run critical path (§1.3, §4.3).
• Capability loss is never silent; remote semantic requires proven vector-space compatibility (§24.12).
• The complete local workflow is never moved behind a paid boundary (§4.2, §22.3).

Exit criteria

• Each spike closes with a written recommendation and either follow-up issues or a recorded ADR-level deferral.
• Any shipped feature here leaves the v0.1 guarantees measurably intact (clean-install, offline build, lexical fallback).

Spec references

§5.6, §8.9, §13.8, §16.4, §21 "Explicitly after v0.1", §22.2, §24.12, §24.13.

---

Added exit criterion, 2026-07-31

• This is the final phase, so there is no successor to audit forward into. The rule in AGENTS.md section 4 still applies in reverse: anything learned here that invalidates an assumption in an earlier, still-open ticket is amended there with reasoning.