Back to corpus
architecturetechnical paper candidatescore 48

SEA-0.1-COMPLETE

> **Deprecation note (2026-05-13):** Mac3 was the Tier 2 worker host at the time this phase shipped. Mac3 has since been retired. References in this document reflect the Feb-2026 architecture and are kept for historical accuracy. The current home for Tier 2 scoring is Mac4:8100 (cognitive twin). See SOOP-2 launch memory for migration plan.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> **Deprecation note (2026-05-13):** Mac3 was the Tier 2 worker host at the time this phase shipped. Mac3 has since been retired. References in this document reflect the Feb-2026 architecture and are kept for historical accuracy. The current home for Tier 2 scoring is Mac4:8100 (cognitive twin). See SOOP-2 launch memory for migration plan. ## Summary Verified Ollama embedding infrastructure on Mac4 ([ip]). Installed the `all-minilm` model (was not pre-installed), confirmed 384-dimensional vector output, and benchmarked warm latency at 7.45ms average — well under the 10ms target. Results documented in `phase0-results.md`. ## Changes - File: `phase0-results.md` — appended Mac4 Ollama embedding verification section (Sections 1-5: status, installation, embedding test, latency benchmarks, go/no-go summary) - Remote: Mac4 ([ip]) — pulled `all-minilm` model via Ollama (45 MB) ### Synthesis-Evil - Integration seams: phase0-results.md cleanly extends with Mac4 section after Mac3 section - Emergent behaviors: cold start latency (651ms) is a known concern for production; documented with pre-warm recommendation - State leakage: none — each section is independent - Original task: fully satisfied ## RTD Verification - [x] Structure: phase0-results.md exists with both Mac3 and Mac4 sections - [x] Compilation: N/A (markdown documentation) - [x] Integration: file committed to `sound-sigils-dep` branch - [x] Content: 384-dim verified, 7.45ms avg latency, model installed, all checks pass - [x] User Journey: curl command from task works end-to-end - [x] Deployment: committed as part of 4ee8837

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.