Core Features Architecture 1.4.0

Module ownership, data flow, package boundaries, and the implemented Phase 0–6.1 system map.

Project 2 freeze: documentation reflects the shipped 1.4.0 surface through Phase 6.1. Inspector Overlay, visual selection UI, token probe, and every Phase 6.2+ stage are not started.

Product boundary: Core Features are Velin-native. They do not extend Tailwind Compat/Migrate and do not port Shadcn, Radix, or Tailwind UI.

System map

bootFromDOM({ adapt })
  └─ @birdapi/velinstyle/adapt
       ├─ semantic contract
       ├─ rule-based policy and safe apply
       ├─ optional local candidate ranker
       └─ audit and undo

@birdapi/velinstyle/blocks(-registry)
  └─ owned source + adaptContract

@birdapi/velinstyle/inspector
  └─ Phase 6.1 read/action facade over existing APIs

Adaptive data flow

Signals → Policy → optional Local AI ranker → Intent → Validator → Guardrails → Semantic Apply → Audit / Undo

Only Semantic Apply owns DOM writes. The optional ranker changes order, never capability.

Module responsibilities

Module	Owns	Must not
Runtime	Single boot, component loader, attributes	Spawn a second bootstrap
Adapt	Signals, policy, validation, semantic apply, audit	Generate arbitrary HTML/CSS/JS
Blocks	Manifest, registry, copy-to-project install	Fetch at application runtime
Inspector Core	Read model, selection state, delegated safe actions	Start or fork Adapt

Package entry points

@birdapi/velinstyle/adapt
@birdapi/velinstyle/blocks
@birdapi/velinstyle/blocks-registry
@birdapi/velinstyle/inspector

Implemented phase boundary

Phase	Delivered
1	Semantic Runtime Contract
2	Rule-based Adaptive Runtime, audit, undo
3	Blocks registry and ownership CLI
4	Optional local candidate ranker
5	Top-10 Blocks and Community Manifest validator
6.1	Inspector Core only; no UI