Skip to content

feat: AQE embeddings by explicit consent #352

Description

@pacphi

Why

ak pulls a model into Ollama and aliases it without separate consent (design: What this replaces).

In scope

Default unmanaged; the pull and the alias each need their own yes; projections per project; ak x aqe-embedding becomes an init choice.

Out of scope

Ollama itself.

Acceptance criteria

  • Default init changes nothing in Ollama
  • Each step asks separately

Dependencies

Blocked by: #335

Blocks: #386

Plan

Verification

  • node scripts/run-tests.mjs focus (new embedding tests)

Metadata

Metadata

Assignees

No one assigned

    Labels

    size:MA few modules; one to three daysv4.0.0Routing: v4.0.0 boardws:project-scopeThe project-scoped management redesign

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions