Date: 2026-03-06

Workspace manager

• Root workspace manager: npm workspaces
• Evidence:
  • root package.json defines "workspaces": ["packages/*", "services/*", "apps/*"]
  • package-lock.json also records workspace metadata

Automatic package builds added

Root scripts now include:

• build:packages
  • npm run build --workspace=@kvary/ai-layer && npm run build --workspace=@kvary/memory-layer
• postinstall
  • npm run build:packages

Effect:

• fresh npm install at repo root will build:
  • @kvary/ai-layer
  • @kvary/memory-layer

Package resolution validation

Validation commands executed:

• npm run build:packages
• npm exec -- node -e "import('./packages/ai-layer/dist/index.js')..."
• npm exec -- node -e "import('./packages/memory-layer/dist/index.js')..."

Validation result:

• @kvary/ai-layer build succeeded and packages/ai-layer/dist/index.js resolved
• @kvary/memory-layer build succeeded and packages/memory-layer/dist/index.js resolved

Runtime/dependency observations

Current consumers detected:

• apps/web/next.config.js
  • transpiles and aliases @kvary/ai-layer
  • transpiles and aliases @kvary/memory-layer
• apps/web/lib/docsRagBootstrap.ts
  • imports @kvary/ai-layer
• apps/web/src/app/api/ai/audit/route.ts
  • imports @kvary/ai-layer
• apps/web/src/app/api/ai/audit/verify/route.ts
  • imports @kvary/ai-layer
• apps/web/src/app/api/ai/ask/route.ts
  • imports @kvary/ai-layer
  • imports @kvary/memory-layer

Dependency graph note:

• no package manifest dependency edges were found for these two packages outside their own package manifests
• current usage is runtime/bundler-level from apps/web, not package-to-package build chaining
• no additional build-order changes were required in this commit

Packages still requiring manual build or later migration work

Not handled by this workspace auto-build commit:

• packages/core
  • still source-consumed and not on a dist build pipeline
• packages/identity-infra
  • runtime still starts from tsx src/index.ts
• packages/financial-layer
  • still lacks a proper workspace package boundary and build contract

Non-destructive scope

This commit does not:

• delete any files
• change runtime entrypoints
• rewrite import paths
• change ports or URLs